On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:

Hi everyone,

I've been contracted by Synchrotron Soleil to work on the packaging of Jupyterhub and its dependencies. This turns out to about 20 Python packages, most of which should probably go under the Debian Python Team umbrella (although some may go into Debian Science). So I hereby request to be added to the python-team group on salsa. My salsa login is "lolando", and I have read and accept the https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
policy.

Hello

Good to have more people working on jupyter and related tools. Can you
say what the extent of your goal here is? Does it just relate to the
jupyterhub server, spawners, proxy, etc or does your target also include
some work on the jupyter interfaces/core side?

I wonder if it is time to have a distinct jupyter packaging team given
the (perhaps concerningly?) growing size of this software stack [1].

Although I don't know how much time I'll have to work on this in the
near future (new job, etc), my broad goals for this next cycle would be:

* See if we can get jupyterlab packaged. This has an unpleasant list of
javascript dependencies, but now there is a v3 release I hope it
might stabilise a bit.
* Try and get ipywidgets into better shape - it's currently quite out
of date, requiring patches in consuming libraries, and blocked on
javascript problems (many of which are probably in common with
jupyterlab)
* Go through the list of jupyter kernels for other languages and see
if some of these have matured and stabilised and might be good
candidates where the given ecosystem is already well supported in
debian - iruby, ijavascript, gophernotes (go) look like conceivable
candidates.


Gordon


[1]: A quick survey of jupyter in debian:

Core components:

* jupyter-core
* jupyter-client
* jupyter-console
* jupyter-notebook
* jupyter-packaging
* jupyter-server
* jupyterlab-pygments
* jupyterlab-server
* nbclient
* nbconvert
* nbformat
* qtconsole

Kernels and related:

* ipykernel
* ipyparallel
* ipywidgets
* metakernel
* nbsphinx
* octave-kernel
* r-cran-irdisplay
* r-cran-irkernel
* xeus
* xeus-python

There are probably python or other language libraries which are
exclusively jupyter dependencies also.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 5/18/21 10:06 AM, Gordon Ball wrote:

On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:

Hi everyone,

I've been contracted by Synchrotron Soleil to work on the packaging of
Jupyterhub and its dependencies. This turns out to about 20 Python packages, >> most of which should probably go under the Debian Python Team umbrella
(although some may go into Debian Science). So I hereby request to be added >> to the python-team group on salsa. My salsa login is "lolando", and I have >> read and accept the https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
policy.

Hello

Good to have more people working on jupyter and related tools. Can you
say what the extent of your goal here is? Does it just relate to the jupyterhub server, spawners, proxy, etc or does your target also include
some work on the jupyter interfaces/core side?

I wonder if it is time to have a distinct jupyter packaging team given
the (perhaps concerningly?) growing size of this software stack [1].

We're talking about 2 dozen of Python packages. Do you really think
that's a lot?

Cheers,

Thomas Goirand (zigo)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

I have worked on jupyterlab last year.

Le mardi 18 mai 2021 à 08:06 +0000, Gordon Ball a écrit :

On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:

Hi everyone,

I've been contracted by Synchrotron Soleil to work on the packaging
of
Jupyterhub and its dependencies. This turns out to about 20 Python packages,
most of which should probably go under the Debian Python Team
umbrella
(although some may go into Debian Science). So I hereby request to
be added
to the python-team group on salsa. My salsa login is "lolando", and
I have
read and accept the https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
policy.

Hello

Good to have more people working on jupyter and related tools. Can
you
say what the extent of your goal here is? Does it just relate to the jupyterhub server, spawners, proxy, etc or does your target also
include
some work on the jupyter interfaces/core side?

I wonder if it is time to have a distinct jupyter packaging team
given
the (perhaps concerningly?) growing size of this software stack [1].

I don't think it's that big ; notice that the JS team is to be involved
too : the Python part is a piece of cake, with good developers.

Although I don't know how much time I'll have to work on this in the
near future (new job, etc), my broad goals for this next cycle would
be:

 * See if we can get jupyterlab packaged. This has an unpleasant list
