ForgeRock Community Process
The following are the roles project participants can take, and the process for decision making within the ForgeRock.org community contribution process. It also describes processes for communicating and sharing within the project teams and communities. The ForgeRock project organization is structured as a hierarchy of participants, that are promoted based on merit.
We have four types of participants:
A Listener, also known as a user, is someone that uses software from ForgeRock. As a listener, you are able to contribute to the ForgeRock projects by providing feedback to developers in the form of bug reports and feature suggestions. Listeners are encouraged to participate in the ForgeRock community by helping others on mailing lists and support forums. Listeners are able to view issues in Jira, and are encouraged to contribute to the Wiki.
A Fan, also known as a contributor, has an account on the Forgerock.org IDP, and contributes to a project in the form of code or documentation. They take extra steps to participate in a project, are active on the developer mailing list, participate in discussions, provide patches, documentation, suggestions and criticism. Fans have accounts in the ForgeRock development tools; Confluence, Jira, Fisheye and Crucible.
A Roadie, also known as a committer, is a major contributor to the project, and has been given write access to the code repository trunk. A roadie is considered part of the core development team. Roadies are the only ones able to commit changes to trunk, and only after a code review. Roadies are expected to be active on the mailing list, and a leader within the development community.
A Rockstar is a committer that has been elected to the status of Rockstar based on merit for their evolution of the project and demonstration of commitment. They have write access to the code repository, and the right to vote for the community-related decisions. Rockstars are part of the Band. The Band as a whole is the entity that controls the direction of the project.
The Band (architecture committee)
The Band is the group that controls and directs the project. The Band votes on election of members and commits to release branches. All band members are Rockstars.
5 steps to stardom – AKA how to become a Rockstar!
1. A listener signs up for an account on ForgeRock.org (IDP)
2. Become a Fan: Add documentation, create wiki content, submit patches as diffs into Crucible.
3. Help the band, become a Roadie: Once a Fan has shown commitment to a project, built a reputation among other community members and their submissions are deemed of reasonable quality by The Band, they can be nominated to become a Roadie. Nominations can be made by Roadies and Rockstars. The Band votes on who becomes Roadies.
4. On the road: A Roadie is expected to be a fairly major contributor to the project and has write access to the trunk, Roadies are able to submit simple patches directly to the trunk. Once a roadie has shown a strong commitment to the project, generally by becoming a module owner, or responsible for a significant section of the project, they can be nominated to become a rockstar. The Band then votes on the nomination.
5. Once accepted as a rockstar, they become part of the architecture committee, (the Band) and are an integral part of the project. Anyone can move along this chain, simply by showing a commitment to the code and the project.
How ForgeRock releases are managed
ForgeRock will release packages, known as a ForgeRock release. ForgeRock will determine what features, components and modules are included in a ForgeRock release, which will be driven by the company’s roadmap and other business decisions. ForgeRock provides commercial support for ForgeRock releases.