This project aims to governed in a transparent, accessible way for the benefit of the community. All participation in this project is open and not bound to corporate affiliation. Participants all our bound the project's Code of Conduct.
The contributor role is the starting role for anyone participating in the project and wishing to contribute training materials (e.g. PowerPoint slides, Jupyter notebooks containg Python code and other documentation).
- Review the CONTRIBUTING.md guidelines to ensure your contribution is inline with the project's coding, styling and other guidelines.
- Submit your training materials as a Pull Request (PR) with the appropriate Developer Certificate of Origin (DCO) signoff.
- Have you submission approved by the maintainer(s) and merged into the codebase.
The committer role enables the participation to commit training materials directly to the repository, but also comes with the responsibility of being a responsible leader in the community.
- Show your experience with the training materials through contributions and engagement on the community channels.
- Request to become a committer.
- Have the majority of committers approve you becoming a committer.
- Your name and email is added to the COMMITTERS.csv file for the project.
- Monitor email aliases.
- Monitor Slack (delayed response is perfectly acceptable).
- Triage GitHub issues and perform pull request reviews for other maintainers and the community.
- Make sure that ongoing PRs are moving forward at the right pace or closing them.
- In general continue to be willing to spend at least 10% of ones time working on the project (~4 business hours per week).
If a committer is no longer interested or cannot perform the committer duties listed above, they should volunteer to be moved to emeritus status. In extreme cases this can also occur by a vote of the committers per the voting process below.
The TSC will consist of committers that will provide overall direction and leadership to the project. The TSC will elect a chairperson ( and optionally a co-chairperson ) which will be the primary point of contact for the project and representative to the ODPi TSC. The chairperson will be responsible for the overall project health and direction, coordination of activities, and working with other projects and committees as needed for the continued growth of the project. New TSC members can be added with a supermajority vote of the current TSC members.
Current TSC members are:
- Andre de Waal ( chairperson )
- Susan Davidson
- Zack Ives
- Ana Echeverri
- James Harroun
- Goutam Chakraborty
- Jennifer Priestley
- Aric LaBarr
- David Mongeau
Project releases will occur on a scheduled basis as agreed to by the maintainers.
In general, we prefer that technical issues and maintainer membership are amicably worked out between the persons involved. If a dispute cannot be decided independently, the maintainers can be called in to decide an issue. If the maintainers themselves cannot decide an issue, the issue will be resolved by voting. The voting process is a simple majority in which each maintainer receives one vote.
This project, just like all of open source, is a global community. In addition to the Code of Conduct, this project will:
- Keep all communication on open channels ( mailing list, forums, chat ).
- Be respectful of time and language differences between community members ( such as scheduling meetings, email/issue responsiveness, etc ).
- Ensure tools are able to be used by community members regardless of their region.
If you have concerns about communication challenges for this project, please contact the maintainers.