From ed36bffd6d45b9287fb052f50d656b134c169d4d Mon Sep 17 00:00:00 2001 From: rrrutledge Date: Mon, 12 Aug 2019 13:54:40 -0700 Subject: [PATCH 1/2] Rewrite introductory paragraphs To appeal to an individual who just cares about making progress on their project. --- contributor/01-introduction-article.md | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-) diff --git a/contributor/01-introduction-article.md b/contributor/01-introduction-article.md index 819186e7..125bf58c 100644 --- a/contributor/01-introduction-article.md +++ b/contributor/01-introduction-article.md @@ -23,15 +23,12 @@ How do I best contribute to an InnerSource project? This segment shares a summa ## The Contributor in InnerSource. -Without contributions, an InnerSource community and its project(s) would not exist in a meaningful way. -There would be open repositories, ideally equipped with somewhat specific extra documents (e.g. a CONTRIBUTING.md and a README.md) and person(s) committing to them, e.g. a Trusted Committer. -[EDITOR NOTE: -- In other articles we draw a distinction between guest and host team. -- We argue that the Committer is part of the guest team and needs to fit in with the host team. -- In a more-than-one-person project what do we call the people aside of the TC/PO that are members of the host team? Just team members? - - OSS would likely not make this distinction and everyone would end up as contributor until it's committer / trusted committer at some point I guess? - - In the ASF-Rule-set this would be the distinction between Developer and Committer. -] +Have you ever been blocked in your next coding task because another team didn't have time to add a feature in their system that you depend on? +Perhaps after a while you even had to do some extra work in your project to work around the missing feature. +How nice would it be to never be blocked in this way? + +With projects that run via InnerSource, you'll never be blocked waiting for another team to deliver some needed feature. +If you're not getting what you need you can make the change you need directly in the other team's code repository by acting as an InnerSource Contributor. The Contributor role describes a person that makes contributions to an InnerSource community. A contribution can be a code or non-code artifact such as a bug-report, an addition to documentation or a feature request. From 9df1cd92e180d45eff86580963837120ccf56992 Mon Sep 17 00:00:00 2001 From: rrrutledge Date: Mon, 19 Aug 2019 14:27:14 -0700 Subject: [PATCH 2/2] run via InnerSource -> incorporate InnerSource principles --- contributor/01-introduction-article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributor/01-introduction-article.md b/contributor/01-introduction-article.md index 125bf58c..498f22b3 100644 --- a/contributor/01-introduction-article.md +++ b/contributor/01-introduction-article.md @@ -27,7 +27,7 @@ Have you ever been blocked in your next coding task because another team didn't Perhaps after a while you even had to do some extra work in your project to work around the missing feature. How nice would it be to never be blocked in this way? -With projects that run via InnerSource, you'll never be blocked waiting for another team to deliver some needed feature. +With projects that incorporate InnerSource principles, you'll never be blocked waiting for another team to deliver some needed feature. If you're not getting what you need you can make the change you need directly in the other team's code repository by acting as an InnerSource Contributor. The Contributor role describes a person that makes contributions to an InnerSource community.