should we create an OS development magazine?

01000101 · Post by **01000101** » Fri Feb 29, 2008 2:42 pm

Why not just post the liscence within the magazine, expressing its implicities of the authors of the articles contained within?

Alboin · Post by **Alboin** » Fri Feb 29, 2008 2:49 pm

IANAL

If we removed the clauses, we wouldn't have to print it with every article.

We cannot just put a license on an article not owned by us. The author *must* put it there when he submits it. In fact, if there is no license on an article, we cannot even edit it for grammatical errors, more or less print it.

JackScott · Post by **JackScott** » Fri Feb 29, 2008 4:58 pm

Alboin is correct, afaik. We need a license that isn't going to get the editor's arse sued off (while I trust you all, circumstances can change, and miscommunications can occur).

This is why I support a page on the website that makes the author agree to the license when they submit the work... it makes the legal stuff clearer for everybody. Even if it is just a page that then sends an email to me or Alboin.

PDF is not the best format to submit articles in. TBH, it's one of the worst. Word, ODF, HTML, TXT. Those are good ways to submit articles. If you have images, submit high-res JPEGs or PNGs. As for formatting, that's what my whole job is... so don't worry about that. Just get the spelling and grammar (and meaning) as good as you can get it.

01000101 · Post by **01000101** » Fri Feb 29, 2008 5:09 pm

I agree now that I look at it like that.

Should we have a hierarchial editing structure? eg: writer -> grammatical-editor -> formatting editor -> posted?

JackScott · Post by **JackScott** » Fri Feb 29, 2008 5:14 pm

That's the way it generally works. I wouldn't call it heirachical, it's more of a line from one stage to the next.

jerryleecooper · Post by **jerryleecooper** » Fri Feb 29, 2008 5:14 pm

I think I botched the end of my first article. It's not long too, for an article on FAT itr's not fat. I send it tto you?

JackScott · Post by **JackScott** » Fri Feb 29, 2008 5:19 pm

Proofread it as best you can. Wait until we have chosen a license before submitting anything. You might not like the license, and decide not to submit it. It also makes things clearer legally.

Alboin · Post by **Alboin** » Fri Feb 29, 2008 6:15 pm

I don't believe that we should create our own license. AFAIK, none of us are lawyers, and therefore none of us know enough to draft one up correctly.

JackScott · Post by **JackScott** » Fri Feb 29, 2008 6:20 pm

That's true. So we need to decide on one. I support Alboin's (I think) comment about the FreeBSD documentation license (http://www.freebsd.org/copyright/freebs ... cense.html), without the clauses. The only thing we will have to change are the formats used (HTML and not DocBook, that sort of thing).

01000101 · Post by **01000101** » Fri Feb 29, 2008 7:04 pm

Agreed.

jerryleecooper · Post by **jerryleecooper** » Fri Feb 29, 2008 7:14 pm

That's what I did with my unreleased kernel, I took the bsd license, changed things, and used.
The license itself is public domain, no?

JackScott · Post by **JackScott** » Fri Feb 29, 2008 7:18 pm

It is indeed public domain. I propose the following as the license:

Copyright 2008 <AUTHOR NAME>. All rights reserved.

Redistribution and use in source (HTML, Text, RTF, and so forth) and 'compiled' forms (HTML and PDF) with or without modification, are permitted provided that the following conditions are met:

THIS DOCUMENTATION IS PROVIDED BY <AUTHOR NAME> "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE SYSTEM CALL MAGAZINE NOR THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

01000101 · Post by **01000101** » Fri Feb 29, 2008 7:31 pm

would we change the name from FREEBSD DOCUMENTATION PROJECT etc. to something of our own, or does that stay?

also, are we protecting the articles from being textually modified or not?

JackScott · Post by **JackScott** » Fri Feb 29, 2008 7:38 pm

I missed that one. I'll change it.

The editors need the rights to modify the text. Otherwise I (nor anybody else) can do anything with the text (fix mistakes, basically).

jerryleecooper · Post by **jerryleecooper** » Fri Feb 29, 2008 7:38 pm

We need two license, a license from the authors to the magazine, and a license from the magazine to the end-user, or one license fits all cases and everyone can make theirs own magazines with the material posted on the internet? YOu're better to make a license for editorial use, and a license for distribution.