> I'm still +1 for merging all platform projects together
with Equinox > into one platform project.
> All current leads should become co-leads for the new project, as we > discussed earlier.
But how do you think the planning,
sign-off, bug triage etc. works? Currently we can hold specific people
accountable which got nominated by their peer committers. We would have
to build a system/copy similar to what we have now, otherwise it won't
Lars Vogel <lars.vogel@xxxxxxxxxxx> To:
21.06.2017 17:05 Subject:
Concerns Regarding Sub-Project Merege Sent by:
I'm still +1 for merging all platform projects together with Equinox into one platform project.
All current leads should become co-leads for the new project, as we discussed earlier.
For PDE and JDT I have no strong feelings, IMHO we could leave them as separate projects.
Maybe we could merge JDT core and JDT UI, there seems to be very little activity in JDT UI at the moment. Again, I have no strong feeling here, just a suggestion to simplify the setup in JDT.
Best regards, Lars
On Wed, Jun 21, 2017 at 4:50 PM, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote: > Dear Eclipse PMC Colleagues > > After thinking about this more and talking to my team I still have
strong > concerns to do that move. Here are some of them: > > - All current (sub-) projects will be archived i.e. we and the community > won't be able to find and learn about e.g. JDT in the PMI. > - There will only be one project with all committers. We would have
to > copy/replicate all the details that we currently have in the sub-projects > into that super project to keep users informed. > - Which people will lead that super project? One person can't do that.
Will > existing leads become co-leads? That would mean many leads and the
project > charter does not define the role of a main/super (co-) lead. > - Do we introduce the concept of components, i.e. do we replicate
what we > currently get by the PMI but not based on an official project charter?
If > so, we would have to define that and create web pages that show the > components and (co-) leads. Basically replicate what we currently
have, > except for the commit rights. > - My team was very unhappy when I informed them about this potential
change. > Putting code that's related to Platform UI together is one thing,
but > opening up SWT, JDT and PDE to everyone caused very scary feelings
(also for > me to be honest). > > I would like to ask the PMC to reconsider this decision for now and
instead > resend the message that the PMC encourages a fast track for existing > committers to become a committer on another project > (https://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg10305.html). > > Thanks, > Dani > > _______________________________________________ > eclipse-pmc mailing list > eclipse-pmc@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe
from > this list, visit > https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
-- Eclipse Platform UI and e4 project co-lead CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com _______________________________________________ eclipse-pmc mailing list eclipse-pmc@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe
from this list, visit https://dev.eclipse.org/mailman/listinfo/eclipse-pmc