Skip to content
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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

reiterative
Copy link

  • Based on the format used for OSEP and LFSCS

@reiterative reiterative force-pushed the reiterative/new-wg-template branch from 656e1cb to b7cfb44 Compare December 8, 2021 13:41
@pahmann
Copy link

pahmann commented Dec 8, 2021

The proposed format is fine with me.
I wonder why there is an empty file called "process" in this PR.

* Based on the format used for OSEP and LFSCS

Signed-off-by: Paul Albertella <[email protected]>
@reiterative reiterative force-pushed the reiterative/new-wg-template branch from b7cfb44 to 157918d Compare December 9, 2021 08:37
@reiterative
Copy link
Author

Removed rogue empty file - thanks @pahmann!

@paolonig
Copy link

paolonig commented Dec 9, 2021

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]>
@reiterative
Copy link
Author

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?

Added

@pahmann
Copy link

pahmann commented Nov 4, 2022

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.

@pahmann
Copy link

pahmann commented Nov 4, 2022

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.
Feedback on the PR was requested via mailing list: https://lists.elisa.tech/g/devel/message/1976

@pahmann
Copy link

pahmann commented Nov 30, 2022

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants