New repository format?

[jcarbaugh]

I'm considering changing the format of the repo to something like:

licenses.js
templates/
    - headers/
    - license-id.txt
    - ...

licenses.js would be a JSON file with a description of the available licenses. Each license would have the following fields: id (slug), full name, version, text file name, header file name. I'm considering something along the format of:

{
    id: 'a-license',
    name: 'A Generic License',
    versions: [
        {
            number: '2.1',
            text: 'a-license.txt',
            header: 'a-license-header.txt',
        }
    ]
}

Maybe having separate folders for the header and text files are unnecessary with this config file? A user could specify a specific version as a-license@2.1 or use the newest (or only) version with just a-license.

Thoughts?

[Daniel1of1]

In general agree.. also per license a description property? and original source URL?

on versioning I think there is possibility of confusion for things like BSD2/3 (clause) but still think its ok.

[jcarbaugh]

+1 on adding source URL, just for the sake of documenting where someone picked up the license if there is any confusion. I'm not sure what description would hold. What were you thinking?

BSD2/3 wouldn't really be versions... so there would be bsd2 and bsd3 but only one version of each. Versions would only happen with things like gpl... gpl@2, gpl@2.1, gpl@3, or just gpl as an alias for gpl@3. We could also have aliases so bsd would reference bsd3 by default.