The next six months of project Binder

[betatim]

In https://github.com/jupyterhub/binderhub/issues/933#issuecomment-522272727 @choldgraf mentioned that he would like to give a talk in which he talks about the future of Binder. 🚨 The talk is next week already.

In https://jupyterhub-team-compass.readthedocs.io/en/latest/talking.html we suggest that speakers stick to the past and present unless we've agreed something else.

While predicting the future is an inherently hard task I think writing down what you (team members) personally plan to work on in the form of bullet points is a good start and probably the right level of detail. This is the "to do" item for this thread. Please don't discuss the merit of each suggestion here as it will make people less likely to post because they feel they need to justify their position which takes a lot of time.

My answer to "the next six months" for a talk would be:

• user interface changes and improvements, making it easier for newcomers to use and understand the system (awesome bar, persistent logs, less scary errors, faster builds, better docs)
• growing the federation (finding more partners, maturing the tools that run the federation, improving automation)
• publicity, raising awareness of the project and service in communities not well connected to the Jupyter project (writing guest blog posts, talks at conferences, evangelising, etc)

[sgibson91]

My bullet points are:

• Learning more about helm charts/kube-lego/nginx etc to enable HTTPS on Hub23 and get it running more like a production Hub. Hopefully, I can contribute some documentation supporting other users who wish to set this up.
• Get Private repositories building on Hub23 and store the access token from a GitHub login so that cloning is done "properly" (i.e. with GitHub's security, not our own). Again, the plan is to contribute more documentation for this.
• The Turing Institute joining the Federation. Credit request is being written. My first bullet point will be useful when it comes to deploying the cluster.

[choldgraf]

My thoughts on improvements I'd like to see in the Binder and JupyterHub communities. They are not super code-focused but they'll be the things taking up a lot of my time...

• Another round of cloud credits for mybinder.org's GKE deployment (or some way to pay for it)
• Writing a grant to pay for some community or code development on the Binder project. Maybe for federation
• Get somebody hired @ Berkeley to work on Pangeo hub deployments and onboard them into this community (more info on this one to come in a bit)
• Growing the federation with a few new members. My soft goal is I'd like 50% of the Binder traffic to go to the non-GKE deployments
• Get my jupyter activity dashboard useful for recognizing folks who are doing particular kinds of work