Handbook license?

L

lele

Hello,

I'm considering porting the FreeBSD Handbook to Debian Linux. My understanding is that the license of the Handbook allows it:

"Redistribution and use in source [...] and 'compiled' forms [...] with or without modification, are permitted [...]"

However I don't understand whether I would be allowed to publish such a derivative work under the GNU Free Documentation License while giving credit to the authors of the FreeBSD Handbook. I'd say I would be allowed, but I'm not sure.

Any clarifications? Thank you.
 
The handbook should be under the same BSD license as the OS, but I am not sure about all the legal difficulties. Why are you porting it to Debian linux anyway? There are already alot of linux sites that post manpages and stuff from FreeBSD, couldn't you just download it in htm or something?

What I am getting at is I'm not sure what you would want to change to make it derivative that would make it useful for Debian.
 
@numpad5

The Handbook is what drew me to FreeBSD in the first place. I have given up switching to FreeBSD because, as a non-technically inclined guy, I have found the experience to be too time-consuming and maybe not worth at all for a heavy laptop user like me.

Basically, I would borrow from the Handbook its structure and its Unix-related stuff while rewriting the Debian-specific parts.

Linux distros lack a well-written handbook. Debian has the Debian Reference, but the FreeBSD Handbook is a masterpiece of technical writing, and the Debian project would benefit from having something similar.
 
Just curious, why do want to relicense it ? Maybe I'm wrong but code contribute to GPL-ed software (that was original BSD) can't be contributed back to BSD because GPL says it has to stay GPL.
 
swa said:
Just curious, why do want to relicense it ? Maybe I'm wrong but code contribute to GPL-ed software (that was original BSD) can't be contributed back to BSD because GPL says it has to stay GPL.
Click to expand...

A couple years ago some noobs tried doing that with some openbsd software. They failed miserably. IIRC they even attempted to remove the BSD license in the process which of course is negligent.
 
@swa

You're right: GNU licenses are more restrictive than BSD ones. I subscribe to the GNU philosophy, therefore relicensing a derivative work (when feasible) under a GNU license is desirable. And since BSD licenses have always allowed derivative works under more restrictive licenses, I infer that the BSD philosophy is fine with that.

In this particular case, the derivative work would be useless to the FreeBSD project anyway, because the additional work would be related to Debian.
 
UNIXgod said:
A couple years ago some noobs tried doing that with some openbsd software. They failed miserably. IIRC they even attempted to remove the BSD license in the process which of course is negligent.
Click to expand...

Negligent indeed, and disrespectful of other people's work. GNU-licensed and BSD-licensed works can coexist. The way a software can contain source files released under different compatible licenses, a book could do the same with chapters.
 
lele said:
Negligent indeed, and disrespectful of other people's work. GNU-licensed and BSD-licensed works can coexist. The way a software can contain source files released under different compatible licenses, a book could do the same with chapters.
Click to expand...

IANAL, Have you consulted the FSF about re-licensing? If your new chapters are under a different license but keep the originals intact that may be what the BSD license is all about. Interestingly it came about when AT&T began to remove UC Berkeley's credit from the OS in the 80's.

Curious why you would need a document to be under GPL? Why not keep it BSD or use MIT or even creative commons?
 
How much of the FreeBSD handbook is actually useful information for Debian? We are talking about two very different systems here. What is the motivation for using the FreeBSD handbook as the starting point? Writing a handbook for Debian from scratch using the FreeBSD documentation tools wouldn't be that much more work I bet.
 
UNIXgod said:
IANAL, Have you consulted the FSF about re-licensing? If your new chapters are under a different license but keep the originals intact that may be what the BSD license is all about.
Click to expand...

I've not consulted the FSF, but thanks for the hint: if I end up pursuing this project, it would be wise to do that.

UNIXgod said:
Curious why you would need a document to be under GPL? Why not keep it BSD or use MIT or even creative commons?
Click to expand...

As I stated above, I like the GNU philosophy, therefore a GNU license makes more sense. I could change my mind, though.

