GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — First draft for the Introductory Contributor Section Article #67 by lenucksi · Pull Request #98 · InnerSourceCommons/InnerSourceLearningPath

Conversation

@lenucksi

@lenucksi lenucksi commented Jul 24, 2019 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Member

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Johannes Tigges
First draft for the Introductory Contributor Section Article #67
dc8a67f
@lenucksi lenucksi added the Contributor label Jul 24, 2019
lenucksi
lenucksi commented Jul 25, 2019
View reviewed changes
Comment thread contributor/01-introduction-article.md Outdated
- 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.

@lenucksi lenucksi Jul 25, 2019

Copy link
Copy Markdown
Member Author

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.

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

rrrutledge reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
@rrrutledge

rrrutledge commented Aug 6, 2019

Copy link
Copy Markdown
Contributor

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.

lenucksi reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

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

rrrutledge commented Aug 8, 2019 •
edited
Loading

Uh oh!

There was an error while loading. Please reload this page.

Copy link
Copy Markdown
Contributor

An initial approach could be to link the GitHub articles.

Yes we should do this

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

rrrutledge
rrrutledge requested changes Aug 8, 2019
View reviewed changes

@rrrutledge rrrutledge left a comment

Copy link
Copy Markdown
Contributor

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.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread contributor/01-introduction-article.md Outdated
[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?

@rrrutledge rrrutledge Aug 8, 2019

Copy link
Copy Markdown
Contributor

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.

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@lenucksi lenucksi Aug 11, 2019

Copy link
Copy Markdown
Member Author

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.

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@rrrutledge rrrutledge Aug 12, 2019

Copy link
Copy Markdown
Contributor

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.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

lenucksi reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

@lenucksi lenucksi Aug 15, 2019

Copy link
Copy Markdown
Member Author

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.

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?

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@rrrutledge rrrutledge Aug 19, 2019

Copy link
Copy Markdown
Contributor

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.

Yes, I think so.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

lenucksi reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

@rrrutledge
Typos
2d43df4
lenucksi
lenucksi commented Aug 11, 2019
View reviewed changes

@lenucksi lenucksi left a comment

Copy link
Copy Markdown
Member Author

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.

Addressed your review comments.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Comment thread contributor/01-introduction-article.md Outdated
[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?

@lenucksi lenucksi Aug 11, 2019

Copy link
Copy Markdown
Member Author

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.

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

lenucksi
lenucksi commented Aug 11, 2019
View reviewed changes

@lenucksi lenucksi left a comment

Copy link
Copy Markdown
Member Author

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.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
@rrrutledge
Heading suggestions
1b6fb59
@rrrutledge rrrutledge mentioned this pull request Aug 12, 2019
Heading suggestions #110
Merged
@rrrutledge

rrrutledge commented Aug 12, 2019

Copy link
Copy Markdown
Contributor

I'm happy for suggestions

Left in #110.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

rrrutledge added 2 commits August 12, 2019 13:54
@rrrutledge
Rewrite introductory paragraphs
ed36bff
To appeal to an individual who just cares about making progress on their project.
@rrrutledge
Rephrase contributor definition
7313400
Avoid explicitly bringing up contributions outside of repo contents.
rrrutledge
rrrutledge reviewed Aug 12, 2019
View reviewed changes

@rrrutledge rrrutledge left a comment

Copy link
Copy Markdown
Contributor

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.

Responded to all comments.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Comment thread contributor/01-introduction-article.md Outdated
[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?

@rrrutledge rrrutledge Aug 12, 2019

Copy link
Copy Markdown
Contributor

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.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

lenucksi reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

lenucksi added 2 commits August 15, 2019 14:35
@lenucksi
Merge pull request #112 from InnerSourceCommons/contributor/introduct…
b55b384
…ion-defition

Rephrase contributor definition
@lenucksi
Merge pull request #110 from InnerSourceCommons/contributor/introduct…
2779779
…ion-headings

Heading suggestions
@lenucksi lenucksi added the Article label Aug 15, 2019
@rrrutledge
run via InnerSource -> incorporate InnerSource principles
9df1cd9
rrrutledge
rrrutledge reviewed Aug 19, 2019
View reviewed changes

@rrrutledge rrrutledge left a comment

Copy link
Copy Markdown
Contributor

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.

Almost done!

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread contributor/01-introduction-article.md Outdated
[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?

@rrrutledge rrrutledge Aug 19, 2019

Copy link
Copy Markdown
Contributor

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.

Yes, I think so.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

lenucksi reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
Comment thread contributor/01-introduction-article.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

@lenucksi
Merge pull request #111 from InnerSourceCommons/contributor/introduct…
cb0b317
…ion-persona

Rewrite introductory paragraphs
@rrrutledge rrrutledge mentioned this pull request Aug 26, 2019
Article: The Contributor in InnerSource #67
Closed
rrrutledge
rrrutledge approved these changes Aug 27, 2019
View reviewed changes

@rrrutledge rrrutledge left a comment

Copy link
Copy Markdown
Contributor

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.

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

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

lenucksi reacted with thumbs up emoji
All reactions
  • 👍 1 reaction
@lenucksi

lenucksi commented Aug 27, 2019

Copy link
Copy Markdown
Member Author

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 reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@rrrutledge

rrrutledge commented Aug 27, 2019

Copy link
Copy Markdown
Contributor

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

🆗

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@rrrutledge

rrrutledge commented Sep 3, 2019

Copy link
Copy Markdown
Contributor

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

lenucksi reacted with thumbs up emoji
All reactions
  • 👍 1 reaction

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@rrrutledge
rrrutledge merged commit 3281d93 into master Sep 12, 2019
@rrrutledge
rrrutledge deleted the contributor/introduction branch September 12, 2019 15:47
@marshmallowrobot marshmallowrobot mentioned this pull request Aug 8, 2023
Website build is failing #575
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@rrrutledge rrrutledge rrrutledge approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

Article Contributor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@lenucksi @rrrutledge
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.