Re: Patch policy

[Jonathan Larmour <jifl at eCosCentric dot com>]

Andrew Lunn wrote:
> > In an ideal world, patches from outside our group would
> > be posted to a database which could be queried by anyone.
> > Maybe the easiest way to do this would be to forward the
> > patch to BugZilla.
>
>
> Sounds like a reasonable idea. Let bugzilla pick the default owner of
> the patch depending on the component. We would probably want to add
> more HAL components, one per architecture. 
>
> The messy thing is getting the patch from ecos-patches into
> bugzilla. I don't see it being done automagically. Do we have to
> retrain all contributers to use bugzilla instead of the list? Does one
> of us have to import the patch?

I'd suggest not using bugzilla actually. I've already been thinking about 
this problem and there are well established patch managers out there. In 
particular I'm thinking of what is on savannah.gnu.org, e.g.: 
http://savannah.gnu.org/patch/?group=inetutils

I think is is a brilliant, and obviously being purpose-built, ideally 
suited solution. My hope is that we can move straight to using this if we 
become a GNU project.

But I didn't bother suggesting it yet :-).

If we don't become a GNU project, we could see about bringing it onto 
sources.redhat.com ( or ecos.sourceware.org if you like :-)).

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine