Updates to the Corporate Terms of Service - Winter 2019 #158
Conversation
| 8. An "Account" represents your legal relationship with GitHub. A “User Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. A "Corporate Account" refers to an Account created by a User on behalf of an entity, such as a company, non-profit organization, or group. A Corporate Account may include an Enterprise Cloud subscription or a Team plan. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A User Account can be a member of any number of Organizations. | ||
| 9. “Content” refers to content featured or displayed through the Website, including without limitation text, data, articles, images, photographs, graphics, software, applications, designs, features, and other materials that are available on the Website or otherwise available through the Service. “User-Generated Content” is Content, written or otherwise, created or uploaded by All Users. "Your Content" is Content that you create, own, or to which you are the rights holder. | ||
| 10. "Professional Services" means training, consulting, or implementation services that GitHub provides to you pursuant to a mutually executed SOW. Professional Services do not include Support. | ||
| 11. "SOW" means a mutually executed statement of work detailing the Professional Services GitHub will perform for you, any related Fees, and each party's related obligations. |
There was a problem hiding this comment.
If you change all these list items to be 1., future additions won’t require changing the whole list:
1. foo
1. bar
1. bazbecomes:
- foo
- bar
- baz
There was a problem hiding this comment.
I'm pretty sure that applies only to comments, but not to the contents of the files being diffed, which do not get processed further.
There was a problem hiding this comment.
Looks like it’s rendered to me: https://help.github.com/en/articles/github-corporate-terms-of-service
There was a problem hiding this comment.
@j-f1 Thanks for the recommendation and feedback! We won't be making the formatting change at this time, but we'll take a look over the coming week, and may add it in prior to merging this PR next Friday if the formatting works out.
|
|
||
| #### 1. Compliance with Laws and Regulations | ||
| Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control laws, or other laws in your jurisdiction. You are responsible for making sure that your and your Users' use of the Service is in compliance with laws and any applicable regulations. | ||
| Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your and your Users' use of the Service is in compliance with laws and any applicable regulations. |
There was a problem hiding this comment.
Should this be “export control laws, sanctions, or other laws in your jurisdiction”?
| Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your and your Users' use of the Service is in compliance with laws and any applicable regulations. | |
| Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control laws, sanctions, or other laws in your jurisdiction. You are responsible for making sure that your and your Users' use of the Service is in compliance with laws and any applicable regulations. |
There was a problem hiding this comment.
@j-f1 Thanks for your feedback! Those two references have been grouped together, since they both fall under a broad category of trade compliance laws, and we intended to highlight those two specific subcategories of laws with the reference. It's similar to how we referenced "copyright or trademark laws" in that sentence, as well.
There was a problem hiding this comment.
The reason I proposed this change is that “sanctions laws” seemed like a strange phrasing and Google ngrams confirms that “sanctions laws” is much rarer than just “sanctions” alone.
There was a problem hiding this comment.
I see what you're getting at, but this section is about compliance with laws, so what we're referring to is more specific:
- export control laws
- sanctions laws
We've just grouped that together to read export controls or sanctions laws.
There was a problem hiding this comment.
Ok, that makes more sense. Thanks for responding!
|
Thank you all for your comments and feedback! As stated in our blog post, the comment period ends today. I am closing this pull request for internal review of any remaining comments. We will commit final clarifications or edits when we merge this pull request next Friday, April 19. At that time, the updated version of this policy will be effective. |
This update to the Corporate Terms of Service includes a number of changes for compliance purposes and clarifications, including changes to the following sections: