News for hackers. Stuff that matters.
Re:On paying for software by tomjen3 on Sunday June 10, 2018 @10:17AM (#17278218)
As a general point, please put a license on your contributions if you put them on github. Don't much care what it is, and I don't mind paying, but don't make me do a song and dance to see what your price is.

Especially if you are already giving it away to open source projects -- my bet is most people who see "call me" as a clause will move on, even people you are actually trilled to help.

AGPLv3 would be a decent suggestion, but even your own license wouldn't be bad either.

Re:On paying for software by greysteil on Sunday June 10, 2018 @10:50AM (#17278360)
Totally agree on licenses and transparent pricing in general, but I think you've missed the context here.

If a commercial entity wants to add the core functionality of my product to their offering then there's definitely going to have to be a negotiation first. AGPLv3 wouldn't be appropriate, as the commercial entity's code being open source isn't a material consideration for me.

(The license text I was referring to is here: https://github.com/dependabot/dependabot-core#license. I could hire a lawyer and put a proper, proprietary license on the repo but I'm bootstrapped and don't think it's necessary.)