-
Notifications
You must be signed in to change notification settings - Fork 191
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
pattern/not-invented-here #64
Conversation
From 2017-03-16 webinar
Revised, filled in gaps and cleaned up text.
Team will review & resolve further
deleted donut file
team review, revisions & notes - Nov 2nd meeting
… mostly through formatting. Some spelling fixes
…mons/InnerSourcePatterns into pattern/not-invented-here
This pattern seems to have been created at one of the early ISC Summits as well, as it contains many notes from conversations that seem to have happened in-person. To get this pattern into a mergeable state, one would have to remove those notes and rework the content such that it becomes understandable for anybody interested in the Not-Invented-Here Mindset in the context of InnerSource. |
I changed my mind on this PR. The pattern is certainly in an early draft state e.g. it contains many notes that might have been written at an ISC Summit where this draft was ideated. However I still think that this draft would create more value if we merge it into main, as that makes it more likely for readers to find it. |
… appropriate place 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.
Approving this PR on the premise that:
a) the PR is so old that it is unlikely that the original authors will still work on it and
b) it is better to have a half-finished pattern draft in the main branch, than in a PR, as readers are more likely to find it in the main branch
Perfectly good solutions are being rejected because of Not Invented Here. Engineers and their managers will choose to implement functionality themselves first, even if an alternative exists.