<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class=""><br class="">
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 <a class="moz-txt-link-freetext" href="https://github.com/jasongrout/phosphor-notebook/">https://github.com/jasongrout/phosphor-notebook/</a>
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.
<br class=""></div></div></blockquote><div><br class=""></div><div>Done, Jason you are admin, I **think** you can all people to the team. </div><div>I’m hopping on my plane, like in 5 min. Feeling like Linus writing a rc release not from airports as often. </div><div>(I haven’t forked your to make sure it appears as a root repo) </div><div><br class=""></div><div><br class=""></div><div>Quick +1 on typescript the type aliases allow you to so </div><div><br class=""></div><div>define Path extends String {}</div><div><br class=""></div><div>Which auto produce nice docs with meaning instead of just foo(a:string, a:string) you get foo(a:Path, b:NotebookName)</div><div>which is really good for docs.</div><div><br class=""></div><div><br class=""></div><div>See you Tuesday morning on dev meeting, which for once should **not** be public, as we are trying BlueJeans. </div><div>-- </div><div>M</div><br class=""><blockquote type="cite" class=""><div class=""><div bgcolor="#FFFFFF" text="#000000" class="">
<br class="">
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.
<br class="">
<br class="">
Also, I totally agree with Thomas that dogfooding the notebook (and
watching/helping others actually use it to get work done) is <b class="moz-txt-star"><span class="moz-txt-tag">*</span>extremely<span class="moz-txt-tag">*</span></b> 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.<br class="">
<br class="">
Thanks,
<br class="">
<br class="">
Jason
</div>
_______________________________________________<br class="">IPython-dev mailing list<br class=""><a href="mailto:IPython-dev@scipy.org" class="">IPython-dev@scipy.org</a><br class="">http://mail.scipy.org/mailman/listinfo/ipython-dev<br class=""></div></blockquote></div><br class=""></body></html>