[IPython-dev] Proposal: soft moratorium on re-architecting for 5.0
Matthias Bussonnier
bussonniermatthias at gmail.com
Mon Jun 29 09:43:54 EDT 2015
>
> In another message on this thread, Min suggested having a 5.x branch for further development, like the phosphor notebook. For now, I think the phosphor notebook can proceed as a separate project - it's totally a front-end thing at this point, and we're doing enough code clean-up and rewriting from js to typescript that I think it's all right to start in a fresh repo. Which brings up another point: can we make an official Jupyter repo for the phosphor notebook work, rather than using my personal repo? I'm happy to continue hosting https://github.com/jasongrout/phosphor-notebook/ <https://github.com/jasongrout/phosphor-notebook/> in my personal github account for the time being, or set up a temporary organization so we can collaborate more effectively, but I think it would make more sense to bump it up to an experimental repo in the jupyter github organization, developed in parallel with the current notebook.
Done, Jason you are admin, I **think** you can all people to the team.
I’m hopping on my plane, like in 5 min. Feeling like Linus writing a rc release not from airports as often.
(I haven’t forked your to make sure it appears as a root repo)
Quick +1 on typescript the type aliases allow you to so
define Path extends String {}
Which auto produce nice docs with meaning instead of just foo(a:string, a:string) you get foo(a:Path, b:NotebookName)
which is really good for docs.
See you Tuesday morning on dev meeting, which for once should **not** be public, as we are trying BlueJeans.
--
M
>
> Thomas, one thing to consider is that us working on a phosphor notebook doesn't preclude interested people from enhancing the existing notebook in the short term. We'd like the phosphor notebook to get to a comparable state with the current notebook as quickly as possible, but it will still take some time.
>
> Also, I totally agree with Thomas that dogfooding the notebook (and watching/helping others actually use it to get work done) is *extremely* important to understanding what we want here. And I also agree with others on this thread that documentation is sorely lacking. We'll be working on that in the phosphor notebook as we go along too.
>
> Thanks,
>
> Jason
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150629/9f08952f/attachment.html>
More information about the IPython-dev
mailing list