The MirOS Project

CVS log for src/share/misc/licence.template

Up to [The MirOS Project] / src / share / misc

Request diff between arbitrary revisions - Display revisions graphically

Keyword substitution: kv
Default branch: MAIN

we are now officially listed

Message-ID: <18716.26951.86587.900700@desk.crynwr.com>
The MirOS Licence was approved by the OSI board. Listing pending…

clarify the part about including others’ work, as we do not have a clause
like the EUPL¹’s “chain of authorship” (paragraph 6)

① http://www.crynwr.com/cgi-bin/ezmlm-cgi?17:mss:206:kokiblmeljajbpncpbnc

• thanks to Jonathan Gray and Rufus Pollock, we’re certified as OKD confor-
  mant licence by the OKFN now
• add pointers to FSF definitions of Free Software and Free Documentation
  licences, mention that the MirOS Licence qualifies

remove recommendations about the optional advertising clause
‣ who still wants to use one can look in e.g. cvsweb for the syntax

the OSI changed their website

move rcs id to end of file like install docs et aliï

• licence.template: let it look less like a big monolith, put emphasis on
  the licence's shortness (kind of like with the ISC licence)
• license.template: put back a slightly modified (to address the issues
  pointed out by various people) version, since the MirOS website is still
  the primary resource on the ISC licence template for the ifrOSS Lizenz-
  zentrum (and maybe referenced by others); point out that our template is
  superiour (especially for authors in droit d'auteur legislations) though

changes in the licence body:

* change state to "Rel", bsiegert@ is ok with the new draft
  and nobody from the passive developers or contributors complained

fixes in the descriptive section:

* typo (pasto)
* GPLv2 compatible. GPLv3 isn't released yet. (we're probably
  compatible, even if advertising clauses are used, except that
  the FSF doesn't see that. we'll see.)
* not only advertising clauses, but also other (restrictive) text
  that ought to be avoided to be added (see above in the descrip-
  tive section) can void GPL compatibility (and OSD/DFSG compliance)

Remove the one comma too many

"free commit" tg@

a new draft, resulting out of a "comma too much" found by bsiegert@,
a missing comma found by me, and the subsequent restructuring, trying
to make it as short as possible without losing meaning (especially
focusing on easy understanding, not so much shortness), and not worsening
the use of English in here.

XXX I'm not too sure about the comma after "immediate fault"

reword the "rationale" section, put emphasis on being universally usable, and
remove the mention of the "choice of law" clauses because they won't be GPLv3
compatible, and the authors' countries' laws apply anyway, implicitly.

"notices above, these terms, and the disclaimer"
       |                            |
       |                            |
       V                            V
"notices above, these terms, and below disclaimer"

seems more consequent to me

working draft: improve grammar of disclaimer
thanks to: http://www.bartleby.com/116/402.html

* fix enumeration
* error -> fault (replace germanism by correct term - Verschulden)
* [out of] its use -> [out of] dealing with the work (to make it
  clear that not only use, but also distribution, modification, etc.
  are addressed here)
* except -> unless ("language feel", I lack a description for this change)

* wording
* update to MirOS #9
* mksh-style expression syntax fix
* link to (formal) online version of the template
* shorten
* multimedia -> audio + graphics (and etc.)
* spelling (a an, ...)

it's not always "software", d'oh

add missing help verbs

It's simply "avoid adding text"(*). And remove another almose useless
historic paragraph(**).

*) except to specify a licensor different from the (original) author,
   might be necessary in some cases, e.g. with my substantial modifi-
   cations to elf2aout(1)

**) whose first part was, with regards to (*), slightly wrong as well

A british lawyer (although totally computer-illiterate) suggested
to rather use the word "defect" here, which strikes me as fitting.

This is still difficult. I read this as:
- bugs in upstream are not "a direct error"
- "even if advised of the...existence of a defect" means that, if
  they issue a security advisory, I still can choose to not upda-
  te (e.g. to not break more stuff)
- unknown mistakes are not "advised"
- if an unknown mistake does not prevent any "intended use of the
  work" (testing!) we're out of the wood as well
- documented mistakes shift the moving target "intended use"

Comments? This is still a draft.

do the change of http://article.gmane.org/gmane.os.miros.general/1987
this is preliminary, don't use until RCS State is changed to Rel
this is RCS State = Exp until discussed, Stab until approved by team

* use continuation properly
* remove outdated information (according to Daniel Seuffert)
* link more

* license.template: point to web version too
* licence.template: small wording change (fixed English)

forgot to add a [4] link

* shorten and straighten out non-licence text
* move instructions before "advertising clause" template
* add DFSG reference

no changes to licence

fix my Engrish

from sap@ - thanks

Message-ID: <Pine.BSO.4.64L.0512032305320.16076@odem.66h.42h.de>
"ok, ist gut so" bsiegert@

* straighten out the disclaimer and adjust the stuff you're
  liable for and not a bit more after studying law and some
  law analysts' texts for a while longer
* make the instructions a bit easier and promise less

Inspired by: ifrOSS, rechtliches.de, CECILL, some of the OSI debates

cut down a bit, especially OSI references
i.e. shrink to the minimum, since less legalese = good
add some "at the time of this writing"

The MirOS Licence Template, final version.