3 ms·
So yet again the FAQ has conflicting information: https://rhodecode.com/faq#communitylicense https://rhodecode.com/faq#communitylicense Being AGPL means my int
by stephenr 10y ago
So yet again the FAQ has conflicting information: https://rhodecode.com/faq#communitylicense https://rhodecode.com/faq#communitylicense
Being AGPL means my interest in this is now extinguished anyway, but the information on the site doesn't inspire confidence either.
- marcinkuzminski 10y agoMind sharing why AGPL is not a good fit for you ?
- stephenr 10y agoI think this is a decent summary. http://stu.mp/2010/02/why-i-hate-the-agpl.html http://stu.mp/2010/02/why-i-hate-the-agpl.html
- ergo14 10y agoThis is interesting, especially this part: > you must also publicly release any code that connects to an AGPL piece of software over a network. I fear the day that an HTTP server is built using AGPL. Think about it. I don't think this is true, which part of the AGPL license implies that? It is my understanding that AGPL means that even if you don't redistribute the software with that license - you still need to put the sources online. Nothing about interaction of 3rd part software. After all database servers are released under AGPL - like mongoDB among the popular ones.