Update feature proposal guidelines in documentation - #2478
Open
zhangyanzhao wants to merge 1 commit into
Open
Conversation
Clarified guidelines for proposing new features, including details on community leads assignment.
Collaborator
|
/azp run |
|
No pipelines are associated with this pull request. |
There was a problem hiding this comment.
Pull request overview
Updates the feature-proposal guidance in the SONiC documentation, adding clarification around community lead assignment for organizations proposing new features.
Changes:
- Adds guidance on assigning community leads and emailing GitHub IDs to the TSC mailing list.
- Touches the deferred/withdrawn status guidance line (currently unchanged text, but now part of the edited region).
|
|
||
| 1. For people who have NO edit permission to this project but want to contribute, please follow the “Call for participation” message, e.g Re: Call for participation for SONiC 202305 release (sonicfoundation.dev). <br> | ||
| 2. For people who can edit github project, if you want to propose a new feature from scratch, please follow below steps: <br> | ||
| 2. For people who can edit github project (Each company can assign up to two community leads. Please email the GitHub ID(s) of the assigned lead(s) to sonic-tsc@lists.sonicfoundation.dev using the subject: Community Leads Assignment from <Company Name>.), if you want to propose a new feature from scratch, please follow below steps: <br> |
| 4. After the HLD is reviewed in SONiC community, the feature should be moved to “In Progress” slot. Team should update the HLD based on the community feedbacks while working on the code PRs. Code PRs need be added to HLD PR by referring to Pull Request [EVPN VxLAN update for platforms using P2MP tunnel based L2 forwarding #806](https://github.com/sonic-net/SONiC/pull/806) | ||
| 5. Later, after all code PRs and HLD PR are merged, the feature should be moved to “Done” slot. | ||
| 6. If one feature need be deferred or withdrawn, the feature should be moved to “Deferred” slot (candidate for next release), or “Backlog” slot (candidate for future releases post next release). No newline at end of file | ||
| 6. If one feature need be deferred or withdrawn, the feature should be moved to “Deferred” slot (candidate for next release), or “Backlog” slot (candidate for future releases post next release). |
rck-innovium
approved these changes
Jul 27, 2026
rck-innovium
left a comment
rck-innovium
left a comment
Collaborator
There was a problem hiding this comment.
This aligns with what was agreed in the TSC. LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarified guidelines for proposing new features, including details on community leads assignment.