[blog] Crowdsource a Quarter 3 Community Update

[choldgraf]

Summary / idea for post

Quarter 3 is almost over, and so it is time for us to update communities with what we have accomplished and learned over the last several months. I tried and failed to do this last quarter (#452), so I wonder if we can take a different approach to things this time around.

Content from each team please!

Can we collaboratively create this blog post together, by sourcing the major accomplishments from each of our teams? For now, I think we can define those teams as @2i2c-org/tech-team , @2i2c-org/partnerships-and-community-guidance , and @2i2c-org/organization-wide .

Here's a HackMD where I've got a blog post draft:

• HackMD draft post

Some suggestions:

• The biggest accomplishments within your group, and why they're important
• The most important things you learned
• The most-notable upstream contributions that happened as part of this
• Anything else you think is important to share with others.

Provide enough information so that a person with relatively little context can understand what you're talking about and why it's useful.

Checkpoints

• 2022-10-05: Crowdsource content from our team as comments in this issue
• 2022-10-14: Draft of post ready for review
• BLOG: q3 2022 2i2c-org.github.io#117
• Send out tweets and LinkedIn
• Send to 2i2c listserv

[choldgraf]

Update: updated checkpoint date and structure above

I didn't have time to keep track of this one because of all the conference travel, so let's bump the checkpoint date a little bit. I've also simplified the prompts a little bit to keep things simple for our first iteration. Can @damianavila and @jmunroe and @colliand please lead efforts to fill out their respective sections above? I'll do the same as well

[damianavila]

@choldgraf, can you update the checkpoint date here since the current one is no longer relevant?

[choldgraf]

Good point - I've updated the date to Friday, when I'd like to have a draft ready for review, with or without input from others.

[damianavila]

@choldgraf, hopefully, this is useful...
I tried to collect the most relevant Eng-related pieces in sections I have already seen in your draft.

New hubs

• [New Hub] PaleoCube and PaleoHack hubs: [New Hub] PaleoCube and PaleoHack hubs infrastructure#1418
• [New Hub] NeuroHackademy 2022: [New Hub] NeuroHackademy 2022 infrastructure#1505
• [New Hub] Alabama Water Institute CIROH hub: [New Hub] Alabama Water Institute CIROH hub infrastructure#1444
• [New Hub] OceanHackWeek 2022: [New Hub] OceanHackWeek 2022 infrastructure#1515
• [New Hub] COESSING Pangeo-Style Hub: [New Hub] COESSING Pangeo-Style Hub infrastructure#1516
• [New Hub] Temple University Education Hub: [New Hub] Temple University Education Hub infrastructure#1648
• [New Hub] Callysto Hub: [New Hub] Callysto infrastructure#1439
• [New Hub] London Interdisciplinary School: [New Hub] London Interdisciplinary School infrastructure#1485

Events

• [EVENT] NeuroHackademy 2022: [EVENT] NeuroHackademy 2022 infrastructure#1300
• [EVENT] OceanHackWeek 2022: [EVENT] OceanHackWeek 2022 infrastructure#1576
• [EVENT] Allen Institute Summer Workshop on the Dynamic Brain: [EVENT] Allen Institute Summer Workshop on the Dynamic Brain infrastructure#1621

Features

• Authenticated and optionally private static websites served from a hub: Authenticated and optionally private static websites served from a hub infrastructure#1500 and Setup ability to provide authenticated ingresses to arbitrary web apps infrastructure#1502
• Design a secure method to receive secret keys: Design a secure method to receive secret keys infrastructure#639
• Allow access to multiple s3 buckets from the hub: Allow access to multiple s3 buckets from the hub infrastructure#1455

Improvements and fixes

• Document the central Grafana: [Monitoring] Document the central Grafana infrastructure#1438
• Enable choosing an environment for each profile: Enable choosing environment for each profile in AWS carbonplan hub infrastructure#1640
• Templates sync bug fixes: Templates sync don't work infrastructure#1695
• Document how to access and modify a user's filesystem: Document how to access and modify a user's filesystem infrastructure#1691
• Document the workflow to post a deployment plan to a PR and Restructure CI/CD section: Document the workflow to post a deployment plan to a PR and Restructure CI/CD section infrastructure#1535
• Split up Authentication docs into individual providers: Split up Authentication docs into individual providers infrastructure#1586
• Centralize the initContainer that fixes ownership: Centralize the initContainer that fixes ownership infrastructure#1591
• Replace GitHub with PagerDuty in our Incident Response process: Replace GitHub with PagerDuty in our Incident Response process #508 (this was technically closed in Oct but most of the work was actually performed during September time).

In-progress work (not sure if we should mention it since we are talking about accomplished things whereas there was some work already done on these projects)

• Pangeo/Columbia potentially joining the mybinder.org federation with an AWS deployment: Deploy and operate a BinderHub for Pangeo infrastructure#919 (comment)
• Exploratory phase to develop an r2d JHub service: GESIS Collaboration - Dynamic image building in a JupyterHub infrastructure#1382 (comment)

Not Eng (but relevant, IMHO)

• Update our Hiring and Candidate Search documentation: Update our Hiring and Candidate Search documentation #436
• Decide on an immediate pricing model for cloud cost pass-through: https://github.com/2i2c-org/meta/issues/147

[jmunroe]

I love the highlighting of all of the new hubs and events that have occured. From a @2i2c-org/partnerships-and-community-guidance point of view, should we be including a invitation to reach out to us if you like to your community to have their own hub? Potentially:

If your education or research community is interested having their own managed JupyterHub, please contact us at partnerships@2i2c.org. We have a shared clusters already deployed on Google Cloud Platform on us-central1-b and europe-west2 and we will soon deploy a shared cluster on Amazon Web Services on us-west-2. Dedicated clusters can be run on any major cloud provider. Please see for more details.

We also should have a section advertising our new engineering position.

I'll add these to the HackMD.

[choldgraf]

I've got a blog post draft up here, let's take conversation over there: 2i2c-org/2i2c-org.github.io#117

My plan is to post this on Friday of this week, unless somebody suggests a different date.

[choldgraf]

We posted this last month! let's close this one, here's the PR that added the blog post:

• BLOG: q3 2022 2i2c-org.github.io#117