Skip to content

Conversation

nyeatestest
Copy link
Contributor

@nyeatestest nyeatestest commented Feb 21, 2017

A formal review committee is setup within an org to "officiate" particular inner source projects with resources, etc. This pattern originates from Georg and Bosch.

Reviewers not yet on github:
Diogo Fregonese

Note that there is a copy file already in master - to be removed later - this is the one to live-on
@nyeates nyeates added Do 1st Review 3-validated Patterns proven in multiple cases with advanced requirements (Please see our contribution handbook) and removed 5 - Draft labels Mar 11, 2017
gruetter added 2 commits May 9, 2017 16:51
…after solution) based on feedback from PLoP shepherd
@gruetter
Copy link
Contributor

Hey @NewMexicoKid : I think this pattern is ready for review.

@gruetter
Copy link
Contributor

Hey @nyeates , @NewMexicoKid and @ErinMB : Since this pattern is in the PLoP paper, I feel we should go forward with the review and try to finalise it before the paper is actually published.

Nick Yeates added 2 commits August 31, 2017 12:48
Copy and pasted paragraphs over; found an error in overleaf where a bullet was copied twice and over wrote other data
@nyeates nyeates merged commit 1feea0d into master Aug 31, 2017
@nyeates nyeates deleted the pattern/review-committee branch August 31, 2017 17:15
@gruetter
Copy link
Contributor

gruetter commented Sep 1, 2017

Thanks for merging, @nyeates !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3-validated Patterns proven in multiple cases with advanced requirements (Please see our contribution handbook)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants