[New Process Improvement Need]: Triaging Change Requests
Open
@riverma is already working on this.
Since Jan 9, 2024.
governance
medium complexity
most requested
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Category
Information Sharing - documentation design, templates, communication, etc.
Describe the need
We have a need for better guidance / standards for:
- Triaging Strategy for New Issue Tickets (+1'd by @kgrimes2)
- Governance approach for acceptance / rejection of proposed software changes
- Dynamic change-management process (make it quick to decide on swapping out or adding a new A&A system, etc.)
- Governance approach for vetting and integrating outside contributions to open source projects (+1'd by @ngachung)
- Governance approach for handling feature requests and community-based decision making.
- Governance approach for creating / modifying core software documentation
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.