>From: Chris Hanson <[EMAIL PROTECTED]>
>
> I think really, the issue of the license for the book content
>should be up to the contributors.
Yes, that is why I wish they did read the reasons for using Creative
Commons or GNU document license. Many professional paid coders
write free, open source
On 26-Sep-06, at 12:20 PM, Paul Martz wrote:
I think any book, even a Gems-style book, requires (at least) an
editor to
give the book an overall consistent look and feel, ensure
readability, etc.
Many people making changes to a book, without a single "governor",
will
produce chaos if the c
Juhana Sadeharju wrote:
Because OSG is being developed and the book authoring is difficult,
the OSG book should come with Creative Commons or GNU document
license. That way we would have a base book which any of us could
extend later. For such successful book project, the Csound manual goes
as a
I think any book, even a Gems-style book, requires (at least) an editor to
give the book an overall consistent look and feel, ensure readability, etc.
Many people making changes to a book, without a single "governor", will
produce chaos if the changes are anything other than trivial.
-Paul
On 25-Sep-06, at 1:27 PM, Juhana Sadeharju wrote:
Because OSG is being developed and the book authoring is difficult,
the OSG book should come with Creative Commons or GNU document
license. That way we would have a base book which any of us could
extend later. For such successful book project,
Because OSG is being developed and the book authoring is difficult,
the OSG book should come with Creative Commons or GNU document
license. That way we would have a base book which any of us could
extend later. For such successful book project, the Csound manual goes
as a good example. No single p
