search

mozilla-l10n / styleguides

Localization styleguides
https://mozilla-l10n.github.io/styleguides
Creative Commons Attribution 4.0 International
27 stars 73 forks source link

Missing License #106

Closed flodolo closed 2 years ago

flodolo commented 6 years ago

CC @gueroJeff @mozilla-l10n/pm-group

The repository is currently missing a license. Should we add one? More important, can we add one that covers all the styleguides in here, or should each styleguide have its own?

gueroJeff commented 6 years ago

Let's do. Even Microsoft has a license agreement for their style guides. Is the MPL sufficient?

MikkCZ commented 6 years ago

Can we explicitly use a different license for Czech locale? We may preferr some CC for better license interoperability with l10n.cz, but I will need to discuss that.

flodolo commented 6 years ago

I don't think we can set safely a license to the entire repository, each styleguide should have their own. And in some cases we copied them from other places, where we don't have source/context.

gueroJeff commented 6 years ago

To my knowledge we didn't directly copy from other places, and where it did, I thought I called it out. The ideas may have been paraphrased though.

On Thu, Jun 21, 2018 at 8:34 AM, Francesco Lodolo notifications@github.com wrote:

I don't think we can set safely a license to the entire repository, each styleguide should have their own. And in some cases we copied them from other places, where we don't have source/context.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla-l10n/styleguides/issues/106#issuecomment-399125350, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZBYLlZDOrt004C1L6aaFYKe1dePIks5t-67mgaJpZM4UxmBo .

flodolo commented 6 years ago

To my knowledge we didn't directly copy from other places, and where it did, I thought I called it out.

See, for example, https://github.com/mozilla-l10n/styleguides/blob/master/docs/gd/ https://github.com/mozilla-l10n/styleguides/tree/master/docs/te

The Italian one was copied and pasted from a website that has it under CC. No idea about others. If they were on the WIKI, they're likely OK under MPL, but I'm far from an expert on licenses.

gueroJeff commented 6 years ago

I was more referring to the en-US style guide. I can't say the same about style guides for other languages.

On Thu, Jun 21, 2018 at 11:08 AM, Francesco Lodolo <notifications@github.com

wrote:

To my knowledge we didn't directly copy from other places, and where it did, I thought I called it out.

See, for example, https://github.com/mozilla-l10n/styleguides/blob/master/docs/gd/ https://github.com/mozilla-l10n/styleguides/tree/master/docs/te

The Italian one was copied and pasted from a website that has it under CC. No idea about others. If they were on the WIKI, they're likely OK under MPL, but I'm far from an expert on licenses.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla-l10n/styleguides/issues/106#issuecomment-399176349, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZCyhJH8PZzNckxZEMufdF41XKGpnks5t-9MKgaJpZM4UxmBo .

flodolo commented 6 years ago

I was more referring to the en-US style guide

The question is about the entire repository, if it can have a single license, or if each license should have one. Background, I've received a question about "forking and changing this repo in other OS projects", and I'm not sure how to answer to that (license is only part of the problem).

gueroJeff commented 6 years ago

Was that request from LocLab?

Could we use an adaptable MLP that includes exceptions under certain circumstances (e.g., "except for content from another licensed style guide (source citing required), all content is licensed under MLP)?

On Thu, Jun 21, 2018 at 11:31 AM, Francesco Lodolo <notifications@github.com

wrote:

I was more referring to the en-US style guide

The question is about the entire repository, if it can have a single license, or if each license should have one. Background, I've received a question about "forking and changing this repo in other OS projects", and I'm not sure how to answer to that (license is only part of the problem).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla-l10n/styleguides/issues/106#issuecomment-399183202, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZKx9PIsH2at0edgk_CY1_Pk8zI3Hks5t-9hggaJpZM4UxmBo .

flodolo commented 6 years ago

The request was from @drashti4, not sure which were the projects.

I don't know the answer to your question unfortunately.

ghost commented 6 years ago

Yes LocLab willing to adapt this styleguide but they're not sure whether they can make changes or not.

gueroJeff commented 6 years ago

Drashti, which style guide are they wanting to adapt, the en-US style guide or all of them?

I would suggest they fork and make their own based on this. Style guides should be unique to each organization's tone and style. Sometimes even different products or content types within one organization need their own unique style guides. Ours is a good starting place for them, but shouldn't strictly be the one they use for all of the organizations they're supporting.

On Thu, Jun 21, 2018 at 12:21 PM, Drashti notifications@github.com wrote:

Yes LocLab https://www.localizationlab.org willing to adapt this styleguide but they're not sure whether they can make changes or not.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla-l10n/styleguides/issues/106#issuecomment-399198140, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZDY5syWQuVdnDqkPdPP5Awd5masUks5t--Q-gaJpZM4UxmBo .

ghost commented 6 years ago

Mostly all of them. Yes, they willing to change existing Mozilla styleguide by having fork. Mozilla styleguide will not get strictly followed. But, basic structure of styleguide like JSON files will be same. So I was just wondering will it violate any copyright rules?

gueroJeff commented 6 years ago

There isn't an easy answer to that, as flod has pointed out. We'll consult with Legal or whomever we need to in order to get an idea of what to do.

El vie., 22 de jun. de 2018 23:31, Drashti notifications@github.com escribió:

Mostly all of them. Yes, they willing to change existing Mozilla styleguide by having fork. Mozilla styleguide will not get strictly followed. But, basic structure of styleguide like JSON files will be same. So I was just wondering will it violate any copyright rules?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla-l10n/styleguides/issues/106#issuecomment-399634048, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZOlPd2bLY3CNtxHkq4k5R85gALaMks5t_dK_gaJpZM4UxmBo .

MikkCZ commented 6 years ago

@gueroJeff Any updates from legal? If not yet, is there some advise, what license to pick now to be compatible with possible future changes? I am thinking about some Creative Commons, which is widely used for written texts.

gueroJeff commented 6 years ago

Sorry, I don't have anything new from legal. Since the en-US style guide is influenced by, not copy/pasted from, other company style guides, let's go with the most relaxed CC license.

On Thu, Aug 9, 2018 at 6:09 AM, Michal Stanke notifications@github.com wrote:

@gueroJeff https://github.com/gueroJeff Any updates from legal? If not yet, is there some advise, what license to pick now to be compatible with possible future changes? I am thinking about some Creative Commons, which is widely used for written texts.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla-l10n/styleguides/issues/106#issuecomment-411735533, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZPa8yvj6Lssnmtde681EhdgZbHRWks5uPCaPgaJpZM4UxmBo .