Skip to content
This repository has been archived by the owner on Apr 13, 2024. It is now read-only.

Switchting to more permissive license #51

Open
DerThorsten opened this issue Mar 6, 2024 · 4 comments
Open

Switchting to more permissive license #51

DerThorsten opened this issue Mar 6, 2024 · 4 comments

Comments

@DerThorsten
Copy link

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

@jelveh
Copy link
Contributor

jelveh commented Mar 7, 2024

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?

@AtkinsSJ
Copy link
Contributor

AtkinsSJ commented Mar 7, 2024

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.

@DerThorsten
Copy link
Author

DerThorsten commented Mar 7, 2024

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.

@DerThorsten
Copy link
Author

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?

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants