Skip to content

Latest commit

 

History

History
17 lines (12 loc) · 1.93 KB

RFC_CREATION.md

File metadata and controls

17 lines (12 loc) · 1.93 KB
Raw

Creating an RFC

When creating an RFC, ensure that it meets these criteria:

  • Most changes, including small features, bug fixes and documentation improvements can be implemented and reviewed via the normal GitHub pull request workflow. Questions or discussions on more substantial changes should first be done on https://our.umbraco.com until further defined to the RFC format if one is deemed necessary.
  • The RFC should be a proposal, whether this is a technical proposal or an idea, it must propose an outcome.
  • All topics for the RFC based on the template must be known in advance of creating the RFC.

Instructions

  • Fork this repository
  • Copy {tempate-name} to /{product}/0000-my-feature.md (where 'my-feature' is descriptive) Don't assign an RFC number yet as this must match the number of the pull request that you will later submit. For example: /CMS/0000-dotnetCore.md
  • Fill in the RFC. Put care into the details ensuring to provide information. RFCs that do not present convincing motivation, demonstrate understanding of the impact of the design, or are disingenuous about the drawbacks or alternatives tend to be poorly-received.
  • Submit a pull request. As a pull request the RFC will receive design feedback from Umbraco HQ and the community, and the author should be prepared to revise it in response.
  • (optional) Now that you have submitted a pull request, you can now assign the RFC number in the filename and title. This must always match the PR number to make the PR easy to find after the RFC has been merged. It's OK to skip this as it can be done while the RFC is being merged.

Note: It is the responsibility of the RFC Author(s) to keep the RFC updated with any changes needed while the RFC is open so that readers of the RFC are always reading the most up-to-date version. Similarly the Author must make sure the RFC is up-to-date at the end of the RFC process when it is either accepted or closed.