Skip to content

Crown copyright statement change #182

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

Open
delisma opened this issue Sep 26, 2022 · 3 comments
Open

Crown copyright statement change #182

delisma opened this issue Sep 26, 2022 · 3 comments

Comments

@delisma
Copy link

delisma commented Sep 26, 2022

Copyright (c) Her Majesty the Queen in Right of Canada, as represented by the Treasury Board of Canada Secretariat, 2018

The Governor General's proclamation of the accession of His Majesty King Charles II brings some changes for all new Government of Canada publications. In particular, the copyright statement for Government of Canada publication has been updated.

The copyright statement for new publications should read as follows:

  • © His Majesty the King in Right of Canada, as represented by the Minister of [legal name of department], [year of publication]
  • © Sa Majesté le Roi du chef du Canada, représenté par le ministre de [appellation légale du ministre], [année de publication]

Also, I'm noticing that the LICENSE isn't bilingual.

@nschonni
Copy link
Member

Also, I'm noticing that the LICENSE isn't bilingual.

Very few OSS licenses have official translations (and WET shouldn't have added them for an MIT license)

@delisma
Copy link
Author

delisma commented Sep 26, 2022

Very few OSS licenses have official translations (and WET shouldn't have added them for an MIT license)

Really, why? Should we check with CIPO if OSS projects led by the Federal Government should have bilingual LICENSE?

@nschonni
Copy link
Member

Licenses are copyrighted themselves, and shouldn't be translated. https://www.gnu.org/licenses/gpl-faq.html#GPLTranslations also talks about why it's generally a bad idea

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

No branches or pull requests

2 participants