-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
larry@garfieldtech.com schrieb:
Gerhard Killesreiter wrote:
Drupal's CVS policy is to not state a copyright or authorship on anything, since most code gets so many people working on it that separating out who did what is infeasible. Commit messages should specify credit. Therefore, po files in CVS should follow the same convention as code: Don't specify an author or a copyright or a license in the file itself and let the packaging system add a LICENSE.txt file as appropriate.
While I agree, this is a bit impractical. The copyright notices in the PO files are usually added by the PO translator software. While it is possible to remove them (man vi), most translators might not know how.
In fact, our own extractor.php adds this to the header of the files:
$output = "# LANGUAGE translation of Drupal (". $file .")\n"; $output .= "# Copyright YEAR NAME <EMAIL@ADDRESS>\n";Since they do not claim something that is not true, I suggest to ignore them.
Cheers, Gerhard
Well they may become untrue over time if multiple people work on a given PO file. That's why PHP files do not carry an author identification. I do not know the usual workflow for PO files well enough to say if it is a valid concern there, so will defer to Gerhard on the enforcement front.
Thank you so much. :p
I guess a good policy would be to place something like "the Drupal translators for foo language" in that line.
Realistically I've no time to enforce this at all.
But maybe Mori would like to draw up some policy that we can add to the translators' handbook.
Cheers, Gerhard
Gerhard Killesreiter wrote:
larry@garfieldtech.com schrieb:
Gerhard Killesreiter wrote:
Drupal's CVS policy is to not state a copyright or authorship on anything, since most code gets so many people working on it that separating out who did what is infeasible. Commit messages should specify credit. Therefore, po files in CVS should follow the same convention as code: Don't specify an author or a copyright or a
license
in the file itself and let the packaging system add a LICENSE.txt file as appropriate.
While I agree, this is a bit impractical. The copyright notices in the PO files are usually added by the PO translator software. While it is possible to remove them (man vi), most translators might not know how.
In fact, our own extractor.php adds this to the header of the files:
$output = "# LANGUAGE translation of Drupal (". $file .")\n"; $output .= "# Copyright YEAR NAME <EMAIL@ADDRESS>\n";Since they do not claim something that is not true, I suggest to ignore them.
Cheers, Gerhard
Well they may become untrue over time if multiple people work on a given PO file. That's why PHP files do not carry an author identification. I do not know the usual workflow for PO files well enough to say if it is a valid concern there, so will defer to Gerhard on the enforcement
front.
Thank you so much. :p
I guess a good policy would be to place something like "the Drupal translators for foo language" in that line.
Realistically I've no time to enforce this at all.
But maybe Mori would like to draw up some policy that we can add to the translators' handbook.
That's *exactly* what I was thinking! :)
Mori
Cheers, Gerhard
_______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
On Thu, Jun 18, 2009 at 12:09 AM, Gerhard Killesreitergerhard@killesreiter.de wrote:
I guess a good policy would be to place something like "the Drupal translators for foo language" in that line.
Realistically I've no time to enforce this at all.
Historically the Hungarian team used "Copyright 2006 by the Hungarian Translation Team" or something like that. There were quite a few debates on wording of certain translations that we felt originality can be claimed :) Also, I've been removing individual names and converting them to this generic format, as I found them.
Gábor
Thanks for the info Gábor. Your argument about originality is interesting.
The reason for asking this question is that one of local user groups in Japan are planning on setting up a l10n server to facilitate translation of modules. My aim is to prevent anyone, including the group who will host the l10n server, from claiming ownership of the fruits of collaboration. We have a long history of conflicts among local user groups (sigh) and people tend to be sceptical when this kind of collaboration effort is attempted. I would like to wither such scepticism by removing elements that potentially benefit certain individuals / group so people can hop in and work together without a concern.
Mori
Gábor Hojtsy wrote:
On Thu, Jun 18, 2009 at 12:09 AM, Gerhard Killesreitergerhard@killesreiter.de wrote:
I guess a good policy would be to place something like "the Drupal translators for foo language" in that line.
Realistically I've no time to enforce this at all.
Historically the Hungarian team used "Copyright 2006 by the Hungarian Translation Team" or something like that. There were quite a few debates on wording of certain translations that we felt originality can be claimed :) Also, I've been removing individual names and converting them to this generic format, as I found them.
Gábor _______________________________________________ translations mailing list translations@drupal.org http://lists.drupal.org/mailman/listinfo/translations
-
Gerhard Killesreiter -
Gábor Hojtsy -
Mori Sugimoto