Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Critical
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

(Note in advance – for consistency I'm posting equivalent text to the following bits in a number of projects. A lot of this is only a bit applicable to Narayana, which mostly just needs GOVERNANCE.md files.)

A requirement to complete onboarding to Commonhaus is resolving violations of CH requirements in Narayana's GitHub repositories. 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).

A possibility to address many of these in a simple way is to add a .github repository to the jberet org and include a GOVERNANCE.md, CODE_OF_CONDUCT.md and CONTRIBUTING.md in it. That assumes the same content is applicable to all repos, which I expect to be the case, except perhaps for CONTRIBUTING.md.

I would like the GOVERNANCE one to be addressed by:

1) Create a narayana folder in https://github.com/wildfly/wildfly-governance

2) Add a GOVERNANCE.md that meets JBeret'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 3) 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. Let me know and I can try using a jbang script I wrote to send PRs to each repo to add it.

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 AS repos. You should of course edit that to reflect the license that is used instead of MIT.

Note that if you go with the approach of putting just one CONTRIBUTING.md in a .github repo a link to dco.txt I believe will point to the one in that repo. If you don't like that it's fine to not make that a hyperlink.

Policy Compliance Report for jbosstm

Generated on: 2026-02-01T21:21:37.731090

jbosstm/narayana