Timeline for Compatibility of RPL (Reciprocal Public License) with other licenses
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 13, 2018 at 8:08 | vote | accept | YetiCGN | ||
| Dec 13, 2018 at 7:04 | comment | added | Bart van Ingen Schenau | See RPL section 6.4(c): "[...] You must notify the software community of the availability of Source Code to Your Extensions within one (1) month of the date You initially Deploy". This is a separate requirement from the manner of distribution, which might be construed as a further restriction if you want to be really picky, but that would probably only fly when you distribute the software as part of a 'consumer product' (a.k.a embedded on a physical device). | |
| Dec 13, 2018 at 6:57 | comment | added | Brandin | @BartvanIngenSchenau Where does the RPL say you must "inform the community"? It does say you must use an "Electronic Distribution Mechanism" for distribution to "the software community," which is more specific and more nit-picky than the LGPL's distribution requirement, but I don't see that the two requirements would be impossible to fulfill at the same time. | |
| Dec 12, 2018 at 18:44 | comment | added | Bart van Ingen Schenau | It is a solid analysis, but I don't agree that the LGPL and RDP are compatible. In particular the requirement from the RDP to inform the community is a restriction that is incompatible sith section 7 of the GPL (and by inclusion also the LGPL). | |
| Dec 12, 2018 at 14:40 | history | edited | Brandin | CC BY-SA 4.0 |
added 780 characters in body
|
| Dec 12, 2018 at 14:21 | history | edited | Brandin | CC BY-SA 4.0 |
added 32 characters in body
|
| Dec 12, 2018 at 14:14 | history | edited | Brandin | CC BY-SA 4.0 |
deleted 6 characters in body
|
| Dec 12, 2018 at 14:06 | history | answered | Brandin | CC BY-SA 4.0 |