-
Notifications
You must be signed in to change notification settings - Fork 166
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
Let there be governance #49
Conversation
### Collaborators | ||
|
||
The [iojs/build](https://github.com/iojs/build), | ||
[iojs/docker-iojs](https://github.com/iojs/docker-iojs), and the |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
for commit-access log an issue or contact a WG member directly and it | ||
will be brought up in the next WG meeting. | ||
|
||
Modifications of the contents of the iojs/website repository are made on |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
removed reference to iojs/website
this WG are made on a collaborative basis. Anybody with a GitHub account | ||
may propose a modification via pull request and it will be considered by | ||
the project Collaborators. All pull requests must be reviewed and | ||
accpeted by a ollaborator with sufficient expertise who is able to take |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
When we merge this @wblankenship we need to add a section that addresses #39. |
Do we have any outstanding issues that needs to be addressed? I think this is in good enough shape to merge regardless of potential open questions since it'd be better to have this living in our repo than not. We could always address them in a forthcoming PR. |
I think this is ready for prime time 👍 Still need to work out the sub-WG clause, but I agree that it can wait. |
LGTM |
Pretty sure @rvagg wanted to have a pass at this before we merged. |
Can we apply the tag |
done |
For consensus, we need a 👍 to merge from: Barring any changes to the 👍s we have already received. |
👍 |
LGTM |
This fell off my radar during finals week. I seriously dropped the ball on it. We do need to get a governance doc merged in. Should I update this with the latest version from https://github.com/nodejs/io.js/blob/master/WORKING_GROUPS.md#bootstrap-governance |
Yes, maybe ping the group for a few +1's before merging the new one |
Conflicts: README.md
@nodejs/build Updated to latest. Ready to merge if everything looks good. |
I'm still participating! Probably more so in the future than in the past! |
@othiym23 sweet! 😃 I'll merge tomorrow evening if nobody has any objections |
@@ -109,3 +109,4 @@ People | |||
* Johan Bergström [@jbergstroem](https://github.com/jbergstroem) | |||
* Ken Perkins [@kenperkins](https://github.com/kenperkins) | |||
* Wyatt Preul [@geek](https://github.com/geek) | |||
* Forrest L Norvell [@othiym23](https://github.com/othiym23) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
@wblankenship ping, don't forget this one |
Action item from the first WG meeting.
For the full recorded meeting, checkout: https://www.youtube.com/watch?v=OKQi3pTF7fs