WildFly in a Foundation
In the last two years we’ve been putting a lot of effort into improving how the WildFly project interacts with our community, including adding new communication channels like our Mini Conferences, adding new user guides and creating a transparent feature development process. WildFly has been a successful project for a long time now, and I believe that’s largely because we are passionate about serving our community.
To help us continue on this path, we are considering moving WildFly to a vendor-neutral software foundation. Our hope is that by doing this we could further expand our community, improve our openness and transparency, refresh our governance model, and encourage more participation by contributors not affiliated with Red Hat.
Important Considerations
Moving to a foundation is not a trivial task, so it’s critical that the choice we make is a net benefit to our community. To help ensure this, there are a number of key factors we’re looking at when evaluating what foundation would be the best fit:
-
Flexibility to continue shipping third-party components using a wide array of Open Source Initiative (OSI)-approved Open Source licences.
-
Maintain as much as possible our current release processes.
-
Retain independence in decision making, particularly on technical matters.
Support and Alignment with Red Hat Values
Red Hat is dedicated to participating in and supporting vendor-neutral collaboration projects, such as the Linux kernel, Kubernetes, and OpenJDK; doing so is part of the company’s DNA. Red Hat business leaders are fully supportive of this move.
Community Feedback
We’d love to hear your thoughts on this. Let us know what you’re thinking either on the developer mail list, in the WildFly google group or in Zulip
Best regards,
Brian