The Developer Experience team is on a mission: we accelerate and simplify the integration of Ping and ForgeRock products into customer apps and websites.
We are responsible for the following open-source projects:
We will also be collaborating on the Unified SDK, bringing the best of both Ping and ForgeRock functionality to the fingertips of developers.
Success requires constant collaboration between contributors; each with their own skills, backgrounds, and beliefs.
This Standards of Practice document establishes our expectations for behavior for working with each other on our mission.
As common as it may be to believe that technology is neutral, apolitical, unbiased and decoupled from the people and culture that produced it, we believe differently.
We believe that technology is a reflection of who we are as a community, so it’s best to be explicit about what we believe.
These standards of practice apply to all open-source projects managed by the Developer Experience team.
 Culture |
 Security |
 Technical |
|---|
Our primary belief is that treating individuals with respect, empathy, and inclusivity is fundamental to our continued success.
We believe in the power of including diverse experiences, backgrounds, educations and ideas into our daily processes, strongly influencing the development of our products.
As we interact with each other, we are mindful to enforce these shared values:
- Psychological safety and mindfulness
- Diverse organizations and inclusive collaboration
- Proactively communicate and passionately listen
- Build with empathy
- Intellectual humility
- All leaders, no owners
- Innovate and inspire
- Balance and harmony
Learn more about our culture >
The software we create is often on the critical path for our customers. We must ensure we follow best practice for SDKs, libraries, and frameworks.
Because we build things that hundreds of millions of people use, we have to ensure that we build things that never risk their safety, privacy and security, no matter how valuable or fashionable we believe it may be.
Learn more about our security guidelines:
As a diverse team of contributors, we believe it is vital to share our expectations for the code we write, and how we write it.
As such, below we outline some technical aspects of creating our products, including the tools we use, our code style, performance requirements, and how we undertake version control.
Don't think of these as mandates or commandments, but guidelines and suggestions that help us build quality, maintainable code as a collaborative collective.
Learn more about our technical guidelines:
This code is provided by ForgeRock on an “as is” basis, without warranty of any kind, to the fullest extent permitted by law. ForgeRock does not represent or warrant or make any guarantee regarding the use of this code or the accuracy, timeliness or completeness of any data or information relating to this code, and ForgeRock hereby disclaims all warranties whether express, or implied or statutory, including without limitation the implied warranties of merchantability, fitness for a particular purpose, and any warranty of non-infringement. ForgeRock shall not have any liability arising out of or related to any use, implementation or configuration of this code, including but not limited to use for any commercial purpose. Any action or suit relating to the use of the code may be brought only in the courts of a jurisdiction wherein ForgeRock resides or in which ForgeRock conducts its primary business, and under the laws of that jurisdiction excluding its conflict-of-law provisions.
© Copyright 2024 ForgeRock AS. All Rights Reserved.