Hello,
On 01/16/2013 08:05 AM, Richard Fontana wrote:
On 01/16/2013 12:24 AM, Tom Marble wrote:
> On 01/15/2013 01:27 PM, Joshua Gay wrote:
>> On 06/15/2013 02:28 PM, Josh Gay will write:
>> It is unlikely we would add it to our list of various licenses and
>> comments about them page until either it has started to have widespread
>> adoption or a lot of people began asking us for our opinion. [...]
>
> It may be difficult to discuss a "release" of a copyleft-next
> license unless there is a "permalink" to point to.
>
http://opensource.org/licenses/MPL-2.0
>
http://www.eclipse.org/legal/epl-v10.html
>
https://www.gnu.org/licenses/gpl.html (interestingly unversioned?)
The FSF somewhat assumes use of their "version X or later" clause, in
that case a permalink to
https://www.gnu.org/licenses/gpl.html is
perhaps appropriate.
However, they also have good links for each version, e.g.:
http://www.gnu.org/licenses/gpl-2.0.txt
http://www.gnu.org/licenses/gpl-2.0.html
http://www.gnu.org/licenses/gpl-3.0.txt
http://www.gnu.org/licenses/gpl-3.0.html
etc..
I hadn't thought about permalinks as such.
I have had vague ideas for a copyleft-next website, and in fact it
exists, but is quite minimal at the moment:
http://copyleft-next.org/
But also, for some time I have had an empty 'Releases' directory in
the file structure for the copyleft-next source repository,
anticipating that numbered releases would be stored therein.
I certainly would appreciate [1] good permanent links for each versioned
release, preferably both a plain text and html version of the license.
Possibly also an unversioned link pointing to the latest version as the
FSF does, if your intent is that copyleft-next is typically used with an
"version X or later" clause.
-- kuno / warp.
[1] as some of you may know, one of my side projects is to build a
database of free software / open source software / free culture license
metadata, which benefits from having a good way to identify a particular
license (
https://licensedb.org ).