of
   javascript dependencies, but now there is a v3 release I hope it
   might stabilise a bit.

The JS part is where the real, deep, pain is.

Here is (a quick translation) of what my personal notes on the matter
are -- they might not be up to date since I haven't worked on it since
november :

BEGIN

- nbconvert needs a more recent nbsphinx ;
- nbsphinx wants a more recent ipywidgets ;
- ipywidgets wants jupyterlab ;
- jupyterlab needs many JS pieces :
* I can get the following going: coreutils, settingregistry, statedb, nbformat, observables, rendermime-interfaces, mathjax2, metapackage, pdf-extension ;
* for ui-components, typestyle would be needed ;
* for vdom, @nteract/transform-vdom would be needed ;
* for vega5-extension, vega-embed is needed ;
- for typestyle, csstype and freestyle are needed.

END

Notice that I initially wanted to update nbconvert, which got me to
look into nbsphinx, which got me to... etc : I took notes as I went
along, and simplified them as I managed to get things in.

I think I stopped after I got lumino at the beginning of november 2020,
for various reasons. Now perhaps I could resume, in which case some coordination will be needed to avoid duplicate efforts.

Cheers,

JP

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 18/05/2021 à 10:06, Gordon Ball a écrit :

On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:

Hi everyone,

I've been contracted by Synchrotron Soleil to work on the packaging of
Jupyterhub and its dependencies. This turns out to about 20 Python packages, >> most of which should probably go under the Debian Python Team umbrella
(although some may go into Debian Science). So I hereby request to be added >> to the python-team group on salsa. My salsa login is "lolando", and I have >> read and accept the https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
policy.

Hello

Good to have more people working on jupyter and related tools. Can you
say what the extent of your goal here is? Does it just relate to the jupyterhub server, spawners, proxy, etc or does your target also include
some work on the jupyter interfaces/core side?

Honestly, I don't know yet.I'm at the prototyping phase, with 20 Python packages (and 20 Node.js packages) that can just about be installed and
end up in something that displays a webpage and allows creating a
notebook. I don't know much more about Jupyterhub, and I guess I'll
first focus on getting packages into shape before widening my scope further.

I wonder if it is time to have a distinct jupyter packaging team given
the (perhaps concerningly?) growing size of this software stack [1].

Although I don't know how much time I'll have to work on this in the
near future (new job, etc), my broad goals for this next cycle would be:

* See if we can get jupyterlab packaged. This has an unpleasant list of
javascript dependencies, but now there is a v3 release I hope it
might stabilise a bit.
* Try and get ipywidgets into better shape - it's currently quite out
of date, requiring patches in consuming libraries, and blocked on
javascript problems (many of which are probably in common with
jupyterlab)
* Go through the list of jupyter kernels for other languages and see
if some of these have matured and stabilised and might be good
candidates where the given ecosystem is already well supported in
debian - iruby, ijavascript, gophernotes (go) look like conceivable
candidates.

Can't help you there, not yet at least.

For reference, the list of Python packages I have so far (thanks to
py2dsc + manual work): backoff escapism python-consul2 certipy pamela onetimepass jupyter-telemetry nteract-on-jupyter nbgitpuller jupyterhub jupyterhub-systemdspawner jupyterhub-dummyauthenticator jupyterhub-firstuseauthenticator jupyterhub-nativeauthenticator jupyterhub-ldapauthenticator jupyterhub-tmpauthenticator mwoauth
oauthenticator jupyterhub-idle-culler jupyter-packaging

And the Node.js packages (thanks to node2npm + manual work): triple-beam winston-transport stack-trace fn.name one-time fecha fast-safe-stringify logform kuler enabled text-hex colorspace @dabh/diagnostics strftime statsd-parser mersenne lynx http-proxy winston configurable-http-proxy.

Still missing: traefik, but there's an ITP for that.

I'll push the repositories to Salsa in the coming days. I need to do
some history cleanups first. If a jupyter team is created in the
meantime, I'll gladly create the repositories under its umbrella rather
than under the Python team's.

Roland.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi folks,

I work on the Jupyter project and am one of the maintainers for JupyterHub.

