Skip to content

Conversation

@mhdawson
Copy link
Member

Document process for allowing members outside
of the build working group the access required to be able
to edit or run jobs associated with their working group.

Document process for allowing members outside
of the build working group the access required to be able
to edit or run jobs associated with their working group.
@mhdawson
Copy link
Member Author

@nodejs/build please take a look.
Supports: #526

gibfahn

This comment was marked as off-topic.

joaocgreis

This comment was marked as off-topic.

@mhdawson
Copy link
Member Author

mhdawson commented Dec 6, 2016

@jbergstroem, @gibfahn @joaocgreis updated based on comments so far. Let me know what you think.

gibfahn

This comment was marked as off-topic.

@mhdawson
Copy link
Member Author

mhdawson commented Dec 7, 2016

@gibfahn @jbergstroem second set of comments addressed.

gibfahn

This comment was marked as off-topic.

@mhdawson
Copy link
Member Author

mhdawson commented Dec 9, 2016

Addressed next set comments.

gibfahn

This comment was marked as off-topic.

@mhdawson
Copy link
Member Author

mhdawson commented Dec 9, 2016

Addressed new comments.

gibfahn

This comment was marked as off-topic.

@mhdawson
Copy link
Member Author

@jbergstroem can you review now that @gibfahn is happy with it.

jbergstroem

This comment was marked as off-topic.

jbergstroem

This comment was marked as off-topic.

@gibfahn
Copy link
Member

gibfahn commented Dec 13, 2016

@mhdawson After nodejs/security-wg#9 (comment), maybe we should s/workgroup/working group everywhere...

@mhdawson
Copy link
Member Author

mhdawson commented Dec 13, 2016

Ok addressed most of the remaining comments. @jbergstroem in respect to formatting to W80 is there an easy way to do that ? I've tried to stick under the 72 chars but evening out by hand would be a bit of work and I don't think it matters since when its viewed in markdown, markdown will handle making it look good.

gibfahn

This comment was marked as off-topic.

@jbergstroem
Copy link
Member

@mhdawson: 72 or 80 doesn't really matter. For me, the point of markdown is that its very readable rendered (github) and in your editor (vim, et al). A consistent line length is just generally easier to consume. Anyway, since we're down to bikeshedding I'm +1 regardless.

@gibfahn
Copy link
Member

gibfahn commented Jan 3, 2017

@nodejs/build would be really good to get this landed so people in teams can get access to jobs.

@mhdawson With two reviews I think if there are no objections this should be good to land, people can always PR improvements.

phillipj

This comment was marked as off-topic.

@phillipj
Copy link
Member

phillipj commented Jan 3, 2017

Other than a microscopic nit, this LGTM

jbergstroem

This comment was marked as off-topic.

@mhdawson
Copy link
Member Author

mhdawson commented Jan 3, 2017

Since there are 2 LGTMs now I'll plan to land tomorrow.

gibfahn pushed a commit that referenced this pull request Jan 4, 2017
Document process for allowing members outside
of the build working group the access required to be able
to edit or run jobs associated with their working group.

PR-URL: #554
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Reviewed-By: Phillip Johnsen <johphi@gmail.com>
@gibfahn
Copy link
Member

gibfahn commented Jan 4, 2017

Landed in 1fcbba2

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.

5 participants