Hacker News new | ask | show | jobs
by dataflow 1479 days ago
May I suggest you don't license the work in a way that allows it to be commercialized without your explicit permission and handsome compensation to you and any other contributors. You'll need this to be sustainable and it'll be incredibly frustrating if a company de-facto hijacks the development and takes it in a direction you don't expect or want.
4 comments

Oh but then half of HN will complain about how that's not truly open according to a dictionary definition thus automatically becomes untrustworthy and they won't touch it with a ten foot pole. (/s)

Jokes aside, technically I don't disagree on the "dictionary definition" thing there... but it's interesting how the current landscape has shifted and now more control for the developer starts to become a common interest between "hackers".

The original OSS licenses protected users (as in, final users) from predatory devs; nowadays, small devs and hackers talk in their forums about how to preemptively protect themselves against predatory users (as in, not final users, but other bigger devs that leech on other's work)

You're confusing closed source blobs and proprietary licenses with restrictive but truly open licenses like AGPL which would also protect the authors.
It doesn't look like we can say "licenses like AGPL". It's more that AGPL is basically the only one in that vein. Remove the A, if you please, but that's pretty much it in terms of variety.

On the other hand, reading HN over time I also got the idea that *GPL has been tried with the intention of avoiding abuse, and it failed several of those intentions. I now regret not having taken note each time I saw comments in that regard, for quick references.

But there are big cases, not only small comments spread over HN; I guess the stereotypical one is MongoDB, which tried the AGPL path and in the end was not satisfactory enough for them.

The problem is not with the GPL. The GPL is just as enforceable as any other proprietary license. The difference is that these amateur projects often don't have the resources to fight infringement.
If the problem is that there are no resources to fight infringement, then how would changing the license help at all?
I was addressing what seems to be an unfair criticism of the GPL, and not claiming that the license would help. In fact your comment reinforces the point - even a proprietary license wouldn't help with no legal backing.
You have a legal leg to stand on that some lawyer might potentially fight for you, that's still better than just giving up and surrendering your weapons.
In this case I don't think AGPL does what you want; it's oriented towards SaaS but this project is a bootloader.
Sure, hence the "like". They could create or use a license that is fully open but prevents commercial use without a license.
Such a license is not possible.
How exactly is that? There are plenty of licenses that don't allow commercial usage.
I don't generally like restrictive licenses but in this case we're taking about running closed, commercial software on closed, commercial hardware. It makes sense to use a GPL to prevent one of those companies from taking all of that hard work and incorporating it back into their platforms for free.
Mine was just a lighthearted reflection on the issue, but in general I'm supportive of the copyleft ethos. And yes, in this case it would make a lot of sense.

Actually my first reaction was to think, "Why are Microsoft themselves not doing this job?"

I'll definitely take this into account thanks for bringing it up! Licensing is something I've thought about a bit before starting, right now since m1n1 (the hypervisor I'm iterating on) is MIT licensed for the most part, I'm inheriting that license too for my fork of m1n1 (i'll mainline the changes btw! need to work with marcan once they're done), but as the project goes further I'll definitely consider the question of licensing again.
It'll just be sad to see apps like VMware or Parallels release a new version claiming they made a breakthrough after you've made some milestone release...
IANAL but I'd like a license that goes something like this:

Companies: If you are working for a company/corporation/profit-generating entity, or otherwise intend to sell or use such code derived from this repository for profit-generating purposes, you shall not be permitted to use any of the source code herein until you email me (author email here) and we can come up with the appropriate terms and conditions for your use case.

Everyone else: Have fun!

Obviously it's missing some necessary edge cases and disclaimers, but yeah.

I mean, that's basically what CC-BY-NC is. Any licence that prohibits commercial use does not prohibit an alternative commercial licence being negotiated.
I would love a reference to a formalized version of this..

Edit: Found Polyform! https://polyformproject.org/what-is-polyform/

Found one - Polyform

https://polyformproject.org/what-is-polyform/

> PolyForm is a project to draft and make freely available plain-language source code licenses with limited rights. > > Source code licenses with limited rights? What does that mean? Many software developers want to make software available under source code licenses that grant some, but not all rights. Some licenses that have been released before include the Commons Clause, Elastic and Confluent licenses, and others. These licenses grant broad rights, including source code access, but reserve some rights to the licensor.

Imagine you license a word processor this way, would it then be a violation to use that word processor to edit your resume?
Microsoft Office does that: https://answers.microsoft.com/en-us/msoffice/forum/all/licen...

It might be technically a violation, but nobody’s going to send a license audit to a private citizen.

Technically, yes! A perfect example of an edge case that I knew would be difficult to find.

Very clever!

To be clear I'm not just trying to be a pedant and poke holes in your legalese here. I'm trying to show that it is genuinely hard to draw a line between what kinds of profit seeking are morally acceptable and what are not. People generally deserve to seek out prosperity, and I suspect in most cases trying to differentiate between these cases will end up being a game of "people richer than me have to pay, people poorer get it for free" which is way less morally justified than the current situation with software licenses.
Do this, but make allowances for small businesses under a certain MRR.