Targets for the hub service alpha

[choldgraf]

Description

We are getting close to resolving #262 and having a 2-pager ready to send to communities that wish to use our service. In that document, we're outlining roughly these offerings:

• Education-focused hubs
• Research-focused hubs
• An option to run on a dedicated k8s cluster
• An option to run Dask Gateway

The goal of the alpha service to test our infrastructure and process, gather some data about what works and what doesn't, figure out product/market fit, and generate some revenue for our work.

We also want to roll out this service in a way that is sustainable for our team, and that won't create undue stress for others.

Rather than leaving it open-ended for any communities that are interested in the service to join, I think we should consider setting targets to shoot for, with checkpoints when we hit those targets to decide what to do next (thanks @colliand for this idea!). For example, maybe we start by taking on only 10 communities (including the ones we're already serving) spread across the different types of hubs. If more communities want to join, we ask them to be patient and wait a few weeks. After that time, we decide as a team whether to grow the service by taking on another 10 communities. We can deliberately grow in this way.

Value / benefit

Growing in a slower and more deliberate fashion is a way to do the following things:

• Avoid putting too much strain on our engineering and sales team, given that we have many things going on!
• Give ourselves intentional checkpoints for reflection and iteration on our processes
• Getting "new data" from communities in chunks that we can then incorporate into our processes for subsequent iterations

Implementation details

No response

Tasks to complete

• Discuss what kind of roll-out plan we'd like to follow...
• Encode that plan somewhere so we can track it over time.

Updates

No response