[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Patch proposal forbugzilla154854-gdbconsoleenhancem ents

PMC Approval can come from one of the members of the Tools PMC. BTW, I am
one of those members. If you aren't getting a response from me, try the
tools-pmc@xxxxxxxxxxx mailing list.

Doug Schaefer
QNX Software Systems
Eclipse CDT Project Lead

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Chris Recoskie
Sent: Friday, August 25, 2006 10:11 AM
To: CDT General developers list.
Cc: CDT General developers list.; cdt-dev-bounces@xxxxxxxxxxx
Subject: RE: [cdt-dev] Patch proposal

The legal statement comes in the form of the contribution questionnaire.
See http://www.eclipse.org/legal/ContributionQuestionnairePart1-v1.0.php


Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto

             <Martin.Oberhuber                                          To 
             @windriver.com>           "CDT General developers list."      
             Sent by:                  <cdt-dev@xxxxxxxxxxx>               
             cdt-dev-bounces@e                                          cc 
                                       RE: [cdt-dev] Patch proposal        
             25/08/2006 06:57          forbugzilla154854-gdbconsoleenhance 
             AM                        ments                               
             Please respond to                                             
               "CDT General                                                
             developers list."                                             

Hi CDT committers,

Currently, the "significant contribution" limit seems to
be at 250 lines of code, including configuration files: See

I'm not exactly sure what rules you follow on CDT,
but for Target Management we have come up with some
nice guidelines:

Basically we ask contriutors to add some legal statement
like "I wrote this myself" to the bugzilla entry upfront,
in order to clarify the Legal things without having extra
E-mail exchange.

Regarding PMC approval, Bjorn has blogged that a single
PMC member's opinion may stand for the entire PMC:

This means its sufficient if you send an E-Mail to the
Tools PMC Mailing list, asking OK to apply the contribution,
and you get at least one PMC member's OK (that would be
Doug S I guess). Other PMC members can veto this later,
then you'd have to remove the patch again, but this is
really unlikely I guess.

But as I said, each project has its own guidelines, and
DougS is your master -- I just thought that giving you
the two links above might be helpful.

Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ploett, Norbert
> Sent: Friday, August 25, 2006 10:47 AM
> To: CDT General developers list.
> Subject: AW: [cdt-dev] AW: [cdt-patch] Patch proposal
> forbugzilla154854-gdbconsoleenhancements
> Davide / (Mikhail),
> I also have this 100-line rule in the back of my head and I
> assume that you will need to fill in the
> http://www.eclipse.org/legal/ContributionQuestionnairePart1-v1.0.php
> This implies that we must get PMC approval for your
> contribution, I'll have yet to find out how this is obtained
> (anyone knows?).
> I also think that somehow you must prove that your company
> lets you put your contributions under the EPL (as you stated
> you would in the headers of the new files ...)
> Cheers
> Norbert
cdt-dev mailing list

cdt-dev mailing list