Question: Adopt a governance model?

[callahad]

This may be premature, but should we establish a formal governance model for this project, yet? Rust, Node, and the Linux Foundation might have good examples we can look at. Google's AMP Project has a GOVERNANCE.md that explicitly lays out a lightweight BDFL model.

[jleclanche]

Agreed, let's discuss this next meeting.

[callahad]

The general feeling is to go with something along the lines of AMP's structure:

1. A "Tech Lead" with ultimate go / no-go on technical decisions.
2. Several "Core Committers" with autonomy to commit to the project and the ability to recall or overrule the tech lead through a majority vote.
3. Core Committers are selected by the Tech Lead.

...eh, just read the AMP document ;)

Owing to the battle scars from Persona, I'm happy to take the lead role until we hit 1.0.

Sound good? If so, who's willing to be involved from a core committer standpoint? Expectations are pretty light right now: just be responsive to communications and be able to dedicate a few hours a week to pushing this forward.

[grafana-dee]

Agreed. I like the AMP one.

[skorokithakis]

I like the AMP document too. I'm willing to be involved as a core committer.

[onli]

Expectations are pretty light right now: just be responsive to communications and be able to dedicate a few hours a week to pushing this forward.

That I could do.

[djc]

I can be responsive to communications for a few hours a week, but I think it will mostly be reactive (i.e. reviewing code/docs, not much writing of code/docs).

[onli]

Since we did this, I'll close here. Re-open if needed (like when wanting to change who fills which role).