Doug Cutting wrote: > David Reiss wrote: >> We have been doing this a little differently. I prefer to have all of >> the development in one place instead of having to look around at >> everyone's repository. We have one central repository (with a mirror) >> and everyone posts their branches there. Whether they also use GitHub >> on the side is up to them. > > This needs to be well documented. Also, will non-Git users need to > consult this "one place"? Yes. As per the workflow I described in my first email. However, we always either send mail to the list or make JIRA issues about the branches that we want reviewed (and this process can be formalized).
> If it would make it a lot easier, we could make Git the preferred method > for contributors. It is definitely the preferred method for me. :) I have some code set up to allow submission via Git by anyone (even if they have not sent me their public key), but it needs a little bit of cleaning. > Without a lot of automatic notifications, it seems > like a non-Git contributor could miss a lot. I personally prefer manual notifications (at least on the -dev list. Auto-notifications on a separate list like -commits or -git-commits or [EMAIL PROTECTED] or whatever) because often you want to give a little more context than fits in the commit message. Also, not all branches are of constant interest to everyone. For example, Ross announced his C+Glib branch when he first pushed it, but we don't need an email every time he pushes some new commits. However, if the consensus is that we want an email sent every time someone updates a branch, I'm happy to help set this up. --David
