You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of writing some go packages which I would like to open source, however this has the problem of selecting a license.
I would want strong copyleft if someone were to change my packages and only my packages, so they can use it in closed source programs. The best license I found so far is MPL v2.0, but this has a loophole, it is a per file license. So someone could do something like the following and not release their codes:
I'm not a lawyer, but I believe the license used by Go, as well as by many 3rd party Go packages, is compatible with use in closed source programs just fine basically by simply adding the original text of the LICENSE file somewhere visibly with[in] the proprietary product.
But there isn't one that assures improvements/changes to one's package would be released and at the same time allows for closed source usage. I feel like many packages would benefit from such a license since choosing one or the other is a very difficult choice.
@AlexRouSg It's a fine idea but this is not the place for it. To draft a new license you need a lawyer. We are programmers. And there is nothing Go-specific about the idea.
I am in the process of writing some go packages which I would like to open source, however this has the problem of selecting a license.
I would want strong copyleft if someone were to change my packages and only my packages, so they can use it in closed source programs. The best license I found so far is MPL v2.0, but this has a loophole, it is a per file license. So someone could do something like the following and not release their codes:
So I propose go should have it's own license that works on the package level.
The text was updated successfully, but these errors were encountered: