(Disclaimer: as member of both Technology and Runtime my reply is likely biased.)
I think, a PMC is more than just approving CQs. One key element is monitoring projects and retiring inactive projects. How is that supposed to work in a PMC-less project? That work cannot be dumped on EMO and/or Webmaster. There are also important aspects about reviewing and approving committer nominations, project lead elections and not to mention resolving disputes.
Yes, managing/approving CQs is the most time-consuming part today. As a PMC member, I'm desperately looking forward of never having to approve a standard CQ again (which are about 90%). :)
FWIW, I also recommend raising specific issues with the PMC, though. Especially when the PMC is a bottleneck this should be raised ASAP. Sometimes I miss an email from IPzilla in my inbox. A reminder usually helps. I appreciate your feedback, though.
-Gunnar
I have a similar view regarding Runtime.
+1
Jesse Hi all,
In parallel of the IP improvements proposal, I see that PMC duty and value is a recurring topic. More specifically, I have the impression that for many or even most of projects in Technology and Tools top-project, the PMC doesn't really help in the IP process, it's more a bottleneck than an assistance. And it's somehow similar for reviews.
So let's just throw the idea one more time in the air: what about allowing projects to be detached from any PMC ? That would IMO really make most of processes much faster and I don't see any loss of value/quality. --
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxxhttps://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
|
