Opinions on migrating to Git, and possibly Github

[Benjamin Moran]

Hello everyone,

What do you think about Ole Herman Schumacher Elgesem's proposal, opened here: https://bitbucket.org/pyglet/pyglet/issues/251/move-to-git-and-githubcom

This gets brought up from time to time.
Any opinions for or against?

-Ben

[Patrick Armstrong]

I'm for, I love github and am more familiar with it than bitbucket

--
You received this message because you are subscribed to the Google Groups "pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyglet-users...@googlegroups.com.
To post to this group, send email to pyglet...@googlegroups.com.
Visit this group at https://groups.google.com/group/pyglet-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/pyglet-users/1a7f8b3d-9b21-4c40-a9bd-61c1017454e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

-Patrick

[Adam Bark]

I did the initial move to bitbucket because we were using mercurial on
google code and that was going away. It was also before python and the
remaining major users of mercurial switched to git so I thought it might
still have some traction. I use git mostly myself now and even github
but I'm hesitant to move to yet another proprietary platform, how do you
feel about gitlab? I don't really contribute these days so I think it
depends most on what you, and any other major contributors, are most
comfortable with.

I've been following ESR's progress with switching GCC to git and I'd be
up for investigating reposurgeon to switch us over if you want that.
From what ESR says I'm not sure the tool that comes with git is
particularly good.

One other thing, I don't know if we can migrate our 'issues' from bitbucket.

To sum up, it doesn't really affect me either way but if you want to
move to git I will try to do that. Where to host perhaps needs more
discussion.

[Mark Schafer]

I'm also for gitlab or github.
Inkscape had a big discussion about this as well and chose gitlab in the end for its more open future than github.

But they were happy to go either way really.

--
You received this message because you are subscribed to the Google Groups "pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyglet-users...@googlegroups.com.
To post to this group, send email to pyglet...@googlegroups.com.
Visit this group at https://groups.google.com/group/pyglet-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/pyglet-users/5CFDA469.7080809%40gmail.com.

[Benjamin Moran]

Hi Adam,

On the technical side, it seems not too difficult to migrate the codebase including commits and branches.
I think Ole Herman Schumacher Elgesem has already done that as a proof of concept.
I also came across a few scripts that will replicated the issues across, using the APIs.

Regarding Github itself, I agree with you. Thinking pragmatically however, the reality is that
Github is where the users and potential contributors are at the moment.

Gitlab does have a feature to automatically keep a repository synced after importing,

so maybe if we go to Github, we can set up the Gitlab repository as a plan B?

[Charles M]

I think it's worth switching to git. I personally haven't contributed more because I don't know mercurial and don't wish to install it just for one project. Git is more popular and could possibly attract more contributors.

As far as moving to another platform, not sure it's necessary. If it's not too much trouble and has the same or more features, than go for it.

--
You received this message because you are subscribed to the Google Groups "pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pyglet-users...@googlegroups.com.
To post to this group, send email to pyglet...@googlegroups.com.
Visit this group at https://groups.google.com/group/pyglet-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/pyglet-users/c50f3f28-5ea1-4651-a69d-25f8ae5fe344%40googlegroups.com.

[Ole Herman Schumacher Elgesem]

Thanks for posting here, Benjamin.

Regarding GitLab:

• GitLab is Open Source, GitHub is not. It makes sense to support another open source project.
• GitLab has some nice/more advanced features (GitLab CI, more flexible tickets, cherry-picking in PR UI), but I don't think they are very relevant for pyglet.
• GitHub is more popular, and so I think it gives the project more exposure.

So, I'm leaning towards GitHub, which is why I proposed it, but I'm okay with either. My main motivation for proposing this is increasing exposure and encouraging more contributions. More people are on GitHub, so this makes the most sense for me. It should also be noted that after moving to either platform, switching from one to the other, or setting up a mirror, should be fairly easy.

Regarding bitbucket issues:

I think it makes sense to leave the bitbucket project intact, with all the open issues still here. This is important so links don't get broken. New pull requests and issues should go to GitHub/GitLab. Those who already have issues in bitbucket can keep linking to them and discussing them there, at least for a transition period. We could also try to migrate the issues, but I'm not sure that's the best approach.

-Ole Herman

[Benjamin Moran]

The feedback towards moving to Git and specifically Github has been overwhelmingly positive.

Ole Herman was gracious enough to do the legwork of setting up a pyglet organization + repository

on Github, as well as manually migrating over the codebase from HG to Git. All branches and tags

remain, so nothing is lost in that respect. Thanks Ole for the work! 

Anyone who currently has project ownership on Bitbucket and wishes to be added to Github, please let me know! 

I'm still considering the course of action for Bitbucket, but for right now I will manually handle replicating
any PRs across if we get any.

-Ben