Ask HN: ALGPL-Like License?
We have a couple of internal libraries we would like to open source. * We'd like to receive patches back if you modify it to: distribute it (LGPL-like) or offer it as part of a service (AGPL-like) * We don't care about the rest of the app you use it in (LGPL-like, unAGPL-like) * We want businesses to use/compile verbatim binaries/source without fear they need to open source their proprietary bits * We want businesses to have the right-to-repair and run modified copies internally without fear they need to open source their proprietary bits, but they do need to publish the modifications to the library Is there an OSI Approved license, or a license from a commonly used project we could adopt? 0 comments on Hacker News.
We have a couple of internal libraries we would like to open source. * We'd like to receive patches back if you modify it to: distribute it (LGPL-like) or offer it as part of a service (AGPL-like) * We don't care about the rest of the app you use it in (LGPL-like, unAGPL-like) * We want businesses to use/compile verbatim binaries/source without fear they need to open source their proprietary bits * We want businesses to have the right-to-repair and run modified copies internally without fear they need to open source their proprietary bits, but they do need to publish the modifications to the library Is there an OSI Approved license, or a license from a commonly used project we could adopt?
We have a couple of internal libraries we would like to open source. * We'd like to receive patches back if you modify it to: distribute it (LGPL-like) or offer it as part of a service (AGPL-like) * We don't care about the rest of the app you use it in (LGPL-like, unAGPL-like) * We want businesses to use/compile verbatim binaries/source without fear they need to open source their proprietary bits * We want businesses to have the right-to-repair and run modified copies internally without fear they need to open source their proprietary bits, but they do need to publish the modifications to the library Is there an OSI Approved license, or a license from a commonly used project we could adopt? 0 comments on Hacker News.
We have a couple of internal libraries we would like to open source. * We'd like to receive patches back if you modify it to: distribute it (LGPL-like) or offer it as part of a service (AGPL-like) * We don't care about the rest of the app you use it in (LGPL-like, unAGPL-like) * We want businesses to use/compile verbatim binaries/source without fear they need to open source their proprietary bits * We want businesses to have the right-to-repair and run modified copies internally without fear they need to open source their proprietary bits, but they do need to publish the modifications to the library Is there an OSI Approved license, or a license from a commonly used project we could adopt?
Hacker News story: Ask HN: ALGPL-Like License?
![Hacker News story: Ask HN: ALGPL-Like License?]()
Reviewed by Tha Kur
on
October 10, 2021
Rating:
No comments: