I hope we're not mandating using github or even git. If a group of folks get together and decide to work together on a feature it should be up to them to decide how to organize themselves. If they want to use github (which probably is the most obvious choice) that is fine, but if they decide to SVN, P4, CVS, Mercurial, bzr (or VisualSourceSafe :) )... That should be up to them, as long as the end result is a stream of patches that can be applied to the canonical SVN repository.
-- Lars ----- Original Message ----- From: Andrew Purtell <[email protected]> To: [email protected] Cc: Sent: Wednesday, September 12, 2012 12:24 AM Subject: Re: Thoughts about large feature dev branches Yes, the consensus at the dev meetup (a poll of the room) was we should move forward with use of git and GitHub hosting for feature development / branches. On Tue, Sep 11, 2012 at 11:49 PM, Dave Wang <[email protected]> wrote: > Hello, > > Shall we move forward with this proposal? Let's get this in place soon so > larger projects such as snapshots can make use of this. > > - Dave Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
