-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update README.md #3
Conversation
Proposed changes for the README.md template
Should we also update the template when creating the mailing list to be the repo name instead of the short name? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't put the last release into the scope section. Better create a new section like we've already done this in several Sub Projects.
As soon as this PR is merged into the repo template we also have to make sure that all existing repos (readme files) are updated to the same structure, and also all the website pages.
We need to think about if we want to have a mailing per API Sub Project or in same cases would have one mailing list per API Working Group (e.g. if we split EdgeCloud in multiple API Sub Projects). |
Moved latest release section Added clearer instructions
Updated mailing list instructions from "all contributors" to "the community" Co-authored-by: Herbert Damker <52109189+hdamker@users.noreply.github.com>
Changed release tracking to CHANGELOG
Update release section Co-authored-by: Herbert Damker <52109189+hdamker@users.noreply.github.com>
Changed release section
Proposed changes for the README.md template