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.

Sign up for GitHub

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

Jump to bottom

Clarify Contributor workbook question #446

Merged
merged 1 commit into from
Sep 6, 2021
Merged

Clarify Contributor workbook question #446

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
13 changes: 7 additions & 6 deletions workbook/04-contributor.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,18 +30,19 @@ Why 4 is correct: Contributions go beyond just code. There are many aspects that

===== Question 2. What is a productive assumption for a contributor to make when joining an InnerSource project?

. I need to make sure to communicate my intent when adding or changing the project.
. I need to make sure my code serves the hosting teams goals.
. If the hosting team is in a bind to meet their deadlines, I have to spend time to code for them.
. Needs that are shared across the business are good candidates for InnerSource.
. My project will move the fastest if I have as few dependencies as possible.
. The hosting team will implement the features that I need.
. I should work only on features needed by my team.

====== Correct answer: 1

Why 1 is correct: If your contribution isn’t understood by the host team or the community at large, then they may reverse your hard work or make other changes that weaken the value of your contribution. Open and early communication with the community and the hosting team will help you to drive successful contributions.
Why 1 is correct: When many teams across the business have the same need, an InnerSource project is a great way to meet those needs at scale without duplicated work.

Why 2 is incorrect: You should make sure that your goals do not conflict with those of the hosting team, but beyond that you can still promote your own team’s goals.
Why 2 is incorrect: If you skip the chance to leverage code that is already written, you will waste time coding solutions to problems that are already solved rather than adding unique value in your team.

Why 3 is incorrect: Your work on another team’s project reflects your own team’s needs, but you are not working for the other team. If the hosting team (or any community participant) is in a bind, you and your management might offer help as a gesture to benefit the whole company., However, it is not your task to make up for the time or staffing shortcomings at the hosting team.
Why 3 is incorrect: You can ask, but there may be times where the next need that you have in the project is not the next priority for the host team to work on.
In these cases you can still get what you need by making an InnerSource contribution to the project.

Why 4 is incorrect: Working on other features of a project, or doing background work such as reorganizing code or documentation, may indirectly contribute to your team’s success, so it is legitimate for you to invest time on those things.

Expand Down