We've taken a bit of an August holiday away from the WildFly Governance topic, but I'd like to pick it up and try and by the end of October get GOVERNANCE.md files in places for the WildFly Application Server project and the overall WildFly Commonhaus Organization. From our discussions I think we need to do 3 things: 1) Identify all the people who currently have write permissions to all the various repos. This list becomes the base for identifying the initial set of folks in the proposed Maintainer role. Maybe on Friday I'll take a crack at a JBang script to extract this data via the GitHub REST API. 2) For WildFly AS itself, for all the various subprojects, identify which have leads. For this, you tell me. :-) I don't think either 1) or 2) really block the big one, which is.... 3) Adopt GOVERNANCE.md documents for the WildFly Commonhaus Organization and the WildFly Application Server top level WCO project. Toward this end, I've taken the content of the draft governance Google doc we discussed this summer and converted the WCO and WildFly AS tabs into markdown files. I then opened PRs in the new 'wildfly-governance' repo: WCO -- https://github.com/wildfly/wildfly-governance/pull/4 WildFly AS -- https://github.com/wildfly/wildfly-governance/pull/5 Each of those branches has a commit for the original Google doc content and then other commits to incorporate various ideas we discussed in July. I propose the following: A) Between now and Mon Oct 6 we discuss those PRs via comments on the PRs, making appropriate edits as we go. Goal is to finalize the proposed text. B) For two weeks starting then we let more formally express their agreement disagreement via a simple GitHub emoji reaction thing Commonhaus has used. (I'll explain more on that later; this message is already long enough.) So the key thing is to look at and react to those 2 PRs! Thanks, -- Brian Stansberry WildFly Project Lead He/Him/His