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?)
Of course "beta" or 0.x "point" releases may not merit
the finality that a permalink implies. Perhaps with a
sufficiently easy UI simply using a "tag" from the VCS would be
acceptable. For example, in viewing the history of a file:
https://github.com/tmarble/gtk3py3/commits/master/README.md
or specific tags:
https://github.com/tmarble/kspsig/tags
https://github.com/tmarble/kspsig/blob/v0.6/kspsig
https://github.com/tmarble/kspsig/blob/v0.5/kspsig
Richard have you given any thought to how or where the license(s)
would be "published"?
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.
- RF