This section of the wiki is meant to communicate how the Open Horizon open-source software project (OH) accepts and handles submissions requesting new functionality. The process outlined below is intended to be complete and thorough but can always be improved. If there is a situation that this document does not cover, please bring it to the attention of a Technical Steering Committee (TSC) voting member along with a suggested resolution.
Definition of Terms
This document will use the term Feature to describe a cohesive and internally consistent collection of functionalities intended to accomplish one or more specific user outcomes (defined by Design Thinking as “Hills”). The intent of the Feature Request process is to allow anyone to propose their ideas for OH Features and to clearly communicate at least the minimum amount of information required to successfully present and evaluate the submission.
This document will use the term Feature scope, or scope, to refer to the appropriate organizational group that will have authority over a particular Feature submission. Some Feature Candidates may clearly fall within the jurisdiction of a single Working Group (WG). Others may have cross-group impacts, or even affect all WGs, and thus fall under the oversight of the TSC. The intent of this process is to properly identify the scope, and the relevant decision-maker for that scope, before the proposed Feature is deemed ready for presentation to the appropriate audience.
This document will use the term Sponsor User, or Sponsors, to refer to an individual or organization that has a vested interest in the user outcomes of the proposed Feature Candidate. The author of the submission may also be the Sponsor User.