CentOS Stream Feature Request SIG
SIG Status: Approved
1. Purpose
The purpose of this SIG will be to serve as a gate for feature requests that are first developed in CentOS Stream from contributors who wish to request these features to be included in future RHEL releases and are then filed in bugzilla. The SIGs overall goal is to make sure that features which have been filed and have technical merit are triaged internally to the correct venue for further review and development. The SIG will take ownership of regular bugzilla reviews filed under Stream and map feature requests from these bugzillas against the formal RHEL Feature Request criteria to identify and file qualifying requests inside Red Hat to achieve this.
2. Goals
Provide an entrypoint for features coming from external contributors to request features based on technical merit, developed and verified in CentOS Stream, to be filed as a feature request for the next RHEL release.
3. What's in Scope
- Weekly bugzilla triaging based on CentOS Stream filing
- Review potential feature requests against existing RHEL feature request criteria
- Engaging with external feature requesters to clarify and refine requirements if the feature meets the criteria
- Create a RHEL Feature request for the external requestor based on qualifying criteria in Jira
- Make jira ticket public to allow external requestor visibility on progress and provide feedback to development team
- Provide a feedback loop to feature requestor on ticket progress
Updates to documentation on CentOS Stream contributor guide to reflect this process & provide step by step guide for filing Features
4. Whats out of Scope
- Direct ownership of feature delivery once accepted in RHEL development
- TBD
5. Deliverables
- Provide a clear and accessible process for external contributors to engage in to file Feature requests for RHEL through CentOS Stream
- Provide a space for open and transparent decision making on Feature Requests for RHEL through the CentOS Stream project
Regular communication with the wider CentOS Project on status of requests - what has been rejected & why and what has been accepted and why
6. Administrative Duties
Meeting place, cadence, Time & Day
- IRC - #centos-stream
- Weekly, 1500 UTC+1 on Tuesdays
- Feature Filing
- Bugzilla is the first stop. Features need to be filed here with a note in ‘additional information’ that this is a proposed Feature Request for RHEL
- Feature candidates are mapped against RHEL Feature Request Criteria in a jira ticket under the following headers:
- Feature Description
- User Benefits
- Requirements
- Use Case/Proof of Concept/Partial Development demo
- The jira ticket is set to public and added to the CentOS Stream development board
- Features are linked to a Market Problem (where applicable)
- Request Tracking
- Bugzilla Update - original BZ should be updated with jira ticket link and a comment added if needed
- Jira ticket update - requester should be tagged in the ticket to allow them follow progress
- Communication
- Weekly email to centos-devel updating the project of BZs that have been picked up as feature requests
- Continuous updates to documentation on Stream outlining Feature Request process to external contributors
7. Proposed Initial Members
The following people are the proposed initial members of the SIG based on areas of expertise and value they can provide to developing this process. The membership of this SIG is subject to change and approval.
- Brian Stinson - CentOS Stream Architect
- Josh Boyer - RHEL Product Owner
- Rich Bowen - CentOS Community Architect
- Aoife Moloney - CentOS Stream Product Owner
- Kyle Walker - Product Experience, RHEL
- Brian Exelbierd - Community Business Owner, RHEL BU