Julien

That is untrue. Vendor updates takes mainly good unit and acceptance testing.

Plus everyone in the org is a maintainer in my vision.

in VP we have it in the governance: https://github.com/voxpupuli/plumbing/blob/master/share/governance.md

Do you have specific concerns with the apache exporter being independent? I wonder if we should move the exporter to the community without knowing what the future would bring -...

Regarding the projects we can limit the initial scope for: - exporters - file_sd - notifiers - LTS The only conditions should be: - There is no equivalent (then a...

Regarding governance, membership I would apply this: https://github.com/voxpupuli/plumbing/blob/master/share/governance.md With the only change : PMC would be 4 people elected by community (who could be from prometheus team) and 1 by...

Projects adopted by the org: Get maintained by the org for the standard part (e.g the org would switch them to open metrics, update vendors, ...) Use the same ci...

To answer your question more precisely, the best case is a maintainer of a project that wants to share the burden of maintaining it ; to prevent to be the...

Another good reason to give the exporter to the community is that in the community there is overall a good knowledge of go. You might have written an exporter for...

To come back to the initial topic: https://github.com/voxpupuli/plumbing/blob/master/share/governance.md + the rule PMC would be 4 people elected by community (who could be from prometheus team) and 1 by prometheus team...