Timeline for How can an AGPL web application allow proprietary plugins?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2022 at 14:11 | vote | accept | Jérôme | ||
| May 23, 2022 at 10:40 | answer | added | MadHatter♦ | timeline score: 3 | |
| May 20, 2022 at 13:39 | comment | added | Martin_in_AUT | It is difficult for me to come to a definitive assessment of your situation. You will have to judge yourself. There is another part of the Q&A you might be interested in: gnu.org/licenses/gpl-faq.html#LinkingOverControlledInterface , you might want to add this, just to be on the safe side. | |
| May 20, 2022 at 9:49 | comment | added | Jérôme | Thanks. The backend plugins would extend the backend to add DB tables and REST resources. The frontend plugins would add web pages to the frontend. Your comment sounds like the plugins are separated from the app by the API, or maybe I'm misunderstanding. | |
| May 20, 2022 at 8:56 | comment | added | Martin_in_AUT | Thank you for asking, and thank you for already having done some research yourself (too few people do that). It is not entirely clear to me how close and intimate the REST API calls will be. There is likely no b/w answer to your question, but you might want to have a look at the GPL FAQ, and you might be able to build your API in a way to allow what you plan to do. | |
| May 20, 2022 at 8:50 | history | edited | Jérôme | CC BY-SA 4.0 |
added 571 characters in body
|
| S May 20, 2022 at 8:34 | review | First questions | |||
| May 20, 2022 at 13:58 | |||||
| S May 20, 2022 at 8:34 | history | asked | Jérôme | CC BY-SA 4.0 |