Skip to content

Active voice and typos#295

Merged
spier merged 13 commits intoInnerSourceCommons:masterfrom
doronkatz:active_voice_and_typos
Feb 20, 2021
Merged

Active voice and typos#295
spier merged 13 commits intoInnerSourceCommons:masterfrom
doronkatz:active_voice_and_typos

Conversation

@doronkatz
Copy link
Copy Markdown
Contributor

Reviewed the introduction.md as part of my review, and corrected typos, passive voice usage, and grammatical errors.

Comment thread book/introduction.md Outdated
Copy link
Copy Markdown
Collaborator

@NewMexicoKid NewMexicoKid left a comment

Choose a reason for hiding this comment

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

Overall looks okay; found one typo (patter instead of pattern) in an edit. This should be fixed; after, the changes can be merged. Thanks for the attention to detail.

Fix lint-reported issue

Fixed typo with patter(n)

Fix lint-reported issue
@doronkatz
Copy link
Copy Markdown
Contributor Author

Thanks ive made the fixes hopefully (and rebased)

Comment thread book/introduction.md Outdated
@spier
Copy link
Copy Markdown
Member

spier commented Feb 18, 2021

Hi @doronkatz. Thanks for this fantastic contribute. I especially love what you did with the changes from passive to active voice in the Introduction to the book. Helps me a lot as a non-native English speaker :)

About the spelling of Open Source, open source, open-source ...

So far we mostly use "Open Source", and "open source". When reviewing new patterns, I have kept it this way, due to these two resources where they use the same spelling:

Could you explain more about why you would opt to change the spelling to open-source?

If we would change this now, I think we might find even more places where this is spelled without a hyphen, at least when we include the form with capital letters as well. Before moving ahead I would want to understand this area in more detail, so that we can make a consistent decision for all patterns and content in this repo.

If these contemplations about the open source spelling take too long, I would also be happy to get just the changes to Introduction merged via a separate PR.

Thanks again for taking the time to review the content so thoroughly. We appreciate any help we can get on the patterns and the book.

Copy link
Copy Markdown
Member

@spier spier left a comment

Choose a reason for hiding this comment

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

Left a comment on the PR with some thoughts about the "open source" spelling. Also one tiny question inline.

@spier spier added 📖 Type - Content Work Working on contents is the main focus of this issue / PR Type - Maintenance / Cleanup Maintaining / cleaning the repo is the main focus of this issue / PR labels Feb 18, 2021
@doronkatz
Copy link
Copy Markdown
Contributor Author

doronkatz commented Feb 18, 2021 via email

@spier
Copy link
Copy Markdown
Member

spier commented Feb 18, 2021

Yeah, let's go with that approach then.
If you can pull the "open source" spelling out of this PR, then I can review this shortly after and get it merged.

Thanks again!

@NewMexicoKid
Copy link
Copy Markdown
Collaborator

No worries. I was a technical writer in the past and at amazon everything Is about technical writing.
As for open source, I follow the Merriam Webster spelling (https://www.merriam-webster.com/dictionary/open-source) however you are right I have seen it spelt the other way too. Happy to pull that out of the PR rather than break everything.

I've found two sources (https://www.computerhope.com/jargon/o/opensour.htm and https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/o/open-source) that talk about using "open-source" when using it as an adjective and "open source" when using it as a noun. So your proposed changes looked okay to me...

@doronkatz
Copy link
Copy Markdown
Contributor Author

doronkatz commented Feb 19, 2021 via email

@doronkatz doronkatz requested a review from spier February 19, 2021 04:04
Comment thread book/introduction.md Outdated
@spier
Copy link
Copy Markdown
Member

spier commented Feb 19, 2021

@doronkatz is this already the version that you would like to get reviewed and merged?

Did you and Tim agree on the route "open-source" (when adjective) and "open source" (when noun)?
This is how I interpret the conversation above.

While I expect that there are more instances outside of the 15 files in this PR that would have to get fixed, I am happy to get this PR merged, given that the changes to the Open Source spelling are consistent within this PR itself.

@doronkatz
Copy link
Copy Markdown
Contributor Author

@doronkatz is this already the version that you would like to get reviewed and merged?

Did you and Tim agree on the route "open-source" (when adjective) and "open source" (when noun)?
This is how I interpret the conversation above.

While I expect that there are more instances outside of the 15 files in this PR that would have to get fixed, I am happy to get this PR merged, given that the changes to the Open Source spelling are consistent within this PR itself.

Not sure we are fully aligned but for the benefit of this PR, how about I take out the open source changes and merge and we can have a separate PR for that?

@doronkatz doronkatz force-pushed the active_voice_and_typos branch from fccf8ea to d3266af Compare February 20, 2021 04:38
@doronkatz doronkatz requested a review from spier February 20, 2021 04:48
Comment thread book/introduction.md Outdated
Comment thread meta/innersource-spelling.md Outdated
Comment thread meta/innersource-spelling.md Outdated
Comment thread patterns/2-structured/innersource-license.md Outdated
Copy link
Copy Markdown
Member

@spier spier left a comment

Choose a reason for hiding this comment

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

LGTM

@spier spier merged commit cd56f64 into InnerSourceCommons:master Feb 20, 2021
@spier
Copy link
Copy Markdown
Member

spier commented Feb 20, 2021

The greatly improved intro the book is now live at:
https://innersourcecommons.gitbook.io/innersource-patterns/

Thank you so much @doronkatz!

And if you still want to help us get the Open-Source-Spelling improved, we would greatly appreciate your help in a new PR. I for one would certainly benefit from that help as a non-native English speaker :)

@doronkatz
Copy link
Copy Markdown
Contributor Author

doronkatz commented Feb 20, 2021 via email

@spier
Copy link
Copy Markdown
Member

spier commented Feb 20, 2021

Nice!

If you haven't found it yet, there is also the InnerSource Commons Slack where you can talk to other InnerSource practitioners. Would be great to see you there :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📖 Type - Content Work Working on contents is the main focus of this issue / PR Type - Maintenance / Cleanup Maintaining / cleaning the repo is the main focus of this issue / PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants