Skip to content
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/get-contributions-despite-silo-thinking #38

Closed

Conversation

gruetter
Copy link
Contributor

@gruetter gruetter commented Feb 8, 2017

In hierarchical and silo-organized organizations, getting voluntary contributions in InnerSource projects can be challenging. It is crucial to create mechanisms to incentivize managers to foster voluntary contributions.

Hey everyone. Here's a new donut from the Bosch guys. Have at it ;)

Clarified problem statement, added new possible solution (used at Red
Hat)
Removed “donut” from front of file name to be consistent with file
names in root directory
Copy link
Contributor

@nyeates nyeates left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved after editing formatting/grammar and adding an additional solution

@nyeates nyeates changed the title Feature/donut get contributions despite silo thinking pattern/get-contributions-despite-silo-thinking Feb 21, 2017
@nyeates nyeates added Pattern and removed 5 - Draft labels Mar 11, 2017
@nyeates nyeates added 2-structured Patterns with existing instances (Please see our contribution handbook for details) and removed 2 - Needs Revision labels Mar 12, 2017
@dmittman
Copy link

First time commenter on these patterns. I've observed that although the title of this pattern seems to be "Incentive mechanisms to foster voluntary contribution" (differs from the filename, but that's a different matter), the gist of the pattern seems to be finding ways to recast the contribution effort as something other than voluntary. That is, not that the contribution is "compulsory," but that the contribution is a part of the InnerSource participant's compensation. I've done some thinking about the differences between Open Source volunteerism (where an individual is contributing to an Open Source project on their own, uncompensated time), versus InnerSource where, as an employee of a company, labor laws often prohibit you from "volunteering" your time. Is there a way to remove the word "volunteer" from InnerSource? I believe that the idea that we're "volunteering" on an InnerSource project is what sets some project managers against the idea of InnerSource.

@rrrutledge
Copy link
Contributor

rrrutledge commented Oct 18, 2017

Thanks for commenting, @dmittman . I like that point.

@maxcapraro maxcapraro added the Stale We mark issues as stale after 90 days of inactivity. This does not make any judgement about value. label Apr 21, 2020
@spier
Copy link
Member

spier commented Jul 28, 2020

We have reworked the different maturity levels of our patterns. Based on that, Donuts should be able to be merged into master much faster.

Given that this is only a Donut (i.e. no solution yet), I would suggest to rebase this branch on master, move the file to folder patterns/1-initial and close this PR.

Any objections @gruetter?

@spier spier added the 📖 Type - Content Work Working on contents is the main focus of this issue / PR label Dec 26, 2020
spier added a commit that referenced this pull request Dec 26, 2020
…the Donut pattern directly, rather than to the PR.

Also adapted pattern slightly to fit the current Pattern template better.
@spier
Copy link
Member

spier commented Dec 26, 2020

Trying to get this branch into a mergeable shape turned out to be hard, as it is so old.

Therefore I cherrry-picked just the Donut file, and included it in #254 so that it can get into the mainline soon.

Closing this PR here as we don't need it any more.

@spier spier closed this Dec 26, 2020
@spier spier deleted the feature/donut-get-contributions-despite-silo-thinking branch December 26, 2020 11:03
spier added a commit that referenced this pull request Jan 8, 2021
* Remove the extra group "Reviewed Pattern Ideas (not yet proven but reviewed)".
Also adapt status in the patterns accordingly.

Rational: 
by definition the 1-Initial patterns don't have a Known Instance yet, i.e. they are not proven. Therefore we don't need an extra group to state this.

* Move all patterns that have a patlet already out of the extra group "Pattern Ideas (not yet proven; brainstormed)".
Those pattern are similar in quality to the ones that we already list in "### Maturity Level 1: Initial", so they don't have to be in an extra group.

* Move remaining patterns from sub-group "Pattern Ideas (not yet proven; brainstormed)" to "Maturity Level 1: Initial".
Also updating the Status in the patterens themselves.

Rational:
* These patterns were not all that different from the ones directl in "Maturity Level 1: Initial".
* Often times they don't have a solution yet, or just a brainstormed solution.
* Many of them don't have a Patlet, likely because they were written at a time when the Pattern Template didn't ask for that yet

* update links to point to files, rather than to PRs

* port the  Donut pattern from old PR #38 into this, so that we can link to the Donut pattern directly, rather than to the PR. Also adapted pattern slightly to fit the current Pattern template better.

* various other smaller fixes

Co-authored-by: Georg Grütter <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2-structured Patterns with existing instances (Please see our contribution handbook for details) 📖 Type - Content Work Working on contents is the main focus of this issue / PR Stale We mark issues as stale after 90 days of inactivity. This does not make any judgement about value.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants