There is, but it's really off topic for the Open Source Initiative's license discussion list, since the license in question would be very from compliant with the OSD :-)
Actually, now that I read your question more closely, the answer to #2 is probably 'no'. If someone authors a contribution to your software, they own the copyrights on that contribution, so it will be challenging to control what they are allowed to do with that code. If your license attempts to restrict usage of code written by third parties (in cases where the the code is a derivative work of your work), then the contributor wouldn't even be able to push their code to GitHub to send you a Pull Request, since doing so requires providing GitHub, Inc. permission to publish the code themselves. On Thu, Sep 5, 2019 at 4:21 AM ALIEN Quake <[email protected]> wrote: > > Hello, > > I'm the one and only author of the specific software. The software it's > proprietary. I would like to release source code and allow people to > contribute to it. But at the same time, I would like to: > > 1. Prevent the usage of the original code to be used elsewhere, for eg: > inside very similar software, practically a copy with minor > differences/different logic. > > 2. Prevent the usage of the all future contributions which comes from the > Pull Requests to be used elsewhere, for eg: inside very similar software, > practically a copy with minor differences/different logic. > > Is there any kind of licensing which work like that? > _______________________________________________ > License-discuss mailing list > [email protected] > http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org _______________________________________________ License-discuss mailing list [email protected] http://lists.opensource.org/mailman/listinfo/license-discuss_lists.opensource.org
