HI Florian On Fri, Jan 8, 2016 at 12:42 AM, Florian Apolloner <f.apollo...@gmail.com> wrote:
> Hi Yamila, > > On Thursday, January 7, 2016 at 2:22:21 PM UTC+1, Yamila Moreno wrote: >> >> I just wanted to let you know that me or anyone in our team would be glad >> to answer any question about the product, saas or installation, migrating >> issues or anything related. No strings attached, of course!!! >> > > I personally do actually have one question. I was looking through your > source code and realized that you are apparently importing DRF and changing > a few parts and relicensing it as AGPL. I am not a lawyer and you might > actually be allowed to do that, but what about contributing to DRF back > instead? Your AGPL code (again I am not a lawyer and might be wrong), > actually forbids Tom to take your changes back into DRF… That said, the DRF > license requires you to retain the copyright information, either I missed > it or you did not retain it. > The DRFv2 (as DRFv3) as far as I know is licensed using MIT permissive license that does not impide take the source and re-license it under other license. taiga.io initially have started using the DRF just like a dependency but over time the dev-team found the needs monky-patch many and many parts of it... Later, the dev-team have decided just include it in the code base and remove useless (for taiga) code and add additional features. Much of code/improvements is contributed back to the DRF (v2), other as third party packages and some other is no, because the approaches are diverged and the changes are just to much opinionated/coupled to the taiga usage. I hope I have solved your question. Regards. Andrey > > Do not get me wrong, but if half what I wrote is true; I'd personally be > very worried if Django switched to Taiga, given the signal that this would > send to our userbase (might be just me though). > > Cheers, > Florian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/4f189a3c-9011-4b06-994f-ec4b1a346c9c%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/4f189a3c-9011-4b06-994f-ec4b1a346c9c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Andrey Antukh - Андрей Антух - <n...@niwi.nz> http://www.niwi.nz https://github.com/niwinz -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAOQnsABOv9-o8h1Cstv4UU4SEFpebaiQoJf3ADA9PdX1QaiQsQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
