License Update suggestions about licenses

[hlainchb]

We have an process for submitting new licenses. it's documented here: http://opendefinition.org/licenses/process/

…

On Thu, Nov 24, 2016 at 5:03 AM, Ludee ***@***.***> wrote: New licences are added by pull request? No discussion needed? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAJkPzBJWo5pnx2CJ-coiA4iRnPw68ssks5rBYssgaJpZM4DcYCv> .

-- Herb Lainchbury, Dynamic Solutions 250.704.6154 http://www.dynamic-solutions.com

[mlinksva]

Rather than removing, probably the status field should be updated. Feel free to submit a pull request doing that and adding those additional licenses. Thanks!

[LibrarPotter]

I see that I can replace "active" with "retired", but I cannot tell which files to update as there appear to be 3 places they exist:
licenses/licenses
licenses/licenses/groups
licenses/licenses/jsonp
Do you have to change all three for every update?
I'm still fairly new to Github, so I'll look into making a pull request that matches your schema. Thanks!

[mlinksva]

Just change the one in licenses/licenses.

The other two are generated by the script bin/deploy.py. If you want to run the script and add the changes it makes to your commit, go ahead. You may have to install some dependencies first (documenting that would be another great commit ;-)) so feel free to just change the one file and I'll run the script.

[Ludee]

New licences are added by pull request? No discussion needed?

[mlinksva]

@Ludee @hlainchb two different things. http://opendefinition.org/licenses/process/ is for Open Definition conformance. Adding records to this repo is indeed done by pull request -- and a pull request is a venue for discussion.

Looks like @LibrarPotter made some of the changes suggested in #52 and #53. I'm closing this; if anyone wants to make further changes they can open discrete issues or pull requests.