NewPipe
NewPipe copied to clipboard
TeamNewPipe
Switch to Gitlab
ChoCho here comes the hype train.
Well. I'm not a big fan of M$ since they destroyed a lot of services they bought in the past, and I don't trust them at all.
I don't purpose to switch away from github that quickly (maybe not even at all), but the way I'm used to how these companies work is they promise not to change something and F*** it up just a few months later. Just look at our beloved YouTube, and their all mighty awesome new subscription thing. However weather we switch or not is up to you.
I would be fortified and prepare, so we can switch quickly once the time comes.
Here are some proposals
gitlab.com
| Pros | Cons |
|---|---|
| - biggest alternative to github | - veeery slow |
| - has a project importer that can import even the issues from github | - confusing/bad UI |
| - centralized (runs an Azure) |
git.schabi.org
| Pros | Cons |
|---|---|
| - verry slick | - does not have an auto importer |
| - self hosted (runs on Hetzner) | - does not support code review |
| - github like UI |
Preperation
So I think a step in the right direction for the beginning would be to try swtich our CI to a service that supports platforms other than github.com. Apropose would be bitrise, or gitlab CI
First off, I also think that now since Microsoft bought Github, we will probably see that things change and very likely not for the better. So I support this project moving to an alternative. In my opinion your self-hosted Gittea will be better in the long-term, only the beginning will be quite difficult due to it not having an auto importer. I also think too many people were to quick to run directly to Gitlab, just because it's the next most popular Git-Service after Github. Gitlab can be self-hosted too, which many people overlook, so it is worth looking into too.
We could go for a mirrored approach, with git.schabi.org being the main site, and GitHub and GitLab being the mirrors. That way if any of them decide to take down the repo, the core is still within project's control. Other than having more redundancy, we also keep the benefit of people being able to discover and contribute to the code if they are coming from those more popular hosting platforms.
@theScrabi I've seen some interesting p2p git solutions appear recently. Maybe we could look into that as well?
We could go for a mirrored approach
This is what I would suggest anyway. Wherever we go we have to mirror.
I also realized since we use jitpack for the extractor we have to use a service that is supported by it.
@theScrabi The table about GitLab is somewhat one-sided. You write that Gitlab is "centralized (runs an Azure)", but not about that it can be downloaded and deployed to your own server. I don't propose to get one, but it has to be mentioned too, I guess. "confusing/bad UI" - it's a relative thing, tastes differ. There interfaces don't differ so much, you get used to it. Many large projects went to gitlab: GNOME, GIMP, Inkscape etc. The only thing I can agree it's too slow. With its web-interface. But console git works too.
The only thing I can agree it's too slow. With its web-interface. But console git works too.
This is the biggest disadvantage I have with it. Pourly not all things can be done via cli, and even pull push is slow.
Selfhoating gitlab was an alternative, since I witnesed that selfhosted it can get pretty fast, but then we still have the problem with jitpack
@theScrabi Isn't (self-hosted) GitLab supported by Jitpack? Or are there other issues with that? https://jitpack.io/docs/PRIVATE/#self-hosted-git
I use Self Hosted Gitlab CE on a day basis for work and I can assure you that it rocks waaaaaaay more than GH and isn't slower than it. The whole Git + CI + Deployments trio is a game changer to me and makes Gitlab way more elaborated & complete than GitHub for me. Give it a try you won't be deceived, trust me 😇
GH and isn't slower than it.
Yea the selfhosted gitlab at our university is also not slow.
... Yea maybe we should consider selfhosted gitlab. @TheAssassin what do you think.
Folks, please calm down, and don't start to hastily switch from GitHub to some random alternatives. This doesn't make any sense, really. There's a lot of disadvantages in switching from GitHub to something else, see e.g., https://github.com/AppImage/AppImageKit/issues/803#issuecomment-396711385.
TL;DR: Before the end of 2018, it doesn't make any sense to switch to some alternative. If the situation gets worse then, we can switch easily. I expect some migration helpers to be developed and become more mature by then, increasing the list of suitable alternatives. Then, one can discuss to switch to alternative platforms.
And please don't limit yourself to the two which are most GitHub-like. There's also self-hosted alternatives like e.g., Phabricator, which employ a less repository but more project focused workflow, and provide a vast amount of tools that help non-devs to work more efficiently. It provides e.g., a mockup review tool that might come in handy for web development or UI discussions, and a simple non-public chat that can be used to send messages to people without knowing their mail address or having them join IRC. Sure, one has to get used to its workflow at first, but there must be a reason so many projects use it.
@TheAssassin A (partial) migration plan will be needed before then, to avoid chaos in case GitHub suddenly suspends or deletes the project. This is a real possibility for NewPipe. Microsoft is more likely to cave and suspend if a project is as much as perceived to be "infringing copyright" or something similarly broad, certainly moreso than the previous management. We shouldn't try to rush it, but we certainly should start shortlisting alternatives. I think that, whether we like it or not, we may not be able to remain on GitHub. I'm not a contributor (yet), but I wanted to share my thoughts on this.
@pabru we are already mirroring the repositories into several places for backup purposes, and what I am looking for currently is for someone to develop an issue export and migration tool, allowing us to make restorable backups of the issue trackers and migrate to any tool we want to once we need to actually migrate to some alternative platform. Ideally, that tool won't just create issues using some bot account, but allows to restore the issues properly.
Suggestions welcome!
@TheAssassin thats why i suggest gitlab they have an issue importer. I've tried it with somw of my other projects, and it works
@theScrabi that is only half of what I required in my last comment. I'd like to have a way to actually back up the issues, and import them on demand, ideally on any platform.
@theScrabi by the way, Gitea does support PRs just normally. In fact, they're even called "pull requests", not "merge requests".
All you request and more is available in Gitlab guys... Gitea is pretty cool project but it's still pretty young and not fully feature complete...
@SkyzohKey no, it's not. That's the point. See https://github.com/TeamNewPipe/NewPipe/issues/1499#issuecomment-406281784. This "migration" stuff is far from good.
@TheAssassin this is going to be a vim vs. emacs discussion :D I don't have a favourite as well, however I see it like this: Gitlab on the on hand all the functionalities we might want, like a github importer, and inline code reviews. Gittea on the other is more swift and has the cleaner UI.
Lets do what you said and just wait a bit. Maybe things will improve somewhere in the future and give a clear direction:)
@TheAssassin this is going to be a vim vs. emacs discussion :D
That's wrong. I never claimed Gitea had that feature of "proper" migrations. But neither does GitLab. That's the problem with both of them.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
I am not a Microsoft fan either and I think by switching to gitlab will be a good move.
As Github now blocks developers from certain countries, switching to an alternative is now more relevant than ever.
https://techcrunch.com/2019/07/29/github-ban-sanctioned-countries/
So what? Where do you think GitLab is located? Running for the next platform doesn't make any difference, nor sense. It's not worth it.
As stated in the tech crunch article
A selection of GitHub services such as access to public repositories will remain available to everyone.
- This is a public repo
@dimqua next "big player".
If any, we'd go for self hosting, I guess. That's more sustainable and less annoying.
The big problem though is reaching developers. After all, on GitHub, it's fairly easy. On other platforms, the audience is much smaller. Noone likes to register at a ton of services.
@TheAssassin GitLab supports logging in with Google, Twitter, Facebook and GitHub , so maybe the users won't have to remember an extra username and password.
