From: Jeff McAffer
[mailto:Jeff_McAffer@xxxxxxxxxx]
Sent: Monday, October 22, 2007 6:56 PM
To: Tools PMC mailing list
Cc: mik@xxxxxxxxxxx
Subject: RE: [tools-pmc] RE: [ve-dev] Contribution on VE with XML editor
Mik, I
understand setting the bar high but wonder... The concern boils down to
person X claiming some status as a "Mylyn committer" when really they
are a committer on the "Mylyn Incubator component" or "Mylyn
XPlanner component". Personally I think you are cutting off part of
the communtiy by not letting folks inside the gate as it were. Nothing in
Bjorn's post or comments from the others indicated this sort of concern.
In the Eclipse project we have 5 subprojects and tons of components.
People get commit rights on a per component basis. Some folks are
committers only in the Incubator or on some special cases (e.g., supplying a
port to QNX (who let them in?! :-)). And yes, some have, from time to
time, attempted to inflate their status by stating they are Eclipse project
committers. So what? In short, I encourage you to think more
component-oriented (no pun intended) and get commit rights for people who are
doing good work and are trustworthy.
Jeff
Doug
Schaefer <DSchaefer@xxxxxxx>
Sent by:
tools-pmc-bounces@xxxxxxxxxxx
10/22/2007
01:32 PM
Please respond to
Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
|
|
To
|
mik@xxxxxxxxxxx,
Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
|
cc
|
|
Subject
|
RE:
[tools-pmc] RE: [ve-dev] Contribution on VE with XML editor
|
|
In my
view it’s really simple. A component is a Unix user group that controls
write access to various parts of the Eclipse serversphere. Committers for a
project can select new committers and grant them access to select components
based on whatever bar they decide. Obviously, Helen needs to show a track
record to meet PMC approval, but given that she contributed the component, that
should be sufficient for to give here access to that component.
My
suggestion is that we allow the “incubator” status to apply to
components and that any “release” off the download site be marked
as incubator in the file name, and that the component under source control has
the word incubator in it’s path name.
Doug Schaefer, QNX
Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
From: tools-pmc-bounces@xxxxxxxxxxx
[mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of Mik Kersten
Sent: Monday, October 22, 2007 1:17 PM
To: 'Tools PMC mailing list'
Subject: RE: [tools-pmc] RE: [ve-dev] Contribution on VE with XML editor
Thanks Doug.
I wasn’t detailed enough in
my response. The problem is not that we can’t have separate
committers for components, and we already do that. The issue is that we
have a pretty high bar for being a committer on the core Mylyn project.
In an incubator project we could have a lower bar for making contributors
committers.
For those interested in the
details: A concrete example of this issue is Helen of CodeGear, who has
contributed the XPlanner connector to Mylyn. In terms of a code
contribution, this was big, and all her participation in the project has been
great. However, the XPlanner connector is an Incubation quality component
in our Sandbox, there has been little community feedback, and only 10 bugs have
been fixed on it (http://www.eclipse.org/mylyn/contributors/). Until there are considerably
more user-reported bugs fixed on this component I feel unable to nominate Helen
for commit rights, because I don’t yet have enough indication that this
component will have the community adoption needed to bring it out of Incubation
status. So in spite of her great work I haven’t nominated Helen for
commit rights yet, and I would have done so if we this were an incubation
project. At some level this is splitting hairs, because if I considered
Components to be more primary then I should be fine with nominating her.
In other words, I’m a bit confused about how primary a unit the
Component is vs. a Project, and the fact that only projects can have a parallel
IP process currently seems to be a deciding factor. So I’ll be
curious to see whether this is changed, because I certainly see arguments for
keeping everything under one project umbrella, and am sure that if we create a
Mylyn Technology project we will cause some end user confusion.
Mik
From: Doug Schaefer
[mailto:DSchaefer@xxxxxxx]
Sent: Monday, October 22, 2007 9:42 AM
To: mik@xxxxxxxxxxx; Tools PMC mailing list
Subject: RE: [tools-pmc] RE: [ve-dev] Contribution on VE with XML editor
Cool,
thanks Mik.
BTW,
projects can have components and the components can have different sets of
committers. You should be able to do this for your sandbox components.
Doug Schaefer, QNX
Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
From:
tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf
Of Mik Kersten
Sent: Monday, October 22, 2007 12:31 PM
To: 'Tools PMC mailing list'
Subject: RE: [tools-pmc] RE: [ve-dev] Contribution on VE with XML editor
Just fyi, this is pretty much how
Mylyn operates. We haven’t yet bitten the bullet of creating
another project, but for the past couple of years we’ve had a separate
set of Sandbox components where we incubate things. While we don’t
have the benefit of the parallel IP process, this does give us the ability to
communicate Incubation status on those components, given them their own update
site, project set, etc.
In addition to the lack of
parallel IP process, which is probably the biggest benefit of incubation, the
thing that’s I’ve been finding most awkward about the single
project approach is that the incubation components don’t have their own
set committers, as they would with a separate incubation project. Bjorn
made some other good points about the split project approach here:
http://eclipse-projects.blogspot.com/2007/09/getting-new-people-started-in-your.html
Mik
From:
tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On
Behalf Of Doug Schaefer
Sent: Monday, October 22, 2007 8:09 AM
To: Bjorn Freeman-Benson; Doug Schaefer
Cc: Tools PMC mailing list
Subject: RE: [tools-pmc] RE: [ve-dev] Contribution on VE with XML editor
Incubator
components would make sense. Having to recreate the project structure, even if
it is the same people, is where I have issues. Also the façade that they are
two separate projects is misleading to the community since operationally they
are not. Projects in my mind are organizational things, i.e. the people. Is it
the code that’s incubating or the people? _______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc