blog post copyright info
1 unresolved thread
1 unresolved thread
Per conversation in Slack; to clarify for our community writers.. https://gitlab.slack.com/archives/marketing/p1480611212003725
Merge request reports
Activity
2 2 Thank you for your interest and help! 3 3 4 4 We don't mind people inside and outside the company making suggestions to change significant things. 5 Feel free to make a proposal, we can discuss anything and if we don't agree we'll feel free not to merge it and thank you for caring about it. 5 Feel free to make a proposal, we can discuss anything and if we don't agree we'll feel free not to merge it and we'll thank you for caring about it. 6 6 7 By submitting code as an individual you agree to the GitLab [individual contributor license agreement](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/legal/individual_contributor_license_agreement.md) 8 By submitting code as an entity you agree to the GitLab [corporate contributor license agreement](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/legal/corporate_contributor_license_agreement.md). 7 8 By submitting code or text for the website as an individual you agree to the GitLab [individual contributor license agreement](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/legal/individual_contributor_license_agreement.md) 9 By submitting code or text for the website as an entity you agree to the GitLab [corporate contributor license agreement](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/legal/corporate_contributor_license_agreement.md). 10 11 If you submit blog post contributions, those contributions are also governed by the Contributor License Agreements linked to above. This means that copyright of submitted materials will belong to GitLab, but under the Creative Commons license you are free to re-use the material with attribution. mentioned in commit 885cd3c0
Please register or sign in to reply