-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template for proposing new WGs #71
base: master
Are you sure you want to change the base?
Conversation
reiterative
commented
Dec 8, 2021
- Based on the format used for OSEP and LFSCS
656e1cb
to
b7cfb44
Compare
The proposed format is fine with me. |
* Based on the format used for OSEP and LFSCS Signed-off-by: Paul Albertella <[email protected]>
b7cfb44
to
157918d
Compare
Removed rogue empty file - thanks @pahmann! |
Hi Paul. I would add a "Rationale" field where the proposer should add a quick summary of why a new WG is being proposed and if there is gap that the new WG fills. WDYT? |
Signed-off-by: Paul Albertella <[email protected]>
Added |
This PR marks failing "Travis CI" as code is marked for pyhton. This PR only include markdown, so there is no risk in merging it. The DCO check is properly passing. |
The proposed template is already used for the formation and request of new working groups. Recent examples are the systems WG and the Aerospace WG. These proposals miss the "Rationale" part. |
From: TSC meeting 30-Nov: Steve agrees on Rationale to be added to the template. (He embedded this in the proposal for the aerospace WG implicitly already) |