David Roundy wrote:
> On Thu, Jun 28, 2007 at 12:48:58PM +1000, Dave Harrison wrote:
>> Key, or core devs publish their own outgoing trees alongside your own
>> at some location (an example of what I mean is evident here :
>>http://www.selenic.com/mercurial/wiki/index.cgi/DeveloperRepos>>>> This means that people like David (Roundy, not me ;-) ) can publish
>> their own tree containing the stuff they are responsible for, and also
>> directly manage the patches for their own code. Then the release team
>> (yourself and Spencer ?) can pull from their published repo whenever
>> you want to, merge it all together into a single release repo, and cut
>> a tag for it.
>>>> Not sure if this works with darcs since I've never used it
>> (personally, I'm a git ;-) ). But it would solve the problem of
>> people being able to publicly maintain their own code, without you
>> having to worry about the current patch management problem you have -
>> you just have to trust the maintainers.
>> That'd work fine with darcs, but seems like overkill for this stuff. Most
> of the time what I have doesn't differ from main xmonad (except in private
> changes).
I wasn't really thinking in terms of you differing from what's in the
release repo, just that you could take ownership of patches to your
own contrib modules. This way if someone wants to submit a patch they
can just submit it directly to the author / maintainer of the code,
instead of having to go the long way round via the core maintainers.
It seems to me, that some of these contrib modules (Tabbed especially)
have functionality that alot of people might want. So instead of
increasing the workload for the core maintainers by having them vet
each module patch with its author, the module authors can just accept
the patches themselves. They can then feed releases of their module
back into the release repo.
Dave