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.

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

OSS FAQ for Engineers #303

Merged
merged 2 commits into from Jan 5, 2017
Merged

OSS FAQ for Engineers #303

merged 2 commits into from Jan 5, 2017

Conversation

orta
Copy link
Contributor

@orta orta commented Jan 4, 2017

screen shot 2017-01-04 at 10 59 57 am

@ArtsyOpenSource
Copy link

ArtsyOpenSource commented Jan 4, 2017

Proselint found issues

_posts/2017-01-04-OSS-FAQ.md

Line Message Severity
10 Inconsistent spacing after period (1 vs. 2 spaces). warning
10 Inconsistent spacing after period (1 vs. 2 spaces). warning
24 'thought leader,' is cliché. warning
24 Inconsistent spacing after period (1 vs. 2 spaces). warning
28 Substitute 'damn' every time you're inclined to write 'very;' your editor will delete it and the writing will be just as it should be. warning
30 Inconsistent spacing after period (1 vs. 2 spaces). warning
69 Inconsistent spacing after period (1 vs. 2 spaces). warning

Spell Checker found issues

_posts/2017-01-04-OSS-FAQ.md

Line Typo
10 and our senior counsel [Yayoi Shionoiri](http://www.theartgorgeous.co
14 e code (whether in adapted or un-adapted form) be themselves licensed
44 (for e.g., GPL License) or [non-OSI approved licenses](https://op
44 rce.org/licenses/) (for e.g., WTFPL license).
48 ontinuous integration set up, linters, tests and documentation.
52 mple [see how we migrated the artsy.net](http://artsy.github.io/blog/
64 Copyright: Art.sy, Inc., 2017
64 :* [Developer], Art.sy, Inc., 2017
65 aster/LICENSE#L1)
69 like to personally thank [Gil Yehuda](http://gilyehuda.strikingly.

Generated by 🚫 danger

series: Open Source by Default
---

We have a lot of Open Source code. For engineers without considerable experience in the open source realm, understanding some of the copyright issues around copyrights and code ownership can be tricky. I've been working with [dB](http://artsy.github.io/author/db/), our CTO and [Yayoi Shionoiri](http://www.theartgorgeous.com/yayoi-shionoiri/) (our Senior Counsel) on documenting how this works.
Copy link
Contributor

Choose a reason for hiding this comment

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

Link "open source code" to something, list of OSS projects or github.

Copy link
Contributor

Choose a reason for hiding this comment

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

dB. is spelled with a period :) Also maybe flip "our CTO dB., and our senior counsel Yayoi...", I don't think senior counsel needs to be capitalized but I could be wrong.

Copy link
Contributor

Choose a reason for hiding this comment

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

copyright issues around copyrights is redundant, remove "around copyrights"

Copy link
Contributor

Choose a reason for hiding this comment

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

documenting how this works => maybe "creating an open-source FAQ for engineers"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I agree with all of this 👍


We have a lot of Open Source code. For engineers without considerable experience in the open source realm, understanding some of the copyright issues around copyrights and code ownership can be tricky. I've been working with [dB](http://artsy.github.io/author/db/), our CTO and [Yayoi Shionoiri](http://www.theartgorgeous.com/yayoi-shionoiri/) (our Senior Counsel) on documenting how this works.

I'd like to personally thank [Gil Yehuda](http://gilyehuda.strikingly.com) of Yahoo! for answering a lot of our questions, you really helped. For Artsy staff, you can get the living document at the [Engineering page on Artsy Atlas](https://sites.google.com/a/artsymail.com/intranet/team-pages/engineering).
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be at the bottom of the post.


<!-- more -->

### What is Open Source “by default”?
Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Cool, good point, I've made the first mention of OSS by Default a link (its in the paragraph above )

@orta
Copy link
Contributor Author

orta commented Jan 5, 2017

Rock, all feedback addressed


Inbound Open Source code refers to the use of third party code under an Open Source license for Artsy's products. Outbound Open Source code refers to the publication of Artsy code.

When we publish Outbound Open Source code, as mentioned before, Artsy has a right to do so because we have the copyright to this code. We give third parties the right to use the code usually through [this type](https://github.com/artsy/eigen/blob/master/LICENSE) of broad license ([MIT](https://tldrlegal.com/license/mit-license)). (For more on code licenses, see [Orta’s talk on code licenses](http://artsy.github.io/blog/2015/12/10/License-and-You/.)
Copy link
Contributor

Choose a reason for hiding this comment

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

The period needs to be outside of the parenthesis, it's part of the sentence, not the link. The link here is broken.

@dblock
Copy link
Contributor

dblock commented Jan 5, 2017

Fix the link above and feel free to merge. Thanks.

@orta orta merged commit 5805fe3 into source Jan 5, 2017
@orta orta deleted the oss_faq branch January 5, 2017 20:02
@orta
Copy link
Contributor Author

orta commented Jan 5, 2017

nice catch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants