Resolve Commonhaus policy-panda errors in the 'jboss-threads` GitHub repo

[bstansberry]

A requirement to complete onboarding to Commonhaus is resolving violations of CH requirements in JBoss Threads's GitHub repository. Below I list all the things that need correcting, as extracted from a report created using CH's policy-panda tool (https://github.com/commonhaus/foundation/blob/main/templates/panda/README.md).

I would like the GOVERNANCE one to be addressed by:

1. Create an jbosss-threads folder in https://github.com/wildfly/wildfly-governance

2. Add a GOVERNANCE.md that meets JBoss Threads's needs. Whatever the project likes so long as it doesn't contradict the simple requirement of WildFly Commonhaus Organization governance (https://github.com/wildfly/wildfly-governance/blob/main/wildfly-commonhaus-org/GOVERNANCE.md)

3. Add a Team.md file that lists the Project Lead and all Maintainers. Those people all become WCO maintainers.

4. Add a link to 2) in https://github.com/wildfly/wildfly-governance/blob/main/wildfly-commonhaus-org/Team.md
   Re the 'Developer Certificate of Origin - File does not exist' ones, each repo must have a dco.txt file.

All CONTRIBUTING.md files should have a section that deals with legal stuff. I recommend largely copying the 'Legal' section from https://github.com/commonhaus/foundation/blob/main/CONTRIBUTING.md. That is what I'm doing in 'wildfly' and 'wildfly-extras` repos. You should of course edit that to reflect the license that is used instead of MIT.

Policy Compliance Report for jboss

Generated on: 2026-02-01T21:00:43.872065

jboss/jboss-threads

❌ Governance - File does not exist
❌ Contributing - File does not exist
❌ Developer Certificate of Origin - File does not exist

[bstansberry]

A note about governance:

Last summer as part of the prep work for creating the governance docs for the WildFly Commonhaus Organization and the WildFly AS project, I created a google doc with draft governance language:

https://docs.google.com/document/d/1r2i17R6VtqGeslKlyH6lWVIQix0-QCiMa_6naq1tn-c/edit?tab=t.0#heading=h.944q0qy2t7ox

That doc has a "Simple Project Governance" tab that I wrote as a possible document for use by projects that don't have all the complexity of WildFly AS (e.g. the need for component leads or distinct leads for subprojects). I'm just pointing that out in case it is useful. Note that the WCO and WF AS governance text that is in evolved some from what's in that doc. Perhaps some of that evolution would be relevant to the "Simple Project Governance" text as well. I haven't done any analysis.

See also https://github.com/weld/.github/blob/main/GOVERNANCE.md which is the governance doc used by Weld, another top-level WCO project.