-
Notifications
You must be signed in to change notification settings - Fork 15
Switchting to more permissive license #51
Comments
Hi Thorsten, Thank you for considering Phoenix. At this point, we've decided to stick with AGPL to maintain a coherent project over a very long term. I'm sure we can find way to make integration easy without license issues. @KernelDeimos and @AtkinsSJ, could you chime in on this? |
Can you be more specific in how you're wanting to use Phoenix? EDIT: Whoops, I misread and thought this was the Puter repository, not Phoenix. Still good to know what your intended use is though. |
JupyterLite (demo) is a Jupyter Distribution that runs completely in the browser. The individual kernels, like a python kernel, are compiled to wasm and can therefore run in the browser. I want to add a bash-like shell/terminal which operates on some virtual filesystem. So the phoenix shell would be used to manipulate files via command like tools. These files would then be accessible in a jupyterlite kernel. |
Thanks for your quick answer. I would assume a licence like MIT would bring in more external contributors / free labour. For instance I would be happy to contribute. I am maintaining a wasm distribution of many conda-packages (https://github.com/emscripten-forge/recipes). Commands like python or other wasm compiled binaries could run in the phoenix shell. Greetings |
Hi there,
I came across this project on HackerNews and I am particularly interested in using it in projects like JupyterLite. To do this, a more permissive license would be required. Would you consider switching to a more permissive license like MIT?
Thanks for considering this request!
Best regards, Thorsten
The text was updated successfully, but these errors were encountered: