RhodeCode Goes Open Source

Re:RhodeCode Goes Open Source by stephenr on Wednesday May 25, 2016 @08:01AM (#11769111)

So yet again the FAQ has conflicting information: 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.

[ Parent | on HN ]

Re:RhodeCode Goes Open Source by marcinkuzminski on Wednesday May 25, 2016 @08:15AM (#11769194)

Mind sharing why AGPL is not a good fit for you ?

[ Parent | on HN ]

Re:RhodeCode Goes Open Source by stephenr on Wednesday May 25, 2016 @08:57AM (#11769407)

I think this is a decent summary. http://stu.mp/2010/02/why-i-hate-the-agpl.html

[ Parent | on HN ]

Re:RhodeCode Goes Open Source by ergo14 on Wednesday May 25, 2016 @09:32AM (#11769595)

This 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.

[ Parent | on HN ]