Thanks, everyone for the input.

I've only heard opposition to requiring commit signoffs, so, at least for the projects in the 'wildfly' and `wildfly-extra` GH orgs, I think we have a consensus not to do them. For other orgs, well this is the kind of thing that top-level projects in the WildFly Commonhaus organization decide for themselves. And for other orgs that are part of WildFly AS I don't see any reason the relevant project leads can't decide for themselves. For those I think the default assumption is no signoff required.

For the CONTRIBUTING.md text, for repos in the 'wildfly' and `wildfly-extra` GH orgs I think what Narayana has in https://github.com/jbosstm/narayana/blob/main/CONTRIBUTING.md#certificate-of-origin-and-license is good, except the copyright notice should say "The WildFly Authors" not "The Narayana Authors". It's similar in message to others I've read. The DCO language is also similar to others, and it follows some suggested language from Red Hat's Open Source Program Office.

On Thu, Jul 31, 2025 at 10:21 AM Richard Opalka <ropalka@redhat.com> wrote:
On Thu, Jul 24, 2025 at 2:21 PM Brian Stansberry via wildfly-dev <wildfly-dev@lists.jboss.org> wrote:
Thanks, Tom and Yoann.

So, people with professional knowledge of these things (I've now seen the Red Hat OSPO guidelines Tom mentioned; unfortunately not public but quite clear) have indicated that not requiring Signed-off-by and doing things the way Narayana and Hibernate do is ok.

Do we want to do signoffs anyway? Personally, I don't. It would be a lot of logistics I think.

+1 to "don't want" 


--
Brian Stansberry
Architect, JBoss EAP
WildFly Project Lead
He/Him/His