WildFly would like to join Commonhaus

[bstansberry]

Project information

• Project name: WildFly
• Project website: https://www.wildfly.org/
• Code repository: https://github.com/wildfly/wildfly (primary among many)
• License: ASL 2.0

Do you have authority to represent this project?

• I own or maintain this project

Describe your project

WildFly is a powerful, modular and lightweight application server that helps you build amazing enterprise Java applications. Among other things, it provides implementations of the Jakarta EE and MicroProfile specifications.

It is primarily written in Java.

WildFly, formerly known as JBoss Application Server, has been one of the better known open source projects in the enterprise Java space since the early 2000s.

Motivation for joining Commonhaus

WildFly is a well-established project that wishes to continue to grow and develop. We believe being associated with Commonhaus can help us:

• Grow our contributor and user communities by associating the project with a vendor-neutral foundation.
• Update our governance model to incorporate current open source best practices.
• Continue to improve our openness when it comes to roadmaps, designs and solution discussions.

We want to continue to evolve and improve, but we also have a lot of experience running a successful and very complex project. We believe Commonhaus’ guiding principles around honoring project and community identity and offering guidance instead of mandates, with its “community-first” governance model, make it an excellent fit for WildFly.

Things that must be done (bootstrap phase)

• [X ] Review the bylaws, especially sections about projects, decision making, and voting for significant decisions.

• [X ] Read the bootstrapping agreement.

• If all is well, and you agree to participate in the bootstrapping phase to help us build this thing, then create a PR with the following:

  1. A filled out copy of the bootstrapping agreement. You can make a copy of bootstrapping.md file and check that in, or checkin a filled out pdf. Please follow naming conventions.
  2. An updated CONTACTS.yaml that names your project representative in the EGC section
  3. An updated PROJECTS.yaml that provides details / describes your project
  4. An updated TRADEMARKS.md that adds your project name and project logo (if you have one). Please include the footnote reference, as we are using your project name and logo with your permission until we have a formal agreement in place and resources are transferred.

  The commit should be "Signed-off-by" your GH login (git commit -s -m "<project> bootstrapping agreement, yyyy-mm-dd")

[ebullient]

Welcome to Commonhaus!

More to come.