1. As I said, I'll keep code derived from SymPy Gamma BSD licensed. To be more specific, all python code under logic directory, factordiagram.js, plot.js (and CSS, if anyone cares). So there will be no barrier for moving code bidirectionally. For Pyodide and new UI part, since no one in SymPy core team has knowledge/time/willingness to maintain, I don't see benefits to keep them BSD. Moreover, most part of the current SymPy Gamma is 9 years old. Could an unmaintained project be hurt by being forked and re-licensed?
Please notice, SymPy is a library, while SymPy Gamma is a service for end user. I respect John Hunter as matplotlib author. Matplotlib is also a library, thus being BSD-style do benefit it as he said. However, an end user application can only be reused/redistributed as another application, and a service can only be reused/redeployed as a service. Once being permissive, there is far less interest/necessity for re-users to contribute back an application/service than a library. So to protect the project, keeping the core permissive but application/service viral is very common in open source community. That's what I believe. Making it AGPL is very different from what the companies I accuse did, because AGPL is an OSI-approved Free and Open Source license. The reason that it prevents anybody to use it, is their prejudice towards (A)GPL or their compromise to proprietary software vendors. It's not AGPL's fault. Even though SymPy Gamma can be self-deployed, SymPy team still pay to deploy it. We all know the importance of having an available service for users to directly use. The new project still needs a server for hosting static files, including compiled packages. As long as there's need for that, AGPL is a better fit than GPL. 2. I don't care that much about server side data collection, or the proprietary server platform itself, or Google the company. I myself would like to host the project on vercel. I just don't like the way that browser fetches the Google Analytics and run it on client. I simply want to gain control of what code runs on my device, whenever I could. 3. Though contributing to SymPy, I personally prefer the No Code of Conduct that diofant chooses. That was one of the reason Sergey B Kirpichev started the fork. It is for me too. I saw some people outside SymPy team that interested in migrating to Pyodide at issue 83 of sympy live. That was also the place I got the idea and decided to work on this. Hopefully they are not so busy as I am (I'm working from 9am to 8pm 5 days). And, thanks for your initial answer. I'll keep working and release it soon. I also don't want people pass this conversation by, think "hey you say so much words against the community's philosophy, but where is your code?" for too long. Qijia Liu -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/d7ed5d30-de51-43f8-805c-fcea5b632b49n%40googlegroups.com.
