Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support this project #42

Open
Jawnnypoo opened this issue Jun 17, 2015 · 11 comments
Open

Support this project #42

Jawnnypoo opened this issue Jun 17, 2015 · 11 comments

Comments

@Jawnnypoo
Copy link

@ekx Please consider merging in pull requests or turning over the app to someone who can manage it at this time. It is sad to let a project like this die, as it is a great foundation and has users on the Play Store.

@robinpaulson
Copy link

Yes, I'd like to see this happen too. @Jawnnypoo , @burrito82 , @JosephTurner and others have fixed a number of the issues, perhaps one of those contributors would be a good candidate if @ekx does not have time or inclination?

@burrito82
Copy link

I suggest that @ekx adds someone as an additional developer with commit/merge rights. This is if he would continue to publish versions to the Play Store. Otherwise, we could just establish a fork as the new main project, but distribution would be a lot more complicated.

@Jawnnypoo
Copy link
Author

I think the fork might have to be the option as far as I can tell, I have tried emailing the developer about 3 times now. Looks like he is not managing the app on the Play Store either, since he has yet to give it a rating.

@fahrul66
Copy link

#1

@robinpaulson
Copy link

It's been over a month now folks, I think it's acceptable to assume @ekx won't be continuing development of this. From a cursory glance at the "network" (https://github.com/ekx/GitLabAndroid/network) page, @Jawnnypoo looks like he has made the furthest progress in fixing problems, might I tentatively suggest using that fork as the one to base development efforts on? There are a few other patches from other forks which it would be useful to merge in as well. Any suggestions, comments, problems?

@Jawnnypoo
Copy link
Author

I agree, and I have forked the repo. I have merged most of the pull requests in this repo:

https://github.com/Commit451/GitLabAndroid

@robinpaulson
Copy link

Fantastic, good to see. Now, is there any way to export the issues from the ekx repo to the commit451 repo?

@Jawnnypoo
Copy link
Author

I have replicated most of the pull requests that are on this project, but I have not transferred the issues yet. I will get to that today. I also plan on releasing to the app store soon so that the app can gain traction so that others are not downloading the unmaintained version.

@burrito82
Copy link

Great news! 👍

@Jawnnypoo
Copy link
Author

Jawnnypoo commented Jan 7, 2016

It is worth mentioning on this issue, in case anyone stumbles across it, that the fork repo has been moved here:
https://gitlab.com/Commit451/LabCoat

@robinpaulson
Copy link

And that fork has now been included in f-droid also.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants