Skip to content

Commit

Permalink
[RFC] Add ECS team's role in finding a sponsor (elastic#1664)
Browse files Browse the repository at this point in the history
* Clarify that ECS team can help community users identify an internal sponsor

* also list under ECS team responsibilities
  • Loading branch information
ebeahan authored Nov 15, 2021
1 parent 9b703b9 commit ad013d4
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion rfcs/PROCESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Each RFC is represented as a markdown document following a prescribed template t

If proposing new fields or changing existing fields, the RFC should also have a corresponding folder (named after the RFC number) in [rfcs/text/](./text/). The folder should contain the proposed schema changes as standalone YAML files or extended example mappings and larger source documents.

Generally speaking, the ECS team will help steward the process, but the work of researching and iterating on aspects of an RFC will be owned by that RFC's contributor. If an RFC is being contributed by a community member, then someone at Elastic will need to act as a sponsor of the change to act as a long term owner after completion of the process. If it's not obvious who such a sponsor might be, then the ECS committee will assign a sponsor.
Generally speaking, the ECS team will help steward the process, but the work of researching and iterating on aspects of an RFC will be owned by that RFC's contributor. If an RFC is being contributed by a community member, then someone at Elastic will need to act as a sponsor of the change to act as a long term owner after completion of the process. The ECS team can help community users with identifying an internal sponsor. If it's not obvious who such a sponsor might be, then the ECS committee will assign a sponsor.

## Key questions we seek to answer through RFC process

Expand Down Expand Up @@ -37,6 +37,7 @@ The **ECS team**:
* curates the overall RFC process, including closing stalled or abandoned RFCs
* reports on the status of open RFCs
* acts on behalf of the committee for some but not all PRs
* helps community users identify a sponsor at Elastic

The **contributor**:
* takes responsibility for doing all necessary legwork to move their RFC forward including but not limited to responding to feedback, identifying and bringing in subject matter experts, and researching the scope of impact
Expand Down

0 comments on commit ad013d4

Please sign in to comment.