Rick Hillegas wrote:
The legal-discuss alias has discussed the process of contributing localized message files to Derby. Two email threads touch this topic on http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200807.mbox/browser :

 Blanket software grant
 Question about handling external updates to contributed files

I would like to try to summarize these threads:

1) There seems to be consensus that these files can be checked in under a committer's ICLA. The committer would enjoy extra protection if the contributing company's CCLA explicitly granted permission for these contributions.

The CCLA causes a lot of confusion. Roy said it exceptionally well [1]:
If you have permission from your company, you can contribute them under
your own ICLA.  However, it is better for your sake (not Apache's) that
you have a signed CCLA in place that formally says you have permission
to commit stuff that is copyright the company.  Only one CCLA is needed
for all such commits.

[1] http://mail-archives.apache.org/mod_mbox/www-legal-discuss/200807.mbox/[EMAIL PROTECTED]

2) Although the localizations were prepared by people who have not signed ICLAs, a commit-by-proxy of their contributions is allowed under section 4 of the committer's ICLA. See http://www.apache.org/licenses/icla.txt

3) It would be good to document these conclusions on a wiki page.

If the community agrees with these conclusions, then I propose to check in the 10.4 localizations under my ICLA. In addition, I propose to

A) Capture this discussion on a wiki page

B) Point to that wiki page from my localization JIRA: https://issues.apache.org/jira/browse/DERBY-3804

Please let me know whether you think this is acceptable.


I agree -- it makes sense to handle the translated message files in this way because this same set of files gets updated for (nearly) every release.

thanks, Rick,

-jean

Thanks,
-Rick



Reply via email to