[wildfly-dev] Re: Applying to Commonhaus

On Thu, Mar 13, 2025 at 7:31 AM Carlo de Wolf <cdewolf(a)redhat.com&gt; wrote: Before answering, I'll give a bit of context for the benefit of others. There are quite a lot of repos in the 'jbossas' org that relate to Red Hat JBoss EAP. So my basic thinking is to leave that org to EAP, and move the few remaining unarchived repos that host WildFly components to the 'wildfly' org. This is subject to agreement with the relevant maintainers, but these are the projects hosting upstream components that I think make sense to move to 'wildfly' Github org and include in any move to Commonhaus: jboss-classfilewriter jboss-dmr jboss-iiop-client jboss-invocation jboss-vfs remoting-jmx staxmapper I didn't list the JBoss Threads repo, as that's a commonly used component, not something with the bulk of its use and requirement definitions coming from WildFly. That project is actually quite far ahead of what WildFly uses. (Work is underway to catch up though!) If any of the others are similar and I'm just unaware of it, please someone let me know. Makes sense to me. -- Brian Stansberry Principal Architect, Red Hat JBoss EAP WildFly Project Lead He/Him/His