I would recommend opening a conversation on discourse.jupyter.org. There is a JupyterHub in HPC group that is active and you would probably find interest.

Carol Willing

Project Jupyter Steering Council
Python Steering Council
On May 18, 2021, 8:24 AM -0700, Roland Mas <lolando@debian.org>, wrote:

Le 18/05/2021 à 10:06, Gordon Ball a écrit :

On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:

Hi everyone,

I've been contracted by Synchrotron Soleil to work on the packaging of Jupyterhub and its dependencies. This turns out to about 20 Python packages,
most of which should probably go under the Debian Python Team umbrella (although some may go into Debian Science). So I hereby request to be added
to the python-team group on salsa. My salsa login is "lolando", and I have
read and accept the https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
policy.

Hello

Good to have more people working on jupyter and related tools. Can you
say what the extent of your goal here is? Does it just relate to the jupyterhub server, spawners, proxy, etc or does your target also include some work on the jupyter interfaces/core side?

Honestly, I don't know yet.I'm at the prototyping phase, with 20 Python packages (and 20 Node.js packages) that can just about be installed and
end up in something that displays a webpage and allows creating a
notebook. I don't know much more about Jupyterhub, and I guess I'll
first focus on getting packages into shape before widening my scope further.

I wonder if it is time to have a distinct jupyter packaging team given
the (perhaps concerningly?) growing size of this software stack [1].

Although I don't know how much time I'll have to work on this in the
near future (new job, etc), my broad goals for this next cycle would be:

* See if we can get jupyterlab packaged. This has an unpleasant list of javascript dependencies, but now there is a v3 release I hope it
might stabilise a bit.
* Try and get ipywidgets into better shape - it's currently quite out
of date, requiring patches in consuming libraries, and blocked on javascript problems (many of which are probably in common with
jupyterlab)
* Go through the list of jupyter kernels for other languages and see
if some of these have matured and stabilised and might be good
candidates where the given ecosystem is already well supported in
debian - iruby, ijavascript, gophernotes (go) look like conceivable candidates.

Can't help you there, not yet at least.

For reference, the list of Python packages I have so far (thanks to
py2dsc + manual work): backoff escapism python-consul2 certipy pamela onetimepass jupyter-telemetry nteract-on-jupyter nbgitpuller jupyterhub jupyterhub-systemdspawner jupyterhub-dummyauthenticator jupyterhub-firstuseauthenticator jupyterhub-nativeauthenticator jupyterhub-ldapauthenticator jupyterhub-tmpauthenticator mwoauth oauthenticator jupyterhub-idle-culler jupyter-packaging

And the Node.js packages (thanks to node2npm + manual work): triple-beam winston-transport stack-trace fn.name one-time fecha fast-safe-stringify logform kuler enabled text-hex colorspace @dabh/diagnostics strftime statsd-parser mersenne lynx http-proxy winston configurable-http-proxy.

Still missing: traefik, but there's an ITP for that.

I'll push the repositories to Salsa in the coming days. I need to do
some history cleanups first. If a jupyter team is created in the
meantime, I'll gladly create the repositories under its umbrella rather
than under the Python team's.

