Merge Clipol.org data into this repo

[kmewhort]

Clipol.org has more extensive metadata for many of this repo's licenses that could be pulled-in. However, the sets of licenses of each don't entirely intersect, so I propose the following:

1. Restructure Clipol.org data:
   (a) Restructure the Clipol JSON definitions so that the fields are a perfect superset of the existing OD data; this will make the clipol data backwards compatible with the OD data. Note that Clipol data is pretty close to a superset already.
   (b) Provide better documentation and definitions for the new fields.
2. Merge Clipol.org data into this repo: export the clipol data to the OD file tree and push.
3. Update Clipol.org website: after clipol data is in the OD repo, make this the primary source for Clipol's data (probably through an automatic import script).
4. Also merge the license texts?

[rufuspollock]

@kmewhort this sound great and I'd be +1

Relatedly would you like commit rights on this repo?

[kmewhort]

Sure, I'll do a pull request when the data merge from Clipol is ready, but commit rights would be useful for me to do any data fixes or additions after that.

[enyst]

Sounds awesome and clipol is cool!

Regarding 4, I'd suggest to not merge text directly, we can set up an external repo to take as submodule. It's also useful on its own for other projects. Could take markdown from okfn/opendefinition, there's also txt I pulled from spdx repo.

[rufuspollock]

@kmewhort you have commit rights :-) ditto for @enyst

[rufuspollock]

@kmewhort @enyst just pinging here. Would love to move this forward :-)

[jonschlinkert]

@kmewhort / @rgrp If/when the clipol.org change are made, would you consider refactoring import logic to node.js/javascript? (would be great for this repo as well).

I'm working on a "project linting and validation" tool that, among other things, will warn you when a license is missing on your GitHub project and offer to fix it. It would be great if I could require this library, or even a wrapper, so that other projects can include this in their build chain. For example, Yeoman generators could use this to populate data based on user prompts g "What license do you want to use?"

[rufuspollock]

@jonschlinkert I'd be +1 on node.js / javascript refactor (its my language of choice). And your suggestion for usage sounds great.

[rufuspollock]

@kmewhort what do you reckon on moving this forward?

[jonschlinkert]

@rgrp sorry I must not have seen the reply last year. I was really interested in doing this, still am. Give me a few days to look over the lib, I'll come back with some ideas. Let me know if you have a wishlist or ideas for what you'd like to see

[rufuspollock]

@jonschlinkert great. At the moment as per #45 i think we probably do the actual website work in the opendefinition repo but we are definitely interested in moving this forward. Take a look at #45 and this and let me know what you think are next steps.