CiviCRM Community Forums (archive)

I'm curious what experience people have had with large projects that modify the CiviCRM code base, hopefully with the goal of landing these changes later into the official repository.

I'm about to start some experiments with porting 3.1 to Drupal 7, and I'd like to make the work available to as many of you as would be interested in hammering on it.  It's not clear yet if Lobo will use this later -- I'm guessing that the core team will do this later when they're confident that Drupal 7 is far enough along -- so it's entirely possible that they will look on this as a "proof of concept" only.  But still, for a project I'm now starting, it would help to have good Drupal 7 support sooner than the core team is likely to be able to do.

My guess is the best thing is to clone either the trunk or the 3.1 branch using either git-svn or bazaar,  with a public mirror of this somewhere that people can get access to it.  This seems straightforward enough, although I haven't done this with git before, and it's been years since I tried it with bazaar.

Do any of you have advice as to the pros and cons of using bazaar over git or visa versa, and for whichever you think is easier to work with, how you set up access?

Lobo --

That would be great.  I'm also guessing that the number of files I'll need to touch will pretty limited as well.

Just tell me what the branch is, and send me the credentials.  My guess is that it'll be easiest to start using 3.1 as a base, if that's cool with you.

Rob

off the trunk it is, then.

Thanks!

Rob