Proper license

[adelevie]

No description provided.

[fbennett]

We seem to be on track for BSD. Mike plans to make the adjustment on CourtListener, and the license can be mapped through as appropriate on Walverine. I'll be happy to make a pull request covering the change.

[adelevie]

Great. Thanks, @fbennett.

[mlissner]

Looks like you've got the Affero license as of now. That's the strictest that we've got on any of our code. If you leave that, you'll be all set and rock solid, legally speaking.

I just re-licensed constants.py, so it is BSD as of a moment ago. I don't know how much code other than that you guys have from CL, but if that's all you have, you could license this as BSD. If not, then Affero is probably more appropriate.

I'm considering relicensing the rest of the citation code as BSD, but I don't think I can do so with out the developer's consent. Besides that though, I like the Affero license, as it gives us protection against closed-source usages of the code (a good thing!)

[mlissner]

Oh, and thanks for taking this seriously. We do appreciate it.

[adelevie]

Not a problem. I'm just a caretaker of your great work, and I'm happy to accommodate your licensing needs.

[mlissner]

Excellent. Glad license-talk can be so easy, and thanks for the awesome tool.

I'm tempted to add it to our API, actually, but haven't had a chance to check it out properly. A few people have already asked for something like this in API form.

[adelevie]

What would be added to the API? User POSTs text, API returns citations?

[mlissner]

Something like that, yeah.

On Tue, Nov 26, 2013 at 3:41 PM, Alan deLevie [email protected]:

What would be added to the API? User POSTs text, API returns citations?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-29346627
.

[adelevie]

👍

Though it still is always nice to be able to run such a potentially-processor-intensive function on my own equipment.

[mlissner]

Exactly...hence our not having done it just yet despite people wanting
it....

On Tue, Nov 26, 2013 at 3:43 PM, Alan deLevie [email protected]:

[image: 👍]

Though it still is always nice to be able to run such a
potentially-processor-intensive function on my own equipment.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-29346764
.

[konklone]

Just wanted to see if there was any actionable stuff here. Is preventing closed-source use of the citator really a good thing? I'd love to get closed-source companies to use this citator, and mine, and for that to lead to their contribution and investment in the code -- thus improving it for all the open-source uses.