Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [technology-pmc] Requesting approval for code contributions?

Hello David,

FYI: A bug has been opened to clear this:

There is a response from the legal team asking to "read the document with that statement removed" (document = IP Poster).

Abel Muiño

El 08/12/2008, a las 17:25, David Whiteman escribió:

I agree with Abel that it seems like overkill to get PMC approval on all fixes (including simple ones) provided by non-committers.  Has this always been the process in Eclipse?  I would think not given the volume of contributions typically received.  The committer guidelines statement seems more reasonable than the information provided on the IP poster.  Does it make a difference if the non-committers are employees of the same company as the submitting committer?

Actually, in rereading the poster, it does say "all code" at the top.  Does this include any code contributed for any fix/enhancement, even by committers?  Does "under the supervision of the PMC" mean the same thing as having each defect/enhancement individually approved by the PMC?  I can't imagine this doing anything but reducing progress to a slow crawl.

David Whiteman | IBM Tivoli Autonomic Computing
Tivoli Integrated Portal development |
Resource Modeling lead, Eclipse COSMOS project |
dlwhiteman@xxxxxxxxxx | 919-254-8224 | T/L 444-8224

technology-pmc-bounces@xxxxxxxxxxx wrote on 11/26/2008 02:37:10 PM:

> There is currently a flag on bugzilla (in the attachmen details) for  
> "review". I'm not sure if that's useful for this case. Otherwise,  
> maybe we can manually CC this list on bugzilla when requesting a  
> review and the PMC can remove it after approving.
> On the other hand, I've kept looking at IP information and found that:
> "For simple bug fixes and minor enhancements contributed under the  
> Eclipse Foundation Terms of Use, PMC and EMO approval is not required."
> ... which is the opposite of what's written on the top of the IP Poster.
> The list of bugs with patches is currently 15 (
> ) so once we have cleared if they need PMC approval or not, and how to  
> request it, we will start processing them.
> Thanks!
> --
> Abel Muiño (IAM project lead)
> El 26/11/2008, a las 20:04, Wayne Beaton escribió:
> > "Code" means everything you check into CVS/SVN or make available as  
> > part of a download. So images, XML, etc. are subject to IP review.
> >
> > The easiest way to get PMC approval is to ask on this mailing list.
> >
> > It occurs to me that this mailing list is relatively difficult to  
> > use for these purposes. As a general rule, I don't imagine that  
> > there are many non-PMC folks who really want/need to listen to this  
> > list. So... in order to communicate with the PMC, you need to  
> > subscribe to this list for the duration of your communcation. All  
> > the while, you have to listen to our mindless banter on other topics.
> >
> > I'm thinking that we might consider adding the Bugzilla mail daemon  
> > to the PMC mailing list and inviting people to cc the technology-pmc  
> > on bugs that they want our input on. We could then do the short-term  
> > communication through the bug (copied on to the list, naturally) and  
> > then remove ourselves from cc when our input is no longer required.
> >
> > The architecture council does this currently.
> >
> > Thoughts?
> >
> > Wayne
> >
> >
> > Abel Muiño Vizcaino wrote:
> >> Hello PMC:
> >>
> >> I've just realized this sentence on the IP poster: "All Code Must  
> >> be approved by your PMC".
> >>
> >> How should we handle that? We have several bugs with attached code  
> >> from non-committers, some of them are small (<250 lines) and do not  
> >> require IP review.
> >>
> >> Also, I'm not sure if by "code" it also refers to "non source  
> >> code" (xml, images, build scripts...)
> >>
> >> Thanks!
> >> Abel.
> >>
> >> _______________________________________________
> >> technology-pmc mailing list
> >> technology-pmc@xxxxxxxxxxx
> >>
> >>
> > _______________________________________________
> > technology-pmc mailing list
> > technology-pmc@xxxxxxxxxxx
> >
> _______________________________________________
> technology-pmc mailing list
> technology-pmc@xxxxxxxxxxx
technology-pmc mailing list

Back to the top