JupyterHub Community Strategic Lead

[choldgraf]

Context

We are going to begin @sgibson91's tenure as JupyterHub's "Community Strategic Lead" (CSL) soon. This is an issue to keep track of this work on 2i2c's side so that we know what her availability and commitments will be over the coming months.

Note
We shouldn't use this issue for a lot of discussion and planning, it is here to connect 2i2c's planning with upstream issues / work in JupyterHub, which is where most of the work should take place.

Plan for timing

Start date: August 1st 2022

At that point, @sgibson91 will split her time 50% on 2i2c engineering work, and 50% on JupyterHub CSL work.

Next steps

Late July

• Create an issue / project in the JupyterHub org to start tracking this work: EOSS JupyterHub Strategic Lead jupyterhub/team-compass#536
• Tell CS&S and NumFocus that @sgibson91 is beginning her 50/50%

Planning and meeting notes

See this HackMD for planning notes.

Upstream issue

• EOSS JupyterHub Strategic Lead jupyterhub/team-compass#536

[choldgraf]

cc also @malvikasharan who has been working with @sgibson91 on making connections with Community Management communities.

[sgibson91]

Tell CS&S and NumFocus that @sgibson91 is beginning her 50/50%

I emailed Page at CS&S about this, so I think we can consider them "aware" of my 50% time status. Specifically I asked if my contract needing rewriting or if it was ok to just bill 50% time on my invoices -> We're going with the invoicing route.

I am unsure what needs to happen on the NumFOCUS side to consider this item "done".

[choldgraf]

I'm removing myself from this issue because I don't have any dedicated time to it. I will provide @sgibson91 with support throughout her tenure in this role, but it's not something that I can dedicate time to on a daily basis so don't want to track it as part of our ongoing work planning. If there's a task etc I need to complete we can track it in a dedicated issue.

[choldgraf]

Proposal: move to a check-in system for this issue

Right now we have a "checkpoint date" of August 1st. We should remove this date and decide how we'd like to incorporate this ongoing issue into our workflow.

I propose that we define periodic checkpoints (maybe once every month) for @sgibson91 and myself to meet and discuss how this work is going, provide direction about priorities to take next, and write down updates for the community.

@sgibson91 what do you think about this? Is once a month too much? Do you prefer a different way of keeping track of this work?

[sgibson91]

This sounds fine to me

[damianavila]

and write down updates for the community.

That would include some updates here as well, right? Maybe just references to the updates for the community...

Should we keep this one in the team backlog in a longstanding waiting state?
Should we have a new board containing the "external" projects (as long as they don't have a dedicated board)
(question for myself mostly, but happy to hear your thoughts 😉)

[damianavila]

Closing as per updates in jupyterhub/team-compass#663.