The V Public License.

Recently, I learned that at least one of my readers is dissatisfied with my current favourite "open source license". For him and any others like him, I would like to propose a new one, and offer to "relicense" under it any of the VTronic items I have published on my site (strictly by explicit request, to be issued via PGP-signed comment, from a member of my L1 WOT.)

My position regarding open source "software licenses" is that they are, for the most part, a waste of bandwidth: on account of the elementary fact that any enforcement of a software license of whatever kind is generally impractical for anyone other than a tentacle of the Reich.

However, the text of such a license can still serve a propagandistic purpose.

And so, the proposed text of a V Public License :

(C) $YEAR $AUTHOR ( $AUTHOR'S_WWW )

This product is distributed under "The V Public License" ("VPL"; version 0xFF.)

This means that it is a document with a cryptographically-verifiable history of attributable authorship, rather than one of the many vile agglomerations of faecal droppings from anonymous vermin typically met with in public digital cesspools.

The V Public License mandates that all redistribution of this product is to take the canonical form of a VTree, which consists of: a Genesis VPatch; zero or more revision VPatches; and one or more VSeals which authenticate each such VPatch, including the Genesis.

A VPatch is defined as the output of "VDiff" on a revision against its predecessor: this is presently equivalent to standard Unix "diff -uNr PREDECESSOR SUCCESSOR", where the timestamp normally found in every delta is replaced with a Keccak hash of the original or transformed file. A Genesis VPatch is a VDiff of a "revision" constituting the initial public release of the product against a null predecessor (i.e. an empty directory).

A VSeal is a public key signature (typically generated via GPG or a compatible program) of a particular VPatch, by an author, coauthor, or reviewer who wishes to be known as a signatory. If the creator of a VSeal has a public presence, e.g. a WWW site, the public key against which the VSeal validates must be publicly accessible and publicly associated with said presence (e.g. offered for download on the creator's WWW site.)

This product may be used for ANY PURPOSE WHATSOEVER, and is supplied with NO WARRANTY OF ANY KIND, unless otherwise specified by written and signed agreements with all of its VSeal signatories.

However, if you choose to redistribute the product and/or any changes you have made to it, you must do so in VTree form, and the latter must include all VPatches and VSeals you had originally received. The VTree you redistribute must be fully-compatible in every respect with the format of the one you had received.

You may offer copies of a VPL-licensed product for download to third parties in variant (i.e. non-VTree) forms, so long as the canonical VTree form at all times exactly corresponding to every such variant is made readily and conspicuously available. Concretely, this means that if you intend to distribute a binary build of a VPL-licensed computer program, you must not only distribute its VTree with it, but must also include any and all components and instructions required to reproduce a bitwise-identical binary build.

Similarly, if you distribute a VPL-licensed product as a source archive, via a publicly-facing version control interface, as a printed book, inside a physical device, or in any form whatsoever other than a VTree, then a VTree corresponding exactly to the item you are distributing, retaining all of the history which you had originally received, must be distributed along with every such variant copy.

The only permitted exception to the three paragraphs above is that a VPL-licensed product MAY be incorporated whole into a new (i.e. with a novel Genesis) VTree, so long as the latter contains a statement of this fact, along with any information required to locate and retrieve a copy of the original product's canonical VTree. All provisions of the VPL shall apply to the new VTree.

The text of this notice is itself licensed under the VPL, and is to be retained where found.


An abbreviated version of the V Public License notice for convenient inclusion in program files:

This file is part of $PRODUCT.

(C) $YEAR $AUTHOR ( $AUTHOR'S_WWW )

This product is distributed under "The V Public License" ("VPL"; version 0xFF.)

This means that it is a document with a cryptographically-verifiable history of attributable authorship, rather than one of the many vile agglomerations of faecal droppings from anonymous vermin typically met with in public digital cesspools.

See LICENSE.TXT for further details.

This notice is to be retained where found.


A V-Genesis of the VPL is available:

vpl_genesis.vpatch

vpl_genesis.vpatch.asciilifeform.sig


Edit: discussion and elaboration.

This entry was written by Stanislav , posted on Friday February 11 2022 , filed under Chumpatronics, Copyrasty, Friends, Hot Air, Idea, ModestProposal, Philology, Philosophy, ShouldersGiants, SoftwareArchaeology, SoftwareSucks, VPL, VTronics . Bookmark the permalink . Post a comment below or leave a trackback: Trackback URL.

One Response to “The V Public License.”

  • Well my oh my, how so interesting this is.

    Regarding the second paragraph, I'm inclined to agree about license enforcement, and the belief doesn't really lend itself to the idea of a license which prohibits usage, as that old new software licensing paradigm did. These measly requirements would, I figure, lock out effectively all loathsome people, anyway.

    It's shortly after my first reading, but I've no criticisms of this license. I like how its viral nature is related to these technical aspects of its storage and proliferation.

    I've been intending, any year now, to use V, with one reason being how some people have hounded me to use some program source control system, and this would be an amusing way to satisfy that want; this has given me renewed interest in V. Perhaps this year will be the year.

    I'll make certain to send a signed request as specified, but I'll avoid doing so until I've actually finished reading and studying the relevant software first.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre lang="" line="" escaped="" highlight="">


MANDATORY: Please prove that you are human:

91 xor 19 = ?

What is the serial baud rate of the FG device ?


Answer the riddle correctly before clicking "Submit", or comment will NOT appear! Not in moderation queue, NOWHERE!