>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3585326. --> Reported by: [webchick](https://www.drupal.org/user/24967) Related to !9 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p><em>See "background" discussion at <a href="https://drupal.slack.com/archives/C0803LX4536/p1776359940186029">https://drupal.slack.com/archives/C0803LX4536/p1776359940186029</a></em></p> <p>While I am the one who originally started this project, from the beginning the vision here has very much been a <em>shared</em> governance model, since the Skills / Guidance in this project will more or less map to Skills / Guidance for Drupal itself (in a way that both agents AND humans can benefit!).</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>A few of us got together and starting drafting a <a href="https://docs.google.com/document/d/15ISe3dbbsEsnGxZvhlujJr6oUZe99N4jA9m-G-7PLaw/edit?tab=t.0#heading=h.rbsobnrbmijv">list of maintainers</a> (deprecated; see the merge request) that more or less just documents the "do-ocracy" as it stands, but also creates some explicit openings for other roles that don't have an identified owner yet.</p> <p>This includes:</p> <ul> <li><strong>Project leadership</strong>: Various * Leads and Managers</li> <li><strong>Subsystem Maintainers</strong>: Those heading up specific technical areas of the project (e.g. evals framework, developer bootstrap tooling)</li> <li><strong>Skills Maintainers</strong>: Those heading up specific skill areas of the project.</li> </ul> <p>It sounds like from the discussion in Slack that not having this explicitly defined isn't <em>blocking</em> anyone (which is great!) but my goal with this is to encourage people to feel <strong>bold and empowered</strong> to make major "rocket surgery" changes to this in the furtherance of getting it to a shippable "MVP" state. (Especially with Dev Days around the corner, where ideally this could be hacked on "live" during the event.)</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Make sure people mentioned in that doc have <strong>enthusiastic consent</strong> (or at least, "consent" &#128517;) to being listed there</li> <li>Figure out if we need more headings (leadership positions, subsystems, skills delineations) in the doc. (Not super pressing; making future changes is just a MR away, but it's nice to lay down strong foundations so future intent is clear)</li> <li>Make a MR that incorporates the changes</li> <li>SHIP IT! :D</li> </ul>