All contributions to the Python JwtConnect packages are welcome!
Note that as this library is planned to be used in high-profile production code, we insist on a very high standards for the code and design, but don't feel shy: discuss your plans over GitHub Issues and the mailing list, and send in those pull requests!
In order to contribute to this project, you need to execute two legal agreements that cover your contributions. Pull requests from users who have not signed these agreements will not be merged.
- Visit http://openid.net/contribution-license-agreement/
- Tap Execute OpenID Foundation Contribution License Agreement for the version relevant to you (Individual or Corporate).
- Follow the instructions to sign the agreement.
In addition to the Code License Agreement, the OpenID Foundation also requires a working group contribution agreement to cover any contributions you may make towards the OpenID Connect spec itself (e.g. in comments, bug reports, feature requests).
- Visit http://openid.net/intellectual-property/
- Tap Execute Contributor Agreement By Electronic Signature in the box marked Resources.
- Follow the instructions to sign the document, state
OpenID AB/Connectas the Initial Working Group.
Before you work on a big new feature, get in touch to make sure that your work is inline with the direction of the project and get input on your architecture. You can file an Issue discussing your proposal, or email the list.
The JWTCOnnect-Python-OidcMsg library follows the PEP8 coding style for Python implementations. Please review your own code for adherence to the standard.
All pull requests, even by members who have repository write access need to be reviewed and marked as "LGTM" before they will be merged.