68
you are viewing a single comment's thread
view the rest of the comments
[-] thingsiplay@beehaw.org 0 points 2 days ago

Right, but the other fork became its own project. I have no problem with it. As long as the original code license is not changed.

[-] LeFantome@programming.dev 1 points 2 days ago

The original code remains available under the original.

Any proprietary code would have to be code that was added on top of that.

You always have the ability to keep using the Own Source code. That is a freedom you have.

If you decide that proprietary version is “better” and choose to use that, well that is a freedom you have. But now you have accepted a proprietary license. Your choice.

[-] 7dev7random7@suppo.fi 1 points 2 days ago

Any proprietary code would have to be code that was added on top of that.

That generalization is wrong. If the license does not state that freedom one can revoke said thing. The author(s) can change the entire license.

If not stated you may be able to fork off a previous version. Depending on the CLA (or its absence) you may have to speak with any contributor prior to publishing your fork!!!!

[-] 7dev7random7@suppo.fi 1 points 2 days ago* (last edited 2 days ago)

Good luck picking another license than GPL for this requirement.

this post was submitted on 13 Jun 2025
68 points (98.6% liked)

Rust

7063 readers
21 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS