Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] PMC or parent TLP-less projects


On Thu, Jun 2, 2022 at 1:39 PM Ed Merks <ed.merks@xxxxxxxxx> wrote:

With CQs going away, isn't the only thing each PMC needs to do is give a +1 once a year for a review?   Moreover, such a review can just be a progress review that's scheduled any time and hence a delay in the approval, if there is a significant delay, would not hold up the project's release process.   Is there some other more regularly occurring bottleneck that I've overlooked?

I can think of:
* Approve committer/PL votes
* Approve bigger code contributions (technically still CQs but handled differently)

The former is just a blanket +1 if there is "some" proof of the contribution, while for the later all meaningful actions are up to IP team so PMC makes even less sense there.

On 02.06.2022 12:18, Mickael Istria wrote:
Hi all,

We discussed in some not too old call the capability of having projects without a PMC, or could we say being their own PMC, their own top-level project and thus being more autonomous on many things
How feasible would that be? Any idea when this can be implemented?

I'm asking that because these days, I think the Technology PMC is a bottleneck in m2e development; and I don't remember the Technology PMC has not created any value for the m2e project for a long time. So m2e would be better without having to deal with Technology PMC.
Note that it's not blaming the Technology PMC and its members in any way, same could be said for some other projects and other PMCs, it just happen that m2e is my current example. This is more discussing the concept of PMC or having a parent Top Level Project not being best for m2e -and probably others- in general.

Cheers,

--
Mickael Istria
Eclipse IDE developer, for Red Hat Developers

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council


--
Aleksandar Kurtakov
Red Hat Eclipse Team

Back to the top