-
Notifications
You must be signed in to change notification settings - Fork 19
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
add Governance for the Standards Group #22
Conversation
# OpenJS Standards Group | ||
|
||
<!-- yet to add --> | ||
For the current list of Team members, see the project [README.md](./README.md). |
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.
should the list maybe be in a separate file, rather than the main readme?
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.
@ljharb across the node.js project and within this org we've maintained the list within the readme
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.
not a huge deal, but keeping a changing list in the readme makes it harder to look at git history for the prose in the readme ¯\_(ツ)_/¯
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.
Added some notes in line
Great first pass!
Is there something pending to do here? |
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.
Did another quick pass and have some suggestions. We should discuss this in a meeting before landing
Co-Authored-By: Myles Borins <myles.borins@gmail.com>
|
||
Pull requests require approval by at least two members and must remain open for at least 72 hours before being landed. If there are any objections the Pull Request cannot land until they are resolved. | ||
|
||
A pull request that is opposed will be discussed in the meeting. |
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 think this can be inferred from the above paragraph.... this is a tiny nit though
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.
LGTM. Great job @sendilkumarn!
I really think this is a great first version of this doc, thank you for doing this work @sendilkumarn. We did discuss it at the meeting yesterday, but of course want to make sure everyone has had a chance to see it an +1. For avoidance of doubt, can we get the @openjs-foundation/standards team & others to add their +1 / review approval? |
|
||
The Team meets bi-weekly on Zoom.us. A designated moderator | ||
approved by the Team runs the meeting. Each meeting should be | ||
published to YouTube. |
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.
If the streaming doesn't work for any reasons, should the meeting be postponed?
It happened to one node.js meeting and to be 100% transparency we did it so
The meeting can be recorded and posted afterwards
…On Tue, Sep 17, 2019, 5:15 PM Manuel Spigolon ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In GOVERNANCE.md
<#22 (comment)>
:
> +## Team Membership
+
+Team Membership is not time-limited. There is no fixed size of the Team.
+
+There is no specific set of requirements or qualifications for Team Membership beyond these rules.
+
+The following groups automatically qualify for membership and can request to be added to the GitHub team:
+
+* OpenJS Foundation CPC Members
+* OpenJS Foundation Project Maintainers
+
+## Team Meetings
+
+The Team meets bi-weekly on Zoom.us. A designated moderator
+approved by the Team runs the meeting. Each meeting should be
+published to YouTube.
If the streaming doesn't work for any reasons, should the meeting be
postponed?
It happened to one node.js meeting and to be 100% transparency we did it so
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22?email_source=notifications&email_token=AADZYVYB3ZJKL74CRPVTQ73QKFCGJA5CNFSM4ISAKW5KYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCFBDHDI#pullrequestreview-289551245>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADZYV3JKXG32CVWDTVOPQDQKFCGJANCNFSM4ISAKW5A>
.
|
r? @MylesBorins
Based on the discussion from #21 #19