On Thu, May 22, 2008 at 06:38:12PM -0700, Brian Finney wrote: > > As a non active (hopefully active in the future) > contributer/developer, I would find emailed patches very useful for > visibility into the code base and where things are going, and as a > nice carrot hanging out in front of me to hopefully motivate me to > contribute. Of course the usability of actual contributers is more > important. Perhaps a merge mailing list that automatically gets > emailed patches when merges happen on major branches if this doesn't > go through? (github probably has something I could subscribe to > though, I'll have to look into it)
For me that's the best solution: having a -commits mailing list that
gets all the commits done on the master branches will ensure maximum
peer review of the actual master code, the one that matters.
Branch maintainers still have the duty to actually review the topical
branches before they merge so I'm not sure it's relevant to share those
"proposed patches" with everyone, unless we want to distribute the task
of reviewing proposed patches to the master branches.
In the case, the same process could be follow: hooks in topical
repositories would send mail to -commit@ on push.
In general, it would be important to have tags in the commitmail saying
what the patch applies to: a topical branch (and which(, a "stable" master
branch,
the "next release" master branch, etc.
A.
--
Information is not knowledge
Knowledge is not wisdom
Wisdom is not truth
- Frank Zappa
signature.asc
Description: Digital signature
