EOSS JupyterHub Strategic Lead

[choldgraf]

Context

We have a CZI EOSS grant to fund a JupyterHub Community Strategic Lead role. This is an issue to keep track of the work items and deliverables on this project as we do the work. Generally this should be pointers to other issues / boards / etc where work is actually happening.

People involved

• Project leader / Community Strategic Lead: @sgibson91
• Strategic support and guidance on Community Management: @malvikasharan

In addition, @choldgraf is the Principal Investigator on the grant and will provide general support and guidance where he is useful.

References

Here are some references from the original proposal:

• Grant text
• Google Drive Folder
• Other grant materials
• Issues with the CSL tag

Actions and updates

• [x] Connect @sgibson91 with @malvikasharan and start attending Community Manager community of practice meetings
• [ ] Initial work plan meeting (late July)
• [x] Anticipated start: August 1 2022
• [x] #537
• [x] #641
• [ ] #663

Related issues

• #548
• https://github.com/jupyterhub/team-compass/issues/550

[choldgraf]

A note on timing

We technically got this grant around last November. However we hadn't yet started work on it because 2i2c was waiting to finish a hiring round for a Product and Community Lead. That process is now wrapped up so @sgibson91 plans to reduce her time at 2i2c by 50% in order to spend that time focusing on this role within JupyterHub. See above for anticipated dates.

[sgibson91]

FYI, I think I'll create a "community strategic lead" label so we can get an overview of all the issues. Things are still a bit too early for me to create project boards yet, but those will come too!

Search org-wide for label: https://github.com/search?q=org%3Ajupyterhub+label%3Acommunity-strategic-lead

[choldgraf]

Update on project plan + budget uses

@sgibson91 and I had another sync about this today. Just wanted to share a few relevant bits of information below:

• For now, we'll use this GitHub issue to track high-level updates about the project as well as relevant information, but over time we will likely try to centralize it in documentation either in team-compass/ or somewhere dedicated. See the community strategic lead label for issues related to this project.
• We have some budget in the grant as "discretionary" spending that can be used to support our team or the people we work with. @sgibson91 will provide recommendations for using this funding to support her in her role. She may use this to cover things like training for JupyterHub mentors, honoraria for work people do on this project, etc.
• We have 4 interns a year, over 2 years, in groups of 2 at a time.
• Some of that discretionary funding will go towards the increased cost of Outreachy interns ($6,000 now)
• I'll also provide guidance to Sarah over the course of the grant. I'm not funded on the grant, so I'll do this as an in-kind support of the project from 2i2c. Just wanted to make that explicit! We'll create a "project team" and list all of these roles when we start documenting the project more formally.

[sgibson91]

I have created a project board to track some efforts here: https://github.com/orgs/jupyterhub/projects/3/views/1

P.S. If anyone with owner rights on the org wants to make that project board public, I won't be mad :D

[GeorgianaElena]

P.S. If anyone with owner rights on the org wants to make that project board public, I won't be mad :D

@sgibson91, I made it public just now. 🚀

Also, I believe you should have owner rights on the org too, but not sure how to proceed about it. @choldgraf do you think you can help out with this? Thanks!

[choldgraf]

@GeorgianaElena help out with what? The board seems to be public to me?

[GeorgianaElena]

@choldgraf , sorry for not being clear. Help out with making @sgibson91 an owner of the org. I'm not sure which is the process for this or how to do it?

[choldgraf]

Ahh gotcha - will do when I'm at my computer!

This makes me wonder if we have some kind of policy about "who gets admin status in the jupyterhub org". If we don't we should probably define one.

IMO, anybody on the steering council should have the authority to have "admin powers" in all repositories, which I think comes with "owner" status. I'm pretty sure that is similar to what we do already?

[sgibson91]

I think there was a case for disassociating "status in team" from "commit rights", particularly when elevated permissions are only required for a short period, or for members who provide strategic guidance but are not as involved on the technical implementation side of things. As in, people shouldn't have permissions they don't use regularly. A discussion for another thread though :)

[manics]

IMO, anybody on the steering council should have the authority to have "admin powers" in all repositories, which I think comes with "owner" status

Sounds fine to me, as long as the emphasis is on "have the authority" rather than "is an owner", since security best practice is to minimise privileges to only what's needed.

Edit: What Sarah said 😄