We are looking to build a thriving community and we need your help. Users of Open Identity Stack are already providing significant time and resources to improving the overall experience. Here’s how you can help:

Use the products and give us feedback

By using the products, asking questions, reporting bugs and making feature requests, you can provide critical input as part of the community process.  User feedback can strongly drive the projects and the technologies.

Give back to the community

If you want to provide more, we welcome you to participate in the development of the projects. This can mean getting involved with the discussions on the development mailing lists, answering user questions, providing patches for bugfixes or features, and helping to improve the documentation.

Our Development Process is well documented and it is the place to start if you want to get down with the code.

Become an official contributor

Some community members are so involved they fix bugs themselves, or even add features to the software. When you contribute your work back to the community, everyone benefits. You get the benefit of the whole developer community maintaining and improving the code you wrote, and the community gets the new capabilities you created.

When you contribute back to the community you show the commitment that means we can make you an official contributor and have you join in. When you signed up with forgerock.org, you accepted the terms of service, which includes the terms under which your contributions are made. This Agreement is not like other “Contributor Agreements” – it gives you the free choice of either contributing under the project’s open source license or sharing ownership of the code with ForgeRock.

Q & A

Will you be using a contributor agreement?

No. We believe accumulating the copyright to an open source project centrally – especially in the hand of a for-profit company – is bad for community relationships and best avoided. Copyright accumulation only becomes necessary when a business decides to use a business model that requires it. We devised a business model for ForgeRock that does not rely on copyright accumulation and thus we do not practice copyright accumulation. All the rights everyone in the project (including ForgeRock) needs are delivered through the OSI-approved open source license – the rights to use, study, modify and distribute the software.

When we started the OpenAM project, we did have a “community participation agreement” in place for everyone to complete, which ensured everyone was committed to licensing their contributions under the project’s open source license (the CDDL in most cases for legacy reasons). We found that even the step of completing and returning that form was a barrier to community. We realized the Terms of Use for the community web sites actually included all the promises necessary, so we have scrapped use of the FCPA.

What if I have questions about the open source licensing or the terms of use?

Please address all questions on these subjects to the community ombudsman, ombudsman at forgerock dot com, who will consider all matters impartially.

You forked existing projects to create the ones above. Will you fork all the projects you work on?

No. ForgeRock is committed to being a good community citizen. Where it is essential to offer hosting for a community (as has been necessary for OpenAM and OpenDJ) we will do so, but generally a fork should be the last resort. Where we become unable to make timely upstream contributions we will, however, create a downstream repository and in time such things do become forks.