Separate wrapspawner to other repository

[jupyterhub]

Separate wrapspawner to other repository

[zonca]

Hmm actually better do the repo for wrapspawner and include profilespawner, profilespawner might be a bit misleading as a name.

[minrk]

what do folks here think about pulling the RemoteUser authenticator into the Jupyterhub org?

Absolutely!

[willingc]

Seems reasonable to me. @minrk thoughts?

[minrk]

Sounds great!

[willingc]

@zonca Here's a repo for wrapspawner https://github.com/jupyterhub/wrapspawner Do you want a separate repo for profilespawner too?

[zonca]

I would do one repo for profilespawner that provides also wrapspawner but better see what @mbmilligan thinks first

[willingc]

@mbmilligan I'm still hoping for heavymetalspawner 😉

[mbmilligan]

No objection here to separating BatchSpawner into its own repo - it only
depends on Jupyterhub itself. I would keep ProfileSpawner with WrapSpawner
though, since the former directly depends on the latter.

Related question - what do folks here think about pulling the RemoteUser
authenticator into the Jupyterhub org?

Michael

On Sep 21, 2016 5:06 PM, "Carol Willing" [email protected] wrote:

@mbmilligan https://github.com/mbmilligan I'm still hoping for
heavymetalspawner 😉

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#16 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKP4Zzsce-RvhHrGP5Oycx7sYWB1Fkpgks5qsapogaJpZM4KDN25
.

[zonca]

gave a first implementation of this,
@mbmilligan, in the wrapspawner repo I used an example about DockerSpawer which I think is a more common use case. I think the BatchSpawner + ProfilesSpawner example currently in the README.md should stay in this repo instead.

[zonca]

Implemented in https://github.com/jupyterhub/wrapspawner

[zonca]

we should remove wrapspawner from this repository and add other package as requirement, I'll work on this.

[zonca]

ok, see #21

[mbmilligan]

Ok, this has been merged and I added a note to the README in both places. Resolving this issue.