Migrating to Gitlab #131
Comments
|
What about |
|
Agreed that the lack of a good build service integration is a point against Github. |
|
I like what Drew DeVault is doing. I think he's fighting the good fight. I really wouldn't mind paying for the hosting service, but I feel it's a risky move given their development stage. Maybe in a few years? :) |
|
I don't think we have that much risk with isbg - you're the main contributor, velocity is pretty low, etc. I wouldn't spend any time migrating issues etc. to sourcehut, just push the git repo over and archive the github repo (if we end up being happy with it). |
|
As an aside, CircleCI works nicer than Travis and GitHub Actions is in beta. You can even use GitLab CI with GH. (Not trying to dissuade anyone from moving, but that "Travis is bad" thing is quite separate from GH.) On topic, I have no strong opinion on GitHub vs. GitLab. I happily use both. But of course it's a definite pro that you can roll out your own or use an alternative hosted instance like https://framagit.org. |
|
I've given Sourcehut a go and I don't think it's ready yet :) @Frenzie I didn't know about the Gitlab CI integration on Github! I've never really liked Circle CI though, and I'm not sure I like the whole Github Actions thing either. That said, my primary reason for wanting to move is Github being proprietary. |
|
sight. I mean, come on Gitlab. Now I'm not so sure it's the right platform anymore and I'm thinking hard about migrating to sr.ht instead... |
|
Gitlab has done the right thing and rolled back on that decision, so I'm still planning on migrating to gitlab.com. I don't fell 100% down with it, but in my honest opinion it's still the best option ATM. |
|
I've migrated the repository to Gitlab: https://gitlab.com/isbg/isbg I'll make this clear in the project's header and send an email on the ML. |
I really dislike Github. It's proprietary and Travis CI is bad.
I'd really like to move this project to a Gitlab instance, more specifically to gitlab.com. It would imply some effort to port the Travis script and change a bunch of variables, but I'm ready to do that work.
We could also use Gitlab Pages instead of relying on readthedocs.io (it isn't great).
I'd like to get people's thoughts on this. From having talked with him before, I know @duk3luk3 also prefers Gitlab over Github.
I've already created the "isbg" group on Gitlab just in case... https://gitlab.com/groups/isbg
Let's give people... 2 months to reply to this issue and tell us what they think about moving to Gitlab. If on November 19th 2019 we don't have a strong consensus here against moving to Gitlab, I'll initiate the move.
The text was updated successfully, but these errors were encountered: