Question about pushing to maven

[ghost]

I would like to put work using material scancode-toolkit.
The work is in java.
So the best case is to put basic code in maven (resource).

The part im interested in is scancode-toolkit/src/licensedcode/data/licenses.
I would but into a project: openCage/scancode-toolkit-licenses/

To get into maven the artifact name would be: de.pfabulist:scancode-toolkit-licenses.
The license cc0-1.0 the authors from NOTICE file.
In the Readme would be link to the specific checkin of original and formulation
that this is just maven suitable copy.

Does that sound ok ?
Should I use rather use everything ?

[pombredanne]

That's a great idea. There is already a ticket for this which is #477 to get a separate repos for the licenses data. My idea for this would then to have there multiple package manifests (for Maven, Ruby, JS, Python, Debian, RPMs, etc) such that the same dataset can be made available in multiple repos and published from one place to these repos. This would help a lot on the Debian side per #477
Also this would make the licenses more visible and easier to reuse per #57

Would this work for you?

[ghost]

There is now a new github project https://github.com/openCage/scancode-toolkit-licenses.

Its layout is data in one dir, programming specific code in an other dir.
This is java only at moment.
A version for scancode license data is published to maven central.

What do you think?

Who can help with other languages / packages / os packages ?

[pombredanne]

@OpenCAGE that's great! so about adding more packaging formats (rather than more language per se, since adding a packaging for Python or Ruby would not mean adding Python or Ruby code IMHO) .... let me think a bit about it. I might want to have a format with less nested directories. And also have the manifests (pom, setup.py, package.json, etc) at the root of the repo rather than in sub dirs. But these are minor. Give me a couple days to come back with concrete suggestions

[pombredanne]

It looks like opencage has gone awol ... closing this then