We help communities create and share knowledge with open infrastructure for interactive computing. We work in the open, follow along š 2i2c.org/blog
- Tweets 196
- Following 7
- Followers 1,030
- Likes 31
Weāre proud to share a public roadmap for 2i2c's team - it's a step toward more participatory, transparent open development with our member and upstream communities.
š 2i2c.org/blog/public-roadmapā¦
1
1
2
490
2i2c retweeted
Estamos muy contentos que tenemos nuestra plataforma escalable para JupyterHub y por eso armamos este Taller.
@2i2c_org and @metadocencia helped us to boot up in Interactive Computing.
š Taller JupyterHub en UNC SupercĆ³mputo. Ā”ExprimĆ sus 8 servidores de 128 nĆŗcleos y 512GiB RAM!
šØāš« Dr. A. Quevedo š„ Docentes, nodocentes y alumnos avanzados (con mail @unc)
š
Vi 12/6, 9hs
š Lab 30, FAMAF
Gratis. Cupos limitados š
docs.google.com/forms/d/e/1Fā¦
8
24
838
A new Linux kernel zero-day called CopyFail lets code break out of containers onto the host. We took a close look at our community hubs, confirmed they're likely safe, and added another layer of protection just in case. Here's a post on what we learned
š 2i2c.org/blog/copyfail-mitigā¦
1
106
We're sharing this writeup because we think transparency about security work matters. If you run JupyterHub on Kubernetes, this might save you some investigation time.
š 2i2c.org/blog/copyfail-mitigā¦
30
We just contributed a JupyterHub feature that lets hub admins keep their admin powers while still using a shared password for participants (often used in workshops).
š 2i2c.org/blog/shared-passworā¦
1
45
As part of this work we contributed the SharedPasswordAuthenticator upstream to the JupyterHub project, check out the docs here, and thanks to MinRK for the reviews!
jupyterhub.readthedocs.io/enā¦
29
Why does 2i2c upgrade core infrastructure quickly when new versions come out? Our collaborators at NASA VEDA recently asked us this exact question. Here's how Yuvi explained it.
š 2i2c.org/blog/why-upgrade-reā¦
1
39
If you encounter a bug in popular open source software, you can often "just wait" for a fix. But someone, somewhere, has to put in the effort to make it happen. 2i2c is committed to being one of those someones!
š 2i2c.org/blog/why-upgrade-reā¦
10
Here's a little post from Chris about work we did helping Jupyter Book deploy jupyterbook.org from a collection of github repositories with MyST:
blog.jupyter.org/how-we-combā¦
1
63
We're proud to support the Berkeley Institute for Data Science in joining the mybinder.org federation! This strengthens the resilience of mybinder.org and shares the load across another contributing institution!
blog.jupyter.org/berkeley-inā¦
42
We spent a bit of time updating Jupyter Book's landing page documentation, and making it more useful for communities with multiple content repositories under one domain. Here's a little post about it:
2i2c.org/blog/jupyterbook-muā¦
1
1
3
212
For a deeper technical dive, check out a blog post we wrote for the Jupyter Book blog here:
jupyterbook.org/blog/posts/2ā¦
1
40
The Jupyter Book and Jupyter Hub teams are hiring a community manager! This is a one-year contract to help us pioneer this critical role by improving and growing our community. Read more here, and please share and apply!
blog.jupyter.org/call-for-apā¦
122
Weāre proud to share a public roadmap for 2i2c's team - it's a step toward more participatory, transparent open development with our member and upstream communities.
š 2i2c.org/blog/public-roadmapā¦
1
1
2
490
We also want to use this to experiment with fractional co-funding, so multiple member communities can share the cost of impactful work. You can learn more about how our membership model works here:
2i2c.org/membership
1
29
This is part of our open practices: doing our work in the open, inviting feedback, and making it easier for communities to see and influence priorities.
2i2c.org/open-practices
14