[wildfly-dev] Commonhaus update

I'm pleased to report that yesterday Tom Jenkinson and I signed the agreement with Commonhaus for them to sponsor the WildFly family of projects. And last week Red Hat and Commonhaus signed an agreement that transfers intellectual property associated with WildFly to Commonhaus. These are the legal agreements involved with moving the project from Red Hat to Commonhaus sponsorship, so I'm very pleased that this is done and Commonhaus is now our sponsor! There's still more to do as we complete the Commonhaus onboarding process, including things like the transfer of domains to the registrar Commonhaus uses, making sure repos and github orgs meet requirements etc. I've created a Zulip channel where more chatty discussions focused on things related to WildFly and Commonhaus can happen: https://wildfly.zulipchat.com/#narrow/channel/507977-Commonhaus One thing to do is to update the SECURITY.md files in our repos, as the ones many repos currently use are focused to greater or lesser degrees on Red Hat. https://github.com/wildfly/.github/blob/main/SECURITY.md is a standard one to use. The main wildfly/wildfly repo has one much like that which I updated as follows: https://github.com/wildfly/wildfly/pull/18978 That file and the one in https://github.com/wildfly/.github/blob/main/SECURITY.md differ only in the presence of the 'Note that we will only fix such issues in the most recent minor release of WildFly' sentence in the wildfly/wildfly repo. That sentence is valid but may be less appropriate for a repo that produces a component where the typical thing is to fix a security issue by producing a bug fix release. Projects in the WildFly family that have their own separate identity of course might use different language. Best regards, -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His