oed said:
lele, are you aware of "The Debian Administrator's Handbook"?

http://debian-handbook.info/
Click to expand...

Thanks for the link. Yes, I know about that book, and actually I'm reading it at the moment. Besides being "the missing manual", it is a good book, yet I enjoyed reading the FreeBSD Handbook much more. It may be that the Debian Administrator's Handbook is much younger. That said, after I'll have finished reading it, I may realize that another manual on Debian would not be useful, and limit myself to sending suggestions to the authors, or filling the gaps.

You know what? I suspect I've fallen in love with FreeBSD... I can't help it ;-) And the Handbook did the trick. Hence, I thought that since using FreeBSD wouldn't be a pragmatic decision, I could at least port some of its awesomeness in my environment.

kpa said:
How much of the FreeBSD handbook is actually useful information for Debian? We are talking about two very different systems here. What is the motivation for using the FreeBSD handbook as the starting point? Writing a handbook for Debian from scratch using the FreeBSD documentation tools wouldn't be that much more work I bet.
Click to expand...

You are underestimating the advantage of having a great roadmap available when starting a journey. GNU/Linux is a Unix derivative, hence the differences are not that great. The FreeBSD Handbook, being the technical masterpiece it is, would serve as both a great roadmap and a style reference. One would only have to fill in the gaps.
UNIXgod said:
IANAL, Have you consulted the FSF about re-licensing? If your new chapters are under a different license but keep the originals intact that may be what the BSD license is all about.
Click to expand...

I've not consulted the FSF, but thanks for the hint: if I end up pursuing this project, it would be wise to do that.

UNIXgod said:
Curious why you would need a document to be under GPL? Why not keep it BSD or use MIT or even creative commons?
Click to expand...

As I stated above, I like the GNU philosophy, therefore a GNU license makes more sense. I could change my mind, though.

oed said:
lele, are you aware of "The Debian Administrator's Handbook"?

http://debian-handbook.info/
Click to expand...

Thanks for the link. Yes, I know about that book, and actually I'm reading it at the moment. Besides being "the missing manual", it is a good book, yet I enjoyed reading the FreeBSD Handbook much more. It may be that the Debian Administrator's Handbook is much younger. That said, after I'll have finished reading it, I may realize that another manual on Debian would not be useful, and limit myself to sending suggestions to the authors, or filling the gaps.

You know what? I suspect I've fallen in love with FreeBSD... I can't help it ;-) And the Handbook did the trick. Hence, I thought that since using FreeBSD wouldn't be a pragmatic decision, I could at least port some of its awesomeness in my environment.

kpa said:
How much of the FreeBSD handbook is actually useful information for Debian? We are talking about two very different systems here. What is the motivation for using the FreeBSD handbook as the starting point? Writing a handbook for Debian from scratch using the FreeBSD documentation tools wouldn't be that much more work I bet.
Click to expand...

You are underestimating the advantage of having a great roadmap available when starting a journey. GNU/Linux is a Unix derivative, hence the differences are not that great. The FreeBSD Handbook, being the technical masterpiece it is, would serve as both a great roadmap and a style reference. One would only have to fill in the gaps.
 
lele said:
In this particular case, the derivative work would be useless to the FreeBSD project anyway, because the additional work would be related to Debian.
Click to expand...

If I remember well, Debian does not accept the GFDL license as a free license:
See http://www.debian.org/vote/2006/vote_001

"Within the Debian community there has been a significant amount of concern about the GNU Free Documentation License (GFDL), and whether it is, in fact, a "free" license. This document attempts to explain why Debian's answer is "no"."

edit: I'm wrong. This is one option of the vote, the result is that GFDL is free if there is no invariant section. http://wiki.debian.org/DFSGLicenses#GNU_Free_Documentation_License_.28GFDL.29

Also did you read the GFDL? IMHO it is too hard to understand this f* license just for a documentation. This is why I prefer BSD like license :-)

Regards.
 
You must log in or register to reply here.
Back
Top