This repository has been archived by the owner on Jan 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 42
SEPherding
Wayne Werner edited this page Jan 27, 2020
·
3 revisions
To keep our Salt Enhancement Proposals moving along, we need to "SEPherd" them. There are a couple of steps to take when a new SEP comes in:
- Go to the list and add another row, with N+1 and a link to the SEP. The status should be set to Draft initially.
- Reply to the SEP author, giving them the # of the SEP, as well as editing
SEP <N> -
into the title of the PR. - The author should update their SEP file with the link to their PR - maybe just use
[SEP <N>](https://....)
so it shows up as a fancy link when rendered with Markddown. - SEPs should be read/digested and then added to Core team discussion agenda.
- Check the SEP list regularly and make sure that the statuses reflect the actual SEP status, and the labels are also up to date.
- When a SEP is merged it should be merged with either
Accepted
orAbandoned
. - When a SEP is closed it should be closed with
Rejected
orWithdrawn
.
- When a SEP is merged it should be merged with either
- When SEPs are merged in, ensure that the status gets updated, they're put in the right folder, etc.