On Wed, 2015-09-23 at 07:08 -0400, Gary Oberbrunner wrote: > Could be; pretty much _every_ project I can think of is using git > now. I > have to twist my brain around every time I work on SCons. :-)
Which is sad because Git still has so much wrong with it, and Mercurial has so much going for it. However, the social and commercial pressure seems inexorable that Git shall be the monopoly. I think there possible needs to be a new debate about whether to switch to Git and GitHub. When the decision was made to move from Subversion on Tigris to Mercurial on BitBucket, I had some issues/doubts, but the final decision seemed fine and not a problem. However time has moved on and we are are now in an era where to get any traction as a FOSS project you appear to have to use GitHub. OK, I realize it is all "kool kids", "hipsters", and "people who say awesome evey sentence", but the issue is not one of what is best as a technology, it is what is best as a way of gaining traction. I appreciate Mercurial is written in Python (mostly) and Python users Mercurial, but they have PSF. SCons is just another ancient build system trying to exist as a FOSS project. I propose therefore that we switch from Mercurial/BitBucket to Git/GitHub and that we start a new GitHub issue tracker (even though it is shite really). Issues from Tigris can be moved over by hand as needed. This then gives access to Travis, CodeShip, etc. The point here is not that they are reliable CIs, it is that they are ways of promoting and marketing the project in the Git-sphere. Given Buck, Bazel,… SCons needs to do something to make a new presence or simply drift into the dustbin of history. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev
