...
- v0.1 - Joseph Pearson, initial creation
- v0.2 - Joseph Pearson, pointed to developer documentation site
- v0.3 - Joseph Pearson, added Feature Request Lifecycle section
Introduction
This is a living document, intended to be updated periodically as needed by a majority of the TSC or designees as specified.
...
Thank you for expressing an interest in learning more about our community. The following steps will help you understand how we work together. Each person wishing to join us should:
- Read and understand:
- Read the Developer Certificate of Origin and sign all commits (per Technical Charter, section 7.b.ii).
- For step-by-step instructions, visit the Common Requests section of the documentation to find:
- How to contribute to the project
- How to get technical support
...
If you'd like to propose a new product feature read about our Feature Request Lifecycle processes. These processes will show you how requests move from Feature Candidate through the requirements design process, and ultimately become supported.
Submitting ideas
If you have a thought or idea for something we should be working on, create a new discussion in our GitHub project's Project Summary repo. This will allow you to specify as much about the idea as you can, and then allow others to give feedback and to flesh it out into something actionable. If possible, add descriptive labels to your discussion topic.
...
- Notify TSC Chair
- Complete discussions with a successful outcome, including identifying what Working Group the product would fall under, and if this contribution is tied to a TSC voting seat.
- Have a name for the code contribution (hereinafter, product)
- Have or create a GitHub project for the product containing at least one repository with the code and a compatible license (Apache 2, MPL 2, MIT, etc.)
- Successfully complete code acceptance process (license scanning, etc., code quality including test coverage, documentation/tutorials/training, and so on)
- TSC vote to accept the code contribution and related obligations agreed to in the second step above, if any.
- Notify LF Edge GM, Marketing, LF new projects team as a courtesy
- Transfer "ownership" of GitHub project to LFX DevOps team and implement LF automation (DCO checks, etc.)
- Implement Open Horizon repo best practices (CONTRIBUTING, MAINTAINERS, etc.)
...