On 8/12/12 1:19 PM, Peter Hartmann wrote: > On11.08.2012 03:33, Greg Stein wrote: >> IMO, perform as little core re-engineering as possible, and move rapidly >> towards a release. So, strip Hg rather than rebuild. >> >> Second, as a consumer of this project, having *no* SCM is simply >> ridiculous >> and a non-starter. I cannot imagine any possible installation or use-case >> without SCM. My view is that you start with SCM, and build on top of that >> with something like Allura. > I see what you mean. As I understand from ticket #3883, there were plans > to make Hg (Mercurial) default SCM in Allura. But since dev team > realized it's GPL'd, Hg will be moved to separate package and possibly > even out of Allura's source tree. So now we have two options: > 1) make SCM support non-default so that Allura will be less opinionated, or > 2) choose default SCM from the other ones left (Git or Subversion). > > Note that even with 2), with the work i'm doing, SCM support can still > be optional, i.e. user would be able to remove it from default > installation. This is relevant to me because if 1) is chosen - which > Dave seems to favor - things like Git repos in default installation will > have to be pruned. I imagine this would be troublesome for new users, > who clearly expect code hosting to be available by default, even though > there certainly are use cases that don't require it. >
PySVN can be very difficult to build, so that should be optional for sure during installation. Going with #2 and keeping git as a default part of Allura installation (but removable) is fine with me. IIRC, it's not too hard to install the git libraries, and git is a pretty popular SCM. And all libraries needed for ForgeGit to work are BSD licensed (gitdb, gitpython, async, smmap) -- Dave Brondsema : [email protected] http://www.brondsema.net : personal http://www.splike.com : programming <><
