First draft for the Introductory Contributor Section Article #67 by lenucksi · Pull Request #98 · InnerSourceCommons/InnerSourceLearningPath

lenucksi · 2019-07-24T15:20:24Z

Content

This is an initial draft for the "The Contributor in InnerSource" article based upon the outline and video proposal document.
Feedback, Change proposals either using the GitHub change feature or as pushes to the branch for larger changes (hence the direct push to this repo) are more than welcome.

Technical detail

I've included headers from the outline document and video proposal for drafting purposes. Once they document is ready, those should obviously disappear.
The referenced articles currently have no URL yet, thus the link fields are currently left blank. They need to be replaced once they are ready. An initial approach could be to link the GitHub articles.

lenucksi · 2019-07-25T10:01:43Z

+- 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.


This distinction is taken from https://www.apache.org/foundation/how-it-works.html#developers

rrrutledge · 2019-08-06T16:09:04Z

Thanks for this pull request, @lenucksi. I think that I'll be able to have a look before this week's call for the learning path.

rrrutledge · 2019-08-08T21:35:22Z

An initial approach could be to link the GitHub articles.

Yes we should do this

rrrutledge

Thanks so much for doing this article @lenucksi. I like the way that you speak with a strong, friendly, guiding voice to the reader.

Left a few comments. Also, suggest shorter headings.

rrrutledge · 2019-08-08T21:38:54Z

+[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?


I think that something like host team members is fine. Is this concept used somewhere in this article?

We're using that concept implicitly in lines 41,42 and explicitly in line 55.
Also, we're announcing to use the concept extensively in line 85.

And since home/guest might establish a mental concept of separation (us/them) I think that we should give that a aspect a consideration to see if and how we want to deal with it throughout the content.
This could enhance clarity and prevent contradictory information later on. (Me being a nitpick and definition pedant here ;))

I've suggested the Apache source below since that gives an example for this

I think in a corporate context we assume that division is already built in by the organization. We want to bring it together and suggest the terminology of Host/Guest to encourage people to give warm welcome and collaboration to each other.

Sounds good to me.
So we're using host team member for a person that is part of the host team but no trusted committer (yet) then?

Yes, I think so.

lenucksi

Addressed your review comments.

lenucksi · 2019-08-11T11:27:09Z

+[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?


We're using that concept implicitly in lines 41,42 and explicitly in line 55.
Also, we're announcing to use the concept extensively in line 85.

And since home/guest might establish a mental concept of separation (us/them) I think that we should give that a aspect a consideration to see if and how we want to deal with it throughout the content.
This could enhance clarity and prevent contradictory information later on. (Me being a nitpick and definition pedant here ;))

I've suggested the Apache source below since that gives an example for this

lenucksi

Left a few comments. Also, suggest shorter headings.

The titles are actually taken verbatim from the outline. I'm happy for suggestions to shorten them - and maybe I'll come up with something shorter myself.

rrrutledge · 2019-08-12T19:59:52Z

I'm happy for suggestions

Left in #110.

To appeal to an individual who just cares about making progress on their project.

Avoid explicitly bringing up contributions outside of repo contents.

rrrutledge

Responded to all comments.

rrrutledge · 2019-08-12T22:17:11Z

+[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?


I think in a corporate context we assume that division is already built in by the organization. We want to bring it together and suggest the terminology of Host/Guest to encourage people to give warm welcome and collaboration to each other.

…ion-defition Rephrase contributor definition

…ion-headings Heading suggestions

rrrutledge

Almost done!

rrrutledge · 2019-08-19T21:27:50Z

+[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?


Yes, I think so.

…ion-persona Rewrite introductory paragraphs

rrrutledge

Looks good to me. We can revisit the EDITOR NOTE later.

lenucksi · 2019-08-27T09:33:44Z

Looks good to me. We can revisit the EDITOR NOTE later.

Thanks, I'd say we put this up for merge discussion on the next call.
I'd think the EDITOR NOTE was dealt with the term host team member according to this.
What do the others think?

(And we can still add new PRs on top of this later.)

rrrutledge · 2019-08-27T16:03:44Z

I'd say we put this up for merge discussion on the next call.

🆗

rrrutledge · 2019-09-03T13:05:54Z

@lenucksi we forgot on the call to discuss this article, specifically, if it can be merged. If you think so then go ahead.

First draft for the Introductory Contributor Section Article #67

dc8a67f

lenucksi added the Contributor label Jul 24, 2019

lenucksi commented Jul 25, 2019

View reviewed changes

lenucksi requested a review from rrrutledge August 6, 2019 18:32

rrrutledge requested changes Aug 8, 2019

View reviewed changes

Typos

2d43df4

lenucksi commented Aug 11, 2019

View reviewed changes

Heading suggestions

1b6fb59

rrrutledge mentioned this pull request Aug 12, 2019

Heading suggestions #110

Merged

rrrutledge added 2 commits August 12, 2019 13:54

Rewrite introductory paragraphs

ed36bff

To appeal to an individual who just cares about making progress on their project.

Rephrase contributor definition

7313400

Avoid explicitly bringing up contributions outside of repo contents.

rrrutledge reviewed Aug 12, 2019

View reviewed changes

lenucksi added 2 commits August 15, 2019 14:35

Merge pull request #112 from InnerSourceCommons/contributor/introduct…

b55b384

…ion-defition Rephrase contributor definition

Merge pull request #110 from InnerSourceCommons/contributor/introduct…

2779779

…ion-headings Heading suggestions

lenucksi added the Article label Aug 15, 2019

run via InnerSource -> incorporate InnerSource principles

9df1cd9

rrrutledge reviewed Aug 19, 2019

View reviewed changes

Merge pull request #111 from InnerSourceCommons/contributor/introduct…

cb0b317

…ion-persona Rewrite introductory paragraphs

rrrutledge mentioned this pull request Aug 26, 2019

Article: The Contributor in InnerSource #67

Closed

rrrutledge approved these changes Aug 27, 2019

View reviewed changes

rrrutledge merged commit 3281d93 into master Sep 12, 2019

rrrutledge deleted the contributor/introduction branch September 12, 2019 15:47

marshmallowrobot mentioned this pull request Aug 8, 2023

Website build is failing #575

Open

Conversation

lenucksi commented Jul 24, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Content

Technical detail

Uh oh!

Choose a reason for hiding this comment

Uh oh!

rrrutledge commented Aug 6, 2019

Uh oh!

rrrutledge commented Aug 8, 2019 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

rrrutledge left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

lenucksi left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

lenucksi left a comment

Choose a reason for hiding this comment

Uh oh!

rrrutledge commented Aug 12, 2019

Uh oh!

rrrutledge left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

rrrutledge left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

rrrutledge left a comment

Choose a reason for hiding this comment

Uh oh!

lenucksi commented Aug 27, 2019

Uh oh!

rrrutledge commented Aug 27, 2019

Uh oh!

rrrutledge commented Sep 3, 2019

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

lenucksi commented Jul 24, 2019 •

edited

Loading

rrrutledge commented Aug 8, 2019 •

edited

Loading