Website Terms of Use: Explicit "inbound=outbound" policy

Why is this change being made?

I didn't see an explicit inbound=outbound policy in GitLab's terms.

From what I understand, inbound=outbound is the precedent and assumed default for all open source contributions.

GitHub makes this explicit in its terms anyway, just to be safe. GitLab does not (yet).

I think adding this term would make GitLab a friendlier place for open source owners, sponsors, and maintainers, since an inbound=outbound clause helps explicitly de-risk not having a contributor license agreement (CLA).

For background, grep for "inbound=outbound" in:

• https://www.finnegan.com/en/insights/articles/what-you-should-know-about-contributor-license-agreements-in-open-source-projects.html
• https://opensource.com/article/19/2/cla-problems

Without this change, section 6 of the Website ToU could be read as a bit scary-- while it properly disclaims GitLab for responsibility for the content of its users, its very explicit declaration that GitLab may be hosting material that infringes IP rights of 3rd parties also had the effect of making me nervous as an open source maintainer who prefers not to force contributors to sign CLAs.

Side note

I only addressed inbound=outbound in this MR, but there are a lot of other comforting terms in GitHub's "D. User-Generated Content". Worth a look?

I think adopting GitLab equivalents of most (or all) of these terms would be helpful in the quest to get large open source projects like Sails migrated over to GitLab.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.