Roland.

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Hi folks,<br />
<br />
I work on the Jupyter project and am one of the maintainers for JupyterHub.<br />
<br />
I would recommend opening a conversation on discourse.jupyter.org. There is a JupyterHub in HPC group that is active and you would probably find interest.</div>
</div>
<div name="messageSignatureSection"><br />
<div class="matchFont">Carol Willing</div>
<div class="matchFont" dir="auto"><br /></div>
<div class="matchFont" dir="auto">Project Jupyter Steering Council</div>
<div class="matchFont" dir="auto">Python Steering Council</div>
</div>
<div name="messageReplySection">On May 18, 2021, 8:24 AM -0700, Roland Mas &lt;lolando@debian.org&gt;, wrote:<br />
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">Le 18/05/2021 à 10:06, Gordon Ball a écrit&#160;:<br />
<blockquote type="cite">On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:<br />
<blockquote type="cite">Hi everyone,<br />
<br />
I've been contracted by Synchrotron Soleil to work on the packaging of<br /> Jupyterhub and its dependencies. This turns out to about 20 Python packages,<br />
most of which should probably go under the Debian Python Team umbrella<br /> (although some may go into Debian Science). So I hereby request to be added<br />
to the python-team group on salsa. My salsa login is "lolando", and I have<br />
read and accept the https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst<br />
policy.<br /></blockquote>
Hello<br />
<br />
Good to have more people working on jupyter and related tools. Can you<br /> say what the extent of your goal here is? Does it just relate to the<br /> jupyterhub server, spawners, proxy, etc or does your target also include<br /> some work on the jupyter interfaces/core side?<br /></blockquote>
Honestly, I don't know yet.I'm at the prototyping phase, with 20 Python<br /> packages (and 20 Node.js packages) that can just about be installed and<br /> end up in something that displays a webpage and allows creating a<br /> notebook. I don't know much more about Jupyterhub, and I guess I'll<br />
first focus on getting packages into shape before widening my scope further.<br />
<blockquote type="cite">I wonder if it is time to have a distinct jupyter packaging team given<br />
the (perhaps concerningly?) growing size of this software stack [1].<br />
<br />
Although I don't know how much time I'll have to work on this in the<br />
near future (new job, etc), my broad goals for this next cycle would be:<br /> <br />
* See if we can get jupyterlab packaged. This has an unpleasant list of<br /> javascript dependencies, but now there is a v3 release I hope it<br />
might stabilise a bit.<br />
* Try and get ipywidgets into better shape - it's currently quite out<br />
of date, requiring patches in consuming libraries, and blocked on<br /> javascript problems (many of which are probably in common with<br /> jupyterlab)<br />
* Go through the list of jupyter kernels for other languages and see<br />
if some of these have matured and stabilised and might be good<br />
candidates where the given ecosystem is already well supported in<br />
debian - iruby, ijavascript, gophernotes (go) look like conceivable<br /> candidates.<br /></blockquote>
Can't help you there, not yet at least.<br />
<br />
For reference, the list of Python packages I have so far (thanks to<br /> py2dsc + manual work): backoff escapism python-consul2 certipy pamela<br /> onetimepass jupyter-telemetry nteract-on-jupyter nbgitpuller jupyterhub<br /> jupyterhub-systemdspawner jupyterhub-dummyauthenticator<br /> jupyterhub-firstuseauthenticator jupyterhub-nativeauthenticator<br /> jupyterhub-ldapauthenticator jupyterhub-tmpauthenticator mwoauth<br /> oauthenticator jupyterhub-idle-culler jupyter-packaging<br />
<br />
And the Node.js packages (thanks to node2npm + manual work): triple-beam<br /> winston-transport stack-trace fn.name one-time fecha fast-safe-stringify<br /> logform kuler enabled text-hex colorspace @dabh/diagnostics strftime<br /> statsd-parser mersenne lynx http-proxy winston configurable-http-proxy.<br /> <br />
Still missing: traefik, but there's an ITP for that.<br />
<br />
I'll push the repositories to Salsa in the coming days. I need to do<br />
some history cleanups first. If a jupyter team is created in the<br /> meantime, I'll gladly create the repositories under its umbrella rather<br /> than under the Python team's.<br />
<br />
Roland.<br />
<br /></blockquote>
</div>
</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, May 18, 2021 at 12:29 PM Roland Mas <lolando@debian.org> wrote:

I just created a topic on discourse to announce my effort.

the link is https://discourse.jupyter.org/t/debian-packaging-effort/9240
for those who want to follow


--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format.
I just created a topic on discourse to announce my effort.

Roland.

Le 18/05/2021 à 17:29, Carol Willing a écrit :

Hi folks,

I work on the Jupyter project and am one of the maintainers for
JupyterHub.

I would recommend opening a conversation on discourse.jupyter.org.
There is a JupyterHub in HPC group that is active and you would
probably find interest.

Carol Willing

Project Jupyter Steering Council
Python Steering Council
On May 18, 2021, 8:24 AM -0700, Roland Mas <lolando@debian.org>, wrote:

