Hi there,
On 05.01.2016 18:25, Bill Deegan wrote:
Not a rumor. ;)
http://lwn.net/Articles/669924/
http://thread.gmane.org/gmane.comp.python.devel/150459/focus=150960
when I read those two threads/articles it doesn't seem to be about "moving Python to Github"...they're considering (PEP481) to
migrate certain supporting repositories, that don't need a bug tracker and can be used as a stand-alone repo.
Am I getting this right?
If yes, this is a different situation than we would have...we still have a bug tracker to migrate. And so far, everybody who tried
to come up with a proposal about how to do it, while losing no significant data, seems to have given up on it. Would this change if
we move to Github?
It may be true that a lot of people nowadays simply know how to use "git" (or maybe they only "think" that they know ;) ), but I
can't see a big boost of new contributors growing from this fact alone. OpenHatch has moved to Github recently (including their bug
tracker) and they're still struggling and desperately calling for help. Maybe it is the "wrong" example, but it doesn't seem to be
*that* easy. And someone has to do the migration work...I'd like to see volunteers and their ideas for the migration first, before
supporting this idea.
I'm not completely opposed to the idea of moving to Github ( and git, which I also know a bit, at least I "think" I do ;) ), but
deep in my heart I still very much feel like Nick Coghlan (see http://thread.gmane.org/gmane.comp.python.devel/150459/focus=150960 )
and think about Mercurial and SCons as part of the Python family. This weighs a lot in my opinion, so you have to put much more than
"convenience" and "I suspect"s on the other side of the scale to convince me. :)
So much for my 2c.
Best regards,
Dirk
_______________________________________________
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev
