/site-policy

Updates to the Standard Terms of Service - Spring 2018 #102

Merged
merged 3 commits into from May 24, 2018
+65 −49

Conversation

Reviewers

@KOLANICH KOLANICH

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@bluemazzoo @KOLANICH
@bluemazzoo
Contributor

bluemazzoo commented Apr 19, 2018

Most of the changes to our terms are clarifications of pre-existing sections. Here are a few sections we'd like to highlight:

  • Third Party Applications: We combined the Marketplace section with general requirements for those creating integrations for other users to provide better protections for GitHub users and their data. The Marketplace section is now called "Third Party Applications," since it now applies to more than just GitHub's Marketplace. We've also added a "Third Party Applications" section to the Privacy Statement to discuss our users' privacy expectations in regards to those applications
  • Access to Private Repositories: In Section E, we clarified the purposes for which we may be required to access private repository contents, in line with the security obligations of our GDPR compliance program
  • More definitions: We included definitions of "User Accounts" and "Organizations" and described who has control of those types of accounts
@bluemazzoo
Updates to the Standard Terms of Service - Spring 2018 
Most of the changes to our terms are clarifications of pre-existing sections. Here are a few sections we'd like to highlight:

* Third Party Applications: We combined the Marketplace section with general requirements for those creating integrations for other users to provide better protections for GitHub users and their data. The Marketplace section is now called "Third Party Applications," since it now applies to more than just GitHub's Marketplace. We've also added a "Third Party Applications" section to the Privacy Statement to discuss our users' privacy expectations in regards to those applications
* Access to Private Repositories: In Section E, we clarified the purposes for which we may be required to access private repository contents, in line with the security obligations of our GDPR compliance program
* More definitions: We included definitions of "User Accounts" and "Organizations" and described who has control of those types of accounts
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.
GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
a7eb36c

@nsqe nsqe referenced this pull request Apr 19, 2018

Closed

Spring 2018 updates are live! #105

bluemazzoo added some commits May 10, 2018

@bluemazzoo
Incorporate Definitions + Section J update - Terms of Service 
This pull request:
- incorporates the new "Accounts" definition through the agreement
- adds "User-Generated Content" and "User Personal Information" to section J(1) and updates two of the requirements in that section
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.
GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
ecfd0ed
@bluemazzoo
Merge pull request #107 from github/incorporate-definitions-tos-sprin… 
…g-2018

Incorporate Definitions + Section J update - Terms of Service
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.
GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
790ebb9
Policies/github-terms-of-service.md
+#### 1. Account Controls
+- Users. Subject to these Terms, you retain ultimate administrative control over your User Account and the Content within it.
+
+- Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one User Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization.

This comment has been minimized.

Show comment Hide comment
@KOLANICH

KOLANICH May 13, 2018

I guess it's not right to make an owner of an org responsible for actions of other GH users in an org. I mean as I understand, if someone came to an org-owned repo and created an issue with prohibited content the org owner is a scrapegoat. I guess it is not quite right since an org and a repo owner has no control on the messages before he saw them.

I guess this part needs clarification.
@KOLANICH

KOLANICH May 13, 2018 •
edited
Edited 1 time
  • @KOLANICH KOLANICH edited May 24, 2018

I guess it's not right to make an owner of an org responsible for actions of other GH users in an org. I mean as I understand, if someone came to an org-owned repo and created an issue with prohibited content the org owner is a scrapegoat. I guess it is not quite right since an org and a repo owner has no control on the messages before he saw them.

I guess this part needs clarification.

This comment has been minimized.

Show comment Hide comment
@bluemazzoo

bluemazzoo May 24, 2018

Contributor

Hi @KOLANICH, thank you for your feedback. The purpose of this section is to clarify what Organizations are and how users may control and maintain them. At this time, we will not be making any changes to this section.
@bluemazzoo

bluemazzoo May 24, 2018

Contributor

Hi @KOLANICH, thank you for your feedback. The purpose of this section is to clarify what Organizations are and how users may control and maintain them. At this time, we will not be making any changes to this section.
@bluemazzoo

This comment has been minimized.

Show comment Hide comment
@bluemazzoo

bluemazzoo May 24, 2018

Contributor

Thank you all for your feedback and comments, but we won't be making any additional changes at this time.
Contributor

bluemazzoo commented May 24, 2018

Thank you all for your feedback and comments, but we won't be making any additional changes at this time.

@bluemazzoo bluemazzoo closed this May 24, 2018

@bluemazzoo

This comment has been minimized.

Show comment Hide comment
@bluemazzoo

bluemazzoo May 24, 2018

Contributor

The public comment period has ended. This version is being merged into master.
Contributor

bluemazzoo commented May 24, 2018

The public comment period has ended. This version is being merged into master.

@bluemazzoo bluemazzoo reopened this May 24, 2018

@bluemazzoo bluemazzoo merged commit 83d0862 into master May 24, 2018

@bluemazzoo bluemazzoo deleted the terms-of-service-spring-2018 branch May 30, 2018

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