Re: patch to fix IPv6 reassembly, et al

[Mark Salter <msalter at redhat dot com>]

>>>>> Andrew Lunn writes:

> Hi Folks
> This is a general issue about RedHat accessing the public version of
> eCos. Ascom still have a maintenance contract with RedHat which has
> now been moved to the USA. I've asked that all patches they send to us
> they also CC to the ecos-patch list. So i assumed that RedHat were not
> going to directly add to the public CVS tree.

> I think i prefer that the public maintainers add RedHat patches to the
> CVS tree, just like any other contribution. That way its easier for
> them to keep track of what is going on.

Hi Andrew,

>From a Red Hat perspective, I'd like to generally follow the process 
of other open source projects Red Hat is involved in. Red Hat maintains
an internal repository which is kept in sync with the public repository.
The internal and external repository differ only in that the internal
repository contains a few extra ports that are covered by NDA and can't
be made public. Any changes we (Red Hat) makes which may be made public
shall be posted as patches to ecos-patches.

What we might want to do is create a MAINTAINERS file which explicitly
lists who is responsible for reviewing and approving patches in a given
area of eCos. The maintainer for a given area won't need permission to
check in a change for that area (patches must still be posted). Some
folks other than maintainers could be given "write after approval" status
so that they can check in approved changes without having to burden the
maintainer with the task of checking in a change.

Thoughts?

--Mark