Diff for "Translations/LicensingFAQ"

Not logged in - Log In / Register

Differences between revisions 10 and 11
Revision 10 as of 2009-06-02 21:19:10
Size: 7457
Editor: cpe-24-193-42-111
Comment: Include text of BSD license; link to it where appropriate. See bug #375944 for why.
Revision 11 as of 2009-06-02 21:20:20
Size: 7455
Editor: cpe-24-193-42-111
Comment: Fix anchor syntax.
Deletions are marked like this. Additions are marked like this.
Line 74: Line 74:
<<<Anchor(license-text)>>> <<Anchor(license-text)>>

Launchpad Help > Translations > Translation licensing FAQ and other legal aspects

We have now updated the "Translations copyright" section of the Launchpad terms of use to require that translations submitted in Launchpad licensed using the BSD licence.

Why was this needed?

Translations are freely shared between projects on Launchpad. Copyright complicates that free exchange. That's why our terms of use require that, when you translate in Launchpad, you grant us the right to share those translations with other projects.

Unfortunately there was some inconsistency in how we presented that condition. The FAQ at https://translations.launchpad.net/+faq said:

We ask that all translations submitted through Launchpad use the BSD licence. This makes the strings available to the widest number of open source projects.

But those at https://help.launchpad.net/TermsofUse said:

All translations submitted into Launchpad are the work of the translator that created them, and are submitted under the same license as the software being translated. In addition, the translator grants to Canonical Ltd the right to publish the translation and use the translation in other software packages under their license.

Which was it? Whose is "their" license in that second one? We wanted to clear this up by going with the BSD license and consulted people using Launchpad Translations.

We have updated our Launchpad terms of use as follows:

All translations imported from sources external to Launchpad are owned by the translator that created them. In general, these translations are licensed under the same terms as the software for which they are a translation.

All translations in Launchpad are the work of the translator that created them.  These translations are made available to Canonical and in turn to you under the BSD license [[#license-text|(revised, without advertising clause)]].  We require this so that other projects can use these translations as sources for their own translations, without suffering licensing incompatibilities.

What changes?

In practice, very little and probably nothing. If you went by the conditions as described in the FAQ, definitely nothing.

Why the BSD license?

The BSD license is universally compatible. This lets you share and combine with projects under GPL, LGPL, BSD, and many other licenses.

Why not public domain like the FSF's Translation Project?

For all practical purposes, BSD license is very much like disclaiming any copyrights, similar to what Translation Project does by asking for disclaimers in writing. However, you still get to keep your copyright, which is slightly easier to manage.

Does that mean my translations may be used in proprietary software?

Yes, this risk exists and will remain. However, we believe that the advantage of having large translation memories for free software far outweighs the risk of having free software translations end up in proprietary software.

Keeping track of how each string is allowed to be used would be much more difficult, and gain us relatively little.

If and when we allow proprietary projects to use Launchpad for translation, they will get the same translation suggestions as anyone else. Those may include translations you entered (and conversely, those projects' translations may be included in the suggestions you receive as well).

If I don't want my translations licensed under BSD, what will you do?

If you've already told us that you definitely don't want your contributions licensed under BSD, we've removed your contributions from Launchpad.

However, all your future contributions through Launchpad will still be licensed under BSD, and if you've got explicit concerns about this, we'd like to hear them on the launchpad-users mailing list.

If you don't want your contributions licensed under BSD, do not use Launchpad for translating, although we'll be very sad to see you go.

Will I still be able to select a packaged translation from some other template?

Yes, however, it will be clearly noted that it's up to you to check licensing compatibility. For example, you should not reuse nontrivial translations from a GPL module in a BSD-licensed project without asking the author for permission. An icon will warn of potential licensing issues.

You can freely reuse a few translations, though, because that's what copyright laws allow. Also, accidental matches between translations for short phrases should not make you worry.

I have no problem with BSD myself, but I also uploaded translations from upstream. What do I do?

As long as the uploads were marked as translations that were published elsewhere, they fall under a separate copyright regime: those imports will retain their original copyright license. The licensing cleanup only applies to translations that are (as far as the system knows) original to Launchpad. .

What is the exact text of the BSD license?

There are a few variants of the text available, but the differences are minor and the variants should be legally equivalent.

     Redistribution and use in source and binary forms, with or without
     modification, are permitted provided that the following conditions are
     met:

       * Redistributions of source code must retain the above copyright
         notice, this list of conditions and the following disclaimer.

       * Redistributions in binary form must reproduce the above
         copyright notice, this list of conditions and the following
         disclaimer in the documentation and/or other materials provided
         with the distribution.

       * Neither the name of the <ORGANIZATION> nor the names of its
         contributors may be used to endorse or promote products derived
         from this software without specific prior written permission.

     THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
     "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
     LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
     A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
     HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
     SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
     LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
     DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
     THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
     (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
     OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

(In the third clause, "the <ORGANIZATION>" would be replaced with your name.)

Note that this is the modern, simplified BSD license, that is, without the advertising clause (see the full history of the license for more information). In modern times, this simplified, three-clause version is the most widely used.

Translations/LicensingFAQ (last edited 2018-05-24 17:23:08 by cjwatson)