[IPython-dev] [jupyter] Re: IHaskell on Jupyter

Matthias Bussonnier bussonniermatthias at gmail.com
Thu Mar 26 11:20:57 EDT 2015

Le 26 mars 2015 à 06:00, Doug Blank <doug.blank at gmail.com> a écrit :

> On Thu, Mar 26, 2015 at 8:30 AM, Nicholas Bollweg <nick.bollweg at gmail.com> wrote:
> Congrats!
> What is the PR (repo, requirements) process for getting something up on try.j.o? I've been bumbling around with getting hy_kernel ready for a real-ish release, and would love to be able to get it up there.

PR against https://github.com/jupyter/docker-demo-images

IIRC deployment is automatic. Otherwise it should be made automatic :-)

> Would love to make try.jupyter.org a general place for trying different kernels! Now would be a great time to talk about some conventions. I can think of a couple:
> 1. First help link for a kernel: "Getting Started" with simple code examples, and pointers to full doc on using language in notebook

We have `Welcomme <Language name>` each language can do its notebook !

> 2. Another help link: "Installing X Kernel" with instructions on how to install kernel on your own system

I would put that in the welcome notebook too. 

> Also, what criteria for including a kernel on try.jupyter? 
> Easy install?

I guess if you can install with Docker... and the kernel not dead in the water you could install it.
But depends on community and if people help with the deployment.

> Robust?

Robust to what ??

> Specific licenses only? 

We don't derive anything from the project so I don't see any restriction on Licenses

> Commercial kernels? 

Well, this is hosted for free[1], so commercial project might be required
some "contribution" to get hosted to be fair.

> How will new versions of a kernel (or its dependencies) get included?

PR. But depends on community and if people help with the deployment.

> How often will it be updated?

Depends on community and if people help with the deployment.
And on the rhythm of PR. 

Does that make sens ?

Back to [1], the server is on a machine we "borrow" from Rackspace. 
So in the end what get into the server have to be vetted by Rackspace.
We do our best for "Fair" usage, and not to make them un-happy. 

It would also be great to have a nice website, all responsive 
and good design that list the kernels and make some better promotion of
the notebook. 

If any of you want to do that, or have a web designer student
looking for a project :-)

In conclusion, the project is to everyone as soon as you participate. 
And we'll be happy to give you more rights on github if we see you
making contribution/maintenance relatively often.


> -Doug
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150326/ef54ee8f/attachment.html>

More information about the IPython-dev mailing list