merge with dask-examples

[martindurant]

Would it make sense to include these notebooks as a directory in dask-examples, to take advantage of HTML rendering, CI tests and binder integration? Currently, the setup depends on conda env or a docker file.

The alternative would be to implement all that stuff here, which seems like a lot more work.
Thoughts, @mrocklin ?

[mrocklin]

Seems like a cheap solution to me. The only constraint I suppose would be that they would have to have the same software environment.

…

On Thu, May 23, 2019 at 12:54 PM Martin Durant ***@***.***> wrote: Would it make sense to include these notebooks as a directory in dask-examples, to take advantage of HTML rendering, CI tests and binder integration? Currently, the setup depends on conda env or a docker file. The alternative would be to implement all that stuff here, which seems like a lot more work. Thoughts, @mrocklin <https://github.com/mrocklin> ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#88?email_source=notifications&email_token=AACKZTH3FJIJ4C7Y2EJC74LPW3K4TA5CNFSM4HPI45QKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVQ2PHA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACKZTCLHED4JR5S76ZJBG3PW3K4TANCNFSM4HPI45QA> .

[mrocklin]

Also, stylistically it might be nice to have a dedicated page tutorial.dask.org, but that might be future work. I think the question is "how hard is it to duplicate the system behind examples.dask.org?" If it's not that hard, then I would go ahead and make a separate standalone system. If it's annoying, then I would go with a unified system? Just my thoughts though. I don't think I have any particular experience here over others.

…

On Thu, May 23, 2019 at 1:58 PM Matthew Rocklin ***@***.***> wrote: Seems like a cheap solution to me. The only constraint I suppose would be that they would have to have the same software environment. On Thu, May 23, 2019 at 12:54 PM Martin Durant ***@***.***> wrote: > Would it make sense to include these notebooks as a directory in > dask-examples, to take advantage of HTML rendering, CI tests and binder > integration? Currently, the setup depends on conda env or a docker file. > > The alternative would be to implement all that stuff here, which seems > like a lot more work. > Thoughts, @mrocklin <https://github.com/mrocklin> ? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#88?email_source=notifications&email_token=AACKZTH3FJIJ4C7Y2EJC74LPW3K4TA5CNFSM4HPI45QKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GVQ2PHA>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AACKZTCLHED4JR5S76ZJBG3PW3K4TANCNFSM4HPI45QA> > . >

[martindurant]

If it's not that hard, then I would go ahead and make
a separate standalone system. If it's annoying, then I would go with a
unified system

I don't know yet, but not as simple as I might have thought. It occurs to me, though, that simply having the separate repos and page roots may well be confusing for newcomers (they don't even refer to one-another).