Licensing TN: update authors

[jouvin]

define M. Jouvin as the first author and J. Harvey as the second one

Contributes to #4.

[HadrienG2]

As I mentioned on the hep-sf-tech-forum mailing list, I think that some of the discussions yesterday revealed a couple of misunderstandings in our community when it comes to the relationship between licensing and copyright, and I believe this document is a great opportunity to clear that up 😃

Here are a couple of proposals which I think could help to this end:

• In the "Basic terminology" section, there should be a "Licensing" paragraph (probably after the "Copyright" one). This paragraph would state that licensing is a mechanism through which the copyright owners of a work can, through common agreement, grant others the right to use or reproduce a work without explicit permission, provided that some license-specific legal terms are respected.
• The second part of the "Public domain software" paragraph could be merged with such a paragraph, as to my eyes it mostly seems to describe the concept of software licensing in general rather than that of public domain in particular.
• In the "Public domain software" paragraph, it may be important to clarify that in most countries, it is legally impossible to waive all of one's legal rights and duties pertaining to a work. For example, in French law, moral rights like the right to attribution are considered inalienable, which means that even the original authors cannot reject them. "Public domain" licenses like CC0 are about waiving as many rights as possible, but cannot completely detach a work from its creator. This is particularly important in countries where voiding one's legal liability in case of a software-originated incident, as the GPL tries to do for example, is illegal (e.g. UK).
• Since the concept of proprietary software is pervasive in the "Basic terminology" section, one might as well define it. For example: "Proprietary software is software for which the copyright owners only allow use and redistribution under highly restrictive licensing terms, if at all. Typical restrictions include demanding that a payment be versed in exchange for every copy, or that software source code be not reused in other projects without permission."
• In the "Examples" section, it might be useful to clarify that copyright statements need not include the circled C symbol, which is not available in all character sets and whose "(c)" ASCII art equivalent has no legal meaning, but must feature the years or year span of all public releases of a project (examples: "Copyright 2005, 2010 Jean Pire" or "Copyright 2006-2008 Clara Tatouille").

[jouvin]

As said in #4, these improvements will be done in the next version.