Jeroen Vermeulen pisze:
Adi Roiban wrote:What would happen to translation for which they author does not access the license update page?They stay around. The existing terms of use already allowed making them available to other projects under different licenses. We're asking people about this because we feel it's the right thing to do, but we don't see any actual conflict between the old terms and the new ones.
But they're still problematic. When you import translations to LP under their upstream license (ie. GPL) then, when you update some parts of them, you can't licence your changes under the BSD license because the whole file is under the upstream license (here: GPL). Rosetta should allow setting a license for every project, or even every file, and should make that clear to translators that by modifying the file they should licence their contributions under the license chosen by upstream.
-- ## Przemysław Kulczycki <<>> Azrael Nightwalker ## # jabber: azrael[na]jabster.pl | tlen: azrael29a # ### www: http://reksio.ftj.agh.edu.pl/~azrael/ ###
Attachment:
signature.asc
Description: OpenPGP digital signature
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)