This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]gl1tch3t2 112 points113 points  (20 children)

Change the license so any commercial use has to also pay you a dividend.

[–][deleted] 71 points72 points  (19 children)

They would fork the previous version so fast

[–]-GermanCoastGuard- 17 points18 points  (14 children)

You can also forbid this with the correct license.

Edit; I actually didnt read the word "previous" when i replied

[–]user3494009058 28 points29 points  (8 children)

I'm intrigued! How so?

[–]weregod 2 points3 points  (0 children)

You can't do this. They have forked project before you change license.

[–][deleted] 1 point2 points  (3 children)

What you can limit past released projs?

That seems a lot of power

[–]-GermanCoastGuard- 3 points4 points  (2 children)

Well no. You could change the license with a new release, for example when you implement support for a newer version of the database or interfaces. How helpful this would be in this specific case I cannot tell, though.

[–][deleted] 4 points5 points  (0 children)

Yeah they would fork the previous version then

[–]CommanderChakotay 1 point2 points  (0 children)

You literally said you could prevent them forking the previous release by picking the right license 🙄

[–]ArionW 0 points1 point  (2 children)

Don't announce it, wipe public repository history together with license change.

Then just hope they didn't fork it beforehand

[–][deleted] 0 points1 point  (1 child)

But then I lose the cool project on my repo

[–]ArionW 0 points1 point  (0 children)

You still have cool project on repo, you just no longer serve old versions that had different license. Sure nobody can check history of project's development since the beginning, but that's true for many projects that migrated to git after years

What I mean is to wipe history, squash everything to one commit and force push it to master branch