Le 18/05/2021 à 10:06, Gordon Ball a écrit :

On Mon, May 17, 2021 at 06:20:19PM +0200, Roland Mas wrote:

Hi everyone,

I've been contracted by Synchrotron Soleil to work on the packaging of >>>> Jupyterhub and its dependencies. This turns out to about 20 Python
packages,
most of which should probably go under the Debian Python Team umbrella >>>> (although some may go into Debian Science). So I hereby request to
be added
to the python-team group on salsa. My salsa login is "lolando", and
I have
read and accept the
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
policy.

Hello

Good to have more people working on jupyter and related tools. Can you
say what the extent of your goal here is? Does it just relate to the
jupyterhub server, spawners, proxy, etc or does your target also include >>> some work on the jupyter interfaces/core side?

Honestly, I don't know yet.I'm at the prototyping phase, with 20 Python
packages (and 20 Node.js packages) that can just about be installed and
end up in something that displays a webpage and allows creating a
notebook. I don't know much more about Jupyterhub, and I guess I'll
first focus on getting packages into shape before widening my scope
further.

I wonder if it is time to have a distinct jupyter packaging team given
the (perhaps concerningly?) growing size of this software stack [1]..

Although I don't know how much time I'll have to work on this in the
near future (new job, etc), my broad goals for this next cycle would be: >>>
* See if we can get jupyterlab packaged. This has an unpleasant list of
javascript dependencies, but now there is a v3 release I hope it
might stabilise a bit.
* Try and get ipywidgets into better shape - it's currently quite out
of date, requiring patches in consuming libraries, and blocked on
javascript problems (many of which are probably in common with
jupyterlab)
* Go through the list of jupyter kernels for other languages and see
if some of these have matured and stabilised and might be good
candidates where the given ecosystem is already well supported in
debian - iruby, ijavascript, gophernotes (go) look like conceivable
candidates.

Can't help you there, not yet at least.

For reference, the list of Python packages I have so far (thanks to
py2dsc + manual work): backoff escapism python-consul2 certipy pamela
onetimepass jupyter-telemetry nteract-on-jupyter nbgitpuller jupyterhub
jupyterhub-systemdspawner jupyterhub-dummyauthenticator
jupyterhub-firstuseauthenticator jupyterhub-nativeauthenticator
jupyterhub-ldapauthenticator jupyterhub-tmpauthenticator mwoauth
oauthenticator jupyterhub-idle-culler jupyter-packaging

And the Node.js packages (thanks to node2npm + manual work): triple-beam
winston-transport stack-trace fn.name one-time fecha fast-safe-stringify
logform kuler enabled text-hex colorspace @dabh/diagnostics strftime
statsd-parser mersenne lynx http-proxy winston configurable-http-proxy.

Still missing: traefik, but there's an ITP for that.

I'll push the repositories to Salsa in the coming days. I need to do
some history cleanups first. If a jupyter team is created in the
meantime, I'll gladly create the repositories under its umbrella rather
than under the Python team's.

