[kepler-dev] [kepler-leadership] release of Ukranian version of Getting Started Guide
David Welker
david.v.welker at gmail.com
Tue Oct 13 21:31:38 PDT 2009
Lack of a copyright statement does in fact lessen your rights. It
doesn't prevent you from receiving copyright in the work, but it does
make you ineligible for statutory damages. Thus, you would be required
to prove actual damages in order to bring a copyright lawsuit, which
in many cases will be insignificant compared to statutory remedies.
The more general point is one should not imagine that their rights are
entirely equal, in terms of remedies, if one fails to signify
copyright and fails to register the work with the Copyright Office.
That notice and registration are no longer required to receive
copyright does not imply that the remedies for copyright infringement
are the same for you in the absence of these actions.
Keep in mind that one does not have to attach a license to the
physical text of a document -- although there is a tradition of doing
so in many cases when it comes to software code. A license to use a
copyrighted work can be either verbal or written. It seems quite clear
that some number of such licenses have been issued by the Kepler
project.
That said, the foregoing is more of theoretical interest. I agree that
it makes sense to unambiguously use the Creative Commons designation
suggested.
On Oct 13, 2009, at 10:31 PM, Christopher Brooks wrote:
> Sure, place it under CC-BY.
> _Christopher
>
> Matt Jones wrote:
>> The original Getting Started Guide was written by a combination of
>> UC academics, UC staff, UNM staff, and a contractor-for-hire for
>> UNM ( a work for hire). Thus it is a joint work, and my assessment
>> is that the copyright is held jointly by UC and UNM, with each
>> having full rights in the work. It was released without a
>> copyright statement, and without a licensing statement. As a
>> consequence, its probably not technically legal for others to
>> modify or redistribute it at all (i.e., the lack of a copyright
>> statement does not in any way reduce our rights). We should remedy
>> that, which I would be happy to do. The BSD license doesn't
>> necessarily work for text documents, but we could release it under
>> a CC-BY license which I think is equivalent for copyrighted texts.
>> Would everyone be happy with that?
>> The same would apply to the User's manual and actor reference.
>> I'm sure that translation requires permission of the original
>> copyright holder. I don't know if the original copyright holder
>> automatically holds copyright on a translated document -- we should
>> probably check. As Loy is from Ukraine, US law may not even govern
>> for his translation. If we don't have copyright on the
>> translations, we should be sure that Loy is willing to release it
>> under an acceptable license. Same is true for the Japanese
>> version. The easiest way to do this is to add the CC-BY license
>> right into the text of the original and translated documents. I
>> could do this if we agree to this approach.
>> Matt
>> On Tue, Oct 13, 2009 at 5:35 PM, Christopher Brooks <cxh at eecs.berkeley.edu
>> <mailto:cxh at eecs.berkeley.edu>> wrote:
>> I'm fine with a Ukrainian version of the docs.
>> Interesting question about licensing. The primary issue
>> is the licensing of the document, it would be good for the
>> Regents to retain the copyright.
>> _Christopher
>> Mark Schildhauer wrote:
>> Same here...
>> Question-- was there some specification in English about the
>> licensing of Kepler? Should we require some such English
>> language statement in any international release?
>> Mark
>> Timothy McPhillips wrote:
>> Sounds good to me!
>> Tim
>> On Oct 13, 2009, at 5:06 PM, Ilkay Altintas wrote:
>> I support it.
>> -ilkay
>> -- Ilkay ALTINTAS
>> Deputy Coordinator for Research, San Diego
>> Supercomputer
>> Center (SDSC)
>> Lab Director, Scientific Workflow Automation
>> Technologies (SWAT @ SDSC)
>> University of California, San Diego
>> 9500 Gilman Drive, MC: 0505 La Jolla, CA 92093-0505
>> Phone: (858) 210-5877 Fax: (858)
>> 534-8303
>> Web: http://users.sdsc.edu/~altintas
>> <http://users.sdsc.edu/%7Ealtintas>
>> <http://users.sdsc.edu/%7Ealtintas>
>> Skype: ilkay.altintas
>> On Oct 13, 2009, at 5:05 PM, Matt Jones wrote:
>> Anatoly Loy has produced a Ukranian translation of
>> the Kepler 1.0.0 Getting Started Guide. This
>> closely follows the existing English and Japanese
>> versions. Anatoly has requested that we release
>> the
>> Ukranian version from the Kepler web site. I
>> indirectly asked for a review of the translation
>> on
>> kepler-dev, and not surprisingly, none was
>> forthcoming. So I think we should go ahead and
>> release it. I said I would clear this with the
>> leadership team. Any objections to me moving it
>> to the web site under Documentation?
>> http://code.kepler-project.org/code/kepler-docs/trunk/outreach/documentation/shipping/getting-started-guide_uk.pdf
>> Matt
>> _______________________________________________
>> leadership mailing list
>> leadership at kepler-project.org
>> <mailto:leadership at kepler-project.org>
>> <mailto:leadership at kepler-project.org
>> <mailto:leadership at kepler-project.org>>
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/leadership
>> _______________________________________________
>> leadership mailing list
>> leadership at kepler-project.org
>> <mailto:leadership at kepler-project.org>
>> <mailto:leadership at kepler-project.org
>> <mailto:leadership at kepler-project.org>>
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/leadership
>>
>> ------------------------------------------------------------------------
>> _______________________________________________
>> leadership mailing list
>> leadership at kepler-project.org
>> <mailto:leadership at kepler-project.org>
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/leadership
>> -- Mark Schildhauer,
>> Ph.D. 735 State St., Suite 300
>> Director of Computing, NCEAS Santa Barbara CA
>> 93101
>> Phone: 805-892-2509 FAX: 805-892-2510
>> Email: schild at nceas.ucsb.edu <mailto:schild at nceas.ucsb.edu>
>> http://www.nceas.ucsb.edu
>>
>> ------------------------------------------------------------------------
>> _______________________________________________
>> leadership mailing list
>> leadership at kepler-project.org <mailto:leadership at kepler-project.org
>> >
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/leadership
>> -- Christopher Brooks (cxh at eecs berkeley edu) University
>> of California
>> CHESS Executive Director US Mail: 337 Cory
>> Hall
>> Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA
>> 94720-1774
>> ph: 510.643.9841 fax:510.642.2718 (Office: 545Q Cory)
>> home: (F-Tu) 707.665.0131 (W-F) 510.655.5480
>> _______________________________________________
>> leadership mailing list
>> leadership at kepler-project.org <mailto:leadership at kepler-project.org
>> >
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/leadership
>
> --
> Christopher Brooks (cxh at eecs berkeley edu) University of California
> CHESS Executive Director US Mail: 337 Cory Hall
> Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA 94720-1774
> ph: 510.643.9841 fax:510.642.2718 (Office: 545Q Cory)
> home: (F-Tu) 707.665.0131 (W-F) 510.655.5480
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
More information about the Kepler-dev
mailing list