Yes. You may want to alter what I send up slightly to tailor it to your community, but I'll come up with something that should be simple enough to tweak.The Commonhaus PolicyPanda compliance check tool[1] will look for a .github repo in an org and if there is one will look for GOVERNANCE.md, CODE_OF_CONDUCT.md and CONTRIBUTING.md files.[2] Any of those in that repo satisfies the requirement for that file in all repos in the org.Further background: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-fileOn Tue, Oct 21, 2025 at 1:04 PM Darran Lofthouse <darran.lofthouse@jboss.com> wrote:So if we create a .github repo at the root of our organisation we can do the same and copy the GOVERNANCE.md you are adding?On Tue, Oct 21, 2025 at 6:56 PM Brian Stansberry via wildfly-dev <wildfly-dev@lists.jboss.org> wrote:I'm pleased to say that both proposals received all positive votes, with no negative. So I've merged them and they are not official governance policies for the WildFly Commonhaus Organization and for the WildFly AS top level project.Thank you all! This is an important step forward for the project.In a next step I'll submit PRs to add GOVERNANCE.md files to the https://github.com/wildfly/.github and https://github.com/wildfly-extras/.github repos. These will basically be pointers to the documents in wildfly/wildfly-governance that we just merged. We need to have a GOVERNANCE.md in each repo, or in a .github repository for any GH organization that has such a repo. For WildFly AS repos at least we shouldn't repeat the details; just point to wildfly-governance which will always hold the currently effective policy.For maintainers of WildFly AS repos in other GH organizations, please let me know how you'd like to proceed adding GOVERNANCE.md files to your repos.On Mon, Oct 6, 2025 at 3:08 PM Brian Stansberry <bstansbe@redhat.com> wrote:I'm requesting your vote on the proposed governance documents for the WildFly Commonhaus Organization and one for the WildFly Application Server top level WCO project.In my September 17 'Next steps on WildFly Governance' post here I noted PRs. Thank you for your feedback on those. I hope I've answered any questions and I know I've made some small adjustments based on your input. Discussion has been quiet for a bit now, so I think it's reasonable to proceed with a formal approval process starting today, as I mentioned in my previous post.
The process is simple, and follows something Commonhaus has done on similar things.
To record your opinion, do one of the following on each PR
* Approve the PR or react with (:+1:) in the top description box if it looks good to you
* Review with Comments or react with (:eyes:) in the top description box if you're "ok" with it (it may not be your favorite.)
* If you think it needs discussion or revision
* Create a review, add your comments and require changes
* Use the +- button to make a suggestion (instead of just adding a comment).We'll record opinions for two weeks. On October 21 I'll tabulate the results.--Brian StansberryArchitect, JBoss EAPWildFly Project LeadHe/Him/His--_______________________________________________Brian StansberryArchitect, JBoss EAPWildFly Project LeadHe/Him/His
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
Privacy Statement: https://www.redhat.com/en/about/privacy-policy
List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message/464OF5UYUL45QXLD25EP2Q63RRML6TKO/
--Brian StansberryArchitect, JBoss EAPWildFly Project LeadHe/Him/His