Roland.

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I just created a topic on discourse to announce my effort.<br>
</p>
<p>Roland.<br>
</p>
<div class="moz-cite-prefix">Le 18/05/2021 à 17:29, Carol Willing a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:4e07fe35-f213-4a27-ba4e-90bef7f97c85@Spark">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title></title>
<div name="messageBodySection">
<div dir="auto">Hi folks,<br>
<br>
I work on the Jupyter project and am one of the maintainers
for JupyterHub.<br>
<br>
I would recommend opening a conversation on
discourse.jupyter.org. There is a JupyterHub in HPC group that
is active and you would probably find interest.</div>
</div>
<div name="messageSignatureSection"><br>
<div class="matchFont">Carol Willing</div>
<div class="matchFont" dir="auto"><br>
</div>
<div class="matchFont" dir="auto">Project Jupyter Steering
Council</div>
<div class="matchFont" dir="auto">Python Steering Council</div>
</div>
<div name="messageReplySection">On May 18, 2021, 8:24 AM -0700,
Roland Mas <a class="moz-txt-link-rfc2396E" href="mailto:lolando@debian.org">&lt;lolando@debian.org&gt;</a>, wrote:<br>
<blockquote type="cite" style="border-left-color: grey;
border-left-width: thin; border-left-style: solid; margin: 5px
5px;padding-left: 10px;">Le 18/05/2021 à 10:06, Gordon Ball a
écrit :<br>
<blockquote type="cite">On Mon, May 17, 2021 at 06:20:19PM
+0200, Roland Mas wrote:<br>
<blockquote type="cite">Hi everyone,<br>
<br>
I've been contracted by Synchrotron Soleil to work on the
packaging of<br>
Jupyterhub and its dependencies. This turns out to about
20 Python packages,<br>
most of which should probably go under the Debian Python
Team umbrella<br>
(although some may go into Debian Science). So I hereby
request to be added<br>
to the python-team group on salsa. My salsa login is
"lolando", and I have<br>
read and accept the
<a class="moz-txt-link-freetext" href="https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst">https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst</a><br>
policy.<br>
</blockquote>
Hello<br>
<br>
Good to have more people working on jupyter and related
tools. Can you<br>
say what the extent of your goal here is? Does it just
relate to the<br>
jupyterhub server, spawners, proxy, etc or does your target
also include<br>
some work on the jupyter interfaces/core side?<br>
</blockquote>
Honestly, I don't know yet.I'm at the prototyping phase, with
20 Python<br>
packages (and 20 Node.js packages) that can just about be
installed and<br>
end up in something that displays a webpage and allows
creating a<br>
notebook. I don't know much more about Jupyterhub, and I guess
I'll<br>
first focus on getting packages into shape before widening my
scope further.<br>
<blockquote type="cite">I wonder if it is time to have a
distinct jupyter packaging team given<br>
the (perhaps concerningly?) growing size of this software
stack [1]..<br>
<br>
Although I don't know how much time I'll have to work on
this in the<br>
near future (new job, etc), my broad goals for this next
cycle would be:<br>
<br>
* See if we can get jupyterlab packaged. This has an
unpleasant list of<br>
javascript dependencies, but now there is a v3 release I
hope it<br>
might stabilise a bit.<br>
* Try and get ipywidgets into better shape - it's currently
quite out<br>
of date, requiring patches in consuming libraries, and
blocked on<br>
javascript problems (many of which are probably in common
with<br>
jupyterlab)<br>
* Go through the list of jupyter kernels for other languages
and see<br>
if some of these have matured and stabilised and might be
good<br>
candidates where the given ecosystem is already well
supported in<br>
debian - iruby, ijavascript, gophernotes (go) look like
conceivable<br>
candidates.<br>
</blockquote>
Can't help you there, not yet at least.<br>
<br>
For reference, the list of Python packages I have so far
(thanks to<br>
py2dsc + manual work): backoff escapism python-consul2 certipy
pamela<br>
onetimepass jupyter-telemetry nteract-on-jupyter nbgitpuller
jupyterhub<br>
jupyterhub-systemdspawner jupyterhub-dummyauthenticator<br>
jupyterhub-firstuseauthenticator
jupyterhub-nativeauthenticator<br>
jupyterhub-ldapauthenticator jupyterhub-tmpauthenticator
mwoauth<br>
oauthenticator jupyterhub-idle-culler jupyter-packaging<br>
<br>
And the Node.js packages (thanks to node2npm + manual work):
triple-beam<br>
winston-transport stack-trace fn.name one-time fecha
fast-safe-stringify<br>
logform kuler enabled text-hex colorspace @dabh/diagnostics
strftime<br>
statsd-parser mersenne lynx http-proxy winston
configurable-http-proxy.<br>
<br>
Still missing: traefik, but there's an ITP for that.<br>
<br>
I'll push the repositories to Salsa in the coming days. I need
to do<br>
some history cleanups first. If a jupyter team is created in
the<br>
meantime, I'll gladly create the repositories under its
umbrella rather<br>
than under the Python team's.<br>
<br>
Roland.<br>
<br>
</blockquote>
</div>
</blockquote>
</body>
</html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)