Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] Concerns Regarding Sub-Project Merege

On Wed, Jun 21, 2017 at 5: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).

Merging everything was surprising to me ( I heard about it yesterday
although I love the idea). The original discussion IIRC was to have
Eclipse TLP with Platform/PDE/JDT(maybe Equinox as 4th when it moves)
and I still think this is the best path forward as it will keep 4 main
subprojects.
 Keeping the current status is clearly not working but we can continue
merging projects one by one as we were doing by now but this just
costs more time and creates more noise in the system.

Regards,
Alex


> 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



-- 
Alexander Kurtakov
Red Hat Eclipse Team


Back to the top