Skip to content

Commit c7ef2e9

Browse files
nashifkartben
authored andcommitted
doc: contribute: consolidate proposal docs
Remove duplicate section about making proposals. Signed-off-by: Anas Nashif <[email protected]>
1 parent b1043de commit c7ef2e9

File tree

2 files changed

+15
-25
lines changed

2 files changed

+15
-25
lines changed

doc/contribute/guidelines.rst

Lines changed: 0 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -836,30 +836,6 @@ attention needed and it will be ready for merge sooner than later:
836836
sure you click the "Re-request review" button on the GitHub UI to notify
837837
those who asked for the changes
838838

839-
840-
Submitting Proposals
841-
====================
842-
843-
You can request a new feature or submit a proposal by submitting an issue to
844-
our GitHub Repository.
845-
If you would like to implement a new feature, please submit an issue with a
846-
proposal (RFC) for your work first, to be sure that we can use it. Please
847-
consider what kind of change it is:
848-
849-
* For a Major Feature, first open an issue and outline your proposal so that it
850-
can be discussed. This will also allow us to better coordinate our efforts,
851-
prevent duplication of work, and help you to craft the change so that it is
852-
successfully accepted into the project. Providing the following information
853-
will increase the chances of your issue being dealt with quickly:
854-
855-
* Overview of the Proposal
856-
* Motivation for or Use Case
857-
* Design Details
858-
* Alternatives
859-
* Test Strategy
860-
861-
* Small Features can be crafted and directly submitted as a Pull Request.
862-
863839
Identifying Contribution Origin
864840
===============================
865841

doc/contribute/proposals_and_rfcs.rst

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,8 +33,22 @@ feature as it is being designed, and incorporate important constraints into the
3333
design while it's easier to change, before the design has been fully
3434
implemented.
3535

36-
Some changes do not require an RFC:
36+
For a Major Feature, first open an issue and outline your proposal so that it
37+
can be discussed. This will also allow us to better coordinate our efforts,
38+
prevent duplication of work, and help you to craft the change so that it is
39+
successfully accepted into the project. Providing the following information
40+
will increase the chances of your issue being dealt with quickly:
3741

42+
* Overview of the Proposal
43+
* Motivation for or Use Case
44+
* Design Details
45+
* Alternatives
46+
* Test Strategy
47+
48+
Some changes or contributions do not require an RFC, the rationale and details
49+
of the changes should however be part of the pull-request:
50+
51+
- Small enhancements and modifications to existing and established subsystems.
3852
- Rephrasing, reorganizing or refactoring
3953
- Addition or removal of warnings
4054
- Addition of new boards, SoCs or drivers to existing subsystems

0 commit comments

Comments
 (0)