Date: Fri, 29 Mar 2024 06:10:37 +0000 (UTC) Message-ID: <1633043052.35461.1711692637911@aws-us-west-2-lfedge-confluence-1.web.codeaurora.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_35460_2018513587.1711692637911" ------=_Part_35460_2018513587.1711692637911 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
"If you can't describe what you are doing as a process, you don't know w= hat you are doing."
- W. Edwards Deming
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 communit= y. The following steps will help you understand how we work together. Each = person wishing to join us should:
Our tool of choice for tracking work is GitHub, and this i= s where all of our code, artwork= , and documentation live. Tasks = to be worked on are created as GitHub issues, and you can view open issues in each repository to see what tasks are availabl= e to be worked on. Issues that are labelled "good first issue"= are most suitable for those learning how to contribute to an open source p= roject.
If you have noticed a problem or bug with the code, or problem with the = documentation, please create a new issue in t= he right repository. If you have a question about which repository to= use, feel free to ask on the #open-horizon-help chat room at https://chat.lfx.linuxfoundation.org/.
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 throug= h the requirements design process, and ultimately become supported.
If you have a thought or idea for something we should be working on, create a new discussion in our G= itHub project's Project Summary repo. T= his will allow you to specify as much about the idea as you can, and then a= llow others to give feedback and to flesh it out into something actionable.= If possible, add descriptive labels to your discussion topic.
If you would like to contribute a large amount of code, it should be sel= f-contained, complete, functioning, and compatible with the existing projec= t codebase. To begin the process, please reach out to the TSC Chair t= o discuss. Any persons involved in this contribution would ideally al= ready be active stakeholders in the project.
The high-level process for accepting the code is as follows:
TSC ... are these the correct s= teps, in the right order, and is anything missing?