subversion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko Čibej <br...@apache.org>
Subject Re: The future of the Subversion book
Date Thu, 18 Oct 2018 18:40:33 GMT
On 06.09.2018 15:25, Branko Čibej wrote:
> On 06.09.2018 15:10, C. Michael Pilato wrote:
>> On 09/05/2018 04:49 PM, Mark Phippard wrote:
>>> Assuming the PMC wanted it, is it possible for the book to be
>>> contributed to this project and hosted in the Apache SVN repository?
>>> Many people seem to post questions and issues in these mailing lists
>>> as if it is part of the project anyway so maybe we ought to just
>>> make this the reality.  I guess what I am saying is, before we gauge
>>> opinion on whether we want to bring this into the project, my
>>> question is whether there are any blockers that prevent this on the
>>> book side from being an option?  Such as copyright or licensing
>>> issues that make it not possible.  It feels like this has been
>>> discussed in the past and there were reasons it was kept separate
>>> from the project even after the publishing of the book by O'Reilly
>>> was in the past, but I no longer recall them.
>> Honestly, I think the book belongs with the PMC. It is easy to imagine a
>> day when a developer is expected to provide at least rudimentary
>> documentation updates in the same commit that carries his or her new
>> feature or behavioral change.
>>
>> The book carries a cc-by-2.0 license, with Ben, Fitz and myself named as
>> the copyright holders. I suspect that in order to be absorbed by the
>> PMC, that licensing would have to change to an Apache License. Does that
>> mean that the three primary authors would need to officially re-license
>> it somehow? Or maybe it's a software grant to the ASF (rather like
>> Subversion itself was)?
> We'd have to ask legal@ but I'd be surprised if we'd be required to
> re-license the book; it's not code, and the Apache license isn't really
> suitable. Also we wouldn't really be making releases of it, just updates
> on the web.


I didn't quite forget about this: LEGAL-421

-- Brane


Mime
View raw message