www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Hobbs <tvho...@googlemail.com>
Subject Re: Foundations of Jini 2 Programming
Date Thu, 23 Jun 2011 08:27:29 GMT
Hi Craig,

Thanks for the confirmation, I'll pass it on and we'll figure out what to



Grammar and spelling have been sacrificed on the altar of messaging via
mobile device.

On 23 Jun 2011 04:39, "Craig L Russell" <craig.russell@oracle.com> wrote:
> Hi Tom,
> Sorry to disappoint, but Apache only hosts content that is licensed
> under the Apache license. Our license doesn't allow restricting
> redistribution to "not make printed copies for sale".
> So I'm afraid this is a non-starter.
> It's fine to have links on the River site to the content elsewhere but
> it's not possible to license the book under the Apache license or host
> it at Apache.
> Craig
> On Jun 21, 2011, at 4:12 AM, Tom Hobbs wrote:
>> Sorry, I'm reposting this to a more appropriate legal-list.
>> Thanks,
>> Tom
>> ---------- Forwarded message ----------
>> From: Tom Hobbs <tvhobbs@googlemail.com>
>> Date: Mon, Jun 20, 2011 at 11:40 AM
>> Subject: Fwd: Foundations of Jini 2 Programming
>> To: legal-internal@apache.org
>> Cc: private <private@river.apache.org>
>> Hi all,
>> The River project needs some advice about wanting to host a Creative
>> Commons version of some documentation.
>> To cut a long story short, before Sun Microsystems donated the Jini
>> code to ASF (and thus birthing the Apache River project) a chap called
>> Jan Newmarch wrote a book about Jini. This book is available for free
>> on the internet under the CC license, it's also published in non-free
>> dead-tree format via APress.
>> As you can see from the email chain below, Jan has kindly agreed to
>> let the River project host his original (electronic) version of his
>> book on river.a.o - assuming we keep the correct attributions,
>> copyright headers etc. The project fully intends to bring this book
>> up to date in respects to referencing River (as the successor to the
>> Jini *implementation*) and also with new functionality, build
>> instructions, and other things.
>> So my question is, how do we go about this? I'm assuming that the
>> hosting the electonic copy is easy to do - we just update our website
>> and there it is. Things get more interesting if/when we talk about
>> asking APress to publish a new version. Note, that will be in the
>> distant, but hopefully still visible, future.
>> It's probably worth mentioning that the included email chain contains
>> everything that has been done so-far in relation to this
>> documentation. So if something is impossible/improbable to do from a
>> legal standpoint, I just have to send an email back to Jan saying
>> "Thanks very much, but we're not allowed." Or words to that effect.
>> What I know about licenses, copyrights etc can be written in very
>> large letters on a very small piece of paper, so any help/advice will
>> be very gratefully received.
>> My apologies if this is the wrong list, can someone point me to the
>> correct list if it is, please?
>> Many thanks,
>> Tom
>> ---------- Forwarded message ----------
>> From: Jan Newmarch <jan@newmarch.name>
>> Date: Mon, Jun 20, 2011 at 9:24 AM
>> Subject: Re: Foundations of Jini 2 Programming
>> To: Tom Hobbs <tvhobbs@googlemail.com>
>> Cc: private <private@river.apache.org>, Jan Newmarch <jan@newmarch.name
>> >
>> Hi Tom
>> The last version I created is at
>> http://jan.newmarch.name/java/jini/tutorial/Jini.html
>> This is later than the version you found, and does not have
>> inappropriate copyright notices.
>> The CC license that I used allowed anyone to make electronic copies,
>> change it, etc, but not make printed copies for sale. That was
>> reserved
>> for APress. But I am not a copyright lawyer either, so it would be
>> worth
>> checking with your legal team.
>> About formats: I prepared everything in XML, using a bastardised
>> version
>> of Docbook. The program files were kept separate so I could compile,
>> run
>> them, etc. I then had Perl scripts to convert the XML to HTML and suck
>> in the Java code. This could be done on the fly as a browser requested
>> them, or as a batch job (which is what you see on the given site). If
>> you substitute .xml for each .html you can see the original XML.
>> Obviously, the HTML will be easier to copy (wget or similar). But I
>> can
>> also bundle up the Java programs, Ant scripts and XML if that helps.
>> Regards
>> Jan
>> --
>> On Sun, 2011-06-19 at 19:54 +0100, Tom Hobbs wrote:
>>> Hi Jan,
>>> Peter Firmstone forwarded to the Apache River PMC an email from you
>>> about your Jini book.
>>> Firstly, many thanks for offer to allow us contribute to it. I think
>>> that it is definitely something the project would like to do. As I'm
>>> sure you're aware, good Jini documentation can be really hard to
>>> find.
>>> With that in mind, I was wondering if you had a 'vanilla' copy you
>>> could send us so that we can host if on the Apache River site. At
>>> the
>>> moment, the only version we can find is here [1] which they've put
>>> their own copyright notices on.
>>> Of course, we'll keep your own notices, comply with the CC license
>>> and
>>> make sure you get the correct credit for the work. I've got no idea
>>> how APress work so I'd have to ask the ASF legal team. I imagine
>>> that
>>> a new published version is a long way away though.
>>> I'm a bit of a numpty when incomes to licenses and legal issues, so
>>> hope that this request is appropriate.
>>> Naturally, if ever you want to get involved with Jini/River again
>>> you're always welcome on the lists.
>>> Cheers,
>>> Tom
>>> [1] http://www.javacommerce.com/displaypage.jsp?
>>> name=jini.sql&id=18224
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
>> For additional commands, e-mail: legal-discuss-help@apache.org
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!

View raw message