RE: [cdt-dev] Committer rationalization

[Sean Evoy <sevoy@xxxxxxxxxx>]

Sebastien,
I thought it was overkill to assign
me a dedicated plug-in for a single file. However, we now have a couple
more files and I can see the range and number of tests growing, so if you'd
like, go ahead and create a new plug-in for me. It sure is annoying to
have to submit JUnit test patches to the mailing list! 

Sean Evoy
Rational Software - IBM Software Group
Ottawa, Ontario, Canada

Sebastien Marineau <sebastien@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx

03/17/2004 06:09 PM

Please respond to
cdt-dev

To	"'cdt-dev@xxxxxxxxxxx'" <cdt-dev@xxxxxxxxxxx>
cc
Subject	RE: [cdt-dev] Committer rationalization

Hi Alain,

> > 
> > Hi folks,
> > 
> > up for vote is a proposal to clean up and group the plugins 
> into a few
> > logical groups, and rationalize the list of committers for 
> each of these 
> > groups. The specific proposal is shown below (also attached 
> as an excel 
> > spreadsheet). In all cases, committers are not losing any commit
> > access to any plugins, but are instead gaining additional 
> commit rights.
> > 
> > The main goal for this is to streamline and align the 
> commiters with the
> > subproject in CDT, and remove the anomalies, such as having 
> committers only
> > having access to cdt.core and not cdt.ui. Note that this 
> list also removes 
> > inactive committers from the project.
> > 
> > Please provide your feedback and votes back to the list.
> > 
> 
> 1- What about the new plugins ?
>    a) org.eclipse.cdt.debug.core.tests
>       Only debug UI tests was created
>    b) the GNU plugins ?

yep, we can add both to the proposal. Which group do we believe the GNU
plugins should go
into? Also, John Healy from Redhat has some Linux plugins he may want to
contribute (RPM,
profiling), along with some developers. Maybe we should create a "GNU"
group?

> 
> 2- If Sean does not have access to the org.eclipse.cdt.core.tests
>    than create a new plugin for the managedbuild tests.
 We want to
>    encourage testing not make it a barrier.

No problem. Sean, are you comfortable with a managedmake JUnit plugin?

> 
> 3- I will need writing access to:
>    a) org.eclipse.cdt.doc.isv
>       The original drafts for this plugin will come
for the developers
>    b) the releng stuff
>       Many time after heavy refactoring, I need it
to fix 
> things .. not a must.

I have no objections. Doug, Kleo, any more thoughts? If not, I'll resend
the
proposal
with these changes made.

Thanks,

Sebastien
>    
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev