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

Give guidance for copyright notice on translations in Workstream Policy #40

Closed
othermaciej opened this issue Dec 10, 2017 · 2 comments · Fixed by #59
Closed

Give guidance for copyright notice on translations in Workstream Policy #40

othermaciej opened this issue Dec 10, 2017 · 2 comments · Fixed by #59
Assignees

Comments

@othermaciej
Copy link
Contributor

Some WHATWG specs link to translations into various languages. These are not official WHATWG Workstream products (I think), but because they are linked and implicitly endorsed, we should recommend an appropriate notice. Workstream Policy describes all the other notices, so that seems like a good place to do it.

According to CC BY recommendations, the right way to do it would be:

This is a translation of X, which is licensed under a Creative Commons Attribution 4.0 International License. Copyright © 2017 WHATWG (Apple, Google, Mozilla, Microsoft).

Where X is the name of the Living Standard, marked up as a link to it.

othermaciej added a commit that referenced this issue Jan 10, 2018
Fixes #40

Since translations are generally produced independently, I framed this
as a recommendation rather than a requirememt. Translators can
technically do whatever they want as long as they follow the
requirements of the license.
@othermaciej
Copy link
Contributor Author

I proposed policy text for the above suggestion in PR #59

@henceproved @michaelchampion @dbaron I'd appreciate agreement or disagreement on this approach.

@othermaciej othermaciej self-assigned this Jan 10, 2018
triple-underscore added a commit to triple-underscore/triple-underscore.github.io that referenced this issue Jan 22, 2018
@henceproved
Copy link
Contributor

I am good with this approach. Add me to the PR if it needs an additional review/LGTM (looks like the editors and lawyers had some comments/suggestions that were being discussed).

annevk pushed a commit that referenced this issue Sep 22, 2022
Fixes #40

Since translations are generally produced independently, I framed this
as a recommendation rather than a requirememt. Translators can
technically do whatever they want as long as they follow the
requirements of the license.
annevk pushed a commit that referenced this issue Sep 22, 2022
Since translations are generally produced independently, this is framed as a recommendation rather than a requirement. Translators can technically do whatever they want as long as they follow the requirements of the license.

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

Successfully merging a pull request may close this issue.

2 participants