diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 44b7ecdd6b4a..1254d1d8c3b7 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,11 +1,11 @@ blank_issues_enabled: false contact_links: - - name: ORY Kratos Forum + - name: Ory Kratos Forum url: https://github.com/ory/kratos/discussions about: Please ask and answer questions here, show your implementations and discuss ideas. - - name: ORY Chat + - name: Ory Chat url: https://www.ory.sh/chat - about: Hang out with other ORY community members and ask and answer questions. - - name: ORY Support for Business + about: Hang out with other Ory community members and ask and answer questions. + - name: Ory Support for Business url: https://github.com/ory/open-source-support/blob/master/README.md - about: Buy professional support for ORY Kratos. + about: Buy professional support for Ory Kratos. diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index d08147739368..0e1ecbf77d2a 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -8,7 +8,7 @@ If this change neither resolves an existing issue nor has sign-off from one of t chance substantial changes will be requested or that the changes will be rejected. You can discuss changes with maintainers either in the Github Discusssions in this repository or -join the [ORY Chat](https://www.ory.sh/chat). +join the [Ory Chat](https://www.ory.sh/chat). --> ## Proposed changes diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 000000000000..2351896e4f54 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,77 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +In the interest of fostering an open and welcoming environment, we as +contributors and maintainers pledge to making participation in our project and +our community a harassment-free experience for everyone, regardless of age, body +size, disability, ethnicity, sex characteristics, gender identity and +expression, level of experience, education, socio-economic status, nationality, +personal appearance, race, religion, or sexual identity and orientation. + +## Our Standards + +Examples of behavior that contributes to creating a positive environment +include: + +- Using welcoming and inclusive language +- Being respectful of differing viewpoints and experiences +- Gracefully accepting constructive criticism +- Focusing on what is best for the community +- Showing empathy towards other community members + +Examples of unacceptable behavior by participants include: + +- The use of sexualized language or imagery and unwelcome sexual attention or + advances +- Trolling, insulting/derogatory comments, and personal or political attacks +- Public or private harassment +- Publishing others' private information, such as a physical or electronic + address, without explicit permission +- Other conduct which could reasonably be considered inappropriate in a + professional setting + +## Our Responsibilities + +Project maintainers are responsible for clarifying the standards of acceptable +behavior and are expected to take appropriate and fair corrective action in +response to any instances of unacceptable behavior. + +Project maintainers have the right and responsibility to remove, edit, or reject +comments, commits, code, wiki edits, issues, and other contributions that are +not aligned to this Code of Conduct, or to ban temporarily or permanently any +contributor for other behaviors that they deem inappropriate, threatening, +offensive, or harmful. + +## Scope + +This Code of Conduct applies both within project spaces and in public spaces +when an individual is representing the project or its community. Examples of +representing a project or community include using an official project e-mail +address, posting via an official social media account, or acting as an appointed +representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. + +## Enforcement + +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported by contacting the project team at office@ory.sh. All complaints will be +reviewed and investigated and will result in a response that is deemed necessary +and appropriate to the circumstances. The project team is obligated to maintain +confidentiality with regard to the reporter of an incident. Further details of +specific enforcement policies may be posted separately. + +Project maintainers who do not follow or enforce the Code of Conduct in good +faith may face temporary or permanent repercussions as determined by other +members of the project's leadership. + +## Attribution + +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 1.4, available at +https://www.contributor-covenant.org/version/1/4/code-of-conduct.html + +[homepage]: https://www.contributor-covenant.org + +For answers to common questions about this code of conduct, see +https://www.contributor-covenant.org/faq diff --git a/README.md b/README.md index 538aaee2bfbf..6cbf4e0ad8bc 100644 --- a/README.md +++ b/README.md @@ -90,10 +90,10 @@ from other products. -The ORY community stands on the shoulders of individuals, companies, and +The Ory community stands on the shoulders of individuals, companies, and maintainers. We thank everyone involved - from submitting bug reports and feature requests, to contributing patches, to sponsoring our work. Our community -is 1000+ strong and growing rapidly. The ORY stack protects 16.000.000.000+ API +is 1000+ strong and growing rapidly. The Ory stack protects 16.000.000.000+ API requests every month with over 250.000+ active service nodes. We would have never been able to achieve this without each and everyone of you! @@ -210,7 +210,7 @@ and past & current supporters (in alphabetical order) on Kennedy, Drozzy, Edwin Trejos, Howard Edidin, Ken Adler Oz Haven, Stefan Hans, TheCrealm. -\* Uses one of ORY's major projects in production. +\* Uses one of Ory's major projects in production. @@ -257,40 +257,40 @@ design: - Scales without effort - Minimize room for human and network errors -ORY's architecture designed to run best on a Container Orchestration Systems +Ory's architecture designed to run best on a Container Orchestration Systems such as Kubernetes, CloudFoundry, OpenShift, and similar projects. Binaries are small (5-15MB) and available for all popular processor types (ARM, AMD64, i386) and operating systems (FreeBSD, Linux, macOS, Windows) without system dependencies (Java, Node, Ruby, libxml, ...). -### ORY Kratos: Identity and User Infrastructure and Management +### Ory Kratos: Identity and User Infrastructure and Management -[ORY Kratos](https://github.com/ory/kratos) is an API-first Identity and User +[Ory Kratos](https://github.com/ory/kratos) is an API-first Identity and User Management system that is built according to [cloud architecture best practices](https://www.ory.sh/docs/next/ecosystem/software-architecture-philosophy). It implements core use cases that almost every software application needs to deal with: Self-service Login and Registration, Multi-Factor Authentication (MFA/2FA), Account Recovery and Verification, Profile and Account Management. -### ORY Hydra: OAuth2 & OpenID Connect Server +### Ory Hydra: OAuth2 & OpenID Connect Server -[ORY Hydra](https://github.com/ory/hydra) is an OpenID Certified™ OAuth2 and +[Ory Hydra](https://github.com/ory/hydra) is an OpenID Certified™ OAuth2 and OpenID Connect Provider which easily connects to any existing identity system by writing a tiny "bridge" application. Gives absolute control over user interface and user experience flows. -### ORY Oathkeeper: Identity & Access Proxy +### Ory Oathkeeper: Identity & Access Proxy -[ORY Oathkeeper](https://github.com/ory/oathkeeper) is a BeyondCorp/Zero Trust +[Ory Oathkeeper](https://github.com/ory/oathkeeper) is a BeyondCorp/Zero Trust Identity & Access Proxy (IAP) with configurable authentication, authorization, and request mutation rules for your web services: Authenticate JWT, Access Tokens, API Keys, mTLS; Check if the contained subject is allowed to perform the request; Encode resulting content into custom headers (`X-User-ID`), JSON Web Tokens and more! -### ORY Keto: Access Control Policies as a Server +### Ory Keto: Access Control Policies as a Server -[ORY Keto](https://github.com/ory/keto) is a policy decision point. It uses a +[Ory Keto](https://github.com/ory/keto) is a policy decision point. It uses a set of access control policies, similar to AWS IAM Policies, in order to determine whether a subject (user, application, service, car, ...) is authorized to perform a certain action on a resource.