From 06649aa2200b624d4a9b4be97ad1e2feb548571b Mon Sep 17 00:00:00 2001
From: jnywong <jnywong@users.noreply.github.com>
Date: Thu, 20 Jun 2024 17:02:26 +0000
Subject: [PATCH] deploy: d0fc20e78bf41a6d3112335335884c8a21fb861b

---
 author/jenny-wong/index.xml            | 10 +++++++++-
 blog/2024/ghg-summer-school/index.html |  3 ++-
 blog/index.xml                         | 10 +++++++++-
 category/partnerships/index.xml        | 10 +++++++++-
 category/updates/index.xml             | 10 +++++++++-
 index.json                             |  2 +-
 index.xml                              | 10 +++++++++-
 tag/community/index.xml                | 10 +++++++++-
 8 files changed, 57 insertions(+), 8 deletions(-)

diff --git a/author/jenny-wong/index.xml b/author/jenny-wong/index.xml
index 143904013..6dd577c03 100644
--- a/author/jenny-wong/index.xml
+++ b/author/jenny-wong/index.xml
@@ -41,7 +41,15 @@ loading="lazy" data-zoomable />&lt;/div>
 &lt;/div>&lt;figcaption>
 Login screen of the GHG hub showing the custom built SSIM-GHG image option.
 &lt;/figcaption>&lt;/figure>
-&lt;/p></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
+&lt;/p>
+&lt;h2 id="acknowledgements">
+Acknowledgements
+&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
+&lt;/h2>&lt;p>2i2c would like to credit the following individuals for their great efforts supporting this workshop:&lt;/p>
+&lt;ul>
+&lt;li>Sanjay Bhangar (Development seed)&lt;/li>
+&lt;li>Slesa Adhikari (NASA IMPACT)&lt;/li>
+&lt;/ul></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
 &lt;figure >
 &lt;div class="d-flex justify-content-center">
 &lt;div class="w-100" >&lt;img src="./cover.png" alt="Group selfie of Project Pythia Cook-off participants." loading="lazy" data-zoomable />&lt;/div>
diff --git a/blog/2024/ghg-summer-school/index.html b/blog/2024/ghg-summer-school/index.html
index 995369639..065dc6ce2 100644
--- a/blog/2024/ghg-summer-school/index.html
+++ b/blog/2024/ghg-summer-school/index.html
@@ -23,7 +23,8 @@
 <a href=https://github.com/NASA-IMPACT/ssim-ghg-workshop-2024-python-image target=_blank rel=noopener>built a customized software environment</a>
 with container technology for use at the workshop. In doing so, this bypasses the need for participants to individually install software on their own machines and the online hub provides a <em>consistent</em> and <em>reproducible</em> interactive computing environment that is easily <em>accessible</em> and <em>scalable</em>.</p><p><figure id=figure-login-screen-of-the-ghg-hub-showing-the-custom-built-ssim-ghg-image-option><div class="d-flex justify-content-center"><div class=w-100><img alt="Login screen of the GHG hub showing the custom built SSIM-GHG image option." srcset="/blog/2024/ghg-summer-school/ghg-hub_hu49ab8e9d23f0127273503033b8b48398_331096_ad9e3e76b81da251fc5541ef6f155271.webp 400w,
 /blog/2024/ghg-summer-school/ghg-hub_hu49ab8e9d23f0127273503033b8b48398_331096_44627a312f86c0adc583a43e55994817.webp 760w,
-/blog/2024/ghg-summer-school/ghg-hub_hu49ab8e9d23f0127273503033b8b48398_331096_1200x1200_fit_q75_h2_lanczos_3.webp 1200w" src=/blog/2024/ghg-summer-school/ghg-hub_hu49ab8e9d23f0127273503033b8b48398_331096_ad9e3e76b81da251fc5541ef6f155271.webp width=760 height=469 loading=lazy data-zoomable></div></div><figcaption>Login screen of the GHG hub showing the custom built SSIM-GHG image option.</figcaption></figure></p></div><div class=article-tags><a class="badge badge-light" href=/tag/community/>Community</a></div><div class=share-box><ul class=share></ul></div><div class="media author-card content-widget-hr"><a href=/author/jenny-wong/><img class="avatar mr-3 avatar-circle" src=/author/jenny-wong/avatar_huc2333c99a5a6960f14279231c17feb93_40255_270x270_fill_q75_lanczos_center.jpg alt="Jenny Wong"></a><div class=media-body><h5 class=card-title><a href=/author/jenny-wong/>Jenny Wong</a></h5><h6 class=card-subtitle>Technical Content Developer</h6><ul class=network-icon aria-hidden=true><li><a href=mailto:jwong@2i2c.org><i class="fas fa-envelope"></i></a></li><li><a href=https://twitter.com/_jennywong_ target=_blank rel=noopener><i class="fab fa-twitter"></i></a></li><li><a href=https://github.com/jnywong target=_blank rel=noopener><i class="fab fa-github"></i></a></li><li><a href=https://jnywong.github.io target=_blank rel=noopener><i class="fas fa-globe"></i></a></li></ul></div></div></div></article></div><div class=page-footer><div class=container><footer class=site-footer><div class="row justify-content-center mb-4"><div class="col-6 col-md-4"><h5>About</h5><ul class="nav flex-column"><li class="nav-item mb-2"><a href=/organization class="nav-link p-0 text-muted">Team and organization</a></li><li class="nav-item mb-2"><a href=https://compass.2i2c.org class="nav-link p-0 text-muted">Organizational documentation</a></li><li class="nav-item mb-2"><a href=/jobs class="nav-link p-0 text-muted">Jobs at 2i2c</a></li><li class="nav-item mb-2"><a href=/blog class="nav-link p-0 text-muted">Blog</a></li></ul></div><div class="col-6 col-md-4"><h5>Technical</h5><ul class="nav flex-column"><li class="nav-item mb-2"><a href=# class="nav-link p-0 text-muted">GitHub</a></li><li class="nav-item mb-2"><a href=# class="nav-link p-0 text-muted">Documentation</a></li><li class="nav-item mb-2"><a href=# class="nav-link p-0 text-muted">Pricing</a></li></ul></div><div class=col-md-4><form><h5>Subscribe to our newsletter</h5><div><a href="https://2i2c.us2.list-manage.com/subscribe?u=494ab59616acdfc381a699b44&id=94ce07e556">Join our mailing list</a></div></form><h5>Follow us online</h5><style>.footer__brand-icons{font-size:1.3em;display:flex;gap:.5rem}</style><div class=footer__brand-icons><a href=https://github.com/2i2c-org/2i2c-org.github.io><i class="fa-brands fa-github"></i>
+/blog/2024/ghg-summer-school/ghg-hub_hu49ab8e9d23f0127273503033b8b48398_331096_1200x1200_fit_q75_h2_lanczos_3.webp 1200w" src=/blog/2024/ghg-summer-school/ghg-hub_hu49ab8e9d23f0127273503033b8b48398_331096_ad9e3e76b81da251fc5541ef6f155271.webp width=760 height=469 loading=lazy data-zoomable></div></div><figcaption>Login screen of the GHG hub showing the custom built SSIM-GHG image option.</figcaption></figure></p><h2 id=acknowledgements>Acknowledgements
+<a class=header-anchor href=#acknowledgements>#</a></h2><p>2i2c would like to credit the following individuals for their great efforts supporting this workshop:</p><ul><li>Sanjay Bhangar (Development seed)</li><li>Slesa Adhikari (NASA IMPACT)</li></ul></div><div class=article-tags><a class="badge badge-light" href=/tag/community/>Community</a></div><div class=share-box><ul class=share></ul></div><div class="media author-card content-widget-hr"><a href=/author/jenny-wong/><img class="avatar mr-3 avatar-circle" src=/author/jenny-wong/avatar_huc2333c99a5a6960f14279231c17feb93_40255_270x270_fill_q75_lanczos_center.jpg alt="Jenny Wong"></a><div class=media-body><h5 class=card-title><a href=/author/jenny-wong/>Jenny Wong</a></h5><h6 class=card-subtitle>Technical Content Developer</h6><ul class=network-icon aria-hidden=true><li><a href=mailto:jwong@2i2c.org><i class="fas fa-envelope"></i></a></li><li><a href=https://twitter.com/_jennywong_ target=_blank rel=noopener><i class="fab fa-twitter"></i></a></li><li><a href=https://github.com/jnywong target=_blank rel=noopener><i class="fab fa-github"></i></a></li><li><a href=https://jnywong.github.io target=_blank rel=noopener><i class="fas fa-globe"></i></a></li></ul></div></div></div></article></div><div class=page-footer><div class=container><footer class=site-footer><div class="row justify-content-center mb-4"><div class="col-6 col-md-4"><h5>About</h5><ul class="nav flex-column"><li class="nav-item mb-2"><a href=/organization class="nav-link p-0 text-muted">Team and organization</a></li><li class="nav-item mb-2"><a href=https://compass.2i2c.org class="nav-link p-0 text-muted">Organizational documentation</a></li><li class="nav-item mb-2"><a href=/jobs class="nav-link p-0 text-muted">Jobs at 2i2c</a></li><li class="nav-item mb-2"><a href=/blog class="nav-link p-0 text-muted">Blog</a></li></ul></div><div class="col-6 col-md-4"><h5>Technical</h5><ul class="nav flex-column"><li class="nav-item mb-2"><a href=# class="nav-link p-0 text-muted">GitHub</a></li><li class="nav-item mb-2"><a href=# class="nav-link p-0 text-muted">Documentation</a></li><li class="nav-item mb-2"><a href=# class="nav-link p-0 text-muted">Pricing</a></li></ul></div><div class=col-md-4><form><h5>Subscribe to our newsletter</h5><div><a href="https://2i2c.us2.list-manage.com/subscribe?u=494ab59616acdfc381a699b44&id=94ce07e556">Join our mailing list</a></div></form><h5>Follow us online</h5><style>.footer__brand-icons{font-size:1.3em;display:flex;gap:.5rem}</style><div class=footer__brand-icons><a href=https://github.com/2i2c-org/2i2c-org.github.io><i class="fa-brands fa-github"></i>
 </a><a href=https://twitter.com/2i2c_org><i class="fa-brands fa-twitter"></i>
 </a><a href=http://eepurl.com/hjHbff><i class="fa-solid fa-envelope"></i></a></div></div></div><div class="license mb-3">© 2024 2i2c. This work is licensed under the <a href=https://creativecommons.org/licenses/by/4.0/>CC-BY 4.0 license</a>.</div><p class=powered-by>Published with <a href="https://hugoblox.com/?utm_campaign=poweredby" target=_blank rel=noopener>Hugo Blox Builder</a> — the free, <a href=https://github.com/HugoBlox/hugo-blox-builder target=_blank rel=noopener>open source</a> website builder that empowers creators.</p></footer></div></div><script src=/js/vendor-bundle.min.ff7771056d34ad9f2de2d8f6a466e748.js></script><script src=https://cdn.jsdelivr.net/npm/leaflet@1.7.1/dist/leaflet.min.js integrity crossorigin=anonymous></script><script id=search-hit-fuse-template type=text/x-template>
     <div class="search-hit" id="summary-{{key}}">
diff --git a/blog/index.xml b/blog/index.xml
index 73facee0c..7da865a11 100644
--- a/blog/index.xml
+++ b/blog/index.xml
@@ -39,7 +39,15 @@ loading="lazy" data-zoomable />&lt;/div>
 &lt;/div>&lt;figcaption>
 Login screen of the GHG hub showing the custom built SSIM-GHG image option.
 &lt;/figcaption>&lt;/figure>
-&lt;/p></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
+&lt;/p>
+&lt;h2 id="acknowledgements">
+Acknowledgements
+&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
+&lt;/h2>&lt;p>2i2c would like to credit the following individuals for their great efforts supporting this workshop:&lt;/p>
+&lt;ul>
+&lt;li>Sanjay Bhangar (Development seed)&lt;/li>
+&lt;li>Slesa Adhikari (NASA IMPACT)&lt;/li>
+&lt;/ul></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
 &lt;figure >
 &lt;div class="d-flex justify-content-center">
 &lt;div class="w-100" >&lt;img src="./cover.png" alt="Group selfie of Project Pythia Cook-off participants." loading="lazy" data-zoomable />&lt;/div>
diff --git a/category/partnerships/index.xml b/category/partnerships/index.xml
index 6c9dbc06c..af2caf1c4 100644
--- a/category/partnerships/index.xml
+++ b/category/partnerships/index.xml
@@ -39,7 +39,15 @@ loading="lazy" data-zoomable />&lt;/div>
 &lt;/div>&lt;figcaption>
 Login screen of the GHG hub showing the custom built SSIM-GHG image option.
 &lt;/figcaption>&lt;/figure>
-&lt;/p></description></item><item><title>Low storage alerting for the UToronto cluster</title><link>https://2i2c.org/blog/2024/utoronto-storage-monitoring/</link><pubDate>Fri, 14 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/utoronto-storage-monitoring/</guid><description>&lt;p>
+&lt;/p>
+&lt;h2 id="acknowledgements">
+Acknowledgements
+&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
+&lt;/h2>&lt;p>2i2c would like to credit the following individuals for their great efforts supporting this workshop:&lt;/p>
+&lt;ul>
+&lt;li>Sanjay Bhangar (Development seed)&lt;/li>
+&lt;li>Slesa Adhikari (NASA IMPACT)&lt;/li>
+&lt;/ul></description></item><item><title>Low storage alerting for the UToronto cluster</title><link>https://2i2c.org/blog/2024/utoronto-storage-monitoring/</link><pubDate>Fri, 14 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/utoronto-storage-monitoring/</guid><description>&lt;p>
 &lt;figure id="figure-the-utoronto-hub-landing-page">
 &lt;div class="d-flex justify-content-center">
 &lt;div class="w-100" >&lt;img src="./cover.png" alt="The UToronto hub landing page" loading="lazy" data-zoomable />&lt;/div>
diff --git a/category/updates/index.xml b/category/updates/index.xml
index 6fbd1c903..d0682d6b7 100644
--- a/category/updates/index.xml
+++ b/category/updates/index.xml
@@ -39,7 +39,15 @@ loading="lazy" data-zoomable />&lt;/div>
 &lt;/div>&lt;figcaption>
 Login screen of the GHG hub showing the custom built SSIM-GHG image option.
 &lt;/figcaption>&lt;/figure>
-&lt;/p></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
+&lt;/p>
+&lt;h2 id="acknowledgements">
+Acknowledgements
+&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
+&lt;/h2>&lt;p>2i2c would like to credit the following individuals for their great efforts supporting this workshop:&lt;/p>
+&lt;ul>
+&lt;li>Sanjay Bhangar (Development seed)&lt;/li>
+&lt;li>Slesa Adhikari (NASA IMPACT)&lt;/li>
+&lt;/ul></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
 &lt;figure >
 &lt;div class="d-flex justify-content-center">
 &lt;div class="w-100" >&lt;img src="./cover.png" alt="Group selfie of Project Pythia Cook-off participants." loading="lazy" data-zoomable />&lt;/div>
diff --git a/index.json b/index.json
index 95cee2832..52a9fd190 100644
--- a/index.json
+++ b/index.json
@@ -1 +1 @@
-[{"authors":["jenny-wong"],"categories":null,"content":"Jenny is the Technical Content Developer for 2i2c. Her work is mainly focused on the CZI-funded Catalyst Project, an initiative aiming to provide research communities in Latin America and Africa with access to large-scale scientific infrastructure. As part of this effort, she will help develop community-based training materials for interactive cloud-native workflows.\nAs a former research software engineer, Jenny has considerable experience supporting researchers with writing documentation, creating video tutorials, and designing and delivering training for advanced research computing. Jenny is also a qualified Software Carpentries Instructor.\nJenny’s background is in mathematics, with a special interest in geophysical fluid dynamics. She obtained a PhD in the subject with her thesis titled “A slurry model of the F-layer in the Earth’s core”.\n","date":1718841600,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718841600,"objectID":"2f015795f698666394aa3c63de977b49","permalink":"https://2i2c.org/author/jenny-wong/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/jenny-wong/","section":"authors","summary":"Jenny is the Technical Content Developer for 2i2c. Her work is mainly focused on the CZI-funded Catalyst Project, an initiative aiming to provide research communities in Latin America and Africa with access to large-scale scientific infrastructure.","tags":null,"title":"Jenny Wong","type":"authors"},{"authors":["angus-hollands"],"categories":null,"content":"Angus Hollands is an Open Source Infrastructure at 2i2c. He was previously a post-doctoral researcher in the Computational High Energy Physics group at Princeton University. He has a long-standing history of working collaboratively in open source projects, such as Executable Books, Jupyter, scikit-hep, and Blender. He is motivated by open-source, open-science, and the FAIR principles to build a more accessible, empowering future for scientific research and publication. His scientific background is in nuclear structure, in which he studied a PhD at the University of Birmingham.\n","date":1718668800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718668800,"objectID":"33be3fd611c72f8b1268083cb150e1c0","permalink":"https://2i2c.org/author/angus-hollands/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/angus-hollands/","section":"authors","summary":"Angus Hollands is an Open Source Infrastructure at 2i2c. He was previously a post-doctoral researcher in the Computational High Energy Physics group at Princeton University. He has a long-standing history of working collaboratively in open source projects, such as Executable Books, Jupyter, scikit-hep, and Blender.","tags":null,"title":"Angus Hollands","type":"authors"},{"authors":["chris-holdgraf"],"categories":null,"content":"Chris is the Executive Director of 2i2c. He was previously a post-doctoral researcher in the Department of Statistics at UC Berkeley , and a Community Architect with the Division of Data Science at Berkeley. He is also a team member of Project Jupyter (particularly the JupyterHub and Binder teams ), with a focus on how infrastructure can support interactive computing workflows in research and education. He’s interested in the boundary between technology, open-source software, and research and education workflows, as well as how open communities can support and extend these workflows in a way that makes science more impactful and inclusive. His background is in cognitive and computational neuroscience, where he used predictive models to understand the auditory system in the human brain.\n","date":1718668800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718668800,"objectID":"6b264ebb4849fa5ae2987cd0caffb03d","permalink":"https://2i2c.org/author/chris-holdgraf/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/chris-holdgraf/","section":"authors","summary":"Chris is the Executive Director of 2i2c. He was previously a post-doctoral researcher in the Department of Statistics at UC Berkeley , and a Community Architect with the Division of Data Science at Berkeley.","tags":null,"title":"Chris Holdgraf","type":"authors"},{"authors":["james-munroe"],"categories":null,"content":"James is Product and Community Lead for 2i2c. Coming from a background as an associate professor in the Department of Physics and Physical Oceanography at Memorial University of Newfoundland , he is a strong advocate for enabling scientists and students to be efficient and effective in their computational workflows. Building on previous work in big data oceanography with links to the Pangeo project, COSIMA : Consortium for Ocean-Sea Ice Modelling in Australia, and CIOOS : Canadian Integrated Ocean Observing System, James wants to bring the strength of the Jupyter ecosystem to users across a broad range of educational and research domains.\n","date":1718668800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718668800,"objectID":"1603084ce2f0780df78913a58b0e5817","permalink":"https://2i2c.org/author/james-munroe/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/james-munroe/","section":"authors","summary":"James is Product and Community Lead for 2i2c. Coming from a background as an associate professor in the Department of Physics and Physical Oceanography at Memorial University of Newfoundland , he is a strong advocate for enabling scientists and students to be efficient and effective in their computational workflows.","tags":null,"title":"James Munroe","type":"authors"},{"authors":["harold-campbell"],"categories":null,"content":"I enjoy building and supporting communities of practice. I have built a small JS visualization library and dabbled in delivery management systems. Recently, I have strong interests in music (programming VST, etc.), AI and data science.\n","date":1713139200,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1713139200,"objectID":"1871ee3c936a96ebd5a3f1d03bd46ac0","permalink":"https://2i2c.org/author/harold-campbell/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/harold-campbell/","section":"authors","summary":"I enjoy building and supporting communities of practice. I have built a small JS visualization library and dabbled in delivery management systems. Recently, I have strong interests in music (programming VST, etc.","tags":null,"title":"Harold Campbell","type":"authors"},{"authors":["yuvi-panda"],"categories":null,"content":"Building participatory open infrastructure for scientific \u0026amp; educational use cases. A Project Jupyter team member working on infrastructure related projects. Ex Wikimedia and ex-GNOME. Let’s eliminate accidental complexities wherever we find them.\n","date":1704329774,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1705090315,"objectID":"0a9477094d0ef5674613765d19d77fa3","permalink":"https://2i2c.org/author/yuvi-panda/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/yuvi-panda/","section":"authors","summary":"Building participatory open infrastructure for scientific \u0026 educational use cases. A Project Jupyter team member working on infrastructure related projects. Ex Wikimedia and ex-GNOME. Let’s eliminate accidental complexities wherever we find them.","tags":null,"title":"Yuvi Panda","type":"authors"},{"authors":["georgiana-dolocan"],"categories":null,"content":"Software Engineer irreversibly in love with open source. A JupyterHub team member, focusing on infrastructure and community growth. Previously JupyterHub Contributor in Residence and Outreachy intern through an internship that supports diversity in open source and free software.\n","date":1688083200,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1688083200,"objectID":"6b99443e1887b9f34a76d5ae9503a4e1","permalink":"https://2i2c.org/author/georgiana-dolocan/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/georgiana-dolocan/","section":"authors","summary":"Software Engineer irreversibly in love with open source. A JupyterHub team member, focusing on infrastructure and community growth. Previously JupyterHub Contributor in Residence and Outreachy intern through an internship that supports diversity in open source and free software.","tags":null,"title":"Georgiana Dolocan","type":"authors"},{"authors":["sarah-gibson"],"categories":null,"content":"Sarah Gibson is an Open Source Infrastructure Engineer at 2i2c, an open source contributor and advocate. She holds more than two years of experience as a Research Engineer at a national institute for data science and artificial intelligence, as well as holding a core contributor role in the open source projects Binder , JupyterHub , and The Turing Way . Sarah is passionate about working with domain experts to leverage cloud computing in order to accelerate cutting-edge, data-intensive research and disseminating the results in an open, reproducible and reusable manner.\nSarah holds a Fellowship with the Software Sustainability Institute and advocates for best software practices in research. She is a member of the mybinder.org operating team and maintains infrastructure supporting over 150k launches of reproducible computational environments per week. She has also mentored projects through two cohorts of the Open Life Science programme, imparting lived experience of her skills participating and leading in open science projects.\n","date":1650326400,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1650326400,"objectID":"83b3d2127330b720674bb862052a869c","permalink":"https://2i2c.org/author/sarah-gibson/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/sarah-gibson/","section":"authors","summary":"Sarah Gibson is an Open Source Infrastructure Engineer at 2i2c, an open source contributor and advocate. She holds more than two years of experience as a Research Engineer at a national institute for data science and artificial intelligence, as well as holding a core contributor role in the open source projects Binder , JupyterHub , and The Turing Way .","tags":null,"title":"Sarah Gibson","type":"authors"},{"authors":["admin"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"2525497d367e79493fd32b198b28f040","permalink":"https://2i2c.org/author/2i2c/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/2i2c/","section":"authors","summary":"","tags":null,"title":"2i2c","type":"authors"},{"authors":["cathryn-carson"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"d06aefb9519756f12b367d49725e76d9","permalink":"https://2i2c.org/author/cathryn-carson/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/cathryn-carson/","section":"authors","summary":"","tags":null,"title":"Cathryn Carson","type":"authors"},{"authors":["damian-avila"],"categories":null,"content":"Father, Software Developer, Quant, (formerly) Biochemist, and some other things ;-) Currently living between Córdoba and Buenos Aires, Argentina. I have made some contributions to popular Open Source projects such as Jupyter, Nikola, and Bokeh. I have also started several projects being RISE (a “live” slideshow for the Jupyter notebook) the most popular one. You can easily find videos of some of my talks and tutorials at multiples national and international conferences. How can I help?\n","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"9a4427d33f68e5b2a7e48689f801048a","permalink":"https://2i2c.org/author/damian-avila/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/damian-avila/","section":"authors","summary":"Father, Software Developer, Quant, (formerly) Biochemist, and some other things ;-) Currently living between Córdoba and Buenos Aires, Argentina. I have made some contributions to popular Open Source projects such as Jupyter, Nikola, and Bokeh.","tags":null,"title":"Damián Avila","type":"authors"},{"authors":["erik-sundell"],"categories":null,"content":"Attracted by an inclusive culture and a leverage for a positive world impact, Erik has steered towards open source development in the Jupyter ecosystem from working as a math and physics teacher in Sweden.\n","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"236074155e2fe6a29b991c7208e4c8e5","permalink":"https://2i2c.org/author/erik-sundell/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/erik-sundell/","section":"authors","summary":"Attracted by an inclusive culture and a leverage for a positive world impact, Erik has steered towards open source development in the Jupyter ecosystem from working as a math and physics teacher in Sweden.","tags":null,"title":"Erik Sundell","type":"authors"},{"authors":["fernando-perez"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"3ef1af30502eabcbfbf1b6b9fdec9086","permalink":"https://2i2c.org/author/fernando-perez/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/fernando-perez/","section":"authors","summary":"","tags":null,"title":"Fernando Perez","type":"authors"},{"authors":["giuliano-maciocci"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"3d1a70b6153ee523987a5adb34530f61","permalink":"https://2i2c.org/author/giuliano-maciocci/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/giuliano-maciocci/","section":"authors","summary":"","tags":null,"title":"Giuliano Maciocci","type":"authors"},{"authors":["jim-colliander"],"categories":null,"content":"Jim is a 2i2c Co-Founder. He is a Professor of Mathematics at the University of British Columbia and previously served (2016-2021) as the Director of The Pacific Institute for the Mathematical Sciences (PIMS). While at PIMS and using infrastructure from Compute Canada, he helped create a national-scale JupyterHub service called Syzygy . He co-founded Callysto , a collaboration between PIMS and Cybera. Callysto develops open education resources and training programs for students and teachers in grades 5-12 leveraging cloud-hosted interactive computing. Colliander also co-found Crowdmark , an education technology company based in Toronto that provides workflows and AI-based improvements to education assessment.\n","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"f4e8cb10915e4de235af6e01631e7fd8","permalink":"https://2i2c.org/author/jim-colliander/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/jim-colliander/","section":"authors","summary":"Jim is a 2i2c Co-Founder. He is a Professor of Mathematics at the University of British Columbia and previously served (2016-2021) as the Director of The Pacific Institute for the Mathematical Sciences (PIMS).","tags":null,"title":"Jim Colliander","type":"authors"},{"authors":["lindsey-heagy"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"a0558a9a07b39d5ff5cb0cc779f87cc5","permalink":"https://2i2c.org/author/lindsey-heagy/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/lindsey-heagy/","section":"authors","summary":"","tags":null,"title":"Lindsey Heagy","type":"authors"},{"authors":["ryan-abernathy"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"ee4ec873203b28c0eeafd2019d926eb5","permalink":"https://2i2c.org/author/ryan-abernathey/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/ryan-abernathey/","section":"authors","summary":"","tags":null,"title":"Ryan Abernathey","type":"authors"},{"authors":["Jenny Wong"],"categories":["updates","partnerships"],"content":" Summer school for inverse modeling of greenhouse gases 2024 The Cooperative Institute for Research in the Atmosphere ( CIRA ) is an interdisciplinary cooperation between NOAA research scientists and Colorado State University. CIRA is hosting a summer school for inverse modeling of greenhouse gases using atmospheric data assimilation techniques. The US Greenhouse Gas Center is supporting the workshop by providing 40+ attendees access to their interactive computing hub operated by 2i2c (see our blog post about their launch ).\nHub administrators have built a customized software environment with container technology for use at the workshop. In doing so, this bypasses the need for participants to individually install software on their own machines and the online hub provides a consistent and reproducible interactive computing environment that is easily accessible and scalable.\nLogin screen of the GHG hub showing the custom built SSIM-GHG image option. ","date":1718841600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718841600,"objectID":"359285341adb9ee283e99471397f154e","permalink":"https://2i2c.org/blog/2024/ghg-summer-school/","publishdate":"2024-06-20T00:00:00Z","relpermalink":"/blog/2024/ghg-summer-school/","section":"blog","summary":"Summer school for inverse modeling of greenhouse gases 2024 The Cooperative Institute for Research in the Atmosphere ( CIRA ) is an interdisciplinary cooperation between NOAA research scientists and Colorado State University.","tags":["community"],"title":"US Greenhouse Gas Center supports summer school at CIRA","type":"blog"},{"authors":["Jenny Wong","James Munroe","Angus Hollands"],"categories":["updates"],"content":" What is Project Pythia? # Project Pythia is the education working group for Pangeo , a community platform for Big Data geoscience in which 2i2c operates a cloud hub. The core aim of Project Pythia is to spearhead the creation and curation of community-driven, open-source documentation, in the form of “cookbooks”, to enable the adoption of open, scalable and reproducible workflows for geoscientists.\nWhat did 2i2c do? # Jenny, James and Angus from the 2i2c team participated in the annual Project Pythia Cook-off 2024 , a hackathon where cookbook authors and collaborators can spend dedicated time on creating and maintaining their content using Jupyter Book and publishing their cookbooks with GitHub actions.\n2i2c teamed up with the infrastructure breakout group during the hackathon, led by Katelyn FitzGerald (UCAR) and Kevin Tyle (University at Albany), and members of the Curvenote team also joined the group.\nDay 1 # 2i2c deployed and demonstrated a dedicated BinderHub service for Project Pythia that allowed hackathon participants to “self-serve” images of their software environment, which were specified by including a list of packages in an environment.yml file placed in their GitHub cookbook repository. Participants could then pull the image from a container registry into their 2i2c hub (or indeed, any other JupyterHub server) to share and reproduce their computational environments with ease.\nDay 2 # During the first half of the day, we quickly identified a number of issues that were proving to be a maintenance headache for the Project Pythia infrastructure group:\nConfiguration files for each cookbook were difficult to update at scale. Project Pythia currently have a gallery of over 30 cookbooks! Changes to Sphinx-based themes inherited from upstream were prone to breaking custom Project Pythia branding downstream. Executable content was not able to run on the Project Pythia’s dedicated BinderHub hosted on JetStream2 (operated by NSF). Cookbooks frequently cross-referenced materials from other cookbooks to build upon pre-existing knowledge, but this was not easy to author and the reader experience was not as smooth as it could be. Following the announcement that Jupyter Book 2.0 will use MyST last month, Rowan (Curvenote) and Angus (2i2c) delivered a compelling demonstration of the MyST ecosystem centered around modern web-first technologies (JavaScript/TypeScript) that offers improved interactivity and accessibility.\nIn the second half of the day, we decided to use the hackathon to explore migrating the Pythia cookbooks from using a Sphinx-based to a MyST-based document structure and engine. Within one afternoon, the group migrated four cookbooks to use MyST MD\nPythia Foundations High Resolution Rapid Refresh on AWS Radar Cookbook Advanced Visualization . This moment was palpably exciting! It was evident that MyST MD supported backwards compatible content out of the box, which alleviated fears of sunk cost into existing Sphinx-based cookbooks. The migration workflow was as simple as executing the following commands\nconda install mystmd\nmyst.\nDay 3 # We spent this day tackling support for managing a gallery of Project Pythia cookbooks at scale. See the Executable Books blog post for technical details on how we\nCentralized configuration Prototyped a gallery plugin in Python Fixed a number of bugs related to integrated computation with Binder and JupyterLite Embraced the referencing and reuse of content with simple markdown syntax for hover-references . Day 4 # Looking to the future, we spent time reflecting on our experiences and discussing the potential, transformative impact MyST MD tooling could have in the hands of the scientific community at large, including the communities served by 2i2c. Knowledge-sharing based on static figures and PDFs would fall obsolete and give way to a dynamic, web-first approach to interactive communication and publishing backed by compute from a Jupyter server.\nThroughout the course of the hackathon, the rate of iterated development for both end users of the community cookbook and the developers of the open-source tooling was astounding. For example, we were able to quickly expose small bugs ( e.g. support for HTML video tags ) in the MyST MD tooling, which were immediately fixed upstream and released within minutes. The feedback loop that connected the user experience with the software tooling was incredibly synergistic, with immediate impact both upstream and downstream that 2i2c hopes to continue replicating across many facets of their operations.\nBeyond the Project Pythia Cook-off, the breakout group will continue conversations around strengthening their community of practice and hopefully advocating for wider adoption of MyST MD amongst the scientific community (say hello to some of our group members at SciPy 2024 in July!).\nAcknowledgements # University at Albany (NSF award 2324302): Led the funding acquisition, helped organize and facilitate the event UCAR (NSF award …","date":1718668800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718668800,"objectID":"fc3f258e0a3863ceb0cb6e0d66ec641a","permalink":"https://2i2c.org/blog/2024/project-pythia-cookoff/","publishdate":"2024-06-18T00:00:00Z","relpermalink":"/blog/2024/project-pythia-cookoff/","section":"blog","summary":"What is Project Pythia? # Project Pythia is the education working group for Pangeo , a community platform for Big Data geoscience in which 2i2c operates a cloud hub. The core aim of Project Pythia is to spearhead the creation and curation of community-driven, open-source documentation, in the form of “cookbooks”, to enable the adoption of open, scalable and reproducible workflows for geoscientists.","tags":["community"],"title":"Hacking the Project Pythia Cook-off with MyST Markdown","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Over the past several years, 2i2c has built a platform for serving community-centric hubs that provide a digital home for workflows in creating and sharing knowledge. See our three-year retrospective for a report about the growth and impact this service has had.\nDuring that time, we’ve experimented with several models for funding and sustaining this infrastructure. We’ve tried everything from direct cost-recovery from individual communities, to institutional contracts that cover several hubs, to grant-based models that fund many communities at the same time.\nThere are pros and cons associated with each, and we believe that a combination of all of them is important for a long-term service sustainability model for 2i2c. However, with this post we’d like to share the community funding model that strikes the right balance between short-term sustainability and scalability.\nIn short: 2i2c aims to serve networks of communities that are joined by a domain or workflow, and fund the network at once rather than through one-on-one contracts.\nA model of the funding and service relationships we aim to build. We believe that this model strikes a balance between “scalable and very simple hubs” (which require a lot of administrative toil) and “fully bespoke hubs” (which are expensive and unscalable). By using a single funding contract to serve many communities, we can reduce the amount of sales and contracting toil for each community. This will let us raise funds more quickly, and focus more of our time on delivering service.\nWe are seeking community leaders to collaborate # If you’re part of one or more communities that would benefit from cloud infrastructure for creating and sharing knowledge, and believe a network like this would benefit you, please reach out! We are seeking leaders collaborate in designing service for networks like the ones described above, and identifying potential funding sources for it.\nIf you’re interested in collaborating on this, send an e-mail to partnerships@2i2c.org .\nLearn more # You can find more information about this fundraising and service strategy in our Team Compass documentation .\n","date":1718668800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718668800,"objectID":"778d786f72c8f47613284a2d5650bab7","permalink":"https://2i2c.org/blog/2024/funding-community-networks/","publishdate":"2024-06-18T00:00:00Z","relpermalink":"/blog/2024/funding-community-networks/","section":"blog","summary":"Over the past several years, 2i2c has built a platform for serving community-centric hubs that provide a digital home for workflows in creating and sharing knowledge. See our three-year retrospective for a report about the growth and impact this service has had.","tags":["sustainability"],"title":"Towards scalable and sustainable networks of community hubs","type":"blog"},{"authors":["Jenny Wong"],"categories":["updates","engineering","partnerships"],"content":" The UToronto hub landing page 2i2c has operated The University of Toronto hub since 2021 and this hub supports over 6000 educators and learners in a day! With a community of this size, file storage can quickly grow out of control and cause issues.\nThe 2i2c engineering team have implemented a low storage alerting system for Microsoft Azure, so that they can pre-emptively take remedial action before the filesystem is about to run out of diskspace.\nGreat job team 🚀\nUToronto hub usage ","date":1718323200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718323200,"objectID":"995e434955e5e4182f24fd1ae4d780d7","permalink":"https://2i2c.org/blog/2024/utoronto-storage-monitoring/","publishdate":"2024-06-14T00:00:00Z","relpermalink":"/blog/2024/utoronto-storage-monitoring/","section":"blog","summary":"The UToronto hub landing page 2i2c has operated The University of Toronto hub since 2021 and this hub supports over 6000 educators and learners in a day! With a community of this size, file storage can quickly grow out of control and cause issues.","tags":["community"],"title":"Low storage alerting for the UToronto cluster","type":"blog"},{"authors":["Angus Hollands","Chris Holdgraf","Rowan Cockett"],"categories":["upstream"],"content":"See the Executable Books blog for a post on the future directions of the Jupyter Book project, which will be built on top of the MyST Markdown engine .\n","date":1716249600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1716249600,"objectID":"db6f343c8a73a07841ec11a7718e2f53","permalink":"https://2i2c.org/blog/2024/myst-jupyter-book/","publishdate":"2024-05-21T00:00:00Z","relpermalink":"/blog/2024/myst-jupyter-book/","section":"blog","summary":"See the Executable Books blog for a post on the future directions of the Jupyter Book project, which will be built on top of the MyST Markdown engine .","tags":["product"],"title":"Jupyter Book 2.0 will use MyST","type":"blog"},{"authors":["Jenny Wong"],"categories":["updates"],"content":" Figure from the preprint showing large and small scale air-sea fluxes are separated. By Julius Busecke et al., licensed under CC BY 4.0 Julius Busecke et al. of the LEAP-Pangeo 1 hub, have recently published a preprint2 that investigates “The Overlooked Sub-Grid Air-Sea Flux in Climate Models” using 2i2c infrastructure. Well done all! 🎉\nNSF Science and Technology Center (STC) Learning the Earth with Artificial intelligence and Physics (LEAP) (Award # 2019625) ↩︎\nhttps://doi.org/10.31223/X5WQ47  ↩︎\n","date":1716249600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1716249600,"objectID":"b200749d9f926d902fa7e2293f759749","permalink":"https://2i2c.org/blog/2024/leap-pangeo-paper/","publishdate":"2024-05-21T00:00:00Z","relpermalink":"/blog/2024/leap-pangeo-paper/","section":"blog","summary":"Figure from the preprint showing large and small scale air-sea fluxes are separated. By Julius Busecke et al., licensed under CC BY 4.0 Julius Busecke et al. of the LEAP-Pangeo 1 hub, have recently published a preprint2 that investigates “The Overlooked Sub-Grid Air-Sea Flux in Climate Models” using 2i2c infrastructure.","tags":["community"],"title":"Researchers at LEAP-Pangeo investigate overlooked sub-grid air-sea heat flux in climate models","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"2i2c recently finished it’s three year retrospective after closing out its original seed grant. As part of this process, we’re revisiting our organizational strategy, structure, and overall plan, in order to incorporate the learning that we’ve done over our first three years.\nOur value proposition is a key framing for 2i2c’s intended impact, key stakeholders, and platform strategy. We recently completed a team exercise to refine this statement for 2i2c, and are excited to share it with you below:\nA global network of community hubs for interactive learning and discovery Our interactive computing platform gives your community a digital home to create and share knowledge, and a global network of communities to learn from. This is an exciting direction that leans into and builds upon the way we’ve described our service so far. It recognizes that the value in our service doesn’t end with simple access to an interactive computing environment, but lies in how that environment’s tools empower a community to create and share knowledge with one another.\nWe believe that this is an exciting direction to build towards, because it is based in the value of the collection of communities we serve, and the way that this network can be greater than the sum of its parts. We’re excited to lean into this direction in how we shape our platform, what open source contributions we make, and where we aim to have impact in the coming years.\nTo begin, we’ve interwoven some ideas from this value proposition into 2i2c.org, and the way that we describe our service. We’d love feedback from anyone who has an idea, a critique, or “yes, and” to share.\nA recent talk with this value proposition # As part of this work, 2i2c’s Executive Director, Chris Holdgraf , gave a talk about 2i2c to the Incentivizing Open and Collaborative Research (ICOR) community. Here are some links in case others are interested:\nSlides for viewing More information for the talk Video link Here’s the video below for quick reference:\nData Sharing and Analysis in Collaborative Open Research Environments from Michael Markie on Vimeo.\n","date":1714953600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1714953600,"objectID":"da52f16079db53f897ddd141995924f2","permalink":"https://2i2c.org/blog/2024/value-proposition/","publishdate":"2024-05-06T00:00:00Z","relpermalink":"/blog/2024/value-proposition/","section":"blog","summary":"2i2c recently finished it’s three year retrospective after closing out its original seed grant. As part of this process, we’re revisiting our organizational strategy, structure, and overall plan, in order to incorporate the learning that we’ve done over our first three years.","tags":["product"],"title":"An update to 2i2c's value proposition","type":"blog"},{"authors":["Chris Holdgraf","Harold Campbell"],"categories":["updates"],"content":"This is a follow-up to our 2023 report of organizational strengths and weaknesses , describing some improvements we’ve made on our team’s coordination and delivery.\nIn 2023, we released a report describing our organizational strengths and weaknesses . This uncovered a key challenge for our team: improving our coordination and delivery. Over the previous two years, our service had grown significantly in its scope and complexity. We were working on more than 7 active grants and were serving more than 70 active communities with around 7,000 monthly active users.\nThis was taxing our small team, and we found ourselves struggling to efficiently deliver on our work. For example, a collaboration with GESIS to bring image building functionality to JupyterHub took longer than we wished, and we felt that our planning and execution was not transparent enough to their team. In addition, in a collaboration to serve communities in Latin America and Africa we felt that 2i2c was not responsive enough to onboarding and deploying infrastructure for new communities.\nSteps we’ve taken to improve delivery # At the beginning of 2024, we hired our first Delivery Manager and Chief of Staff role as well as our first Product Lead role . Both of these roles are meant to develop systems and team practices that improve our planning and delivery.\nIn Quarter 1 of 2024, we designed and initiated an organizational transformation with the following goals:\nProvide clarity about our overall organizational goals and strategy. Define our near-term goals and major projects that drive our work. Define and prioritize the major work items that feed into these goals. Break this major work items into actionable items that our team can work on from day to day. Provide visibility for all of this information across the entire organization. Below is a brief description of the major changes that we’ve made. These are still a work in progress, and organizational transformation takes months, if not years, but we hope that this provides a useful snapshot in time as we kick off this process.\nOur system of work # Our team-wide system of work can be found in the Team Compass at the link below:\nhttps://compass.2i2c.org/cross-functional/workflow/ This system of work attempts to link our strategic goals with concrete chunks of work to deliver. You can see an overview of this system below:\nOur work system shows how initiatives are made up of lists of actions that accomplish them. These actions are distributed across our team’s operational boards for delivery. It is roughly broken down into these major areas:\nOur value proposition: Our system of delivery starts with a value proposition. This is a north-star statement for the value that 2i2c aims to provide to our communities in order to achieve our mission. It is a guiding principle for where we prioritize our time and improve our service.\nWhile updating our delivery model, we decided it was time to update the value proposition we’d been informally using. We’re in the process of validating this value proposition with communities, and will share a draft for public comment soon!\nStrategic goals and major projects: Next we define strategic goals that describe the most important progress we must make as an organization. This considers our current capabilities and challenges, as well as the major projects that we’re already committed to (like grants). Our initiatives (described below) should each represent progress towards one or more of our goals and major projects.\nStrategic initiatives: These are major thrusts of work that represent progress towards our goals. They range in time from weeks to months, and generally require coordination and action across each of 2i2c’s functional areas. Initiatives exist in a dedicated board, where we shape and scope them with enough information to understand them and prioritize. Once an initiative is in progress, it begins driving work on a two-week planning cycle. All in-progress initiatives should make up a significant percentage of 2i2c’s total work allocation.\nOperational boards: Operational boards are used to track our day-to-day workstreams. We organize into two-week sprints, with a collection of work pulled into each sprint according to in-progress initiatives and the other types of reactive and operational work on our plate (for example, responding to support tickets is reactive work). Within each initiative, we coordinate across our teams in order to understand the next steps needed and who is responsible for doing it. This helps teams plan the work for their next iteration.\nThis system is very much still a work in progress, and we’ve already identified a number of ways that we’d like to improve it moving forward. For example, we’d like to find more efficient ways of coordinating across our team, and encouraging team members to own their own work.\nChanges to our team culture # In addition to our system around planning work, we’ve also identified a number of ways that we can …","date":1713139200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1713139200,"objectID":"affa08ea5c8b3279786b5cd50f8bc84b","permalink":"https://2i2c.org/blog/2024/delivery-improvements/","publishdate":"2024-04-15T00:00:00Z","relpermalink":"/blog/2024/delivery-improvements/","section":"blog","summary":"This is a follow-up to our 2023 report of organizational strengths and weaknesses , describing some improvements we’ve made on our team’s coordination and delivery.\nIn 2023, we released a report describing our organizational strengths and weaknesses .","tags":["culture"],"title":"Improvements to our team's planning and delivery","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["engineering","partnerships","updates"],"content":" What happened? # A few weeks ago, the JupyterHub team discovered a security vulnerability in the jupyter-server-proxy package that would allow potential unauthenticated access to a JupyterHub via WebSockets, allowing unauthenticated users to run arbitrary code on the JupyterHub. jupyter-server-proxy is used by many communities to provide alternative user interfaces like RStudio and remote desktops.\nThis vulnerability was detected by the JupyterHub team, with leadership from 2i2c’s engineers. It was resolved through upstream contributions to the JupyterHub project, and we have deployed a fix that mitigates this vulnerability for all the hubs 2i2c manages.\nDoes this impact my 2i2c community hub? # We do not believe that any of 2i2c’s communities were impacted by this vulnerability, and a patch has now been pushed to all community hubs to resolve this issue.\nIf your community was vulnerable to this problem, you might experience slightly slower startup latency while we work out a long-term solution.\nSince this is a vulnerability in the docker image used by our communities, we will be reaching out over the next few weeks to put a more permanent fix in place.\nWhere can I learn more? # See the JupyterHub security advisory for CVE-2024-28179 for more information about the security vulnerability, including details on the mitigation we have put in place to protect our communities.\nConclusion # We’re grateful that the JupyterHub community was quick to acknowledge, respond, and resolve this security vulnerability after it was brought to their attention. We’re also proud that 2i2c’s engineers helped the JupyterHub team throughout the process.\nThis allowed our team to resolve the problem before it impacted any of 2i2c’s communities. Because 2i2c community infrastructure is managed in a central location, we were able to resolve this for over 80 communities with a single team rather than expecting each community to learn about and fix this problem on their own.\nWe also believe this reflects the healthy upstream relationships that we hope to encourage with our team’s Open Source strategy and practices . By working with the JupyterHub community and pushing changes upstream, we’ve resolved this issue for any user of jupyter-server-proxy, not just 2i2c’s own ecosystem. In particular, because of 2i2c’s position running hubs for many communities via Kubernetes, we were able to identify a solution that did not require every user image to be updated (as described in section For JupyterHub admins of Z2JH installations).\nWe believe that all of these lead to a healthier, safer ecosystem of open source tools ❤️.\n","date":1710806400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1710806400,"objectID":"9b65af0a3c3fc20b796ab16baa5c7110","permalink":"https://2i2c.org/blog/2024/cve-jupyter-server-proxy/","publishdate":"2024-03-19T00:00:00Z","relpermalink":"/blog/2024/cve-jupyter-server-proxy/","section":"blog","summary":"What happened? # A few weeks ago, the JupyterHub team discovered a security vulnerability in the jupyter-server-proxy package that would allow potential unauthenticated access to a JupyterHub via WebSockets, allowing unauthenticated users to run arbitrary code on the JupyterHub.","tags":[],"title":"Security report for jupyter-server-proxy: CVE-2024-28179","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"We’re pleased to share a three-year retrospective report that was created to close-out 2i2c’s original seed funding grant provided by the Chan Zuckerberg Initiative .\nSee the Zenodo entry here: See the MyST website for the report at 2i2c.org/report-czi-2021 . Download a PDF version generated by MyST here . This report was written with the new MyST Markdown document engine and shows off some of the functionality that we’ve been working on in collaboration with the MyST team.\nWe’re incredibly grateful for the seed funding that CZI provided to kickstart 2i2c’s mission and operations, and excited about more impact to come!\n","date":1709251200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1712793600,"objectID":"74aa80756eba5914eabcf720a6945927","permalink":"https://2i2c.org/blog/2024/report-czi/","publishdate":"2024-03-01T00:00:00Z","relpermalink":"/blog/2024/report-czi/","section":"blog","summary":"We’re pleased to share a three-year retrospective report that was created to close-out 2i2c’s original seed funding grant provided by the Chan Zuckerberg Initiative .\nSee the Zenodo entry here: See the MyST website for the report at 2i2c.","tags":[],"title":"A three year retrospective report of 2i2c's impact","type":"blog"},{"authors":["Yuvi Panda"],"categories":["engineering","partnerships","updates"],"content":"Thanks to Arnim Bleier , Jenny Wong , Georgiana Elena , Damián Avila , Jim Colliander and James Munroe for contributing to this blog post\nmybinder.org is a very popular service that allows end users to specify and share the environment (languages, packages, etc) required for their notebooks to run correctly by placing configuration files they are already familiar with (like requirements.txt or environment.yml) along with their notebooks. While not without its own set of challenges, this is extremely powerful because it puts control of the environment in the hands of the people who write the code. They can customize the environment to fit the needs of their code, instead of having to fit their code into the environment that admins have made available.\nBut, mybinder.org (and the BinderHub software that powers it) is built for sharing your work after you are done with it, not for actively doing work. BinderHubs often do not have persistent storage nor persistent user identity, and UX is centered around ephemeral interactivity that can be shared with others (via a link), rather than persistent interactivity that a single user repeatedly comes back to. JupyterHub is more commonly used for this kinda workflow, but doesn’t currently have the ability for users to easily build their own environments. Admins who are running the JupyterHub can make multiple environments available for users to choose from, but this still puts admins in the critical path for environment customization.\nOur collaboration with GESIS , NFDI4DS , and CESSDA , aims to bring this flexibility to JupyterHub directly. We aim to empower users to decide for themselves which applications and dependencies are installed on a per-project basis. Our work enables communities with heterogeneous requirements to share a single Hub. Our approach frees administrators from being overwhelmed by installation requests and transforms the JupyterHub platform into a platform for collaborative computational reproducibility. In this update, we report on our progress and upcoming steps in this project.\nWhat does a BinderHub do, exactly? # It is helpful to understand that BinderHub primarily has 3 responsibilities:\nPresent a UI to the end user for them to provide details on what to build (this is what you see when you go to mybinder.org) Call out to repo2docker in a scalable way to actually build and push an image containing the environment for the given repository, and show the user logs as this build process happens. This also allows users to debug issues with their build more easily. Talk to a JupyterHub instance to launch a user server with the built docker image, and redirect the user to this. (2) is really the core feature of BinderHub, and we settled on figuring out how to make that available to JupyterHub users. It was really important to us that this was also done in a way that can be sustainably used by everyone, not just 2i2c. This blog post discusses the various improvements to the broad ecosystem of projects in the Jupyter ecosystem to get this done.\nDemo # But first, a very quick demo of how this looks like right now now!\nThis is very much a work in progress, but the basic flow can be seen clearly. Users see a Server Options menu after they log into JupyterHub. They can specify the two primary things that determine the server configuration:\nThe resources allocated (RAM, CPU and maybe GPU)\nThe environment (container image) used, which can be specified in one of 3 ways:\na. A pre-selected list of environments (container images), provided by the administrators who set up this JupyterHub b. A blank text box where you can enter any publicly available docker image they want c. A mybinder.org style way to specify a GitHub repository, which will be then dynamically built into a docker image for the user!\nSo what did we need to do to accomplish this, in a way that’s very upstream friendly and usable by everyone (and not just 2i2c)?\nA Standalone binderhub-service helm chart # The default upstream BinderHub helm chart includes a JupyterHub as a dependency, and configures itself to be used primarily in a manner similar to mybinder.org . As the person who helped make that choice early on, I can tell you why it was made - for convenience! And it was very convenient, as it allowed us to get mybinder.org going fast. However, it makes it difficult to install a BinderHub service alongside an existing JupyterHub. To this end, we have created a standalone BinderHub helm chart , designed to be installed alongside an existing JupyterHub, so we can use it purely to build images. This allows the BinderHub instance to be used as a JupyterHub Service , which is what we want.\nWhile this helm chart is currently under the 2i2c GitHub org, the hope is that it can eventually migrate to a jupyterhub-contrib organization (once it is created), or it can become the upstream helm chart for BinderHub if enough work can be done in BinderHub to allow it to serve use cases like mybinder.org.\nAs …","date":1704329774,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1705090315,"objectID":"c9a2f2b9d4451cdafd606c391e5b036e","permalink":"https://2i2c.org/blog/2024/jupyterhub-binderhub-gesis/","publishdate":"2024-01-03T16:56:14-08:00","relpermalink":"/blog/2024/jupyterhub-binderhub-gesis/","section":"blog","summary":"Thanks to Arnim Bleier , Jenny Wong , Georgiana Elena , Damián Avila , Jim Colliander and James Munroe for contributing to this blog post\nmybinder.org is a very popular service that allows end users to specify and share the environment (languages, packages, etc) required for their notebooks to run correctly by placing configuration files they are already familiar with (like requirements.","tags":[],"title":"Integrating BinderHub with JupyterHub: Empowering users to manage their own environments","type":"blog"},{"authors":["James Colliander"],"categories":null,"content":" Abstract\nThe International Interactive Computing Collaboration ( 2i2c.org ), working with NASA VEDA , Development Seed and other partners, operates an interactive computing platform for The U.S. Greenhouse Gas Center. The U.S. GHG Center, announced yesterday at the 28th annual United Nations Climate Conference (COP-28) in Dubai, is an interagency collaboration of the Environmental Protection Agency (EPA) , the National Aeronautics and Space Administration (NASA) , the National Institute of Standards and Technology (NIST) , and the National Ocean and Atmospheric Administration (NOAA) . This note places the launch of the U.S. GHG Center in a scientific, international, and national context and argues that similar digital public goods are needed for humanity to understand and manage the Earth system.\nScientific Context # It was controversial in 1827 when Joseph Fourier (the discoverer of the law of heat conduction ) argued 1 that the atmosphere keeps the Earth warm, like a puffy down comforter, but it’s not now. Gases in the atmosphere trap heat near Earth. How much heat is trapped depends on the gas mixture. Putting more heat-trapping gases in is like putting a wool blanket on top of the down comforter. Human activity since industrialization is injecting lots more heat-trapping gas into the atmosphere and changing the Earth’s climate.\nThe science is clear. The up-to-date consensus view of the global scientific community is expressed in the Sixth Assessment Report of the Intergovernmental Panel on Climate Change (IPCC):\nInternational Context # The international community officially recognized human-influenced climate change at the World Climate Conference (WCC-1) 2 in 1979. The 1979 declaration is remarkably prescient and detailed. A complex and interconnected collection of scientific and diplomatic activities were catalyzed by WCC-1. Some important milestones from this history are captured in the chart and numbered list below.\ngantt\rdateFormat YYYY-MM-DD\rtitle International Climate Change Milestones\rsection Study\rWCC-1 (1979) :crit, done, admin0, 1979-02-12, 1979-02-23\rWCP :crit, adminA, 1979-06-01, 2025-12-31 CMIP1: crit, done, adminT, 1995-01-01,1995-12-31\rCMIP2: crit, done, adminR, 1997-01-01, 1998-12-31\rCMIP2+: crit,done,adminS, 2000-05-09, 2001-12-31\rCMIP3 :crit, done, adminP, 2004-10-01, 2006-12-31\rCMIP5 :crit, done, adminO, 2008-09-01, 2013-03-15\rCMIP6 :crit, done, adminQ, 2014-02-01, 2024-12-31\rIPCC :crit, admin1, 1988-12-06, 2025-12-31\rIPCC-AR1 :crit, done, adminH, 1990-08-01, 1992-06-30\rIPCC-AR2 :crit, done, adminI, 1995-01-01,1995-12-31\rIPCC-AR3 :crit,done, adminJ, 2001-01-01, 2001-12-31\rIPCC-AR4 :crit, done,adminK, 2007-01-01,2007-12-31\rIPCC awarded Nobel Prize :crit, done, adminN, 2007-10-12, 2007-11-12\rIPCC-AR5 :crit,done,adminL, 2014-01-01,2014-12-31\rIPCC-AR6 :crit,done,adminM,2023-01-01,2023-12-31\rsection Treaties\rRio Earth Summit (1992) :crit, done, adminC, 1992-06-03, 1992-06-14\rUNFCC :crit, admin2, 1994-03-21, 2025-12-31\rBerlin (COP-1) :crit, done, adminE, 1995-03-28, 1995-04-07\rByrd-Hagel Resolution :crit, done, adminX, 1997-07-25, 1997-07-30\rKyoto (COP-3) :crit, done, adminD, 1997-12-01, 1997-12-10\rKyoto Protocol :crit, done, admin3, 1997-12-11, 2020-12-31 Paris (COP-21) :crit, done, adminF, 2015-11-30, 2015-12-12\rParis Agreement :crit, adminG, 2016-11-04, 2025-12-31\rGlasgow (COP-26) :crit, done, adminV, 2021-10-31, 2021-11-12\rDubai (COP-28) :crit, adminW, 2023-11-20, 2023-12-12\rETF :crit, adminU, 2024-01-01, 2025-12-31 The table above describes a subset (for a more systematic review see 3, 4) of key milestones in global efforts to understand and address climate change. A glossary of acronyms and additional background:\nThe First World Climate Conference (WCC-1) 2 was held in 1979. The World Climate Programme ( WCP ), an activity overseen by the World Meteorological Organization was established after WCC-1. WCP, in partnership with other organizations, operates programs (e.g. the World Climate Research Program (WCRP) ) that organize and integrate international scientific efforts to understand the climate. The WMO also operates the Integrated Global Greenhouse Gas Information System (IG3IS) , a natural partner for the emerging work described below. WCRP manages the Common Model Intercomparison Project (CMIP) . CMIP serves as a kind of league for intercomparing models of the Earth’s climate system developed by teams who approach the problems with different methods and designs. Intercomparison, an approach that enables finding the consensus views of teams with divergent approaches to problems, is used in other modeling scenarios. Research papers on the climate are rapidly produced by scholars from essentially all knowledge disciplines. This overwhelming stream of content, like snowflakes in a blizzard, is coalesced into coherent and carefully scrutinized IPCC Assessment Reports by the Intergovernmental Panel on Climate Change (IPCC) . The Earth Summit held in Rio de Janeiro in 1992 led to the …","date":1701734400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1701734400,"objectID":"439872a921884aafee39428ebea3e093","permalink":"https://2i2c.org/blog/2023/us-ghg-center-launches/","publishdate":"2023-12-05T00:00:00Z","relpermalink":"/blog/2023/us-ghg-center-launches/","section":"blog","summary":"Abstract\nThe International Interactive Computing Collaboration ( 2i2c.org ), working with NASA VEDA , Development Seed and other partners, operates an interactive computing platform for The U.S. Greenhouse Gas Center.","tags":["NASA VEDA","U.S. GHG Center","digital public goods","climate change"],"title":"Digital public goods for Earth system management: U.S. Greenhouse Gas Center launches","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Over the past few months, we’ve been investigating ways to improve our reporting both internally and externally. We’ve decided to experiment with a monthly community update to create a regular cadence of transparency and highlights from 2i2c for our broader community. This is the first such update, so bear with us as we work out the kinks!\nOur goal with these updates is to share what stands out at 2i2c - what we’ve learned, what we’re proud of, where we’ve struggled, and where we’ve had an impact. We hope this can be a historical record of “what stands out” to our team and that it is useful for our broader community to see. We also want this to be relatively short and to the point to make it sustainable to both write and read.\nWe’d love feedback on what else you’d like to see. If you have any ideas, please send an email to hello@2i2c.org.\nRough Numbers # First off, a few numbers on the scale and status of our interactive computing hub service:\nWe are currently running around 73 JupyterHubs that are collectively averaging more than 4000 average monthly users. We have several communities in the educational sector, so October was a peak in the Fall semester of activity.\nWe’re recovering roughly 40% of our monthly staffing costs through recurring service revenue. The remainder we’re making up with a combination of grants and more focused development contracts.\nAssuming minimal growth in our service and fundraising, our runway is roughly until August 2025 - however, we anticipate this to shrink in the short-term once we make critical new hires in the coming months.\nOrganization Updates # This section describes some major organization-wide efforts we’ve started or progressed over the last month.\nImproving Our Quarterly Sprints and Goals # This month our team kicked off the second round of our new quarterly sprints and goals process. This is an attempt to focus our team around a few goals and sub-teams dedicated to them throughout each quarter. Our hope is that this allows us to make strategic “pushes” in directions that feel important for 2i2c’s operations and the communities we serve.\nThis quarter, we incorporated a lot of learning that took place after our first iteration in Q3 2023. We are hoping to sharpen up the timing of events throughout the process, including communicating internally and externally about our status (thus, this blog post series).\nIn the next quarter, we aim to build off of this work, and to identify where our future new hires of Delivery Manager / Interim Chief of Staff and our Product Lead will fit in.\nThree New Jobs Posted # In October, we began a short hiring push to address many of the organizational challenges noted in our organizational structure and strategy audit . We aim to have each of these positions filled by the end of the year and begin incorporating new team members into our organization. Here’s a list of the three job postings:\nDelivery Manager / Interim Chief of Staff Product Lead Open Source Infrastructure Engineer: Cloud Engineering Product Strategy Work # We kicked off a collaboration with Richard Pope to provide us with some short-term product strategy work. In Q3, our team took stock of the many different kinds of services and technology that we deploy, aiming to refine this into a long-term product model.\nRichard will join us for several months to take these outputs and help us craft them into a model for where 2i2c is delivering value that we can build upon for the coming years. We’ll provide more updates for the community as this work continues.\nContinued Onboarding of Communities in Our Catalyst Project Collaboration # We continued onboarding communities onto infrastructure managed by 2i2c as part of a CZI-funded project to serve communities in Latin America and Africa . The grant team began its operations last April and spent the first several months creating an onboarding pipeline and rubric for identifying and connecting with communities. As of October, we’ve onboarded our first few communities - there is still a lot of content, training material, and documentation to create, and we will begin iterating on this in collaboration with our early-adopted communities in Q4 2023 and Q1 2024.\nPartnerships and Impact # This section describes notable new partnerships and developments with communities in our interactive computing hub service.\nWe began several new partnerships with communities in the research space this month.\nThe NASA Visualization, Exploration, and Data Analysis (VEDA) project is an open-source science cyberinfrastructure for data processing, visualization, exploration, and geographic information systems (GIS) capabilities.\nThe US Greenhouse Gas Center provides a cloud-based system for exploring and analyzing U.S. government and other curated greenhouse gas datasets.\nIn addition, we’ve celebrated considerable growth in one of our partner communities: CryoCloud . This community focuses its work around studying the Cryosphere using satellite imagery data. …","date":1699574400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1699574400,"objectID":"eb4bed1d078424b0423eb1005a0937aa","permalink":"https://2i2c.org/blog/2023/update-october/","publishdate":"2023-11-10T00:00:00Z","relpermalink":"/blog/2023/update-october/","section":"blog","summary":"Over the past few months, we’ve been investigating ways to improve our reporting both internally and externally. We’ve decided to experiment with a monthly community update to create a regular cadence of transparency and highlights from 2i2c for our broader community.","tags":[],"title":"Community Update: October 2023","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Over the last several months 2i2c has been working with an organizational consulting group called Difference Digital to help us identify the major opportunities and challenges in our organizational structure and strategy. The result of this work is a report that describes in detail the major strengths, weaknesses, challenges, and opportunities that 2i2c faces. It also recommends major actions to take as an organization.\n2i2c values organizational transparency and a willingness to be honest about where you’re struggling. Stress is a natural part of both individuals and organizations, and should be embraced with the goal of learning and improving. Moreover, as a young organization 2i2c has benefitted heavily from the documents and learning that other organizations have made publicly available. We wouldn’t be where we are without building on the backs of others who are willing to share what they’ve learned.\nSo, we are making this organizational audit and report public for anyone to see. We hope that it provides transparency into 2i2c’s current status, and that it serves as a useful resource for other non-profits that are growing and facing similar challenges.\nHere’s a link to the report on Zenodo .\nFor more background on this report, check out the short description below.\nIn April of this year we had our first in-person team meeting. We were excited and grateful to have the opportunity to speak to each other face-to-face. We also learned that many people on our team were stressed out! Our service had grown slow-but-steadily over the previous year, and we were feeling the tension that comes with growing your partnerships without significantly changing your team’s capacity or structure.\nSo, we decided to work with an organizational consulting group called makeadifference.digital to help us identify where we need to make improvements. They spent several weeks having one-on-one conversations with each member of the team, as well as doing a broader organizational analysis and comparison to other technical organizations at a similar stage of their lifecycle.\nThe result of this work was a report that outlines the major opportunities and strengths, as well as challenges and gaps in capacity, that our team currently faces. It makes a number of recommendations for how we should shift our practices, and importantly it also notes that the only way to gain that capacity is by hiring for new people and skills.\nHere’s a link to the report on Zenodo .\nThe immediate result of this work is that we currently have three jobs posted:\nA Product Lead role to help us build a “product function” within 2i2c’s team. A Delivery Manager / Chief of Staff role to oversee and manage 2i2c’s system of work. A cloud and operations engineering role to grow our cloud engineering team’s capacity in serving communities. Our next steps are to fill these positions, and to then begin the work of implementing many of the recommendations that are contained in the report. We’re confident that this is a natural part of being a small and growing organization, and we are grateful for the expertise of makeadifference.digital in guiding us through this work.\nNote: if you’d like to work with makeadifference.digital , you can reach out to them at hello@makeadifference.digital .\n💡 Follow our work! Sign up for our mailing list for updates about 2i2c. Send us an e-mail about collaborating or partnering on a project. See our Service Documentation or our Team Compass to learn about our service and organization.\n","date":1699401600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1699401600,"objectID":"59480fc276a9d788565555c7b0b50d1c","permalink":"https://2i2c.org/blog/2023/organizational-report/","publishdate":"2023-11-08T00:00:00Z","relpermalink":"/blog/2023/organizational-report/","section":"blog","summary":"Over the last several months 2i2c has been working with an organizational consulting group called Difference Digital to help us identify the major opportunities and challenges in our organizational structure and strategy.","tags":[],"title":"Open organizational report: Strengths and challenges for 2i2c's team","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"It’s been two quarters since our last major update - this isn’t quite as frequent as we’re hoping to post updates from our team, but we’re making adjustments to have more regular communication for reasons that will hopefully be a bit clearer below! In that time, we’ve been hard at work serving and growing our interactive computing service, as well as doing some introspection as a team and identifying major next steps moving forward. More on that in the following sections, but first a short service update.\nHow has our service evolved over the past few months? # New partnerships and service growth # Our service has grown several new partner communities over the last two quarters. A few notable communities are the NASA VEDA project , a team at the Smithsonian , a team at NCAR , and the U.S. Greenhouse Gases Center . We are running about 71 hubs across 24 clusters, with about 4000 weekly users ( more usage stats here ).\nWe also began operations on a major collaboration to serve communities in Latin America and Africa, called the Catalyst Project . This team met together for the first time in April, and we’ve been laying a foundation for service growth in the first several months. We are just onboarding our first communities and hope to grow that service in the coming year.\nFinally, we’ve been fortunate to receive some grants around creating content and designing workflows that utilize cloud infrastructure. For example, a NASA TOPS grant and an upcoming collaboration with Project Pythia around geospatial workflows.\nFinancial picture # At this point, we’re recovering roughly 40% of our operating costs through recurring fees of our managed hub service (making up the remainder in development contracts and grants), and we’ve currently got around 2 years of runway.\nHowever, both of these will be lowered soon because we are about to hire for several more positions. Improvements to our product model will allow us to estimate and recover our service costs more effectively, but we also intend to raise some funds next year to support our efforts in making our service more robust, sustainable, and valuable to communities.\nIt’s always difficult to strike a proper balance of team (and cost) growth against the financial buffer needed to assure your partners you’ll stick around, but we’re confident that the new hires described below will serve critical needs for our team and mission.\nFor more context on why and how we’re trying to make up that capacity, read on…\nHow service growth can lead to team stress # Over the past year we’ve had a slow-but-steady stream of new communities interested in working with 2i2c for managing cloud infrastructure for interactive computing. We’ve taken a “let’s make it work somehow” approach to all of our community partnerships thus far, with the idea that we must use these partnerships to learn what communities want and identify common patterns.\nThis is exciting, and we’re fortunate to see the interest and growth in our service. It suggests to us that something about our model is fundamentally right. Communities really love the Right to Replicate , and our participatory service model based around upstream contributions, transparency, and shared responsibility is attractive to many in research and education.\nHowever, each new community is also a new set of stresses on the technical and social infrastructure of our team. Without the capacity to manage the demands of the service, you run the risk of over-extending – and in a worst case scenario, burning out – your team.\nThis became clear in our first in-person team meeting last May. At that meeting, we realized that many on the team were spending too much of their time “reacting” to demands from the service. We also learned that the scope and complexity of our various workstreams had gotten to a size where our informal team structures of work prioritization were no longer adequate.\nGrowing the complexity of our team to match the complexity of our service # So, for the past several months we’ve been working on a plan to evolve 2i2c’s team structure in order to more effectively manage the complexity of our service, and balance long- and short-term thinking.\nThis began with an organizational audit carried out by makeadifference.digital , a consulting group that focuses on tech-for-good and non-profit products and services. They conducted interviews with everybody on the team, and concluded that we have a few key functions missing that were creating or compounding the stresses people felt.\nWe hope to make some of their key findings public soon (Update: this is now available at this blog post about the organizational report ), and in the meantime here is an overview of some highlights:\nWe need a dedicated product functionality # First, we realized that we have a number of new “signals” pushing our service in many different directions. Some are external - from communities we work with or from funders. Some are internal - from different team member visions …","date":1698710400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1698710400,"objectID":"56a2060396fd8fc0261559080a80c3b2","permalink":"https://2i2c.org/blog/2023/2023-q3-update/","publishdate":"2023-10-31T00:00:00Z","relpermalink":"/blog/2023/2023-q3-update/","section":"blog","summary":"It’s been two quarters since our last major update - this isn’t quite as frequent as we’re hoping to post updates from our team, but we’re making adjustments to have more regular communication for reasons that will hopefully be a bit clearer below!","tags":[],"title":"Community update Q3 2023: Service growth and growing pains","type":"blog"},{"authors":["Chris Holdgraf"],"categories":null,"content":"We’re looking for a Product Lead who will be instrumental in shaping 2i2c’s product vision, strategy, and execution. You’ll own the product vision, align it with user needs, and translate it into a clear product roadmap which defines cross-functional priorities and guides our partnerships and engineering teams, enabling efficient product delivery and continuous improvement.\nFor more information and to apply, see our Greenhouse application page for this job .\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $95,000-125,000 Location: Remote, preference for working hours that maximizes overlap in time zones with the existing team (currently distributed from UTC-7 through UTC+3) Deadline: We will begin reviewing applications around November 5th, and will accept them on a rolling basis until the position is filled. Major duties\nDefine and own the product vision and strategy assuming ‘the voice of the user’, and doing so collaboratively and inclusively.\nCreate a clear product roadmap that guides the engineering and partnerships teams.\nCollaborate closely with our engineers and users in partner organizations to translate the product roadmap into actionable plans and tasks.\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply ","date":1698537600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1698537600,"objectID":"736fcc5a2324d7fcb50c9ab3612b5455","permalink":"https://2i2c.org/jobs/2023/product-lead/","publishdate":"2023-10-29T00:00:00Z","relpermalink":"/jobs/2023/product-lead/","section":"jobs","summary":"We’re looking for a Product Lead who will be instrumental in shaping 2i2c’s product vision, strategy, and execution. You’ll own the product vision, align it with user needs, and translate it into a clear product roadmap which defines cross-functional priorities and guides our partnerships and engineering teams, enabling efficient product delivery and continuous improvement.","tags":null,"title":"Product Lead","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":null,"content":"Please see the Product Lead page .\n","date":1698537600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1698537600,"objectID":"35ad88621447764f761311ccc25df1ae","permalink":"https://2i2c.org/jobs/2023/product-operations-lead/","publishdate":"2023-10-29T00:00:00Z","relpermalink":"/jobs/2023/product-operations-lead/","section":"jobs","summary":"Please see the Product Lead page .","tags":null,"title":"Product Lead","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":null,"content":"We’re looking for a Delivery Manager who will serve as a key facilitator in ensuring the successful and efficient delivery of our product . Acting as a servant leader, you’ll guide our engineering team, promote collaboration, and eliminate obstacles to deliver high-quality results that are aligned with our mission and goals.\nFor more information and to apply, see our Greenhouse application page for this job .\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $85,000 - $107,000 Location: Remote, preference for working hours that maximizes overlap in time zones with the existing team (currently distributed from UTC-7 through UTC+3) Deadline: We will begin reviewing applications around October 23rd, and will accept them on a rolling basis until the position is filled. Major duties\nEnsure the successful and efficient delivery of our product ( https://2i2c.org/service/ )\nOrganize and oversee cross-functional work across the team\nDetailed planning and day-to-day management of engineering tasks\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply ","date":1697155200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1697155200,"objectID":"fcf8bb83f949901857455696d58d36bf","permalink":"https://2i2c.org/jobs/2023/delivery-manager/","publishdate":"2023-10-13T00:00:00Z","relpermalink":"/jobs/2023/delivery-manager/","section":"jobs","summary":"We’re looking for a Delivery Manager who will serve as a key facilitator in ensuring the successful and efficient delivery of our product . Acting as a servant leader, you’ll guide our engineering team, promote collaboration, and eliminate obstacles to deliver high-quality results that are aligned with our mission and goals.","tags":null,"title":"Delivery Manager / Chief of Staff","type":"jobs"},{"authors":["Damián Avila"],"categories":null,"content":"We are looking for an experienced Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on democratizing the design and access to cloud-based resources for research and education purposes. This engineer will be part of an awesome engineering team pushing forward the development and reliable operations of our cloud-based infrastructure.\nFor more information and to apply, see our Greenhouse application page for this job .\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $121,600 - $130,500 Location: Remote, required overlapping for US Pacific timezones Deadline: We will begin reviewing applications around October 16th, and will accept them on a rolling basis until the position is filled. Major duties\nCloud infrastructure management and operations\nSite Reliability Engineering\nDevelopment of open source infrastructure for hosted JupyterHub service\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply ","date":1696896e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1696896e3,"objectID":"6b65905fcd83c557ed5980f2cb93e8c8","permalink":"https://2i2c.org/jobs/2023/23qq4-open-source-infrastructure-engineer/","publishdate":"2023-10-10T00:00:00Z","relpermalink":"/jobs/2023/23qq4-open-source-infrastructure-engineer/","section":"jobs","summary":"We are looking for an experienced Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on democratizing the design and access to cloud-based resources for research and education purposes.","tags":null,"title":"Open Source Infrastructure Engineer","type":"jobs"},{"authors":["Chris Holdgraf","Zack Adell"],"categories":["updates"],"content":"We are thrilled to announce a revitalized visual brand for 2i2c. As we continue to grow and evolve, it’s essential that our branding communicates who we are, what we stand for, and how we envision our future. We hope that this new design will unify our visual style across the many places where 2i2c operates.\nIn pursuit of these objectives, we teamed up with Zack Adell , a designer based in Nairobi who has worked with several similar projects over the years (having most-recently overhauled the Invest in Open Infrastructure brand design ). After several rounds of brainstorming, design reviews, and fine-tuning, we’ve landed on a visual identity that resonates with our organization.\nMeet Our New Logo and design system # Zack has created a set of Brand Guidelines that will guide our use of color and visual style in 2i2c’s materials.\nBelow is our new logo in square and wide form:\nOur logo comprises the International Interactive Computing Collaboration wordmark, characterized by our interactive i. We can fly it just about anywhere. A mark of constant progress \u0026amp; community-driven technology, it isn’t stuck to the borders that separate people. It brings us closer together.\nOur primary and secondary color palette is below:\nColor is the first visual thing we remember and a powerful asset in building brand recognition. Our color is blue. Our community blue says the sky is not the limit. It’s energetic and vibrant, just like the community we serve. And it’s our primary colour, supported by a lively secondary palette that’s as at home on digital platforms as it is on billboards.\nWe’ve chosen two fonts to use in the majory of the text that we write. Poppins for big, bold sentences, and Work Sans for more versatile and everyday use.\nFinally, you might notice these curving, criss-crossing strands in some of our materials. For example, in our new social media header:\nThey’re the strands that intersect and show how our work and values are interconnected to our community. We like them because they represent 2i2c’s core mission, which is to build connections between people, computation, and data in order to share open knowledge. We’ll try and think of creative ways to incorporate them into our visual style.\nWe believe our new visual identity is more than just a fresh coat of paint. It’s a reaffirmation of our commitment to our stakeholders and an exciting milestone in our ongoing journey. We can’t wait for you to see it in action, and are excited to hear what you think about it!\n❗ Note\nIf you’d like to get in touch with Zack Adell, please reach out on his LinkedIn profile , or his Instagram account .\n","date":1694044800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1694044800,"objectID":"7f71c8ae3d34bd6f8c813b9ef11e46d4","permalink":"https://2i2c.org/blog/2023/new-design/","publishdate":"2023-09-07T00:00:00Z","relpermalink":"/blog/2023/new-design/","section":"blog","summary":"We are thrilled to announce a revitalized visual brand for 2i2c. As we continue to grow and evolve, it’s essential that our branding communicates who we are, what we stand for, and how we envision our future.","tags":[],"title":"A new design and logo for 2i2c","type":"blog"},{"authors":["James Munroe"],"categories":null,"content":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for a Technical Content Specialist that will create and curate documentation that supports interactive computing and cloud based open science. It intersects job titles such as “technical writer” and “content creator” while emphasizing previous experience working with open source science and related tools and a desire to share that knowledge.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $75,000 - $85,000 Location: Fully remote Deadline: We will begin reviewing applications around August 2, 2023, and will accept them on a rolling basis until the position is filled. Major duties\nCreate documentation for cloud-based interactive computing.\nCurate documentation and resources from open source and open science projects.\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply If you’re interested in advancing your career at an impact-driven non-profit that is dedicated to open communities and public knowledge, then read on…\nAbout you… # Below are several skills that will make somebody well-suited for this role. You should apply even if you do not have all of these skills. We expect any new hires to learn and grow into this role over time. If you aren’t sure whether you have the right skills for this job, you should just apply! This is a fully remote role with a preference for working hours that overlap timezones with the existing team (currently distributed from UTC-7 through UTC+3).\nNecessary qualities # Demonstrated excellence in communicating complex technical information to learners with a different levels of background and experience Demonstrated experience in using open-science tools (e.g. Python or R) in a scientific or scholarly domain Willingness to continually learn and share emerging technologies and techniques in the interactive computing and open science ecosystems Useful qualities # Experience with open source workflows, research and educational contexts, and an understanding of the value that cloud-based infrastructure provides Experience with the Jupyter ecosystem and other tools for interactive computing Experience working with distributed service teams that use asynchronous methods of communication Experience collaborating and coordinating work via online platforms and distributed revision control Ability to communicate in Spanish, Portuguese, or French What you’ll do… # As a Technical Content Specialist, you’ll be responsible for…\nWorking as part of the 2i2c Partnerships Team towards Community Success Creating documentation (tutorials, how-tos, explainers, and reference materials) that are shared across our communities using cloud-based interactive computing Curating documentation resources from open source and open science projects Developing training materials for communities such as Version control for collaborative cloud-based workflows Environment management for hub administrators Best practices for analysis-ready cloud optimized data Assisting the 2i2c Engineering Team by editing technical documentation and documenting solutions from our support desk Authoring content for 2i2c for use in marketing, blog posts, and website copy. Our benefits and compensation # We believe it is important for mission-driven non-profits to also provide competitive benefits and compensation packages. See our compensation philosophy page for more information about our compensation and benefits.\nHow to apply # 2i2c is committed to hiring processes that are inclusive of people with many lived experiences and qualities. We try to structure our hiring process so that it is predictable, doesn’t take too long, and doesn’t take too much effort.\nIf you’d like to apply for this position, please upload your resume and cover letter using this application form . We will begin reviewing applications after August 2, 2023 and will fill this position on a rolling basis once we find a candidate with the right fit for the job.\n","date":168912e4,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":168912e4,"objectID":"b55c651cd683fdce6e20940d91bbdaf8","permalink":"https://2i2c.org/jobs/2023/technical-content-specialist/","publishdate":"2023-07-12T00:00:00Z","relpermalink":"/jobs/2023/technical-content-specialist/","section":"jobs","summary":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for a Technical Content Specialist that will create and curate documentation that supports interactive computing and cloud based open science.","tags":null,"title":"Technical Content Specialist","type":"jobs"},{"authors":["Georgiana Dolocan"],"categories":["upstream"],"content":"","date":1688083200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1688083200,"objectID":"8c280e2adecd7cb1b2b85030e5aa725a","permalink":"https://2i2c.org/blog/2023/external-jupyter-georgiana-mentor/","publishdate":"2023-06-30T00:00:00Z","relpermalink":"/blog/2023/external-jupyter-georgiana-mentor/","section":"blog","summary":"","tags":[],"title":"On the Jupyter Blog: From intern to mentor.","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"It’s a month after the end of Q1 2023, and we’d like to share a belated update about what we were up to in the first quarter of this year (we have good excuses for being late, including new tiny humans, I promise).\nThis quarter we grew our engineering team significantly, and started to refine our team processes and structures to accommodate this extra complexity. We expanded our managed cloud service with new community partners, and made a number of improvements to our technical infrastructure and organizational processes for managing this service.\nRead on below to learn more about what we’ve been up to!\nNew community partnerships # We added several new community partnerships to our managed hub service. We’ve deployed new hub infrastructure for each of the following groups:\nOur University of Toronto Jupyter service now has a dedicated R hub. We ran an event hub for the Drakkar Ocean project We deployed a hub for the NASA Visuaslization Exploration and Data Analysis (VEDA) project . We deployed a hub for the QuantifiedCarbon organization. We ran an event hub for OceanHackWeek 2023 . We onboarded several new community colleges to our “JupyterHubs Education in Community Colleges” collaboration with CloudBank and UC Berkeley CDSS . Service improvements # Below are a few highlights for ways in which we improved our Managed Cloud Service for our partner communities.\nWe simplified our authentication workflow with CILogon # Authentication services allow us to identify a user when they log onto a hub, which determines their ability to access hub resources. Previously we had used a combination of Auth0 , CILogon , or GitHub for authentication.\nHowever, over the past year we’ve been happy with our use of CILogon so far, especially because of its non-profit status and alignment with many research and education institutions that we work with. This quarter, we decided to streamline our authentication process by dropping the use of Auth0 and grow our partnership with CILogon.\n💡 Learn more\nSee CILogon’s write up about it’s partnership with 2i2c See our blog post about our use of CILogon We exposed user activity dashboards in JupyterHub so communities know how many people are using the service # We tend to work with leaders of communities that utilize our service and infrastructure for many others in their network. For example, a teacher with a classroom of students, or a researcher with a global network of collaborators.\nIn these cases, it’s useful to track how many users are actively using a platform over various metrics of time. This can tell you whether your community finds a service useful, and whether this is growing or shrinking.\nWe use Grafana to automatically generate dashboards of activity for all of our community hubs and clusters. However, tracking daily, weekly, and monthly active users was not part of JupyterHub’s core functionality.\nSo, we decided to upstream this functionality into JupyterHub and expose it via the JupyterHub Grafana project . All 2i2c hubs now track daily, weekly, and monthly unique active users. And importantly, anybody else deploying the Zero to JupyterHub for Kubernetes can use this feature now too.\n💡 Learn more\nSee Yuvi’s blog post about this feature .\nWe made our support process more structured with a new support widget # We’ve added a support widget to our service documentation site . This will allow users to provide structured support requests directly to our team, allowing us to triage and respond more quickly.\nHere’s our support button and widget in action:\nOur fancy new support button! We upgraded Kubernetes across all of our AWS clusters # Kubernetes is at the core of our cloud infrastructure and scalability. We use either a shared or a dedicated Kubernetes cluster for each of our community partners, and it is the foundation upon which all of their Jupyter infrastructure rests.\nOne of the biggest challenges with managing an ongoing cloud service is keeping the underlying infrastructure upgraded. This brings in new stability and functionality, but also often involves manual steps and toil. This quarter, we upgraded each of our AWS JupyterHubs to Kubernetes 1.24 and will continue this effort with other providers in the coming quarters.\nWe streamlined our hub uptime checks to be more efficient # The best kinds of failures are ones that your operations team recognizes and solves before any users run into the problem themselves. We use the Google Cloud Platform HTTP uptime checker to run regular uptime checks for each of the community hubs that we use . This allows us to get quick alerts if any of our community hubs is down for some reason.\nWe made several optimizations to this process so that we can more efficiently monitor hub uptime and trigger alerts to our engineering team if action is needed.\nOrganizational updates # We made a number of broader improvements to our team processes and policies, and even got a shout-out from a few community partners!\nWe defined organizational …","date":168264e4,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":168264e4,"objectID":"837ca10f75690da78e1f6c20c1eef6d2","permalink":"https://2i2c.org/blog/2023/2023-q1-update/","publishdate":"2023-04-28T00:00:00Z","relpermalink":"/blog/2023/2023-q1-update/","section":"blog","summary":"It’s a month after the end of Q1 2023, and we’d like to share a belated update about what we were up to in the first quarter of this year (we have good excuses for being late, including new tiny humans, I promise).","tags":[],"title":"Community update Q1 2023: Growing our community partner network and our team","type":"blog"},{"authors":["Georgiana Dolocan"],"categories":["engineering","partnerships"],"content":" About CILogon # CILogon is an open source service provider that allows users to log in against over 4000 various identity providers, including campus identity providers. The available identity providers are members of InCommon , a federation of universities and other organizations that provide single sign-on access to various resources.\nCILogon and 2i2c # For the past year, 2i2c has been successfully using CILogon for more than fifteen of the hubs it manages.\nCurrently, most of the hubs that use it are hubs for communities in education that want to manage their hub access through their own institutional providers.\nWith using a tool like CILogon, we allow hub access to be managed both through the communities’ institutional providers, but also through social providers like GitHub and Google. Because both authentication mechanisms can coexist, there’s no need to provide specific credentials for 2i2c staff in order to have access to the hub. This reduces both the burden on institution’s IT departments, but also the complexity of a hub deployment.\nMoreover, as we migrate away from our current Auth0 setup, the number of hubs using CILogon will further increase in the following year.\nThe setup # The setup that 2i2c uses, is based on two important tools, the CILogon administrative client and the JupyterHub CILogonOAuthenticator.\nThe CILogon administrative client # The 2i2c administrative client provided by CILogon allowed us to automatically manage the CILogon OAuth applications needed for authenticating into the hub.\nFor each hub that uses CILogon, we dynamically create an OAuth client application in CILogon and store the credentials safely, using the script at cilogon_app.py . The script can also used for updating the callback URLs of an existing OAuth application, deleting a CILogon OAuth application when a hub is removed or changes authentication methods, getting details about an existing OAuth application, getting all existing 2i2c CILogon OAuth applications.\nThe JupyterHub CILogonOAuthenticator # For CILogon’s integration with JupyterHub’s authentication workflow, we’re using the CILogonOAuthenticator , which is part of the JupyterHub OAuthenticator project . This is what allows JupyterHub to use common OAuth providers for authentication, and it’s also a base for writing other Authenticators with any OAuth 2.0 provider.\nAs part of this 2i2c integration with the JupyterHub CILogonOAuthenticator some important upstream fixes and enhancements to the oauthenticator were identified and performed. For example, the GHSA-r7v4-jwx9-wx43 vulnerability was reported and fixed, and a migration guide containing a description of the breaking changes that were made, together with a step by step guide for the users on how to update their usage of JupyterHub CILogonOAuthenticator was provided.\nRead more about how CILogon is setup for use at 2i2c from the docs .\nCelebration # Thanks to the 2i2c - CILogon partnership, during this past year we were able to integrate CILogon into 2i2c’s infrastructure and to observe its importance, usefulness and great support for 2i2c and the communities we server.\nWe are now happy to announce that the 2i2c - CILogon partnership has been expanded to another year!\nAcknowledgements: The upstream jupyterhub-oauthenticator project mentioned in this post as being used at 2i2c is a JupyterHub package, kindly developed and maintained by the JupyterHub community and the 2i2c integration described was developed by the 2i2c engineering team . Also, this post was edited by Jim Basney .\n","date":1677196800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1677196800,"objectID":"ddff52adb91f9fcfcb7d4985bc349b33","permalink":"https://2i2c.org/blog/2023/cilogon-integration/","publishdate":"2023-02-24T00:00:00Z","relpermalink":"/blog/2023/cilogon-integration/","section":"blog","summary":"The following is a summary of how CILogon is used at 2i2c, how the integration works and a celebration of the partnership.","tags":[],"title":"CILogon usage at 2i2c","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["brainstorm"],"content":"This is a brainstorm to consider the principles and guidelines that 2i2c should follow in defining its strategy towards open source communities. See our open source policy documentation for the product of this brainstorm.\nOver the past year the 2i2c team has focused its efforts on deploying, configuring, running, and managing cloud infrastructure that supports open source workflows in research and education. We’ve also done a lot of upstream contribution as a part of our work.\nHowever, we have shied away from taking direct funding for direct development work in open source projects. This is for two primary reasons:\nOur focus has been on managing cloud infrastructure, not developing it. We want to facilitate access to open workflows in interactive computing, which is a different skillset and kind of work than creating those tools. While 2i2c is aligned with the interests of open communities, we are still a distinct organization with our own mission and strategy. We want to be conscious that 2i2c team members have more than one hat, and that their 2i2c hat is necessarily not the same thing as their open source hat. As such, we don’t want to leverage our “other hats” to drive resources to 2i2c without being thoughtful about it. In the last year we’ve found that running infrastructure for research and education gives us great visibility into the kinds of things that these communities want to do, and ways to improve the infrastructure. It also means we can potentially be a conduit of resources from those communities into open source development workflows. For example, we recently partnered with GESIS to make improvements in Binder and JupyterHub .\nSo, this post is a brainstorm to identify some of the major considerations that we should take before agreeing to this kind of work. Its goals is to drive policy that streamlines our ability to seek and accept funding for open source work. It tries to answer this question:\nHow can a stakeholder accept funding on behalf of an open source community in a way that is inclusive, equitable, and effective.\nSome assumptions # First off I want to note that this only applies to open source projects that I’d call “Open communities”. For example, those that follow the principles of open scholarly infrastructure . The ideas here don’t apply to open source projects that are run by single organizations or people. You can assume I’m talking about projects that:\nHave inclusive multi-stakeholder governance and operations. Care about having a broad contributor and leadership base, and want to follow best-practices in inclusive and equitable operations. Need funding to drive major new efforts, or to sustain pre-existing maintenance and community management work. Why is this important? In short, because open projects should care about good governance, and about building sustainable and diverse multi-stakeholder communities around their operations and strategy. While it’s easy to ignore these considerations and just bring in money however you can (open source is perpetually under-funded, after all), it’s crucial that we think about how to do so in a way that aligns with the values of open communities, and that doesn’t simply propagate a “rich get richer” dynamic. Ultimately, the unique value of open communities is not in the technology they create, but in the way that they create it.\ntl;dr: An overview of major considerations # After working with several open source projects over the years, there are a few issues that I’ve seen come up again and again. Here’s a quick summary and I’ll note each in more detail below.\nGovernance: funding should follow major decisions, not make them. It should represent the interests of the project rather than those of a single stakeholder or payer. Transparency: stakeholders that accept funding should be transparent in their accounting (the sources of funding, deliverables attached with it, and operational costs), their plans (the work they plan to do and how they want to do it) and in their strategy (the reason they’re applying for funding in the first place, and how the work fits in with their other operations). Accountability: stakeholders that accept funding should be accountable to the open communities that they are supporting. There should be mechanisms for open communities to provide feedback about and influence their operations, ideally in a powerful position like a board seat. Equity: funding should be shared with others in the project, particularly those that need it or that couldn’t get funding on their own. Moreover, people should be paid for their time - if funding requires work from others, they should be compensated somehow. Inclusion: funding opportunities should be shared with others in a project, particularly those from historically disadvantaged communities. Stakeholders with funding “connections” should use them to boost others in the community as partners, not just as contractors Here is a more in-depth discussion of each below. …","date":1673136e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1673136e3,"objectID":"cb1504c087ebf49007ba3a9d79b5b280","permalink":"https://2i2c.org/blog/2023/open-source-funding-principles/","publishdate":"2023-01-08T00:00:00Z","relpermalink":"/blog/2023/open-source-funding-principles/","section":"blog","summary":"This is a brainstorm to consider the principles and guidelines that 2i2c should follow in defining its strategy towards open source communities. See our open source policy documentation for the product of this brainstorm.","tags":["funding","community","open culture","sustainability"],"title":"Principles and considerations for ethically accepting funding for open source","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["brainstorm"],"content":"2022 was a busy year for 2i2c - we not only grew our operations as well as our organization, but also grew our understanding of our mission and where we can have impact. This is a brief reflection on this experience, and an attempt to identify our opportunities for impact and growth in 2023.\nOur major goals in 2022 # We wrapped up 2021 with two major new changes. We had just finished moving fiscal sponsors and had just finished a prototype of our alpha service offerings .\nOur 2x2 matrix of service offerings and prices created at the end of 2021. See the documentation for more details. Our biggest challenge in 2022 was to identify the bottlenecks in this service model, and to begin building the infrastructure to operate and scale it. This included team infrastructure, technical infrastructure, and administrative infrastructure.\nLet’s see what we did to accomplish this goal.\nHighlights from 2022 # In 2022, we thoughtfully grew the number of communities we worked with, and used this to make iterative improvements in our model. As a result, we learned some important things and made significant improvements to our service model and infrastructure. Here are a few highlights.\nWe grew the number of our partner communities # As noted above, we needed to grow the number and diversity of communities we worked with to understand where our model needed to change. At the end of 2022, we now have 43 community partner hubs across 17 clusters (and at least one on AWS, Azure, and Google Cloud). This amounts to roughly ~2,500 active users each week. We also ran more dedicated infrastructure for more than 11 workshops and events.\nWe grew our revenue from community partnerships # One of our goals is to reach self-sustainability without requiring grant funding for most of the communities we serve. In 2022 we built administrative infrastructure to more efficiently recover monthly costs, and were able to bring in funding for our team from community partnerships. Here’s a plot of our monthly non-grant revenue over the last several months:\nOur monthly non-grant revenue over the last several months. June is much larger because we filled a backlog of invoices from previous months that weren’t billed yet. We got grant funding to serve communities in Latin America and Africa # We also learned that some partnerships may require subsidization from a third party, such as historically marginalized communities and those without dedicated resources. To explore sustainable ways to serve these communities, we applied for and received a new grant to serve communities in Latin America and Africa! Here’s the blog post announcing this grant and our open grant narrative from the proposal .\nWe improved our continuous integration and deployment system # Our ability to sustainably grow our service requires being able to technically serve many communities from a relatively small team. We centralized and standardized configuration and operations of many community hubs in one transparent space for all of our partner communities. This allowed us to more easily grow the number of communities we served from one repository. You can read a write-up about these improvements in this blog post .\nWe defined a Shared Responsibility Model # Our goal is to frame each community hub as a partnership with a clear breakdown of responsibility to give communities more agency over the infrastructure and service. The Shared Responsibility Model provides a framework for assigning responsibility for various tasks with our partner communities. See our Shared Responsibility Model docs here .\nWe defined a formal Incident Response process # Cloud infrastructure inevitably degrades over time, and running ongoing services is largely about quickly responding to issues and resolving them quickly. To do so, we need clear processes to follow in order to quickly identify and respond to major incidents in the infrastructure. Our Incident Response process defines formal team roles and alerting mechanisms that are served by PagerDuty , following best-practices in industry. This will make our service more reliable and make our processes more transparent for our partner communities. Here’s our current incident response process .\nWe expanded our service offerings to include community and workflow guidance # We recognized that many communities need more than just infrastructure running in the cloud - they will also benefit from usecase and community guidance. We’re exploring a new range of roles that we could fill, starting with hiring a new team member to help us lead these efforts. Here’s a blog post about the Product and Community Lead .\nWe began a collaboration with GESIS to develop environment building in JupyterHub # This marks our first efforts into development-focused work as opposed to operating cloud infrastructure. We will use this experience to learn how to pair focused development with cloud operations (more on that below). It will also make it more likely that we can implement …","date":1672790400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1672790400,"objectID":"c0e3dbdaffd9239e9fd35b5e05629012","permalink":"https://2i2c.org/blog/2023/2022-year-in-review/","publishdate":"2023-01-04T00:00:00Z","relpermalink":"/blog/2023/2022-year-in-review/","section":"blog","summary":"2022 was a busy year for 2i2c - we not only grew our operations as well as our organization, but also grew our understanding of our mission and where we can have impact.","tags":["year-in-review"],"title":"2022 in review: growing our partner communities and expanding our operations","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["partnerships"],"content":"We are excited to announce that the team and proposal described in this blog post has been awarded funding by the Chan Zuckerberg Initiative !\nThis announcement may be cross-posted on the websites of several collaborating organizations of this grant. Para leer este post en español, vea el blog de MetaDocencia .\nOur goal is to create a collaborative cloud infrastructure service that enables community-based cloud-native workflows in the biosciences. We will promote values of open and inclusive community practices, infrastructure that enables these practices, and a “train the trainers” approach that empowers community leaders to share expertise in cloud infrastructure with others in their communities. Our focus will be on communities in Latin America and Africa, and we hope to learn how this model could be extended to other global communities that are historically marginalized from large-scale scientific infrastructure projects.\n2i2c will be providing cloud infrastructure operation and support for the communities that we partner with in this effort. We will also assist with creating content to teach cloud-native workflows and assist community leaders in learning this content so that they can share these skills with others.\nThis is a collaborative effort between 2i2c , The Carpentries , CSCCE , Invest in Open Infrastructure , MetaDocencia , and Open Life Science . For more detailed information, see the blog post with our full grant narrative .\nWe are hiring # As a part of this effort, we will also hire several new team members! There are currently two job postings open. Here are links for more information in case you are interested:\nCloud infrastructure engineer to join 2i2c’s Site Reliability Engineering team that will operate and support the cloud infrastructure in this project. Programme manager role to join Open Life Science and support this project via project management and operational support. We may be hiring other positions related to this effort, so please stay tuned for more information if you are interested.\nWhere to follow along # If you’d like to follow along with this work, please share your e-mail address in this short form . We’ll send updates as we work out longer-term spaces for communication or documentation.\n💡 Follow our work! Sign up for our mailing list for updates about 2i2c. Send us an e-mail about collaborating or partnering on a project. See our Service Documentation or our Team Compass to learn about our service and organization.\n","date":1671494400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1671494400,"objectID":"26124d90c14d8aa219d01a1a27ef7a9b","permalink":"https://2i2c.org/blog/2022/czi-global-communities-announcement/","publishdate":"2022-12-20T00:00:00Z","relpermalink":"/blog/2022/czi-global-communities-announcement/","section":"blog","summary":"We are excited to announce that the team and proposal described in this blog post has been awarded funding by the Chan Zuckerberg Initiative !\nThis announcement may be cross-posted on the websites of several collaborating organizations of this grant.","tags":[],"title":"New project: Open science cloud infrastructure and training for communities in Latin America and Africa","type":"blog"},{"authors":["Damián Avila","Arnim Bleier","Chris Holdgraf"],"categories":["partnerships"],"content":" Introduction # Mybinder.org enables researchers across the world to replicate computational environments in the cloud. It allows researchers to turn static code into interactive literate coding environments with a click of a button within seconds. The mybinder.org service is powered by BinderHub , an open-source tool developed by the Jupyter Project that many organizations have deployed for their own communities. It does this by _dynamically building _the software environment needed to reproduce a computation (using a tool called repo2docker ), and making this environment available to users.\nBinderHub was developed for use-cases that are temporary and fully open by design. BinderHub sessions are destroyed after a fixed amount of time and there is no persistent storage or authentication. However, many research institutions also need more “standard” service features like authentication and persistent storage.\nOver the past several years, the GESIS Notebooks team made the first steps towards bridging this gap through their Persistent BinderHub implementation. This was a modified and authenticated BinderHub that included persistent storage across sessions. The Persistent BinderHub service was very successful at GESIS and with its partner communities, and the team wishes to build this functionality into the JupyterHub community’s core technology so that these features can be enjoyed for more use-cases and by many communities.\nTo enable this vision, we have partnered with GESIS in cooperation with NFDI4DS (GAN: 460234259), CESSDA , and members of the JMTE project. This collaboration has three primary goals:\nGeneralize the Persistent BinderHub functionality/experience to run on cloud-agnostic infrastructure, so that other stakeholders in NFDI, CESSDA, and the broader scientific community may benefit from this functionality and experience. Upstream this functionality by making contributions into Jupyter community projects, so that it will be maintained and improved by a community moving forward, thus improving its reliability and sustainability. Improve the implementation and user experience around Persistent BinderHub, in order to make it more reliable, scalable, productive, and enjoyable to use. We began this collaboration several months ago, and have focused our efforts on exploring potential implementation pathways for this functionality. We believe that we now have a path forward for this functionality, and this blog post is a brief report of our efforts and future plans as we undertake this effort. See this GitHub Projects Board for issues that implement this effort .\nExploration 1: Adding persistent storage directly into BinderHub # Our initial intention was to incorporate persistent storage and authentication from the GESIS Persistent BinderHub into the BinderHub codebase . We began by holding a series of meetings to discuss technical requirements from our experience in the JupyterHub/BinderHub ecosystem, and also conducted an audit of the Persistent BinderHub codebase . The Persistent BinderHub implementation is a modified Helm Chart that configures a JupyterHub to expose its authentication and persistent storage functionality, overriding the BinderHub default behavior. We were concerned that building this functionality natively into BinderHub would be challenging given that the BinderHub codebase was designed for ephemeral user sessions.\nSo, we decided to take another approach:\nExploration 2: Add dynamic image building to JupyterHub # We realized that there is a way to make this functionality more broadly useful and more maintainable, while still achieving the end-user experience that the GESIS team needed. Instead of modifying BinderHub to incorporate JupyterHub’s storage and authentication features, we would give JupyterHub the ability do dynamically generate user environments using repo2docker .\nThis would give JupyterHub users more flexibility over the environments served by their hub, and expose Binder-style workflows to the “typical” JupyterHub workflow. BinderHub could then be simplified to re-use JupyterHub’s image building functionality as a part of its own service. We also identified a prototype of this functionality in the tljh-repo2docker project that QuantStack had built for the PlasmaBio project . This implementation was seen as successful, and something others in the community had wanted to generalize for some time.\nOur implementation plan # Two phases of implementation # With this alternative implementation route in place, we identified two major steps to accomplish this project:\nBuild a back-end for dynamic environment building. JupyterHub needs to understand how to call repo2docker’s image generation from a Docker-based environment. It needs to expose this ability via APIs that others can build interfaces on top of. **Build a front-end that is user-friendly and accessible. **Once the back-end is functional, we must build a front-end experience that feels familiar to BinderHub users and …","date":1669593600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1669593600,"objectID":"6a55a575b40906e55bc3821000992da8","permalink":"https://2i2c.org/blog/2022/gesis-2i2c-collaboration-update/","publishdate":"2022-11-28T00:00:00Z","relpermalink":"/blog/2022/gesis-2i2c-collaboration-update/","section":"blog","summary":"Introduction # Mybinder.org enables researchers across the world to replicate computational environments in the cloud. It allows researchers to turn static code into interactive literate coding environments with a click of a button within seconds.","tags":[],"title":"GESIS - 2i2c collaborate to build a persistent BinderHub experience","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"We recently completed a progress report for Year 2 of our primary CZI funding grant. This funding covers some core operations of 2i2c as well as engineering capacity to run our cloud infrastructure for JupyterHubs.\nBelow is a link to the 3-page grant narrative that summarizes some of our major progress and milestones from year two:\nhttps://zenodo.org/record/7319289 ","date":1668297600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1668297600,"objectID":"fdb1d1be20547d95ad76ddc8a5154853","permalink":"https://2i2c.org/blog/2022/czi-year2-progress-report/","publishdate":"2022-11-13T00:00:00Z","relpermalink":"/blog/2022/czi-year2-progress-report/","section":"blog","summary":"We recently completed a progress report for Year 2 of our primary CZI funding grant. This funding covers some core operations of 2i2c as well as engineering capacity to run our cloud infrastructure for JupyterHubs.","tags":[],"title":"Grant progress report: CZI Foundational grant year 2","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Quarter 3 of 2022 has wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.\nBelow we’ll provide a brief update about major developments this quarter, broken down by functional areas of 2i2c.\nThese are the main highlights from this quarter - if you’d like to check out more of the work that we’ve done, see:\nAll the PRs we’ve merged in Q3\nAll closed issues in Q3\nCommunity impact # These are a few ways in which we’ve collaborated with communities and demonstrated impact over the last few months.\nNew JupyterHubs for communities. We’ve deployed JupyterHubs for several new partner communities. Here’s a quick list:\nPaleoCube and PaleoHack Hubs infrastructure#1418 NeuroHackademy 2022 infrastructure#1505 Alabama Water Institute CIROH hub infrastructure#1444 OceanHackWeek 2022 infrastructure#1515 COESSING Pangeo-Style Hub infrastructure#1516 Temple University Education Hub infrastructure#1648 Callysto Hub infrastructure#1439 London Interdisciplinary School infrastructure#1485 We also ran hubs for several community events:\nNeuroHackademy: infrastructure#1300 OceanHackWeek 2022 infrastructure#1576 COESSING workshop: infrastructure#1516 Eddy Symposium: infrastructure#467 Allen Institute Summer Workshop on the Dynamic Brain infrastructure#1621 For a recap of one of these events, see our recent blog post on the Jack Eddy symposium .\nIf you are interested in partnering with 2i2c to have your own managed JupyterHub, please contact us at partnerships@2i2c.org. We have a shared cluster on Google Cloud, with plans to deploy one on AWS soon, and dedicated clusters can be run on any major cloud provider. Please see our service documentation for more details.\nOrganization wide updates # These are large-scale organizational and strategic efforts that impact all of 2i2c.\nWe applied for a CZI Grant: In partership with The Carpentries, CSCCE, MetaDocencia, Invest in Open Infrastructure, and OpenLifeScience, we applied for a CZI grant to provide cloud infrastructure services to global communities .\nWe grew our team: We’ve hired two new team members to lead new major efforts with 2i2c. James Munroe will lead efforts around community guidance and product design, and Jim Colliander will lead efforts around partnerships and sustainability. We also updated our Hiring and Candidate Search documentation in the process.\nWe’re refining our strategy: We’ve begun a process of revisiting and refining our strategy after a year of major operations, see our strategic update blog post for more information .\nWe completed the CSCCE community management training. Two of our team members (James and Sarah) both completed a several-week community management course that was offered in partnership with CZI .\nOur team member Sarah began a part-time role as the JupyterHub Community Strategic Lead. Sarah will be leading community strategy efforts within JupyterHub for the next two years thanks to a grant to the JupyterHub team from CZI. Check out this issue to follow our progress .\nService improvements # We made a number of improvements to our cloud infrastructure and the processes around our service. Here’s a brief breakdown:\nWe expanded our shared clusters to new cloud providers and regions. We now have shared clusters already deployed on Google Cloud Platform on us-central1-b and europe-west2.\nWe defined an incident commander process. This will allow us to coordinate and respond to major outages in our cloud infrastructure more efficiently. See our incident response documentation for more information.\nWe improved our cloud usage monitoring infrastructure. We’ve deployed a centralized Grafana Dashboard that aggregates cloud usage across all of our partner communities, and allows us to keep track of any unexpected behavior or outages across them all.\nWhere we’re focusing next # In the final quarter of this year, we’ve decided to focus our efforts on growing capacity across all of the aspects of our team. Now that we have brought on several more partner communities into our Managed JupyterHub Service, it has shown us where we have bottlenecks in our technology, process, and structure. In 2023 we hope to significantly grow the number of communities we work with, and so we must grow our capacity to be able to take on these new partnerships.\nWe aim to accomplish this in a few ways:\nMake technical improvements to our cloud infrastructure that reduces the amount of human labor associated with regular actions. This will make our cloud infrastructure more scalable and reliable. Improve our invoicing and partnership leads pipeline so that we can reduce the amount of administrative toil for ourselves and for the communities we work with in billing and cloud cost pass-through. Refine our organizational strategy and structure so that we are better-able to agree on our most …","date":1665878400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1665878400,"objectID":"034121fa0c6758b2d545cbf6ae5d813c","permalink":"https://2i2c.org/blog/2022/q3-update/","publishdate":"2022-10-16T00:00:00Z","relpermalink":"/blog/2022/q3-update/","section":"blog","summary":"Quarter 3 of 2022 has wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.","tags":[],"title":"Celebrating our progress in Q3 2022","type":"blog"},{"authors":["Damián Avila"],"categories":null,"content":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for an Open Source Infrastructure Engineer that will join our Site Reliability Engineering team and make our cloud infrastructure more reliable, scalable, and efficient. It will help build a future of data-intensive scientific research and democratize the design and access to cloud-based resources for research and education purposes.\nIf you’re interested, learn more about 2i2c at the links below, and more about this job posting on the rest of this page.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $120,000 - $135,000 Location: preferred at the US/Pacific time zone Deadline: We will begin reviewing applications around November 17th, and will accept them on a rolling basis until the position is filled. Major duties\nSite Reliability Engineering\nCloud infrastructure management, operations, and support.\nDevelopment of open source infrastructure for hosted JupyterHub service\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply Who we are # 2i2c is a non-profit organization with a mission to make interactive computing more accessible, scalable, and powerful for research and education: https://2i2c.org/organization/ .\nWe accomplish this mission by providing managed cloud services for interactive computing, by providing development and technical leadership to researchers and educators that utilize this infrastructure for specific communities, and by providing support for open source tools and communities in this ecosystem.\nWe have deep ties to the open source community, and have been leaders and core contributors across dozens of projects - in particular in the Jupyter ecosystem. We also have deep ties to research and education - our team has spent years deploying infrastructure for universities, community colleges, and research teams, and now we’re bringing this experience to a wider audience with 2i2c.\nWe believe strongly in communities that are inclusive, transparent, equitable, effective, and diverse, especially 2i2c itself. We believe that our values should permeate everything about 2i2c, including the work we do, the communities we serve, and our own organizational culture.\n2i2c is a fiscally sponsored project of Code for Science and Society , a registered US 501(c)(3) nonprofit corporation.\nWhat you’ll do # Ensure the reliable operation of the 2i2c infrastructure (leveraging production-ready cloud-based tools such as JupyterHub, BinderHub and Dask). Address support issues Explore emerging technologies in the Cloud / DevOps space, design and implement cloud computing architecture in partnership with our team. Participate in upstream open source communities we rely on (such as JupyterHub, BinderHub, Dask, etc) in partnership with the established leaders of those communities and collaborate with the Community Lead in the education and outreach around cloud computing. Work with a distributed and global team - team members are given a lot of autonomy, and expected to be proactive at communicating with one another and working with others to allocate effort that will maximize our impact. Essential requirements # Experience deploying applications on cloud infrastructure. Experience deploying and developing with Linux container-based technologies, such as Docker and Kubernetes. Experience with continuous integration services (e.g. Circle CI, GitHub workflows). Experience developing tools in a general purpose programming language (eg. Python). Experience collaborating and coordinating work via online platforms, such as GitHub, GitLab, or BitBucket, and distributed revision control. Experience working with distributed service teams that use asynchronous methods of communication Desirable requirements # Experience with major cloud providers. Experience in programming and software engineering with a track record of leadership in open, collaborative projects with broad community adoption. Experience working on geographically distributed open-source projects. Experience with the Jupyter ecosystem and other tools for interactive computing. Evidence of existing connections and relationships in the worldwide ecosystem of open source software for data-intensive research and ability to establish new ones. Experience with common data science methods, platforms, workflows, and infrastructures; with data management systems, practices, and standards; and the capacity to gain familiarity with new related topics. Experience engaging with highly technical researchers across a variety of methodological fields, research domains, and computational platforms. Experience building and maintaining continuous deployment pipelines. Interpersonal skills to work with researchers and …","date":1665705600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1665705600,"objectID":"fadeab2639f3679bd21677cc03d303a3","permalink":"https://2i2c.org/jobs/2022/open-source-infrastructure-engineer/","publishdate":"2022-10-14T00:00:00Z","relpermalink":"/jobs/2022/open-source-infrastructure-engineer/","section":"jobs","summary":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for an Open Source Infrastructure Engineer that will join our Site Reliability Engineering team and make our cloud infrastructure more reliable, scalable, and efficient.","tags":null,"title":"Open Source Infrastructure Engineer: Site Reliability Engineering and Cloud Infrastructure","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":["brainstorm"],"content":"This post is an exploration of 2i2c’s current strategy and direction after a year of major operations. It is a brainstorm from the Executive Director, shared as a blog post to invite feedback and provide transparency into our current thinking. Its goal is to explore the context of 2i2c’s stakeholders and their needs, and identify an opportunity and plan for having a positive impact with these communities. It is not a concrete proposal but a snapshot of thinking in time meant to trigger reflection. Over time we will incorporate some of these ideas into our Team Compass .\nWhen we founded 2i2c, we largely did so from the “bottom up” - we identified several patterns around hosted infrastructure that were useful at UC Berkeley , Pangeo , and similar communities, and we wished to make them more generalized, accessible, and scalable.\nWe defined our mission as the following:\nOur mission is to make research and education more impactful, accessible, and delightful by developing, operating, and supporting infrastructure for interactive computing.\nAnd a description about our immediate activities to make things a bit more concrete:\n2i2c designs, develops, and operates JupyterHubs in the cloud for communities of practice in research \u0026amp; education. It builds and supports open source infrastructure that serves these communities.\nAround a year ago we began our pilot JupyterHubs project to learn more about our biggest challenges and opportunities in making interactive computing more accessible and useful for research and education. While both of these statements are still accurate, over the past year we’ve also learned more about the value that 2i2c provides. This post is an exploration of how these statements and our strategy may evolve in the near future.\nWhat did we miss with our original strategy? # In short: it is too-focused on actions rather than impact.\nWhile running JupyterHubs is a key part of what 2i2c does, it is a means to an end rather than our end-goal. Infrastructure is only useful if it changes workflows in a way that aligns with the goals and values that we wish to achieve. We’ve historically defined these in a few scattered places. For example, here are the values listed on our website:\n2i2c values fairness and justice as requirements for successful communities. 2i2c values learning and discovery for all people. 2i2c values collaborating and connecting to foster environments for learning and discovery. However, it is difficult to tie our operations directly to values and goals without making them concrete, and without defining a plan that ties them to our work.\nThrough our JupyterHubs pilot, we’ve learned how our actions-focused approach was missing some important aspects of these broader goals. For example, we came to understand that a big part of 2i2c’s value isn’t just providing a JupyterHub, it is de-risking cloud native workflows for communities that are inherently skeptical of what cloud infrastructure offers. Doing this entails many things: teaching, making decisions on behalf of others, supporting and answering questions, building trust, and yes, managing infrastructure.\nRefining our strategy # With this in mind, we’d like to make our strategy more clearly-defined and tied to our operational choices. Here are a few ways we’d like to do this:\nDefine our organization’s values and vision for the impact we wish to have. Define the key stakeholder communities that we wish to serve, the context of tools and services that are relevant to these stakeholders, and the assumptions we’re making. Define the problems these stakeholders have, the ways in which their current workflow could be improved, and the opportunity to help them. Describe our strategy to positively impact these stakeholders with our work. Define a collection of goals and objectives to carry out this strategy in the near-term. The rest of this post will take a crack at answering a few of these questions. It is intentionally messy, and meant both as a public snapshot of my thinking at this moment, and fodder for discussion and more specific proposals in the future.\nContext: Our key stakeholders and the impact we wish to have # 2i2c’s key stakeholders are communities of practice that are dedicated to creating and sharing public knowledge. These are primarily made up of researchers and educators in the global community.\nFor these stakeholders, we wish to catalyze and support a transformation in their data workflows that allows them to be more collaborative, inclusive, efficient, and powerful in the impact they wish to have.\nAssumptions we make about our stakeholders # There are a few unique things about these communities that are important for us:\nResearchers and educators see their job as creating and sharing knowledge with a heterogeneous and global community. They can’t make many assumptions about the organizational context or resources of this community, or their work will become inaccessible to others. They work at vertically-oriented …","date":1665273600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1665273600,"objectID":"6f97410cb47b43db748265b2c83455a3","permalink":"https://2i2c.org/blog/2022/strategic-update/","publishdate":"2022-10-09T00:00:00Z","relpermalink":"/blog/2022/strategic-update/","section":"blog","summary":"This post is an exploration of 2i2c’s current strategy and direction after a year of major operations. It is a brainstorm from the Executive Director, shared as a blog post to invite feedback and provide transparency into our current thinking.","tags":[],"title":"One year later: an update of 2i2c's mission, strategy, and impact","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["partnerships"],"content":"We recently submitted a grant to Chan Zuckerberg Initiative and wish to share some details about it as well as the grant narrative for others to read and re-use.\nGo to Zenodo record Read on for a quick overview of the proposal.\nCollaborators # This grant is a collaboration between several leading organizations in open infrastructure, community, and global leadership:\n2i2c The Carpentries Center for Scientific Collaboration and Community Engagement Invest in Open Infrastructure MetaDocencia Open Life Science Problem statement # Cloud infrastructure is a powerful way to broaden access to workflows and infrastructure across the globe. However, it is also inaccessible to many for a variety of reasons:\nThere is a large, diverse, and messy ecosystem of open source tools to facilitate cloud infrastructure. Most communities don’t already have skills in utilizing cloud workflows. Running infrastructure in the cloud takes dedicated time and expertise that many communities lack. Many communities do not have organized communities of practice around cloud infrastructure. These issues are true for most scientific communities, but they are exacerbated in countries that are often marginalized in the global scientific community.\nOur proposed work # For this reason, our goal in this grant is to provide human and technical services to facilitate learning and knowledge transfer of cloud workflows for communities in Latin America and Africa.\nIt defines four major areas of collaboration:\nCloud infrastructure management - to facilitate access to cloud resources via managed cloud services that integrate open source tools. Application guidance and training - to provide community leaders with the skills to utilize this infrastructure for their needs. This includes language-localized content and training materials. Training for trainers - to provide community leaders with skills to share these workflows with others in their communities. Community leadership and management - to provide community leaders with skills to sustain and grow healthy communities of practice. If this proposal is funded, over the course of two years the team will provide a combination of the services described above for communities in Latin America and Africa, with the goal of understanding how such services can be most useful for these communities, how we can structure them to provide community representation in the direction of these services, and how we can sustain and scale this model of community-focused services for a global community.\nImportantly, we wish to do this work in a way that centers the communities we work with as co-leaders and collaborators in these services. We will explore ways to run these services and workshops so that they are transparent, inclusive, and give agency to the communities they support. Ultimately, we hope that this can be an extensible model for many more communities in the future.\nIf you’re interested in this work, would like to discuss its ideas, or think something similar might be useful for your community, please reach out!\nSend us an email ","date":1661644800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1661644800,"objectID":"5ccaad99757bb2ca2ec3362260d77d89","permalink":"https://2i2c.org/blog/2022/czi-global-communities-proposal/","publishdate":"2022-08-28T00:00:00Z","relpermalink":"/blog/2022/czi-global-communities-proposal/","section":"blog","summary":"We recently submitted a grant to Chan Zuckerberg Initiative and wish to share some details about it as well as the grant narrative for others to read and re-use.\nGo to Zenodo record Read on for a quick overview of the proposal.","tags":[],"title":"Open grant narrative: A Collaborative Interactive Computing Service Model for Global Communities","type":"blog"},{"authors":["James Colliander"],"categories":["community"],"content":" Reflections on the Jack Eddy Symposium # 2i2c supported and participated in the 3rd Eddy Cross Disciplinary Symposium held recently in Vail Colorado. The event was hosted by the Cooperative Programs for the Advancement of Earth System Science ( CPAESS ) team at the University Corporation for Atmospheric Research ( UCAR ) with support from NASA.\nContext # The Symposium was framed by the interesting and interdisciplinary scientific career of the late Jack Eddy . Eddy’s legacy was highlighted and his influence has been extended by dynamic leadership from NASA Program Officer Madhulika Guhathakurta (Lika) . Lika helped launch and has sustained NASA’s Living with a Star (LWS) program over the past two decades. Prior to LWS, NASA had a variety of siloed efforts focused on near-Sun and near-Earth behavior. The LWS program led to an integration of these efforts under “system science” or “systems engineering” approaches and an expressed desired to connect LWS research activities with impacts on Earth (society, biology, culture, etc.). The program has expanded to include explorations of similar questions arising around other planets in our solar system and the recently discovered collection of exoplanets. Scientists from diverse disciplines (plasma physics, stellar evolution, atmospheric chemistry, space weather, planetary science,…) work together on “cross disciplinary” research that helps us understand our lives near our star.\nThe Symposium focused on three disciplinary areas (Exoplanets; Sun-Climate and Star-Climate interactions; Risk and resilience of space weather) unified under the cross-cutting thread of open science. Frequent references were made to the upcoming 2023 Year of Open Science and NASA’s Transform to Open Science (TOPS) mission . Symposium attendees listened to talks surveying the four areas in the morning and participated in hackathon-style breakout projects during the afternoons. Work on the projects launched at the Eddy Symposium continues . The space weather group is investigating ways to make the power grid more resilient. The Sun-climate group is exploring plans to establish an institute focused on Sun-climate interactions and improve connections between climate and heliophysics research communities. The exoplanets team is developing tools to programmatically compare Sun-Earth and star-exoplanet interactions.\n2i2c’s role # 2i2c, with input from Symposium CoChair’s Dan Marsh and Ryan McGranaghan , rapidly deployed a cloud-hosted JupyterHub for use during the event. The hub provided a shared space for participants to explore data, run analyses, and collaborate with one another using modern tools including Zarr, Xarray and Dask Gateway. Access to the interactive computing platform was granted to any member of the Symposium’s GitHub organization . The work to set up that hub, openly chronicled in this GitHub issue ( 2i2c-org/infrastructure#1329 ), included swapping out a Pangeo-style software environment for a heliophysics-specific resource developed by HelioCloud with special thanks to Brian Thomas !\n2i2c co-founder Fernando Pérez gave a talk on how he is “living la vida nube” . Fernando described the ways he, research collaborators, and students are using the Jupyter ecosystem. Diverse and curated tools in Jupyter hubs for the Jupyter Meets the Earth Project and Berkeley’s data science programs were highlighted. The talk showcased how these tools have been integrated to support individuals and communities of practice in data-driven research. In response to requests from the organizers and participants, Fernando gave a demonstration on how to use the hub 2i2c set up for the Symposium and an introduction to version control using git.\n2i2c co-founder Jim Colliander gave a talk titled Governing the Science Commons . Three key points from Jim’s talk were: the virtue that should guide the improvements to the scientific enterprise is intellectual generosity; implementation of intellectual generosity into science requires commons-based governance; the convergence of open source tools that support data-intensive collaborative research and learning (as showcased by Fernando) and agency interest ( NASA TOPS , UNESCO ) in open science is an inflection point for global change. The talk ended with a call to action for the diverse communities represented at the Symposium to improve the ways we do science.\nThings we learned # Our experience with the Symposium taught 2i2c a few things.\nWe learned that our engineering team can rapidly deploy interactive computing resources to support a research and education community. Along the way, we confirmed what we’ve been learning from Pangeo and the neuroscience communities: flexible methods to customize the software environment are necessary. We confirmed that our developing shared responsibility model , enabling domain-specific experts to provide curated toolchains for their communities while leveraging 2i2c’s infrastructure expertise, is the right approach.\nWe …","date":1657756800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1657756800,"objectID":"5d36d9cc84a68609f47fb32b7b8d0f39","permalink":"https://2i2c.org/blog/2022/eddy-symposium-report/","publishdate":"2022-07-14T00:00:00Z","relpermalink":"/blog/2022/eddy-symposium-report/","section":"blog","summary":"Reflections on the Jack Eddy Symposium # 2i2c supported and participated in the 3rd Eddy Cross Disciplinary Symposium held recently in Vail Colorado. The event was hosted by the Cooperative Programs for the Advancement of Earth System Science ( CPAESS ) team at the University Corporation for Atmospheric Research ( UCAR ) with support from NASA.","tags":[],"title":"Reflections on the Jack Eddy Symposium","type":"blog"},{"authors":["Sarah Gibson"],"categories":["engineering"],"content":"2i2c manages the configuration and deployment of multiple Kubernetes clusters and JupyterHubs from a single open infrastructure repository . This is a challenging problem, as it requires us to centralize information about a number of independent cloud services, and deploy them in an efficient and reliable manner. Our initial attempt at this had a number of inefficiencies, and we recently completed an overhaul of its configuration and deployment infrastructure.\nThis post is a short description of what we did and the benefit that it had. It covers the technical details and provides links to more information about our deployment setup. We hope that it helps other organizations make similar improvements to their own infrastructure.\nOur problem # 2i2c’s problem is similar to that of many large organizations that have independent sub-communities within them. We must centralize the operation and configuration of JupyterHubs in order to boost our efficiency in developing and operating them, but must also treat these hubs independently because their user communities are not necessarily related, and because we want communities to be able to replicate their infrastructure on their own .\nA year ago, we built the first version of our deployment infrastructure at github.com/2i2c-org/infrastructure . Over the last year of operation, we identified a number of major shortcomings:\nWithin a Kubernetes cluster, we deployed hubs sequentially, not in parallel. This grew out of a common practice of Canary deployments that allowed us to test changes on a staging hub before rolling them out to a production hub. We used a single configuration file for all hubs within a cluster, which led to confusion and difficulty in identifying a hub-specific configuration. Moreover, any change to a hub within a cluster caused a re-deploy of all hubs on that cluster. This is because we did not know whether a given change touched cluster-wide configuration or hub-specific configuration. Our goal # So, we spent several weeks discussing a plan to resolve these major problems - here were our goals:\nWe should be able to upgrade a specific hub alone, by inspecting which configuration files have been added or modified. Production hubs should be upgraded in parallel when they are effectively run independently. We should use staging hubs as “canary” deployments and not continue upgrading production hubs if the staging hub fails. An overview of our changes # To accomplish this, we needed to identify which hub required an upgrade based on file additions/modifications. This took a lot of discussion and iteration on design, and so we share it below in the hopes that it is helpful to others!\nImprovements to our code and structure # We made a few major changes to the infrastructure repository to facilitate the deployment logic described above. Here are the major changes we implemented:\nWe separated each hub’s configuration into its own file, or set of files. For example, here is 2i2c’s staging hub configuration . We created a separate cluster.yaml file that holds the canonical list of hubs deployed to that cluster and the configuration file(s) associated with each one. For example, here is 2i2c’s GKE cluster configuration , which contains a reference to the previously mentioned staging hub . We updated our deployer module to do the following things: Inspect the list of files modified in a Pull Request. From this list, calculate the name of a hub that required an upgrade, and the name of its respective cluster. Trigger a GitHub Actions workflow that deploys changes in parallel for each cluster/hub pair. In addition to these structural and code changes, we also developed new GitHub Actions workflows that control the entire process.\nA GitHub Actions workflow for upgrading our JupyterHubs # We defined a new GitHub Actions workflow that carries out the logic described above. These are all defined in this deploy-hubs.yaml configuration file . Here are the major jobs in this workflow, and what each does:\ngenerate-jobs: Generate a list of clusters/hubs that must be upgraded, given the files that are changed in a Pull Request.\nEvaluate an input list of added/modified files in a PR Decide if the added/modified files warrant an upgrade of a hub Generate a list of hubs and clusters that require upgrades, and some extra details: Does the support chart that is deployed to the cluster also need an upgrade? Does a staging hub on this cluster require an upgrade? This produced two outputs to be used in subsequent steps:\nA human-readable table including information on why a given deployment requires an upgrade (using the excellent Rich library ). JSON outputs that can be interpreted by GitHub Actions as sets of matrix jobs to run. Our staging and support hub job matrix tells GitHub Actions to deploy staging and support upgrades that act as canaries and stop production deploys if they fail. upgrade-support-and-staging: Update the support and staging Helm charts on each cluster. …","date":1650326400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1650326400,"objectID":"91264ab8963bcd7c30384d1bd6f92b1a","permalink":"https://2i2c.org/blog/2022/ci-cd-improvements/","publishdate":"2022-04-19T00:00:00Z","relpermalink":"/blog/2022/ci-cd-improvements/","section":"blog","summary":"2i2c manages the configuration and deployment of multiple Kubernetes clusters and JupyterHubs from a single open infrastructure repository . This is a challenging problem, as it requires us to centralize information about a number of independent cloud services, and deploy them in an efficient and reliable manner.","tags":[],"title":"Tech update: Multiple JupyterHubs, multiple clusters, one repository.","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Quarter 1 of 2022 just wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.\nThese are the main highlights from this quarter - if you’d like to check out more of the work that we’ve done, see:\nAll the PRs we’ve merged in Q1 All closed issues in Q1 Infrastructure improvements # This quarter we did a deep dive into a number of core infrastructure improvements for our Managed JupyterHubs Service . Here are a few highlights:\nInfrastructure reliability and efficiency. We improved the resiliency, reliability, and efficiency of our deployment infrastructure . For example, we refactored our hub configuration so that each community is better-able to track it, we implemented validation steps to ensure that we don’t accidentally push incorrect config to the hubs, and we’ve significantly improved our CI/CD pipeline to push deployments out to our hubs more efficiently. Automatic deployments to commercial cloud. With the ICESat hackweek as a test-case for AWS, we’ve finished automating the deployment of clusters and hubs to each major commercial cloud. (there’s not a specific issue for this as it has been a multi-month effort over many PRs and issues!) CILogon authentication. CILogon is a non-profit organization that provides “single-sign on” authentication services for the same communities that 2i2c serves. We’ve partnered with them to prototype using CILogon for 2i2c’s hubs , which should make it much easier for communities to user their own institutional sign-ons. Communities we’ve served and lessons learned # As described in our Managed Hub Services strategy , our goals for this phase of our organization are to balance serving communities of practice and learning where we can improve our infrastructure and practices. With that in mind, here are a few highlights of communities we’ve served, and what we’ve learned from it:\nWe grew a hub for the University of Toronto to around 4000 monthly users. This has taught us a lot about where our support and operations can and cannot scale, and where we have gaps in our sustainability / pricing model. We deployed CILogon on a hub for a class at Australian National University . This gives us an opportunity to work out any UX issues and improvements to be made before a deeper CILogon integration. We deployed a dedicated database per user for a databases course at UT Austin . This is helping us learn more about how to pair slightly more customized per-user infrastructure with our standard hub setups, as well as how our Right to Replicate model could be followed for more complex setups like a database. We ran an event hub for the ICESat2 HackWeek at the University of Washington. This helped refine our infrastructure and expertise with AWS, as well as improved our event “ready mode” practices. We deployed a new hub for the LEAP project . This has given us an opportunity to prototype new processes for pass-through cloud costs to simplify our deployments. Organizational improvements\nBeyond our technical and community impact work, we’ve made a lot of significant organizational improvements as well.\nWe designed a new role in Product and Community Management . We’re excited for this new hire to spearhead efforts in guiding and developing relationships with the communities we serve, as well as guiding and collaborating with our engineering team in developing our services. We designed a new Project Manager role . Our engineering team had been operating as a largely autonomous and independent group, but we’ve realized that we would benefit from someone to help coordinate our actions and plans, especially as we balance more operations/support issues in addition to new development. This new role is an experiment at growing this capacity within our team, in the hopes that we can dedicate a team member to it in the future. What’s next # We are still working out our major priorities for the oncoming quarter, but have a few major projects in the works that we’re hopeful to make progress on quickly. Here are a few major examples:\nImprove our process and operations around supporting our users. We are discussing first- and second-line support processes to make our team more responsive and effective at resolving incidents. Improve our invoicing and contracting process. We are discussing how to reduce toil associated with invoicing in order to make this practice more reliable and efficient, along with our fiscal sponsor Code for Science and Society . Improving our reporting and monitoring infrastructure. We’d like to boost our ability to monitor activity on each of our hubs in order to identify when something abnormal is happening and get ahead of any potential problems (e.g., to avoid unintentionally large cloud bills). We’d also like to improve our usage reporting to more create more accurate cloud bills …","date":1649030400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1649030400,"objectID":"454c4a8fe4f63e69b69c0d288694eaad","permalink":"https://2i2c.org/blog/2022/q1-update/","publishdate":"2022-04-04T00:00:00Z","relpermalink":"/blog/2022/q1-update/","section":"blog","summary":"Quarter 1 of 2022 just wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.","tags":[],"title":"Celebrating our progress in Q1 2022","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["people"],"content":"Yesterday we had a quick “drop-in” session to take questions about 2i2c’s job posting for a Product and Community Lead . We spent the hour discussing a number of questions that others had about the position. Below is a short overview of the questions and some responses, for those who were not able to attend. These responses are a bit rough, since they are mostly off-the-cuff based on the questions asked.\nUpdate 2022-03-24: We’ve added extra questions and answers below from our latest drop-in meeting.\nWhat does success look like in the short and long term? # This is an important question, with a few different kinds of answers.\nAs noted, this is the first hire of its kind inside of 2i2c, and it should bring a strategic and organization-building eye to the work that it does. To some extent, this role will be tasked with coming up with their own answers to these questions. This person should build a near- and long-term strategy for how Product and Community Engagement should evolve to be most-effective in accomplishing our mission. This will also mean defining goals and a strategy to meet these goals over time.\nWith that in mind, here are a few ideas we have in mind for goals that will drive this role:\n6 month goals for this role might be:\nBecome familiar with 2i2c’s organization, culture, mission, and team. Define an early strategy for how you’d like to incorporate Product and Community engagement into 2i2c’s operations, and set some Objectives or Key Results that we should use to measure success. This should include a plan for the two major objectives of this role: guiding and connecting with the communities we serve, and building design and planning processes that bring this perspective into our engineering and services. A few iterations on the execution of this strategy, with some demonstration of impact as well as some documented lessons learned. 2 year goals for this role might be:\nAn organizational strategy and structure has been created, defining the various roles that make up this division of 2i2c and their functions. Clearly defined team processes for major programs efforts that this role oversees, as well as interconnections with other major divisions of 2i2c (e.g. engineering or sales). For example, a framework for training community leaders and mechanisms or platforms for communication and engagement with our communities. A team exists that carries out these efforts, led by the Product and Community Lead. Clear demonstrated impact in the communities we serve, according to the OKRs and goals that have been set in this division. How does 2i2c provide mentorship/onboarding? # You can find our onboarding process in our Team Compass . This roughly comes down to choosing an “Onboarding Champion” for the new team member, to help walk them through our team processes and get them access to the right information and accounts. However, 2i2c is quite young, so has only had a few iterations in onboarding new team members. We look forward to improving this process further via this new hire.\nWhat are the largest challenges that someone might face in their first year in this position? # The largest challenge is largely related to ambiguity and fluidity of this role, due to the fact that 2i2c is small and relatively young. As noted above, this position will have a great deal of autonomy, and will be expected to show leadership in defining the nature of this work within 2i2c. This can either be exciting or scary depending on your comfort level with ambiguity! We recognize that it is an anti-pattern to have roles without clearly-defined measures of success, so we’re committed to defining this quickly in partnership with the new hire. However, we don’t want to be overly-prescriptive in this role, because we want it to have space to lead these efforts within 2i2c.\nHow do you hope to protect the “business” aspects of 2i2c, if all the tech is open source? # 2i2c is to some extent committing to a limiting business model: by respecting the Right to Replicate , we encourage other organizations to perform the exact same kinds of services that 2i2c offers. However, we believe this is in-line with 2i2c’s mission, and would consider this to be a measure of impact rather than a sustainability problem. In short: our goal is not to become a tech giant or start-up unicorn, we want to sustain a team with competitive pay, and we want to scale as there is more opportunity to serve new communities. We believe that the complexity of integrating tools and managing cloud services means that there will always be enough of an opportunity to bring in ample funding for this model. We also hope that our mission-driven nature and focus on research and education will bring in new kinds of funding opportunities that can sustain 2i2c and its mission.\nHow would applying the “1000 true fans” approach work in terms of advocacy? # The 1000 true fans approach suggests that it is enough to leverage the support of “1000 true fans” to sustain a product or …","date":1647907200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1647907200,"objectID":"a610fec4ca5e5927b338d93661fa3039","permalink":"https://2i2c.org/blog/2022/product-community-lead-drop-in-notes/","publishdate":"2022-03-22T00:00:00Z","relpermalink":"/blog/2022/product-community-lead-drop-in-notes/","section":"blog","summary":"Yesterday we had a quick “drop-in” session to take questions about 2i2c’s job posting for a Product and Community Lead . We spent the hour discussing a number of questions that others had about the position.","tags":[],"title":"Notes from our drop-in meeting about the Product and Community Lead role","type":"blog"},{"authors":null,"categories":null,"content":"We are looking for a Product and Community Lead to ensure that the communities that 2i2c serves are empowered to have the most impact with our infrastructure.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $120,000 - $130,000 Location: anywhere (prefer a time zone between US/Pacific and Central European) Deadline: We will begin reviewing applications around March 21st, and will accept them on a rolling basis until the position is filled. Major duties\nGuide and learn from our user communities.\nGuide our team to build services and infrastructure for these communities\nLead strategic efforts to grow this work within 2i2c.\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply Position summary # This role will guide and empower the communities that we serve, learn from them, and bring their perspective to guide our service and product development. It is similar to a mixture of product management and community and developer advocacy in a tech firm, but adjusted for research, education, and open source contexts. It is also similar to a Research Applications Manager , but with a focus on using and developing infrastructure.\nThe skills required are a combination of communication, teaching, learning, service design and delivery, and technical acumen. The person that fills this role should feel comfortable learning and sharing ideas, empowering and guiding others, and communicating clearly and collaboratively with a variety of stakeholders including end-users and engineers.\nThis is a leadership role for a strategy-minded practitioner. 2i2c is a young organization, and this role will have a large degree of autonomy and flexibility. We have defined the starting point, but we seek someone who can bring a strategic eye to this position. Over time we hope that the role will grow to define and lead this style of work within 2i2c more broadly.\nWhat you’ll do # This role is a combination of connecting, guiding, leading, learning, communicating, and empowering stakeholders in the communities we serve, as well as the 2i2c engineering team. Here are some key focus areas with core responsibilities under each:\nGuiding and learning from communities we serve # Our users are often not “power-users” with Jupyter, open source workflows, or cloud-native workflows. This role should work with users of these communities to guide them in using our infrastructure for maximal impact. Below are a few example responsibilities:\nUnderstand the goals and needs of the communities we serve, as well as the major pain points and problems that they have. This understanding may not be directly communicated and will be gained through active observation. For example:\nCreate and engage in spaces for sharing information with users. For example, online forums and live community discussions. Engage in community-specific spaces. This role may monitor and participate in community spaces in either research or education (e.g., the Pangeo forum , the Jupyter forum , or forums for education communities) to track relevant conversation and provide guidance as-needed. Guide communities and their leaders for the use-cases that 2i2c wishes to enable, and how our infrastructure (Jupyter, JupyterHub, open source tools, etc) can be used to have the most impact. For example:\nDevelop user-facing materials (documentation, workshops, talks, etc) that demonstrate the basic use-cases that we support, and the best ways that the infrastructure can be used to accomplish community goals. For example “Teaching with Jupyter” or “An Introduction to Scalable Computing with Dask.” Provide one-on-one or group guidance to our user communities (particularly leaders in those communities) with the goal of transferring knowledge that they can then share within their peers. Foster deeper external relationships and engagements with key communities of practice and partners that are important for 2i2c’s strategy, such as the Pangeo Project (which is a key stakeholder for this role).\nEngage with potential communities and stakeholders, with a focus on demonstrating the use-cases we hope to support and generating new service contracts with these communities. Communicate externally to demonstrate impact. For example, by participating in meetings, conferences, and other events where we have an opportunity to highlight the work that 2i2c does. Interact extensively with open source communities that underlie our infrastructure, potentially serving in leadership roles and doing significant work to support these communities. There will be a particular focus on the Jupyter and PyData ecosystems. Guide product and service design and implementation # This role should understand the perspectives of our users and the use-cases we wish to enable, and bring this perspective to guide the evolution of our services and …","date":1646006400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1646006400,"objectID":"2ebe6e02e323565512fb237dc54713cb","permalink":"https://2i2c.org/jobs/2022/product-community-lead/","publishdate":"2022-02-28T00:00:00Z","relpermalink":"/jobs/2022/product-community-lead/","section":"jobs","summary":"We are looking for a Product and Community Lead to ensure that the communities that 2i2c serves are empowered to have the most impact with our infrastructure.\n❌❌❌\nThis posting is closed to new applications.","tags":null,"title":"Product and Community Lead","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":["people"],"content":"The 2i2c team is looking to hire a new team member! We are seeking a product and community lead with the following two goals:\nEmpower the communities we serve to have impact with our infrastructure. Guide our development and service design to reflect the needs of our users. This role will work alongside our engineering team as a partner, and will serve as a high-bandwidth interface to the communities that we work with.\nYou can find a link to the full job posting below, the rest of this post is a short rationale for this role, and how we hope it will fit within 2i2c’s team and strategy.\nLearn more and apply Why a new role? # When 2i2c began a year ago, we hired a team of engineers that had experience in cloud infrastructure, Jupyter, and open source ecosystems. In that time, we’ve built out the infrastructure foundation for scalable interactive computing environments that are customizable for the community, and respects their Right to Replicate .\nHowever, solely providing infrastructure is not enough. Working with the modern open source stack, using the cloud to its advantage, and bringing these tools into specific domains requires a lot of extra experience and expertise. We believe that 2i2c is in a good position to provide guidance and support to leaders in the communities that we serve, allowing them to get up-to-speed with the infrastructure more effectively so that they can have an impact.\nMoreover, we’ve also learned that it’s crucial to develop infrastructure in collaboration with the communities that we’re serving. A team of engineers tends to focus on code and infrastructure, and having a role that focuses on connecting with communities will give them an excellent perspective on what those communities need.\nWe hope that this role will combine these two aspects to create a culture of learning, sharing, and guiding between 2i2c’s team and the communities that we work with.\nWhat are similar roles? # We tried to find similar roles in the private and non-profit sector, but couldn’t find anything that was a perfect fit. However, there were a few close matches.\nThis role is kind-of like a product manager - their job is to understand the communities that we work with, and to use this to help us make decisions about what to build, how to present it, and how to engage with stakeholders. They will need to help us prioritize the work that is most impactful for our mission, and help us navigate trade-offs in the evolution of our services.\nThis role is also kind-of like a customer success manager or a developer advocate - they will guide and teach those in the communities we serve - particularly community leaders that go on to teach others - how to use our infrastructure most-effectively.\nIn fact, the closest role we could find is a relatively new one: the Research Applications Manager . This is a role that has been pioneered by the Turing Institute, and is similarly described as a connector that brings together many perspectives and encourages a participatory, team-based approach to research.\nHowever, the reality is that the person in this role will ultimately get to shape the nature of their work within 2i2c. As a young organization, there is a lot of flexibility for creativity and experimentation in bringing new skillsets into our organization. We hope that the person who fills this role will be excited about growing a culture of team-based approaches to our engineering and collaborations, and to share this culture with the communities that we serve.\nWhat’s next? # Effective today we are opening up applications for this position, and will begin reviewing them in 2 weeks on a rolling basis until the position is filled. For a more formal job posting, and instructions to apply, click the link below!\nLearn more and apply ","date":1645488e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1645488e3,"objectID":"9a790962fde35556190c78d24dace070","permalink":"https://2i2c.org/blog/2022/job-product-community-lead/","publishdate":"2022-02-22T00:00:00Z","relpermalink":"/blog/2022/job-product-community-lead/","section":"blog","summary":"The 2i2c team is looking to hire a new team member! We are seeking a product and community lead with the following two goals:\nEmpower the communities we serve to have impact with our infrastructure.","tags":[],"title":"New job posting: Product and Community Lead.","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"Now that 2021 has come to an end, this marks the end of 2i2c’s first year of operations. In this year we have grown, experimented, and accomplished a lot - we have also faced challenges and learned as a team. Our primary goal in 2021 was to build a strong foundation for 2i2c.\nTo reflect on our work thus far, we’re writing three blog posts that describe progress in major areas of work towards this foundation for 2i2c. These three areas are:\nCreating services for use-cases - these are our first managed infrastructure offerings for communities in research and education. Developing cloud infrastructure and tools - this is the technical backbone that makes these services possible, built entirely on open source tools. Building an organizational foundation - this is the creation of our team structures, processes, and culture that help us carry out our mission. This first post will focus on services that we’ve created in our first year.\nUltimately, 2i2c’s mission is to facilitate use-cases in research and education via open source development and services. Throughout 2021 we ran several pilots to learn more about the needs of communities in research and education, and how we could build sustainable services that meet these needs. Here are some highlights for each major use-case we have targeted thus far:\nEducational community hubs # A primary use-case that 2i2c seeks to enable is collaborative, distributed educational spaces for learning with data. In 2021 we ran several pilots with educational communities:\nA university-wide hub for the University of Toronto. This hub is used in a variety of classes throughout the university, and is made freely available to anyone with a UofT account. We hope to repeat this model for other university-wide communities, and have learned a lot about the challenges of working with particularly large educational communities.\nSeveral hubs for community colleges across California. In partnership with UC Berkeley and CloudBank, we’ve run several hubs for nearly a dozen small community colleges teaching the Data 8 curriculum for their students. These hubs are lightweight and offer standardized environments for their students to use, in order to lower the cost of deploying and maintaining the hubs over time.\nWhat we learned # The organizational context around educational use-cases is different from research communities. Compared with research groups, educucational groups have more variance in their size (classes as small as 10 people and as large as 500) and think about cost by the student, not as a lump sum. This means that our initial hub-based pricing model may not map cleanly onto educational contexts, and we need to improve the match of scalability and price to these communities.\nMoreover, we’ve learned that for these communities, navigating all of the open source tools that are available for pedagogy is confusing! Everybody wants auto-grading but it’s unclear what is the “right tool for the job”. Tools like nbgitpuller have heavy use at “power universities” like UC Berkeley, but many others don’t know that it exists! We will need to invest more time into building guides and documentation that help others leverage these tools.\nResearch in the cloud # In addition to educational use-cases, we ran several pilots for research communities in order to leverage cloud infrastructure for scaling their work or collaborating more effectively.\nWe migrated Pangeo’s cloud infrastructure to be run via 2i2c. The Pangeo Community had been operating and developing their own JupyterHub for several years, but were looking for another organization to provide more reliable/sustained operations and support for their Pangeo Cloud Service. This year we migrated the service to run off of 2i2c’s deployment infrastructure .\nA scalable cloud hub for a SWOT satellite team. The MEOM research group at Grenoble is doing work with the NASA SWOT satellite project . However, the datasets generated from this project are huge, and only storable via the cloud. We’ve set up a JupyterHub to provide cloud-based access to this data, running a Pangeo-like environment.\nWhat we learned # Research communities tend to have more usecase-specific needs than educational ones. While introductory courses in data science tend to be similar across institutions, research needs are much more unique to the problem and team at hand. Moreover, they tend to want infrastructure that runs via institutional cloud accounts. This is possible due to the flexible nature of Jupyter and JupyterHub, but brings extra challenges in bureacracy and access permissions, given that 2i2c engineers usually are not members of these organizations already.\nAdditionally, many research use-cases are based around the location of the data. This is because data is the hardest thing to move from cloud to cloud. For this reason, it’s important to bring interactive sessions to the data. Jupyter’s ecosystem makes this possible, but we’d like to do more to make this easier. For …","date":1643068800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1643068800,"objectID":"858b571dced8d12fbbf3c313fdb00006","permalink":"https://2i2c.org/blog/2022/2021-review-services/","publishdate":"2022-01-25T00:00:00Z","relpermalink":"/blog/2022/2021-review-services/","section":"blog","summary":"Now that 2021 has come to an end, this marks the end of 2i2c’s first year of operations. In this year we have grown, experimented, and accomplished a lot - we have also faced challenges and learned as a team.","tags":[],"title":"2i2c’s first year, part 1: exploring Jupyter services.","type":"blog"},{"authors":["Sarah Gibson"],"categories":["updates"],"content":" Pangeo Cloud is an experimental service providing public cloud-based data-science environments for data-intensive geoscience research. We have recently finished re-creating the Pangeo community JupyterHub hosted on GCP in the 2i2c-org/infrastructure repository. This is a huge milestone in our partnership with Pangeo to provide expertise and operations of cloud-based, vendor-agnostic Jupyter infrastructure and workflows.\nFor users of Pangeo Cloud, the switch should have been a smooth one! The new hub should behave nearly identically to the old one, and will be managed by 2i2c engineers moving forward, in partnership with the Pangeo community. It will be available at the same URL ( https://us-central1-b.gcp.pangeo.io ) and there’s no need to worry about your home directories, they were synced to the new hub only a few days before the migration took place. Development and operations on this hub will all be done in the open and we invite participation and feedback from others in our infrastructure work. Please see this Discourse thread as an initial place to provide feedback.\nOn 22nd November 2021, the old Pangeo GCP JupyterHub will be shut down, and the project will move forward on the new 2i2c Pangeo Hub. Moving forward, we plan to collaborate together in order to find new pathways for development in the Jupyter ecosystem - we will share more ideas of things we will work on soon!\nHistory of Pangeo Cloud Hubs # Pangeo has pioneered a new model in using open source and cloud-agnostic infrastructure to support scientific research in the cloud.\nThe first Pangeo cloud JupyterHub (pangeo.pydata.org; now defuct) was deployed for the 2017 American Meteoroligical Society Meeting ; since then, the Pangeo community has iterated through several different versions of prototype cloud-based hubs. This allowed for many new workflows that enabled a more open and collaborative pathway to doing world class research, and included access to datasets and computational resources that were previously unattainable. Pangeo achieved this by working in partnership with open source communities and building technology that leveraged modular open source components for their platform.\nIn the last several years, Pangeo have built a thriving community of practice around this infrastructure. However as the community has grown, so has the need for more reliable and dedicated operational and developmental support since parts of the Pangeo stack require dedicated expertise and attention to managed. Modern scalable cloud infrastructure is one example of this. Maintaining a complex JupyterHub with many users is a difficult task, and has required significant resources from the Pangeo Project up to this point.\nThe Pangeo-2i2c Partnership # 2i2c is a non-profit team that develops and operates cloud infrastructure for interactive computing workflows. We have extensive experience in Jupyter workflows in the cloud and a long history of contributions to projects in this ecosystem. We have built a cloud deployment management system that allows us to centralise and configure the deployment of many independent JupyterHubs, empowering communities to leverage the same infrastructure (and team!) for JupyterHubs running in the cloud.\nSimilarly to Pangeo, all of 2i2c’s core infrastructure is cloud- and vendor-agnostic, and follows a model of building open source tools and giving back to those communities. Our partnership with Pangeo began through 2i2c’s core competency in these areas and the similarity between the two project’s technical stacks.\nWe’ve begun a partnership whereby 2i2c will manage Pangeo’s cloud infrastructure and lead efforts to develop new features, in partnership with open source communities. We sketched out a few ideas to focus on in this kick-off thread on Discourse . This approach allows each community to focus on it’s core strengths: Pangeo will continue to grow an open community and scientific software ecosystem around geospatial analytics, and 2i2c will oversee the development and operations of the core cloud infrastructure stack that powers Pangeo’s workflows. In some areas we are still experimenting with different collaboration models to ensure that the needs of the Pangeo community are met in a way that is also sustainable for 2i2c. Over the coming weeks, you may see some conversations (and threads for feedback!) about different support and operations models that work best for the community. We are excited to use this as an opportunity to learn more about how to serve more complex and diverse communities like Pangeo.\nWe are extremely grateful to the Pangeo project for giving us the opportunity to serve their community, and we look forward to a long partnership ahead! 🚀\n","date":1637020800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1637020800,"objectID":"24f81ee8ba42c2db1774c4d417072c6f","permalink":"https://2i2c.org/blog/2021/pangeo-goes-live/","publishdate":"2021-11-16T00:00:00Z","relpermalink":"/blog/2021/pangeo-goes-live/","section":"blog","summary":"2i2c are pleased to announce that the first Pangeo JupyterHub is now live on 2i2c-operated infrastructure! :tada: ","tags":["2i2c","pangeo"],"title":"Pangeo Cloud goes live on 2i2c!","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":" This is a (roughly) quarterly update for the 2i2c community, with the goal of providing transparency about what we’ve been up to, sharing what we are working on and where we have struggled, and discussing what we’re up to next. In addition, almost all of the work we do is public and discoverable across our GitHub repositories , and is tracked by GitHub issues. Here’s a list of issues we’ve closed in ~Q3 .\nIt is amazing how quickly 4 months goes by when you’re building an organization from scratch! It seems like only a few weeks ago that we were recapping the beginning of the year in our last community update . Since then, we have been hard at work to make 2i2c’s organizational and infrastructure more robust and sustainable.\nThere are several major strategic areas where 2i2c aims to have impact, and we’ve split this community update along each of these major areas below. We’ll cover major highlights, challenges we’ve faced, and where we’re going next.\nHighlights # Managed JupyterHub Service # Our Managed JupyterHub Service will be a sustainable, scalable, and participatory service to provide cloud-based DevOps around JupyterHub for communities of practice in research and education. For the past several months, we have been running individual JupyterHubs for many organizations as a pilot, in order to learn more about the challenges we’ll face, and give ourselves an opportunity to build centralized infrastructure around the service.\nWe focused on a few major areas for work, outlined below:\nAutomation across cloud providers. We wish to serve communities that run on any of the major commercial cloud providers. We can standardize some of our infrastructure through abstractions like Kubernetes, but must still create cloud-specific deployment infrastructure as well (that Kubernetes cluster has to come from somewhere first!). In the last four months we’ve worked on automating Kubernetes and JupyterHub deployments on AWS as well as Azure to complement our Google Cloud deployments. We would soon like to run more hubs on this infrastructure to test how well it scales. Monitoring and reporting infrastructure. We have worked on the JupyterHub grafana-dashboards project to improve dashboarding around JupyterHub deployments in general, and will soon automatically deploy Grafana dashboards for our hubs so that communities have insight into what is going on in their hubs. User environment management. We want communities to have control over the environments that are available on their hubs. We also want to encourage that our communities follow community standards for reproducible environments that can be re-used elsewhere. For this reason, we’ve improved the repo2docker GitHub action to work with more image registries, and created a 2i2c user image template repository for users to re-use for their hubs. See the User Environment docs for more information. Support and collaboration roles. In addition to technology changes, we have developed an alpha-level support and collaboration model for the communities we serve. Most relevant for our communities is the community representative role, who acts as the main point of contact with 2i2c engineers, and leads administrators on the hub to guide its customization for the community it serves. See the user roles documentation for more information. We have also begun prototyping a FreshDesk support model and team processes around monitoring our support channels and responding to requests and incidents. Pangeo # We are working with the Pangeo Community to migrate the Pangeo JupyterHub deployments to utilize 2i2c’s centralized infrastructure, with the goal of 2i2c taking over the development and operation of Pangeo hubs moving forward. We have spent the last few months re-creating the Pangeo hub environment from scratch on a new cloud project controlled by Columbia University, and are nearly ready to begin migration from the “old” Pangeo hub to the new one. After this, we will focus our attention on re-creating the Pangeo BinderHub and AWS hub. Follow along with this work in this GitHub Project .\nExecutable Books / Jupyter Book # We are nearing the final year of a grant from the Sloan Foundation to support development on the Executable Books Project . As such, we have begun shifting our attention to create a strategy for sustaining the project’s community beyond this grant . In the coming months we plan on prioritizing improving our documentation (both for users and developers), as well as improving the general maintainability and quality of our codebases.\nJupyterHub community support # We recently collaborated with the JupyterHub community to apply for two CZI EOSS awards . Last month, we were notified that our application to support a Community Strategic Lead was funded! This role will fund Sarah Gibson’s time to focus some of her thinking on building community structures and dynamics that are inclusive and sustainable. We’ll update with more information as this project starts moving. …","date":1633824e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1633824e3,"objectID":"eb8170fad0ccceb7840702fd5c2ef642","permalink":"https://2i2c.org/blog/2021/q3-update/","publishdate":"2021-10-10T00:00:00Z","relpermalink":"/blog/2021/q3-update/","section":"blog","summary":"This is a (roughly) quarterly update for the 2i2c community, with the goal of providing transparency about what we’ve been up to, sharing what we are working on and where we have struggled, and discussing what we’re up to next.","tags":[],"title":"Community update Q3 2021: A new fiscal sponsor, improving our infrastructure, nearing an alpha launch.","type":"blog"},{"authors":["Chris Holdgraf","Danielle Robinson"],"categories":["updates"],"content":"This post was originally written for the CS\u0026amp;S blog .\nCode for Science \u0026amp; Society is thrilled to welcome the International Interactive Computing Collaboration (2i2c, for short) as a fiscally sponsored project! After spending a year incubating in the International Computer Science Institute , where 2i2c received critical startup support , 2i2c now joins our fiscally sponsored project program to launch their next phase. 2i2c develops and operates cloud infrastructure for interactive computing, with a focus on the Jupyter ecosystem and cloud-native workflows in research and education. They will build a cloud services model that respects a community’s Right to Replicate their infrastructure by providing transparent and customizable JupyterHub deployments on cloud infrastructure that utilize community-driven open source tools. They aim to use the resources generated from this service in order to support the communities that underlie this infrastructure. Read on for more about 2i2c’s mission and how CS\u0026amp;S will support their team and vision.\n2i2c’s organizational mission is to develop and operate sustainable cloud services that provide interactive computing infrastructure with JupyterHub and an ecosystem of tools that support research and education. This model has been pioneered in the organizations that 2i2c’s co-founders have co-led for many years, including the Pangeo Project , the Syzygy Project , the Binder Project , and the UC Berkeley DataHub . These projects follow an “integrate, customize, and upstream” model. They integrate pre-existing open source tools, make necessary customizations to support their specific use-case, and make upstream contributions to extend the infrastructure beyond its current capabilities. This creates a virtuous cycle where tangible needs are met in research and education, while improvements are made to open source projects that benefit the broader community. 2i2c hopes to scale this model, and provide these JupyterHub-based cloud services available to the broader research and education community.\nCS\u0026amp;S is particularly interested in pursuing the opportunity to work closely with 2i2c as their team explores how to build sustainable, ethical services that support open scholarship as well as open source communities. The model that 2i2c will develop is different in many ways from traditional grant-based development, or service-based business, because it depends on running community-led infrastructure that 2i2c contributes to, but does not control or own. Both CS\u0026amp;S and 2i2c believe that this model is an opportunity to build more distributed, community-led infrastructure and services, as well aligning a sustainability model with both open source communities and the scholarly community. We hope that this work will also provide experience that helps improve CS\u0026amp;S’s other initiatives in this space, including CS\u0026amp;S’s other fiscally sponsored projects and participants in the Digital Infrastructure Incubator program .\nAchieving this mission will involve innovation at an infrastructure level, a business model level, and an open source community strategy level, and will be carried out over the coming years. 2i2c’s next steps are to run pilot JupyterHub infrastructure for select communities of practice in research and education, in order to better understand their needs and how these needs fit in with 2i2c’s developing sustainability model. They will also build infrastructure to deploy and customize a federation of JupyterHubs that are community-specific, and that run entirely on open source infrastructure.\nIf you believe that your community would benefit from a hub like this, please reach out to the 2i2c team , or join their mailing list . Stay tuned as 2i2c builds its sustainable, scalable, and community-driven platform for interactive computing in the cloud.\n","date":163296e4,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":163296e4,"objectID":"2a879062b3520ec9de025b6fcd6be1b1","permalink":"https://2i2c.org/blog/2021/css-announce/","publishdate":"2021-09-30T00:00:00Z","relpermalink":"/blog/2021/css-announce/","section":"blog","summary":"This post was originally written for the CS\u0026S blog .\nCode for Science \u0026 Society is thrilled to welcome the International Interactive Computing Collaboration (2i2c, for short) as a fiscally sponsored project!","tags":["2i2c"],"title":"2i2c launches next phase in partnership with CS\u0026S","type":"blog"},{"authors":["Damián Avila"],"categories":["upstream"],"content":"","date":1630713600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1630713600,"objectID":"7129084e54d4bda7b3ec37c3b41dc2b3","permalink":"https://2i2c.org/blog/2021/myst-nikola-part-2/","publishdate":"2021-09-04T00:00:00Z","relpermalink":"/blog/2021/myst-nikola-part-2/","section":"blog","summary":"","tags":["jupyter","executablebooks"],"title":"A deep dive into MyST, Part 2: The MyST-Parser, Docutils and Sphinx","type":"blog"},{"authors":["Damián Avila"],"categories":["upstream"],"content":"","date":1629676800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1629676800,"objectID":"d6c2657172e1b9cf296716eda7200d3d","permalink":"https://2i2c.org/blog/2021/myst-nikola-part-1/","publishdate":"2021-08-23T00:00:00Z","relpermalink":"/blog/2021/myst-nikola-part-1/","section":"blog","summary":"","tags":["jupyter","executablebooks"],"title":"A deep dive into MyST, Part 1: The MyST-Parser Python API usage in Nikola","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"It has been about six months since 2i2c first began operations (after receiving funding from the Chan Zuckerberg Initiative ). In that time we’ve made progress along several directions, and wish to use this blog post to provide updates about the ways in which 2i2c has evolved over the first months of its existence.\nBelow are a few major updates from the 2i2c community - as always, if you want to learn more about 2i2c, keep an eye on our blog or subscribe to the 2i2c mailing list .\nEarly pilot JupyterHub infrastructure # First off - we have been making progress building out our JupyterHub deployment infrastructure for 2i2c. One of our major organizational goals is to build a sustainable service managing open source cloud infrastructure for interactive computing. This service will provide hosted, customized JupyterHubs for communities of practice in research and education. They’ll be built entirely with open source tools that are community-driven, and that respect the community’s Right to Replicate .\nIn order to accomplish this, 2i2c is running several pilots with partners and interested organizations, supported by our funding from CZI , as well as from the JROST rapid response fund . These pilots are meant to be learning opportunities to understand what kind of infrastructure and service it needs to build moving forward.\nThe documentation for our pilot hubs infrastructure contains information about our deployments and infrastructure. It is served from this 2i2c-org/infrastructure repository , a centralized location for configuring and deploying a federated network of JupyterHubs. Each JupyterHub is independent of one another, and could be spun out from the centralized repository with minimal extra work, giving hub users the ability to replicate their infrastructure, with or without 2i2c . We will continue refining the code in this repository as we learn more from our hub infrastructure pilots.\nJupyterHub for geospatial analytics - A collaboration with Pangeo # As originally announced on the Pangeo blog , 2i2c is forging a collaboration with the Pangeo project around operating and developing cloud infrastructure for large-scale geospatial analytics! This collaboration is funded through a grant from the Moore Foundation (via Pangeo investigator Ryan Abernathey).\nOver the coming months, 2i2c plans to assume operation of infrastructure underlying the Pangeo project, allowing the Pangeo team to focus their efforts on their core scientific and development missions. Because Pangeo’s infrastructure is already running on a fully open source stack with JupyterHub, our first step will simply be to shift control over this infrastructure to 2i2c engineers. We don’t anticipate needing to make major changes to their infrastructure and deployments (part of the benefits of using open, modular tools).\nOnce this is complete, we’ll next shift our attention to some new areas of development that support use-cases in the Pangeo community (and in the scientific community more broadly). There’s a lot of progress that we imagine making - such as supporting publishing pipelines via the Pangeo Gallery or improving tools for scalable computing with Dask Gateway . We’ll provide updates as we formally begin this collaboration and hash out a plan for our next steps.\nJupyterHub for education - A collaboration with CloudBank and UC Berkeley # In addition, we’ve begun a partnership with the UC Berkeley Data Science in Undergraduate Studies program , as well as CloudBank . This collaboration aims to provide hosted JupyterHub infrastructure for community colleges across the state of California. It is an attempt at providing vendor-agnostic and open-source infrastructure to several institutions who would otherwise not be able to deploy this infrastructure on their own.\n2i2c will provide the deployment and configuration architecture for this collaboration, working with Sean Morris in operating this educational infrastructure. All of the cloud infrastructure for this pilot will be funded via CloudBank. We will begin by offering environments that are modeled after the Data 8 course at UC Berkeley . This is part of an effort to build a community of practice around Data Science education using open source tools.\nNew team members # We’ve also welcomed two new members to the 2i2c core team! 🎉\nThese individuals will both work towards 2i2c’s major projects , and collaborate together on running our 2i2c Pilot Hub infrastructure. Here’s a bit about each new team member.\nDamián Avila . Damián has been a Jupyter core team member for many years now, and has done work across many different parts of the PyData stack (in particular, Jupyter , Bokeh , RISE , and Nikola ). Damián will focus his efforts on supporting JupyterHub infrastructure for the Pangeo project , as well as development across the Executable Books Project Sarah Gibson . Sarah will join 2i2c in June, after spending several years as a Research Software Engineer at the Turing Institute . She has …","date":1621900800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1621900800,"objectID":"dd8c28b4e191724ed9c1ebae27d1be38","permalink":"https://2i2c.org/blog/2021/six-month-update/","publishdate":"2021-05-25T00:00:00Z","relpermalink":"/blog/2021/six-month-update/","section":"blog","summary":"It has been about six months since 2i2c first began operations (after receiving funding from the Chan Zuckerberg Initiative ). In that time we’ve made progress along several directions, and wish to use this blog post to provide updates about the ways in which 2i2c has evolved over the first months of its existence.","tags":[],"title":"Pilot hubs, new collaborations, and new team members - A six month update","type":"blog"},{"authors":null,"categories":null,"content":"We are looking for an Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on important problems shaping society. This engineer will lead the development and operation of cloud-based infrastructure, focusing on the Pangeo Project - a community platform for big data geoscience.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $110,000 - $130,000 Location: anywhere (prefer a time zone between US/Pacific and Central European) Deadline: Major duties\nCloud infrastructure management and operations.\nDevelopment of open source infrastructure for hosted JupyterHub service\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply Who we are # 2i2c is a non-profit organization with a mission to make interactive computing more accessible, scalable, and powerful for research and education. We strive to…\nSupport data workflows in research and education through infrastructure for interactive computing. Support open tools and communities that underlie this infrastructure. We accomplish this mission by providing managed cloud services for interactive computing, by providing development and technical leadership to researchers and educators that utilize this infrastructure for specific communities, and by providing support for open source tools and communities in this ecosystem.\nWe have deep ties to the open source community, and have been leaders and core contributors across dozens of projects - in particular in the Jupyter ecosystem. We also have deep ties to research and education - our team has spent years deploying infrastructure for universities, community colleges, and research teams, and now we’re bringing this experience to a wider audience with 2i2c.\nWe believe strongly in communities that are inclusive, transparent, equitable, effective, and diverse, especially 2i2c itself. We believe that our values should permeate everything about 2i2c, including the work we do, the communities we serve, and our own organizational culture.\n2i2c is a project of the International Computer Science Institute , a 501(c)(3) not-for-profit.\nWhat you’ll do # You will define the overall strategy and technical approach to cloud computing usage in Pangeo, and will interface with the Pangeo community on a frequent basis. You will help deploy, customize, and operate cloud infrastructure for research and interactive computing. You’ll use the experience operating this infrastructure to identify development opportunities, with the goal of minimizing maintenance time and toil - your goal will be to spend more time developing and less time operating. You will contribute to the general development and maintenance of open source software packages for the advancement of scientific objectives, and develop applications for extracting, transforming, loading, managing, and cataloging scientific data in the cloud. You will engage and interact with open source communities surrounding the tools that you use in serving the Pangeo community, and will represent 2i2c in these engagements. You will also collaborate with scientists to support research projects, and may conduct some education and training around scientific computing.\nResponsibilities # Develops strategy and technical design for cloud computing architecture within the Pangeo project and related projects with 2i2c. Assists with site reliability for Pangeo infrastructure, and uses experience operating this infrastructure to identify new opportunities for development. Ensures the reliable operation of production cloud-based tools including JupyterHub / JupyterLab and Dask. Participates in the upstream open source communities we rely on (such as JupyterHub, Dask, etc) by contributing code, documentation, etc as needed. Develops dashboards and reports to quantify system usage and costs. Helps to maintain and operate Pangeo Gallery , an interactive showcase for data science projects based on binder and github workflows. Conducts education and outreach around cloud computing. Explores emerging technologies in the cloud / DevOps space. Travels to conferences and workshops (once COVID-19 restrictions end). Will work with minimal supervision from leadership at 2i2c in partnership with collaborators at Columbia and the Pangeo project. Will work independently and make their own decisions about where to best allocate effort. Requirements # Familiarity with deploying applications on cloud infrastructure. Experience developing tools in a general purpose programming language (eg. Python) Experience deploying and developing with Linux container technologies, such as Docker and Kubernetes Experience with continuous integration services (e.g. Travis CI, GitHub workflows) Experience building and deploying backend web services. Experience collaborating and …","date":1607472e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1607472e3,"objectID":"0f43f426f967699a3f706a81695b7caa","permalink":"https://2i2c.org/jobs/2021/osie-pangeo/","publishdate":"2020-12-09T00:00:00Z","relpermalink":"/jobs/2021/osie-pangeo/","section":"jobs","summary":"We are looking for an Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on important problems shaping society. This engineer will lead the development and operation of cloud-based infrastructure, focusing on the Pangeo Project - a community platform for big data geoscience.","tags":null,"title":"Open Source Infrastructure Engineer: Pangeo Project","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"Last week we announced the creation of 2i2c , a non-profit initiative dedicated to improving and facilitating access to infrastructure for interactive computing workflows in research and education. Today we are thrilled to announce that 2i2c has received core support from the Chan Zuckerberg Initiative . You can find CZI’s announcement here .\nThis funding totals around $1.4m over three years. It provides crucial core support for 2i2c as it bootstraps itself into existence. We are so thankful to CZI for this support. 🎉🙏✨\nThe rest of this post is a short run-down of what we’ll use this funding for, and what we hope to accomplish.\nThe big picture # In recent years, several projects including Binder , Pangeo , Syzygy , and the Berkeley DataHubs have built atop the Jupyter architecture to support cloud-based infrastructure for reproducible research, large-scale scientific data analysis, national-scale infrastructure for researchers, and broad-impact educational programs based on freely available computational materials. These projects illustrate the transformative potential of the open Jupyter architecture, but they have also shown that unlocking this potential in service of scientists and educators requires continued development and resources beyond those of open source volunteers.\nIn order to deploy these resources at scale, manage and maintain them for large communities, and to continue developing the underlying technologies for scientific use cases, we need models to sustainably deploy and improve Jupyter technology. We also need capacity for thinking strategically and forging new partnerships to accomplish this goal. This funding will support 2i2c’s early strategic planning and partnership efforts, as well as technical development and operation of Jupyter infrastructure for research and education.\nBelow are two keys goals for this grant:\nGoal 1: Build capacity for Jupyter in research and education # The primary goal of this funding is to build more capacity for Jupyter’s engagement in research and education. This funding will primarily support Chris Holdgraf to build strategic partnerships and collaborations, find opportunities for Jupyter infrastructure to benefit research and education, coordinate activity in the Jupyter project that benefits these communities, and secure more funding for development, maintenance, and support for Jupyter technology.\nWe are grateful to CZI for this funding because strategy, leadership, and community support are often difficult to fund from grants that are focused on technical deliverables. By funding strategic growth and capacity building, CZI is helping 2i2c lay a strong foundation from which it can have a greater impact.\nGoal 2: Support hosted Jupyter infrastructure for research and education # 2i2c will offer hosted interactive computing infrastructure utilizing the Jupyter ecosystem. It will both deploy and operate this infrastructure for researchers and educators, as well as perform core development to ensure that it serves these communities well. Funding from this grant will support 2i2c’s first hire - Georgiana Dolocan as an Open Source Infrastructure Engineer. Georgiana has been the JupyterHub Contributor in Residence for the past year, and we are so excited for her to join 2i2c!\nGeorgiana will begin by supporting several pilot hubs that are run by 2i2c for community colleges, universities, and research institutions. She will help these organizations accomplish their mission through 2i2c infrastructure, and will develop these technologies so they are stable, scalable, and serve a diverse set of needs in research and education. This will hopefully set the foundation for 2i2c to sustainably offer this hub infrastructure to a wider audience in the future.\nThis is the next step in Georgiana’s journey through the Jupyter ecosystem that began with an outreachy internship followed by a term as Contributor in Residence . Both of these steps were made possible thanks to Jupyter stakeholders who invest their resources, time, and mentorship to grow Jupyter’s community beyond the people that have traditionally been involved in the project. It’s also possible because of funders committing resources to broaden participation and inclusion - in particular, the Berkeley Institute for Data Science and NumFOCUS for their original support of our Outreachy interns and the CZI EOSS grant series for funding the original Contributor in Residence.\nWhat’s next # With this core support, 2i2c turns towards its JupyterHub pilot deployments to build early prototypes that serve research and education, and to build organizational models that sustain these hubs and their development. If you or your organization think you’d be a good fit for these pilots, please reach out to 2i2c and let us know!\nMany thanks again to CZI for this support - we believe that it is an excellent investment in the Jupyter community and in open source communities more generally. We also believe it will lead to major …","date":1605744e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1605744e3,"objectID":"110ad797b7358afdff75f2722272af75","permalink":"https://2i2c.org/blog/2021/czi-core-support/","publishdate":"2020-11-19T00:00:00Z","relpermalink":"/blog/2021/czi-core-support/","section":"blog","summary":"Last week we announced the creation of 2i2c , a non-profit initiative dedicated to improving and facilitating access to infrastructure for interactive computing workflows in research and education. Today we are thrilled to announce that 2i2c has received core support from the Chan Zuckerberg Initiative .","tags":["meta"],"title":"2i2c receives core support from CZI","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"👋 hey everyone!\nWe’d like to announce the creation of a new non-profit organization1 that we call 2i2c.\n2i2c stands for The International Interactive Computing Collaboration. It is a non-profit dedicated to making open tools for interactive computing more accessible and more powerful for the research and education communities.\nThis is a short post about why we created 2i2c, what we hope that it will do, and what we are up to next. If you’d prefer to watch a video instead of read a blog post, check out this talk about 2i2c at JupyterCon 2020:\nWhy create 2i2c? # The founding team of 2i2c has spent the last several years running projects that use interactive computing for research and education, including bringing data science education to thousands of students , connecting geospatial researchers with large datasets and computational resources in the cloud , and providing federated online environment hubs to schools across Canada , to name a few.\nOver time we realized that, while infrastructure for interactive computing could be a huge benefit to research and education, it also required a fair amount of expertise to configure, deploy, and develop. We wished for other organizations to enjoy the same success that we had found, but learned that for many, deploying their own infrastructure was a non-starter to adoption. Instead, many were turning to proprietary or vendor-specific tooling.\nWe created 2i2c so that these organizations can use entirely open-source tools without hiring and training their own dev-ops and infrastructure talent, and so that development and support of open tools for interactive computing continues to represent the interests of research and education.\nWhy a non-profit? # It may sound strange to create a non-profit initiative when there are many VC-funded startups and large tech companies offering notebook services these days. However, we think that a non-profit organization is the right approach to balance the interests of all the stakeholders that we wish to serve. We hope that 2i2c will be a partner to:\nResearch and educational communities, who can rely on 2i2c to provide them cutting-edge infrastructure for interactive computing that is 💯 open source. Researchers and educators who need development, who can rely on 2i2c as a collaborator that offers development and expertise in open-source infrastructure to push the cutting edge of interactive computing in the cloud. Open source communities, who can count on 2i2c support and grow the communities that underlie the tools that we deploy. Cloud providers, who wish to help the research and educational community via their infrastructure. Supporters of open source who wish to support interactive computing for research and education via a non-profit dedicated to exactly this mission. As a non-profit initiative, 2i2c is dedicated to supporting an ecosystem of tools and stakeholders across the open source community, and to ensuring that those tools are well-suited for research and education. We believe strongly in mission-driven work, and non-profit status will ensure that the work that we do is always aligned with our mission and values.\nWhat are we going to do? # With all of that in mind, what is 2i2c actually going to do? We are still working out the details, but here’s a rough picture:\nOffer hosted interactive computing environments on cloud infrastructure . These will be entirely open source and vendor-neutral, and customizable for the communities that are using them. They’ll be offered either as a fee-for-service model and/or subsidized through grants and donations. We wish to build upon the success of JupyterHub as a gateway to computational resources and environments, learning environments, and communities of users. For more information about the vision and values of our hosted infrastructure, see the 2i2c Right to Replicate document .\nProvide collaboration and development for interactive computing in research and education . Beyond providing hub infrastructure, there are many ways in which solving problems in research and education can lead to better tools, infrastructure, and workflows in the open source community. For example - how can we generalize a community’s solution to scalable computing so that it can be useful for other use-cases as well? We hope that 2i2c can be an aggregator and integrator of many perspectives in research and education, and build tools that are maximally useful across communities.\nProvide core development and community support for open source projects that we use. While many organizations use Jupyter technology in their projects, it is also crucial that they give back to those tools in order to keep the ecosystem healthy. As a mission-driven non-profit, 2i2c has a core goal in not only deploying and customizing open source tools, but also providing core support for them.\nNext steps # 2i2c is a young organization, but we already have a few exciting ideas to work towards in the coming months. Here’s an idea of …","date":1604966400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1604966400,"objectID":"4fbd63f9efdd7c1913ddfa4eeef26698","permalink":"https://2i2c.org/blog/2021/hello-world/","publishdate":"2020-11-10T00:00:00Z","relpermalink":"/blog/2021/hello-world/","section":"blog","summary":"👋 hey everyone!\nWe’d like to announce the creation of a new non-profit organization1 that we call 2i2c.\n2i2c stands for The International Interactive Computing Collaboration. It is a non-profit dedicated to making open tools for interactive computing more accessible and more powerful for the research and education communities.","tags":["meta"],"title":"Hello World","type":"blog"},{"authors":null,"categories":null,"content":"The Right to Replicate gives communities the right to replicate their infrastructure in its entirety elsewhere, with or without 2i2c.\nThis document describes 2i2c’s commitment to a community’s “right to replicate”, and how this translates into specific infrastructure commitments from 2i2c. We make these commitments because we believe that using infrastructure that follows these principles will lead to a more fair, just, equitable world. We also believe they are the right foundation for more productive and impactful research and education.\n2i2c is committed to running its own infrastructure on open-source tools and vendor-agnostic infrastructure, though it does not force users to use only open-source tools in their own environments, code, and data. Below is a table describing how the Right to Replicate fits into 2i2c hub technology.\n(Definitions of MUST, MUST NOT, SHOULD, MAY, etc are defined in RFC 2119 )\nUser Code and Data May be Open Source We encourage adopting and producing open source code and data, but this is up to the user. e.g., licenses for user content/code User Environment Should be Open Source Strong preference for open source tools only, although in some cases user needs may override this. e.g., Python, R, PyData stack. 2i2c Infrastructure Must be Open Source Strong commitment to using only open source software. e.g., JupyterHub, Kubernetes, Postgresql Cloud Provider Infrastructure Must be Portable See this blog post for more information. Below we describe our commitments in our own infrastructure stack in more detail.\nHow 2i2c infrastructure ensures this right # 2i2c infrastructure and documentation for it MUST BE as transparent \u0026amp; accessible as possible, so communities can replicate our configuration without having to extract any ‘secret sauce’ from 2i2c. If they choose to, they can also inspect, audit \u0026amp; modify the infrastructure they are paying for and using.\nTo ensure the Right to Replicate to our communities, 2i2c makes the following commitments to infrastructure we build and operate:\nWe MUST use only open source software to run our infrastructure. By only using software that is available to everyone on the same terms, we can ensure that communities can replicate the infrastructure without having to negotiate licensing terms with proprietary software vendors. In addition, any changes we make to open source software will be made in public and/or contributed upstream, so communities continue to have access to them regardless of where their infrastructure is.\nWe MUST NOT directly depend on proprietary cloud vendor specific products or APIs. Instead, we use cloud-managed open source software, or hide the dependency behind a layer of abstraction. This ensures that communities can port their infrastructure to any cloud provider of their choice, or run it on their own hardware with purely open source software.\nThis set of commitments acts as a business continuity plan for our partner communities, ensuring 2i2c will follow best practices within the open source, open education and open research ecosystems.\n","date":1530144e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1530144e3,"objectID":"f9d84027023bd7709772a71806b3aca9","permalink":"https://2i2c.org/right-to-replicate/","publishdate":"2018-06-28T00:00:00Z","relpermalink":"/right-to-replicate/","section":"","summary":"The Right to Replicate gives communities the right to replicate their infrastructure in its entirety elsewhere, with or without 2i2c.\nThis document describes 2i2c’s commitment to a community’s “right to replicate”, and how this translates into specific infrastructure commitments from 2i2c.","tags":null,"title":"The Community Right to Replicate","type":"page"},{"authors":null,"categories":null,"content":" ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"c2c20062023db009d767c2f4a7d38088","permalink":"https://2i2c.org/pilot-hubs/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/pilot-hubs/","section":"","summary":" ","tags":null,"title":"","type":"page"},{"authors":null,"categories":null,"content":" ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"74dcede968ab0952007871e9fa0da40e","permalink":"https://2i2c.org/pilot/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/pilot/","section":"","summary":" ","tags":null,"title":"","type":"page"},{"authors":null,"categories":null,"content":" ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"cbf2769f3919dc1ca746df7980be9eff","permalink":"https://2i2c.org/team-compass/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/team-compass/","section":"","summary":" ","tags":null,"title":"","type":"page"},{"authors":null,"categories":null,"content":"2i2c has expertise in cloud infrastructure and managed services for interactive computing in research and education workflows. We focus on the Jupyter ecosystem and adjacent open source communities (e.g., the PyData ecosystem), with a particular emphasis on JupyterHub.\nJoin our mailing list 📰 Send us an email ✉️ Our Team Compass contains all of 2i2c’s organizational strategy, policy, and team practices. Our updates blog series provides all major organizational updates for our community. Our Service Level Objectives describes our day-to-day goals running the service. Our Shared Responsibility Model describes how we collaborate with communities in this hub service. Our Infrastructure Guide describes all of our cloud infrastructure and engineering practices, with links to our codebase. Here are a few ways that you can connect with and collaborate with 2i2c.\nUse and support our managed JupyterHub services # 2i2c aims to provide Managed JupyterHubs in the cloud that are customized for communities in research and education. We are exploring sustainability and services models around this goal, and invite feedback and ideas for ways that we can improve this service. We are running JupyterHubs for many communities already, and are accepting new communities in batches as our capacity grows. If you are interested in having a managed JupyterHub for your community, check out our cloud service page for more information or send an email to partnerships@2i2c.org to discuss.\nPitch a project or grant # Our team is always looking our for opportunities to collaborate and learn from others in order to have an impact. Sometimes these can even lead to new grant ideas or ongoing projects. If you have an idea for collaboration that is aligned with our mission, and that would benefit from our skills and perspective, please send an email to partnerships@2i2c.org and we can discuss.\n","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"5fff794d732d0d9048992165a6c484a4","permalink":"https://2i2c.org/collaborate/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/collaborate/","section":"","summary":"2i2c has expertise in cloud infrastructure and managed services for interactive computing in research and education workflows. We focus on the Jupyter ecosystem and adjacent open source communities (e.g., the PyData ecosystem), with a particular emphasis on JupyterHub.","tags":null,"title":"Contact us to collaborate","type":"page"},{"authors":null,"categories":null,"content":" Brand guidelines # Our Brand Guidelines document describes 2i2c’s overall brand and visual style.\nLogos # Square logo (default) # Logo\nDownload SVG | Download PDF Logo light\nLogo black\nWide logos # Wide logo\nDownload SVG | Download PDF Wide logo light\nColors # Primary colors # Big Blue: #1D4EF5 Pale Blue: #F2F5FC Black: #000000 Secondary colors # Midnight: #230344\nMauve: #B86BFC\nForest: #057761\nLight Green: #0CEFAE\nMagenta: #C60A76\nPink: #FF808B\nCoral: #FF4E4F\nYellow: #FFDE17\nDesign assets # These two links are only accessible to 2i2c team members.\nFigma canvas with design assets Google Drive folder with design assets ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"0cb45ec32ab674771091450a1bc1fdc4","permalink":"https://2i2c.org/brand/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/brand/","section":"","summary":"Brand guidelines # Our Brand Guidelines document describes 2i2c’s overall brand and visual style.\nLogos # Square logo (default) # Logo\nDownload SVG | Download PDF Logo light\nLogo black","tags":null,"title":"Design and brand guidelines","type":"page"},{"authors":null,"categories":null,"content":"Much of the work we do is supported by grants and donations from stakeholders in our community. These resources go towards things like new development of open source technology, maintenance for open source projects, community development efforts, sponsoring hubs for under-resourced communities, and general support for 2i2c in its mission.\nFill our the form below to make a donation to 2i2c via its fiscal sponsor, Code for Science and Society . If you’d rather have a conversation with us first about your donation, please send us an email .\n","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"ac26b9ca282f87df5d5ed826e374bb78","permalink":"https://2i2c.org/donate/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/donate/","section":"","summary":"Much of the work we do is supported by grants and donations from stakeholders in our community. These resources go towards things like new development of open source technology, maintenance for open source projects, community development efforts, sponsoring hubs for under-resourced communities, and general support for 2i2c in its mission.","tags":null,"title":"Donate to 2i2c","type":"page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"07777db7484439a4707d21d09c158fa2","permalink":"https://2i2c.org/mission/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mission/","section":"","summary":"","tags":null,"title":"Mission and strategy","type":"widget_page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"6087c0ef875554f4409ac52928d79279","permalink":"https://2i2c.org/projects/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/projects/","section":"","summary":"","tags":null,"title":"Open Source","type":"widget_page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"8ab4338b5212831f3b729ac977000df4","permalink":"https://2i2c.org/founders/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/founders/","section":"","summary":"","tags":null,"title":"Our Founding Team","type":"widget_page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"6425ff024d90bbffa37d23fc4bf403ee","permalink":"https://2i2c.org/organization/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/organization/","section":"","summary":"","tags":null,"title":"Our organization","type":"widget_page"}]
\ No newline at end of file
+[{"authors":["jenny-wong"],"categories":null,"content":"Jenny is the Technical Content Developer for 2i2c. Her work is mainly focused on the CZI-funded Catalyst Project, an initiative aiming to provide research communities in Latin America and Africa with access to large-scale scientific infrastructure. As part of this effort, she will help develop community-based training materials for interactive cloud-native workflows.\nAs a former research software engineer, Jenny has considerable experience supporting researchers with writing documentation, creating video tutorials, and designing and delivering training for advanced research computing. Jenny is also a qualified Software Carpentries Instructor.\nJenny’s background is in mathematics, with a special interest in geophysical fluid dynamics. She obtained a PhD in the subject with her thesis titled “A slurry model of the F-layer in the Earth’s core”.\n","date":1718841600,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718841600,"objectID":"2f015795f698666394aa3c63de977b49","permalink":"https://2i2c.org/author/jenny-wong/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/jenny-wong/","section":"authors","summary":"Jenny is the Technical Content Developer for 2i2c. Her work is mainly focused on the CZI-funded Catalyst Project, an initiative aiming to provide research communities in Latin America and Africa with access to large-scale scientific infrastructure.","tags":null,"title":"Jenny Wong","type":"authors"},{"authors":["angus-hollands"],"categories":null,"content":"Angus Hollands is an Open Source Infrastructure at 2i2c. He was previously a post-doctoral researcher in the Computational High Energy Physics group at Princeton University. He has a long-standing history of working collaboratively in open source projects, such as Executable Books, Jupyter, scikit-hep, and Blender. He is motivated by open-source, open-science, and the FAIR principles to build a more accessible, empowering future for scientific research and publication. His scientific background is in nuclear structure, in which he studied a PhD at the University of Birmingham.\n","date":1718668800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718668800,"objectID":"33be3fd611c72f8b1268083cb150e1c0","permalink":"https://2i2c.org/author/angus-hollands/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/angus-hollands/","section":"authors","summary":"Angus Hollands is an Open Source Infrastructure at 2i2c. He was previously a post-doctoral researcher in the Computational High Energy Physics group at Princeton University. He has a long-standing history of working collaboratively in open source projects, such as Executable Books, Jupyter, scikit-hep, and Blender.","tags":null,"title":"Angus Hollands","type":"authors"},{"authors":["chris-holdgraf"],"categories":null,"content":"Chris is the Executive Director of 2i2c. He was previously a post-doctoral researcher in the Department of Statistics at UC Berkeley , and a Community Architect with the Division of Data Science at Berkeley. He is also a team member of Project Jupyter (particularly the JupyterHub and Binder teams ), with a focus on how infrastructure can support interactive computing workflows in research and education. He’s interested in the boundary between technology, open-source software, and research and education workflows, as well as how open communities can support and extend these workflows in a way that makes science more impactful and inclusive. His background is in cognitive and computational neuroscience, where he used predictive models to understand the auditory system in the human brain.\n","date":1718668800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718668800,"objectID":"6b264ebb4849fa5ae2987cd0caffb03d","permalink":"https://2i2c.org/author/chris-holdgraf/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/chris-holdgraf/","section":"authors","summary":"Chris is the Executive Director of 2i2c. He was previously a post-doctoral researcher in the Department of Statistics at UC Berkeley , and a Community Architect with the Division of Data Science at Berkeley.","tags":null,"title":"Chris Holdgraf","type":"authors"},{"authors":["james-munroe"],"categories":null,"content":"James is Product and Community Lead for 2i2c. Coming from a background as an associate professor in the Department of Physics and Physical Oceanography at Memorial University of Newfoundland , he is a strong advocate for enabling scientists and students to be efficient and effective in their computational workflows. Building on previous work in big data oceanography with links to the Pangeo project, COSIMA : Consortium for Ocean-Sea Ice Modelling in Australia, and CIOOS : Canadian Integrated Ocean Observing System, James wants to bring the strength of the Jupyter ecosystem to users across a broad range of educational and research domains.\n","date":1718668800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1718668800,"objectID":"1603084ce2f0780df78913a58b0e5817","permalink":"https://2i2c.org/author/james-munroe/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/james-munroe/","section":"authors","summary":"James is Product and Community Lead for 2i2c. Coming from a background as an associate professor in the Department of Physics and Physical Oceanography at Memorial University of Newfoundland , he is a strong advocate for enabling scientists and students to be efficient and effective in their computational workflows.","tags":null,"title":"James Munroe","type":"authors"},{"authors":["harold-campbell"],"categories":null,"content":"I enjoy building and supporting communities of practice. I have built a small JS visualization library and dabbled in delivery management systems. Recently, I have strong interests in music (programming VST, etc.), AI and data science.\n","date":1713139200,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1713139200,"objectID":"1871ee3c936a96ebd5a3f1d03bd46ac0","permalink":"https://2i2c.org/author/harold-campbell/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/harold-campbell/","section":"authors","summary":"I enjoy building and supporting communities of practice. I have built a small JS visualization library and dabbled in delivery management systems. Recently, I have strong interests in music (programming VST, etc.","tags":null,"title":"Harold Campbell","type":"authors"},{"authors":["yuvi-panda"],"categories":null,"content":"Building participatory open infrastructure for scientific \u0026amp; educational use cases. A Project Jupyter team member working on infrastructure related projects. Ex Wikimedia and ex-GNOME. Let’s eliminate accidental complexities wherever we find them.\n","date":1704329774,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1705090315,"objectID":"0a9477094d0ef5674613765d19d77fa3","permalink":"https://2i2c.org/author/yuvi-panda/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/yuvi-panda/","section":"authors","summary":"Building participatory open infrastructure for scientific \u0026 educational use cases. A Project Jupyter team member working on infrastructure related projects. Ex Wikimedia and ex-GNOME. Let’s eliminate accidental complexities wherever we find them.","tags":null,"title":"Yuvi Panda","type":"authors"},{"authors":["georgiana-dolocan"],"categories":null,"content":"Software Engineer irreversibly in love with open source. A JupyterHub team member, focusing on infrastructure and community growth. Previously JupyterHub Contributor in Residence and Outreachy intern through an internship that supports diversity in open source and free software.\n","date":1688083200,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1688083200,"objectID":"6b99443e1887b9f34a76d5ae9503a4e1","permalink":"https://2i2c.org/author/georgiana-dolocan/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/georgiana-dolocan/","section":"authors","summary":"Software Engineer irreversibly in love with open source. A JupyterHub team member, focusing on infrastructure and community growth. Previously JupyterHub Contributor in Residence and Outreachy intern through an internship that supports diversity in open source and free software.","tags":null,"title":"Georgiana Dolocan","type":"authors"},{"authors":["sarah-gibson"],"categories":null,"content":"Sarah Gibson is an Open Source Infrastructure Engineer at 2i2c, an open source contributor and advocate. She holds more than two years of experience as a Research Engineer at a national institute for data science and artificial intelligence, as well as holding a core contributor role in the open source projects Binder , JupyterHub , and The Turing Way . Sarah is passionate about working with domain experts to leverage cloud computing in order to accelerate cutting-edge, data-intensive research and disseminating the results in an open, reproducible and reusable manner.\nSarah holds a Fellowship with the Software Sustainability Institute and advocates for best software practices in research. She is a member of the mybinder.org operating team and maintains infrastructure supporting over 150k launches of reproducible computational environments per week. She has also mentored projects through two cohorts of the Open Life Science programme, imparting lived experience of her skills participating and leading in open science projects.\n","date":1650326400,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":1650326400,"objectID":"83b3d2127330b720674bb862052a869c","permalink":"https://2i2c.org/author/sarah-gibson/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/sarah-gibson/","section":"authors","summary":"Sarah Gibson is an Open Source Infrastructure Engineer at 2i2c, an open source contributor and advocate. She holds more than two years of experience as a Research Engineer at a national institute for data science and artificial intelligence, as well as holding a core contributor role in the open source projects Binder , JupyterHub , and The Turing Way .","tags":null,"title":"Sarah Gibson","type":"authors"},{"authors":["admin"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"2525497d367e79493fd32b198b28f040","permalink":"https://2i2c.org/author/2i2c/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/2i2c/","section":"authors","summary":"","tags":null,"title":"2i2c","type":"authors"},{"authors":["cathryn-carson"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"d06aefb9519756f12b367d49725e76d9","permalink":"https://2i2c.org/author/cathryn-carson/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/cathryn-carson/","section":"authors","summary":"","tags":null,"title":"Cathryn Carson","type":"authors"},{"authors":["damian-avila"],"categories":null,"content":"Father, Software Developer, Quant, (formerly) Biochemist, and some other things ;-) Currently living between Córdoba and Buenos Aires, Argentina. I have made some contributions to popular Open Source projects such as Jupyter, Nikola, and Bokeh. I have also started several projects being RISE (a “live” slideshow for the Jupyter notebook) the most popular one. You can easily find videos of some of my talks and tutorials at multiples national and international conferences. How can I help?\n","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"9a4427d33f68e5b2a7e48689f801048a","permalink":"https://2i2c.org/author/damian-avila/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/damian-avila/","section":"authors","summary":"Father, Software Developer, Quant, (formerly) Biochemist, and some other things ;-) Currently living between Córdoba and Buenos Aires, Argentina. I have made some contributions to popular Open Source projects such as Jupyter, Nikola, and Bokeh.","tags":null,"title":"Damián Avila","type":"authors"},{"authors":["erik-sundell"],"categories":null,"content":"Attracted by an inclusive culture and a leverage for a positive world impact, Erik has steered towards open source development in the Jupyter ecosystem from working as a math and physics teacher in Sweden.\n","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"236074155e2fe6a29b991c7208e4c8e5","permalink":"https://2i2c.org/author/erik-sundell/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/erik-sundell/","section":"authors","summary":"Attracted by an inclusive culture and a leverage for a positive world impact, Erik has steered towards open source development in the Jupyter ecosystem from working as a math and physics teacher in Sweden.","tags":null,"title":"Erik Sundell","type":"authors"},{"authors":["fernando-perez"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"3ef1af30502eabcbfbf1b6b9fdec9086","permalink":"https://2i2c.org/author/fernando-perez/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/fernando-perez/","section":"authors","summary":"","tags":null,"title":"Fernando Perez","type":"authors"},{"authors":["giuliano-maciocci"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"3d1a70b6153ee523987a5adb34530f61","permalink":"https://2i2c.org/author/giuliano-maciocci/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/giuliano-maciocci/","section":"authors","summary":"","tags":null,"title":"Giuliano Maciocci","type":"authors"},{"authors":["jim-colliander"],"categories":null,"content":"Jim is a 2i2c Co-Founder. He is a Professor of Mathematics at the University of British Columbia and previously served (2016-2021) as the Director of The Pacific Institute for the Mathematical Sciences (PIMS). While at PIMS and using infrastructure from Compute Canada, he helped create a national-scale JupyterHub service called Syzygy . He co-founded Callysto , a collaboration between PIMS and Cybera. Callysto develops open education resources and training programs for students and teachers in grades 5-12 leveraging cloud-hosted interactive computing. Colliander also co-found Crowdmark , an education technology company based in Toronto that provides workflows and AI-based improvements to education assessment.\n","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"f4e8cb10915e4de235af6e01631e7fd8","permalink":"https://2i2c.org/author/jim-colliander/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/jim-colliander/","section":"authors","summary":"Jim is a 2i2c Co-Founder. He is a Professor of Mathematics at the University of British Columbia and previously served (2016-2021) as the Director of The Pacific Institute for the Mathematical Sciences (PIMS).","tags":null,"title":"Jim Colliander","type":"authors"},{"authors":["lindsey-heagy"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"a0558a9a07b39d5ff5cb0cc779f87cc5","permalink":"https://2i2c.org/author/lindsey-heagy/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/lindsey-heagy/","section":"authors","summary":"","tags":null,"title":"Lindsey Heagy","type":"authors"},{"authors":["ryan-abernathy"],"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"term","lang":"en","lastmod":-62135596800,"objectID":"ee4ec873203b28c0eeafd2019d926eb5","permalink":"https://2i2c.org/author/ryan-abernathey/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/author/ryan-abernathey/","section":"authors","summary":"","tags":null,"title":"Ryan Abernathey","type":"authors"},{"authors":["Jenny Wong"],"categories":["updates","partnerships"],"content":" Summer school for inverse modeling of greenhouse gases 2024 The Cooperative Institute for Research in the Atmosphere ( CIRA ) is an interdisciplinary cooperation between NOAA research scientists and Colorado State University. CIRA is hosting a summer school for inverse modeling of greenhouse gases using atmospheric data assimilation techniques. The US Greenhouse Gas Center is supporting the workshop by providing 40+ attendees access to their interactive computing hub operated by 2i2c (see our blog post about their launch ).\nHub administrators have built a customized software environment with container technology for use at the workshop. In doing so, this bypasses the need for participants to individually install software on their own machines and the online hub provides a consistent and reproducible interactive computing environment that is easily accessible and scalable.\nLogin screen of the GHG hub showing the custom built SSIM-GHG image option. Acknowledgements # 2i2c would like to credit the following individuals for their great efforts supporting this workshop:\nSanjay Bhangar (Development seed) Slesa Adhikari (NASA IMPACT) ","date":1718841600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718841600,"objectID":"359285341adb9ee283e99471397f154e","permalink":"https://2i2c.org/blog/2024/ghg-summer-school/","publishdate":"2024-06-20T00:00:00Z","relpermalink":"/blog/2024/ghg-summer-school/","section":"blog","summary":"Summer school for inverse modeling of greenhouse gases 2024 The Cooperative Institute for Research in the Atmosphere ( CIRA ) is an interdisciplinary cooperation between NOAA research scientists and Colorado State University.","tags":["community"],"title":"US Greenhouse Gas Center supports summer school at CIRA","type":"blog"},{"authors":["Jenny Wong","James Munroe","Angus Hollands"],"categories":["updates"],"content":" What is Project Pythia? # Project Pythia is the education working group for Pangeo , a community platform for Big Data geoscience in which 2i2c operates a cloud hub. The core aim of Project Pythia is to spearhead the creation and curation of community-driven, open-source documentation, in the form of “cookbooks”, to enable the adoption of open, scalable and reproducible workflows for geoscientists.\nWhat did 2i2c do? # Jenny, James and Angus from the 2i2c team participated in the annual Project Pythia Cook-off 2024 , a hackathon where cookbook authors and collaborators can spend dedicated time on creating and maintaining their content using Jupyter Book and publishing their cookbooks with GitHub actions.\n2i2c teamed up with the infrastructure breakout group during the hackathon, led by Katelyn FitzGerald (UCAR) and Kevin Tyle (University at Albany), and members of the Curvenote team also joined the group.\nDay 1 # 2i2c deployed and demonstrated a dedicated BinderHub service for Project Pythia that allowed hackathon participants to “self-serve” images of their software environment, which were specified by including a list of packages in an environment.yml file placed in their GitHub cookbook repository. Participants could then pull the image from a container registry into their 2i2c hub (or indeed, any other JupyterHub server) to share and reproduce their computational environments with ease.\nDay 2 # During the first half of the day, we quickly identified a number of issues that were proving to be a maintenance headache for the Project Pythia infrastructure group:\nConfiguration files for each cookbook were difficult to update at scale. Project Pythia currently have a gallery of over 30 cookbooks! Changes to Sphinx-based themes inherited from upstream were prone to breaking custom Project Pythia branding downstream. Executable content was not able to run on the Project Pythia’s dedicated BinderHub hosted on JetStream2 (operated by NSF). Cookbooks frequently cross-referenced materials from other cookbooks to build upon pre-existing knowledge, but this was not easy to author and the reader experience was not as smooth as it could be. Following the announcement that Jupyter Book 2.0 will use MyST last month, Rowan (Curvenote) and Angus (2i2c) delivered a compelling demonstration of the MyST ecosystem centered around modern web-first technologies (JavaScript/TypeScript) that offers improved interactivity and accessibility.\nIn the second half of the day, we decided to use the hackathon to explore migrating the Pythia cookbooks from using a Sphinx-based to a MyST-based document structure and engine. Within one afternoon, the group migrated four cookbooks to use MyST MD\nPythia Foundations High Resolution Rapid Refresh on AWS Radar Cookbook Advanced Visualization . This moment was palpably exciting! It was evident that MyST MD supported backwards compatible content out of the box, which alleviated fears of sunk cost into existing Sphinx-based cookbooks. The migration workflow was as simple as executing the following commands\nconda install mystmd\nmyst.\nDay 3 # We spent this day tackling support for managing a gallery of Project Pythia cookbooks at scale. See the Executable Books blog post for technical details on how we\nCentralized configuration Prototyped a gallery plugin in Python Fixed a number of bugs related to integrated computation with Binder and JupyterLite Embraced the referencing and reuse of content with simple markdown syntax for hover-references . Day 4 # Looking to the future, we spent time reflecting on our experiences and discussing the potential, transformative impact MyST MD tooling could have in the hands of the scientific community at large, including the communities served by 2i2c. Knowledge-sharing based on static figures and PDFs would fall obsolete and give way to a dynamic, web-first approach to interactive communication and publishing backed by compute from a Jupyter server.\nThroughout the course of the hackathon, the rate of iterated development for both end users of the community cookbook and the developers of the open-source tooling was astounding. For example, we were able to quickly expose small bugs ( e.g. support for HTML video tags ) in the MyST MD tooling, which were immediately fixed upstream and released within minutes. The feedback loop that connected the user experience with the software tooling was incredibly synergistic, with immediate impact both upstream and downstream that 2i2c hopes to continue replicating across many facets of their operations.\nBeyond the Project Pythia Cook-off, the breakout group will continue conversations around strengthening their community of practice and hopefully advocating for wider adoption of MyST MD amongst the scientific community (say hello to some of our group members at SciPy 2024 in July!).\nAcknowledgements # University at Albany (NSF award 2324302): Led the funding acquisition, helped organize and facilitate the event UCAR (NSF award …","date":1718668800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718668800,"objectID":"fc3f258e0a3863ceb0cb6e0d66ec641a","permalink":"https://2i2c.org/blog/2024/project-pythia-cookoff/","publishdate":"2024-06-18T00:00:00Z","relpermalink":"/blog/2024/project-pythia-cookoff/","section":"blog","summary":"What is Project Pythia? # Project Pythia is the education working group for Pangeo , a community platform for Big Data geoscience in which 2i2c operates a cloud hub. The core aim of Project Pythia is to spearhead the creation and curation of community-driven, open-source documentation, in the form of “cookbooks”, to enable the adoption of open, scalable and reproducible workflows for geoscientists.","tags":["community"],"title":"Hacking the Project Pythia Cook-off with MyST Markdown","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Over the past several years, 2i2c has built a platform for serving community-centric hubs that provide a digital home for workflows in creating and sharing knowledge. See our three-year retrospective for a report about the growth and impact this service has had.\nDuring that time, we’ve experimented with several models for funding and sustaining this infrastructure. We’ve tried everything from direct cost-recovery from individual communities, to institutional contracts that cover several hubs, to grant-based models that fund many communities at the same time.\nThere are pros and cons associated with each, and we believe that a combination of all of them is important for a long-term service sustainability model for 2i2c. However, with this post we’d like to share the community funding model that strikes the right balance between short-term sustainability and scalability.\nIn short: 2i2c aims to serve networks of communities that are joined by a domain or workflow, and fund the network at once rather than through one-on-one contracts.\nA model of the funding and service relationships we aim to build. We believe that this model strikes a balance between “scalable and very simple hubs” (which require a lot of administrative toil) and “fully bespoke hubs” (which are expensive and unscalable). By using a single funding contract to serve many communities, we can reduce the amount of sales and contracting toil for each community. This will let us raise funds more quickly, and focus more of our time on delivering service.\nWe are seeking community leaders to collaborate # If you’re part of one or more communities that would benefit from cloud infrastructure for creating and sharing knowledge, and believe a network like this would benefit you, please reach out! We are seeking leaders collaborate in designing service for networks like the ones described above, and identifying potential funding sources for it.\nIf you’re interested in collaborating on this, send an e-mail to partnerships@2i2c.org .\nLearn more # You can find more information about this fundraising and service strategy in our Team Compass documentation .\n","date":1718668800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718668800,"objectID":"778d786f72c8f47613284a2d5650bab7","permalink":"https://2i2c.org/blog/2024/funding-community-networks/","publishdate":"2024-06-18T00:00:00Z","relpermalink":"/blog/2024/funding-community-networks/","section":"blog","summary":"Over the past several years, 2i2c has built a platform for serving community-centric hubs that provide a digital home for workflows in creating and sharing knowledge. See our three-year retrospective for a report about the growth and impact this service has had.","tags":["sustainability"],"title":"Towards scalable and sustainable networks of community hubs","type":"blog"},{"authors":["Jenny Wong"],"categories":["updates","engineering","partnerships"],"content":" The UToronto hub landing page 2i2c has operated The University of Toronto hub since 2021 and this hub supports over 6000 educators and learners in a day! With a community of this size, file storage can quickly grow out of control and cause issues.\nThe 2i2c engineering team have implemented a low storage alerting system for Microsoft Azure, so that they can pre-emptively take remedial action before the filesystem is about to run out of diskspace.\nGreat job team 🚀\nUToronto hub usage ","date":1718323200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1718323200,"objectID":"995e434955e5e4182f24fd1ae4d780d7","permalink":"https://2i2c.org/blog/2024/utoronto-storage-monitoring/","publishdate":"2024-06-14T00:00:00Z","relpermalink":"/blog/2024/utoronto-storage-monitoring/","section":"blog","summary":"The UToronto hub landing page 2i2c has operated The University of Toronto hub since 2021 and this hub supports over 6000 educators and learners in a day! With a community of this size, file storage can quickly grow out of control and cause issues.","tags":["community"],"title":"Low storage alerting for the UToronto cluster","type":"blog"},{"authors":["Angus Hollands","Chris Holdgraf","Rowan Cockett"],"categories":["upstream"],"content":"See the Executable Books blog for a post on the future directions of the Jupyter Book project, which will be built on top of the MyST Markdown engine .\n","date":1716249600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1716249600,"objectID":"db6f343c8a73a07841ec11a7718e2f53","permalink":"https://2i2c.org/blog/2024/myst-jupyter-book/","publishdate":"2024-05-21T00:00:00Z","relpermalink":"/blog/2024/myst-jupyter-book/","section":"blog","summary":"See the Executable Books blog for a post on the future directions of the Jupyter Book project, which will be built on top of the MyST Markdown engine .","tags":["product"],"title":"Jupyter Book 2.0 will use MyST","type":"blog"},{"authors":["Jenny Wong"],"categories":["updates"],"content":" Figure from the preprint showing large and small scale air-sea fluxes are separated. By Julius Busecke et al., licensed under CC BY 4.0 Julius Busecke et al. of the LEAP-Pangeo 1 hub, have recently published a preprint2 that investigates “The Overlooked Sub-Grid Air-Sea Flux in Climate Models” using 2i2c infrastructure. Well done all! 🎉\nNSF Science and Technology Center (STC) Learning the Earth with Artificial intelligence and Physics (LEAP) (Award # 2019625) ↩︎\nhttps://doi.org/10.31223/X5WQ47  ↩︎\n","date":1716249600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1716249600,"objectID":"b200749d9f926d902fa7e2293f759749","permalink":"https://2i2c.org/blog/2024/leap-pangeo-paper/","publishdate":"2024-05-21T00:00:00Z","relpermalink":"/blog/2024/leap-pangeo-paper/","section":"blog","summary":"Figure from the preprint showing large and small scale air-sea fluxes are separated. By Julius Busecke et al., licensed under CC BY 4.0 Julius Busecke et al. of the LEAP-Pangeo 1 hub, have recently published a preprint2 that investigates “The Overlooked Sub-Grid Air-Sea Flux in Climate Models” using 2i2c infrastructure.","tags":["community"],"title":"Researchers at LEAP-Pangeo investigate overlooked sub-grid air-sea heat flux in climate models","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"2i2c recently finished it’s three year retrospective after closing out its original seed grant. As part of this process, we’re revisiting our organizational strategy, structure, and overall plan, in order to incorporate the learning that we’ve done over our first three years.\nOur value proposition is a key framing for 2i2c’s intended impact, key stakeholders, and platform strategy. We recently completed a team exercise to refine this statement for 2i2c, and are excited to share it with you below:\nA global network of community hubs for interactive learning and discovery Our interactive computing platform gives your community a digital home to create and share knowledge, and a global network of communities to learn from. This is an exciting direction that leans into and builds upon the way we’ve described our service so far. It recognizes that the value in our service doesn’t end with simple access to an interactive computing environment, but lies in how that environment’s tools empower a community to create and share knowledge with one another.\nWe believe that this is an exciting direction to build towards, because it is based in the value of the collection of communities we serve, and the way that this network can be greater than the sum of its parts. We’re excited to lean into this direction in how we shape our platform, what open source contributions we make, and where we aim to have impact in the coming years.\nTo begin, we’ve interwoven some ideas from this value proposition into 2i2c.org, and the way that we describe our service. We’d love feedback from anyone who has an idea, a critique, or “yes, and” to share.\nA recent talk with this value proposition # As part of this work, 2i2c’s Executive Director, Chris Holdgraf , gave a talk about 2i2c to the Incentivizing Open and Collaborative Research (ICOR) community. Here are some links in case others are interested:\nSlides for viewing More information for the talk Video link Here’s the video below for quick reference:\nData Sharing and Analysis in Collaborative Open Research Environments from Michael Markie on Vimeo.\n","date":1714953600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1714953600,"objectID":"da52f16079db53f897ddd141995924f2","permalink":"https://2i2c.org/blog/2024/value-proposition/","publishdate":"2024-05-06T00:00:00Z","relpermalink":"/blog/2024/value-proposition/","section":"blog","summary":"2i2c recently finished it’s three year retrospective after closing out its original seed grant. As part of this process, we’re revisiting our organizational strategy, structure, and overall plan, in order to incorporate the learning that we’ve done over our first three years.","tags":["product"],"title":"An update to 2i2c's value proposition","type":"blog"},{"authors":["Chris Holdgraf","Harold Campbell"],"categories":["updates"],"content":"This is a follow-up to our 2023 report of organizational strengths and weaknesses , describing some improvements we’ve made on our team’s coordination and delivery.\nIn 2023, we released a report describing our organizational strengths and weaknesses . This uncovered a key challenge for our team: improving our coordination and delivery. Over the previous two years, our service had grown significantly in its scope and complexity. We were working on more than 7 active grants and were serving more than 70 active communities with around 7,000 monthly active users.\nThis was taxing our small team, and we found ourselves struggling to efficiently deliver on our work. For example, a collaboration with GESIS to bring image building functionality to JupyterHub took longer than we wished, and we felt that our planning and execution was not transparent enough to their team. In addition, in a collaboration to serve communities in Latin America and Africa we felt that 2i2c was not responsive enough to onboarding and deploying infrastructure for new communities.\nSteps we’ve taken to improve delivery # At the beginning of 2024, we hired our first Delivery Manager and Chief of Staff role as well as our first Product Lead role . Both of these roles are meant to develop systems and team practices that improve our planning and delivery.\nIn Quarter 1 of 2024, we designed and initiated an organizational transformation with the following goals:\nProvide clarity about our overall organizational goals and strategy. Define our near-term goals and major projects that drive our work. Define and prioritize the major work items that feed into these goals. Break this major work items into actionable items that our team can work on from day to day. Provide visibility for all of this information across the entire organization. Below is a brief description of the major changes that we’ve made. These are still a work in progress, and organizational transformation takes months, if not years, but we hope that this provides a useful snapshot in time as we kick off this process.\nOur system of work # Our team-wide system of work can be found in the Team Compass at the link below:\nhttps://compass.2i2c.org/cross-functional/workflow/ This system of work attempts to link our strategic goals with concrete chunks of work to deliver. You can see an overview of this system below:\nOur work system shows how initiatives are made up of lists of actions that accomplish them. These actions are distributed across our team’s operational boards for delivery. It is roughly broken down into these major areas:\nOur value proposition: Our system of delivery starts with a value proposition. This is a north-star statement for the value that 2i2c aims to provide to our communities in order to achieve our mission. It is a guiding principle for where we prioritize our time and improve our service.\nWhile updating our delivery model, we decided it was time to update the value proposition we’d been informally using. We’re in the process of validating this value proposition with communities, and will share a draft for public comment soon!\nStrategic goals and major projects: Next we define strategic goals that describe the most important progress we must make as an organization. This considers our current capabilities and challenges, as well as the major projects that we’re already committed to (like grants). Our initiatives (described below) should each represent progress towards one or more of our goals and major projects.\nStrategic initiatives: These are major thrusts of work that represent progress towards our goals. They range in time from weeks to months, and generally require coordination and action across each of 2i2c’s functional areas. Initiatives exist in a dedicated board, where we shape and scope them with enough information to understand them and prioritize. Once an initiative is in progress, it begins driving work on a two-week planning cycle. All in-progress initiatives should make up a significant percentage of 2i2c’s total work allocation.\nOperational boards: Operational boards are used to track our day-to-day workstreams. We organize into two-week sprints, with a collection of work pulled into each sprint according to in-progress initiatives and the other types of reactive and operational work on our plate (for example, responding to support tickets is reactive work). Within each initiative, we coordinate across our teams in order to understand the next steps needed and who is responsible for doing it. This helps teams plan the work for their next iteration.\nThis system is very much still a work in progress, and we’ve already identified a number of ways that we’d like to improve it moving forward. For example, we’d like to find more efficient ways of coordinating across our team, and encouraging team members to own their own work.\nChanges to our team culture # In addition to our system around planning work, we’ve also identified a number of ways that we can …","date":1713139200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1713139200,"objectID":"affa08ea5c8b3279786b5cd50f8bc84b","permalink":"https://2i2c.org/blog/2024/delivery-improvements/","publishdate":"2024-04-15T00:00:00Z","relpermalink":"/blog/2024/delivery-improvements/","section":"blog","summary":"This is a follow-up to our 2023 report of organizational strengths and weaknesses , describing some improvements we’ve made on our team’s coordination and delivery.\nIn 2023, we released a report describing our organizational strengths and weaknesses .","tags":["culture"],"title":"Improvements to our team's planning and delivery","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["engineering","partnerships","updates"],"content":" What happened? # A few weeks ago, the JupyterHub team discovered a security vulnerability in the jupyter-server-proxy package that would allow potential unauthenticated access to a JupyterHub via WebSockets, allowing unauthenticated users to run arbitrary code on the JupyterHub. jupyter-server-proxy is used by many communities to provide alternative user interfaces like RStudio and remote desktops.\nThis vulnerability was detected by the JupyterHub team, with leadership from 2i2c’s engineers. It was resolved through upstream contributions to the JupyterHub project, and we have deployed a fix that mitigates this vulnerability for all the hubs 2i2c manages.\nDoes this impact my 2i2c community hub? # We do not believe that any of 2i2c’s communities were impacted by this vulnerability, and a patch has now been pushed to all community hubs to resolve this issue.\nIf your community was vulnerable to this problem, you might experience slightly slower startup latency while we work out a long-term solution.\nSince this is a vulnerability in the docker image used by our communities, we will be reaching out over the next few weeks to put a more permanent fix in place.\nWhere can I learn more? # See the JupyterHub security advisory for CVE-2024-28179 for more information about the security vulnerability, including details on the mitigation we have put in place to protect our communities.\nConclusion # We’re grateful that the JupyterHub community was quick to acknowledge, respond, and resolve this security vulnerability after it was brought to their attention. We’re also proud that 2i2c’s engineers helped the JupyterHub team throughout the process.\nThis allowed our team to resolve the problem before it impacted any of 2i2c’s communities. Because 2i2c community infrastructure is managed in a central location, we were able to resolve this for over 80 communities with a single team rather than expecting each community to learn about and fix this problem on their own.\nWe also believe this reflects the healthy upstream relationships that we hope to encourage with our team’s Open Source strategy and practices . By working with the JupyterHub community and pushing changes upstream, we’ve resolved this issue for any user of jupyter-server-proxy, not just 2i2c’s own ecosystem. In particular, because of 2i2c’s position running hubs for many communities via Kubernetes, we were able to identify a solution that did not require every user image to be updated (as described in section For JupyterHub admins of Z2JH installations).\nWe believe that all of these lead to a healthier, safer ecosystem of open source tools ❤️.\n","date":1710806400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1710806400,"objectID":"9b65af0a3c3fc20b796ab16baa5c7110","permalink":"https://2i2c.org/blog/2024/cve-jupyter-server-proxy/","publishdate":"2024-03-19T00:00:00Z","relpermalink":"/blog/2024/cve-jupyter-server-proxy/","section":"blog","summary":"What happened? # A few weeks ago, the JupyterHub team discovered a security vulnerability in the jupyter-server-proxy package that would allow potential unauthenticated access to a JupyterHub via WebSockets, allowing unauthenticated users to run arbitrary code on the JupyterHub.","tags":[],"title":"Security report for jupyter-server-proxy: CVE-2024-28179","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"We’re pleased to share a three-year retrospective report that was created to close-out 2i2c’s original seed funding grant provided by the Chan Zuckerberg Initiative .\nSee the Zenodo entry here: See the MyST website for the report at 2i2c.org/report-czi-2021 . Download a PDF version generated by MyST here . This report was written with the new MyST Markdown document engine and shows off some of the functionality that we’ve been working on in collaboration with the MyST team.\nWe’re incredibly grateful for the seed funding that CZI provided to kickstart 2i2c’s mission and operations, and excited about more impact to come!\n","date":1709251200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1712793600,"objectID":"74aa80756eba5914eabcf720a6945927","permalink":"https://2i2c.org/blog/2024/report-czi/","publishdate":"2024-03-01T00:00:00Z","relpermalink":"/blog/2024/report-czi/","section":"blog","summary":"We’re pleased to share a three-year retrospective report that was created to close-out 2i2c’s original seed funding grant provided by the Chan Zuckerberg Initiative .\nSee the Zenodo entry here: See the MyST website for the report at 2i2c.","tags":[],"title":"A three year retrospective report of 2i2c's impact","type":"blog"},{"authors":["Yuvi Panda"],"categories":["engineering","partnerships","updates"],"content":"Thanks to Arnim Bleier , Jenny Wong , Georgiana Elena , Damián Avila , Jim Colliander and James Munroe for contributing to this blog post\nmybinder.org is a very popular service that allows end users to specify and share the environment (languages, packages, etc) required for their notebooks to run correctly by placing configuration files they are already familiar with (like requirements.txt or environment.yml) along with their notebooks. While not without its own set of challenges, this is extremely powerful because it puts control of the environment in the hands of the people who write the code. They can customize the environment to fit the needs of their code, instead of having to fit their code into the environment that admins have made available.\nBut, mybinder.org (and the BinderHub software that powers it) is built for sharing your work after you are done with it, not for actively doing work. BinderHubs often do not have persistent storage nor persistent user identity, and UX is centered around ephemeral interactivity that can be shared with others (via a link), rather than persistent interactivity that a single user repeatedly comes back to. JupyterHub is more commonly used for this kinda workflow, but doesn’t currently have the ability for users to easily build their own environments. Admins who are running the JupyterHub can make multiple environments available for users to choose from, but this still puts admins in the critical path for environment customization.\nOur collaboration with GESIS , NFDI4DS , and CESSDA , aims to bring this flexibility to JupyterHub directly. We aim to empower users to decide for themselves which applications and dependencies are installed on a per-project basis. Our work enables communities with heterogeneous requirements to share a single Hub. Our approach frees administrators from being overwhelmed by installation requests and transforms the JupyterHub platform into a platform for collaborative computational reproducibility. In this update, we report on our progress and upcoming steps in this project.\nWhat does a BinderHub do, exactly? # It is helpful to understand that BinderHub primarily has 3 responsibilities:\nPresent a UI to the end user for them to provide details on what to build (this is what you see when you go to mybinder.org) Call out to repo2docker in a scalable way to actually build and push an image containing the environment for the given repository, and show the user logs as this build process happens. This also allows users to debug issues with their build more easily. Talk to a JupyterHub instance to launch a user server with the built docker image, and redirect the user to this. (2) is really the core feature of BinderHub, and we settled on figuring out how to make that available to JupyterHub users. It was really important to us that this was also done in a way that can be sustainably used by everyone, not just 2i2c. This blog post discusses the various improvements to the broad ecosystem of projects in the Jupyter ecosystem to get this done.\nDemo # But first, a very quick demo of how this looks like right now now!\nThis is very much a work in progress, but the basic flow can be seen clearly. Users see a Server Options menu after they log into JupyterHub. They can specify the two primary things that determine the server configuration:\nThe resources allocated (RAM, CPU and maybe GPU)\nThe environment (container image) used, which can be specified in one of 3 ways:\na. A pre-selected list of environments (container images), provided by the administrators who set up this JupyterHub b. A blank text box where you can enter any publicly available docker image they want c. A mybinder.org style way to specify a GitHub repository, which will be then dynamically built into a docker image for the user!\nSo what did we need to do to accomplish this, in a way that’s very upstream friendly and usable by everyone (and not just 2i2c)?\nA Standalone binderhub-service helm chart # The default upstream BinderHub helm chart includes a JupyterHub as a dependency, and configures itself to be used primarily in a manner similar to mybinder.org . As the person who helped make that choice early on, I can tell you why it was made - for convenience! And it was very convenient, as it allowed us to get mybinder.org going fast. However, it makes it difficult to install a BinderHub service alongside an existing JupyterHub. To this end, we have created a standalone BinderHub helm chart , designed to be installed alongside an existing JupyterHub, so we can use it purely to build images. This allows the BinderHub instance to be used as a JupyterHub Service , which is what we want.\nWhile this helm chart is currently under the 2i2c GitHub org, the hope is that it can eventually migrate to a jupyterhub-contrib organization (once it is created), or it can become the upstream helm chart for BinderHub if enough work can be done in BinderHub to allow it to serve use cases like mybinder.org.\nAs …","date":1704329774,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1705090315,"objectID":"c9a2f2b9d4451cdafd606c391e5b036e","permalink":"https://2i2c.org/blog/2024/jupyterhub-binderhub-gesis/","publishdate":"2024-01-03T16:56:14-08:00","relpermalink":"/blog/2024/jupyterhub-binderhub-gesis/","section":"blog","summary":"Thanks to Arnim Bleier , Jenny Wong , Georgiana Elena , Damián Avila , Jim Colliander and James Munroe for contributing to this blog post\nmybinder.org is a very popular service that allows end users to specify and share the environment (languages, packages, etc) required for their notebooks to run correctly by placing configuration files they are already familiar with (like requirements.","tags":[],"title":"Integrating BinderHub with JupyterHub: Empowering users to manage their own environments","type":"blog"},{"authors":["James Colliander"],"categories":null,"content":" Abstract\nThe International Interactive Computing Collaboration ( 2i2c.org ), working with NASA VEDA , Development Seed and other partners, operates an interactive computing platform for The U.S. Greenhouse Gas Center. The U.S. GHG Center, announced yesterday at the 28th annual United Nations Climate Conference (COP-28) in Dubai, is an interagency collaboration of the Environmental Protection Agency (EPA) , the National Aeronautics and Space Administration (NASA) , the National Institute of Standards and Technology (NIST) , and the National Ocean and Atmospheric Administration (NOAA) . This note places the launch of the U.S. GHG Center in a scientific, international, and national context and argues that similar digital public goods are needed for humanity to understand and manage the Earth system.\nScientific Context # It was controversial in 1827 when Joseph Fourier (the discoverer of the law of heat conduction ) argued 1 that the atmosphere keeps the Earth warm, like a puffy down comforter, but it’s not now. Gases in the atmosphere trap heat near Earth. How much heat is trapped depends on the gas mixture. Putting more heat-trapping gases in is like putting a wool blanket on top of the down comforter. Human activity since industrialization is injecting lots more heat-trapping gas into the atmosphere and changing the Earth’s climate.\nThe science is clear. The up-to-date consensus view of the global scientific community is expressed in the Sixth Assessment Report of the Intergovernmental Panel on Climate Change (IPCC):\nInternational Context # The international community officially recognized human-influenced climate change at the World Climate Conference (WCC-1) 2 in 1979. The 1979 declaration is remarkably prescient and detailed. A complex and interconnected collection of scientific and diplomatic activities were catalyzed by WCC-1. Some important milestones from this history are captured in the chart and numbered list below.\ngantt\rdateFormat YYYY-MM-DD\rtitle International Climate Change Milestones\rsection Study\rWCC-1 (1979) :crit, done, admin0, 1979-02-12, 1979-02-23\rWCP :crit, adminA, 1979-06-01, 2025-12-31 CMIP1: crit, done, adminT, 1995-01-01,1995-12-31\rCMIP2: crit, done, adminR, 1997-01-01, 1998-12-31\rCMIP2+: crit,done,adminS, 2000-05-09, 2001-12-31\rCMIP3 :crit, done, adminP, 2004-10-01, 2006-12-31\rCMIP5 :crit, done, adminO, 2008-09-01, 2013-03-15\rCMIP6 :crit, done, adminQ, 2014-02-01, 2024-12-31\rIPCC :crit, admin1, 1988-12-06, 2025-12-31\rIPCC-AR1 :crit, done, adminH, 1990-08-01, 1992-06-30\rIPCC-AR2 :crit, done, adminI, 1995-01-01,1995-12-31\rIPCC-AR3 :crit,done, adminJ, 2001-01-01, 2001-12-31\rIPCC-AR4 :crit, done,adminK, 2007-01-01,2007-12-31\rIPCC awarded Nobel Prize :crit, done, adminN, 2007-10-12, 2007-11-12\rIPCC-AR5 :crit,done,adminL, 2014-01-01,2014-12-31\rIPCC-AR6 :crit,done,adminM,2023-01-01,2023-12-31\rsection Treaties\rRio Earth Summit (1992) :crit, done, adminC, 1992-06-03, 1992-06-14\rUNFCC :crit, admin2, 1994-03-21, 2025-12-31\rBerlin (COP-1) :crit, done, adminE, 1995-03-28, 1995-04-07\rByrd-Hagel Resolution :crit, done, adminX, 1997-07-25, 1997-07-30\rKyoto (COP-3) :crit, done, adminD, 1997-12-01, 1997-12-10\rKyoto Protocol :crit, done, admin3, 1997-12-11, 2020-12-31 Paris (COP-21) :crit, done, adminF, 2015-11-30, 2015-12-12\rParis Agreement :crit, adminG, 2016-11-04, 2025-12-31\rGlasgow (COP-26) :crit, done, adminV, 2021-10-31, 2021-11-12\rDubai (COP-28) :crit, adminW, 2023-11-20, 2023-12-12\rETF :crit, adminU, 2024-01-01, 2025-12-31 The table above describes a subset (for a more systematic review see 3, 4) of key milestones in global efforts to understand and address climate change. A glossary of acronyms and additional background:\nThe First World Climate Conference (WCC-1) 2 was held in 1979. The World Climate Programme ( WCP ), an activity overseen by the World Meteorological Organization was established after WCC-1. WCP, in partnership with other organizations, operates programs (e.g. the World Climate Research Program (WCRP) ) that organize and integrate international scientific efforts to understand the climate. The WMO also operates the Integrated Global Greenhouse Gas Information System (IG3IS) , a natural partner for the emerging work described below. WCRP manages the Common Model Intercomparison Project (CMIP) . CMIP serves as a kind of league for intercomparing models of the Earth’s climate system developed by teams who approach the problems with different methods and designs. Intercomparison, an approach that enables finding the consensus views of teams with divergent approaches to problems, is used in other modeling scenarios. Research papers on the climate are rapidly produced by scholars from essentially all knowledge disciplines. This overwhelming stream of content, like snowflakes in a blizzard, is coalesced into coherent and carefully scrutinized IPCC Assessment Reports by the Intergovernmental Panel on Climate Change (IPCC) . The Earth Summit held in Rio de Janeiro in 1992 led to the …","date":1701734400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1701734400,"objectID":"439872a921884aafee39428ebea3e093","permalink":"https://2i2c.org/blog/2023/us-ghg-center-launches/","publishdate":"2023-12-05T00:00:00Z","relpermalink":"/blog/2023/us-ghg-center-launches/","section":"blog","summary":"Abstract\nThe International Interactive Computing Collaboration ( 2i2c.org ), working with NASA VEDA , Development Seed and other partners, operates an interactive computing platform for The U.S. Greenhouse Gas Center.","tags":["NASA VEDA","U.S. GHG Center","digital public goods","climate change"],"title":"Digital public goods for Earth system management: U.S. Greenhouse Gas Center launches","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Over the past few months, we’ve been investigating ways to improve our reporting both internally and externally. We’ve decided to experiment with a monthly community update to create a regular cadence of transparency and highlights from 2i2c for our broader community. This is the first such update, so bear with us as we work out the kinks!\nOur goal with these updates is to share what stands out at 2i2c - what we’ve learned, what we’re proud of, where we’ve struggled, and where we’ve had an impact. We hope this can be a historical record of “what stands out” to our team and that it is useful for our broader community to see. We also want this to be relatively short and to the point to make it sustainable to both write and read.\nWe’d love feedback on what else you’d like to see. If you have any ideas, please send an email to hello@2i2c.org.\nRough Numbers # First off, a few numbers on the scale and status of our interactive computing hub service:\nWe are currently running around 73 JupyterHubs that are collectively averaging more than 4000 average monthly users. We have several communities in the educational sector, so October was a peak in the Fall semester of activity.\nWe’re recovering roughly 40% of our monthly staffing costs through recurring service revenue. The remainder we’re making up with a combination of grants and more focused development contracts.\nAssuming minimal growth in our service and fundraising, our runway is roughly until August 2025 - however, we anticipate this to shrink in the short-term once we make critical new hires in the coming months.\nOrganization Updates # This section describes some major organization-wide efforts we’ve started or progressed over the last month.\nImproving Our Quarterly Sprints and Goals # This month our team kicked off the second round of our new quarterly sprints and goals process. This is an attempt to focus our team around a few goals and sub-teams dedicated to them throughout each quarter. Our hope is that this allows us to make strategic “pushes” in directions that feel important for 2i2c’s operations and the communities we serve.\nThis quarter, we incorporated a lot of learning that took place after our first iteration in Q3 2023. We are hoping to sharpen up the timing of events throughout the process, including communicating internally and externally about our status (thus, this blog post series).\nIn the next quarter, we aim to build off of this work, and to identify where our future new hires of Delivery Manager / Interim Chief of Staff and our Product Lead will fit in.\nThree New Jobs Posted # In October, we began a short hiring push to address many of the organizational challenges noted in our organizational structure and strategy audit . We aim to have each of these positions filled by the end of the year and begin incorporating new team members into our organization. Here’s a list of the three job postings:\nDelivery Manager / Interim Chief of Staff Product Lead Open Source Infrastructure Engineer: Cloud Engineering Product Strategy Work # We kicked off a collaboration with Richard Pope to provide us with some short-term product strategy work. In Q3, our team took stock of the many different kinds of services and technology that we deploy, aiming to refine this into a long-term product model.\nRichard will join us for several months to take these outputs and help us craft them into a model for where 2i2c is delivering value that we can build upon for the coming years. We’ll provide more updates for the community as this work continues.\nContinued Onboarding of Communities in Our Catalyst Project Collaboration # We continued onboarding communities onto infrastructure managed by 2i2c as part of a CZI-funded project to serve communities in Latin America and Africa . The grant team began its operations last April and spent the first several months creating an onboarding pipeline and rubric for identifying and connecting with communities. As of October, we’ve onboarded our first few communities - there is still a lot of content, training material, and documentation to create, and we will begin iterating on this in collaboration with our early-adopted communities in Q4 2023 and Q1 2024.\nPartnerships and Impact # This section describes notable new partnerships and developments with communities in our interactive computing hub service.\nWe began several new partnerships with communities in the research space this month.\nThe NASA Visualization, Exploration, and Data Analysis (VEDA) project is an open-source science cyberinfrastructure for data processing, visualization, exploration, and geographic information systems (GIS) capabilities.\nThe US Greenhouse Gas Center provides a cloud-based system for exploring and analyzing U.S. government and other curated greenhouse gas datasets.\nIn addition, we’ve celebrated considerable growth in one of our partner communities: CryoCloud . This community focuses its work around studying the Cryosphere using satellite imagery data. …","date":1699574400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1699574400,"objectID":"eb4bed1d078424b0423eb1005a0937aa","permalink":"https://2i2c.org/blog/2023/update-october/","publishdate":"2023-11-10T00:00:00Z","relpermalink":"/blog/2023/update-october/","section":"blog","summary":"Over the past few months, we’ve been investigating ways to improve our reporting both internally and externally. We’ve decided to experiment with a monthly community update to create a regular cadence of transparency and highlights from 2i2c for our broader community.","tags":[],"title":"Community Update: October 2023","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Over the last several months 2i2c has been working with an organizational consulting group called Difference Digital to help us identify the major opportunities and challenges in our organizational structure and strategy. The result of this work is a report that describes in detail the major strengths, weaknesses, challenges, and opportunities that 2i2c faces. It also recommends major actions to take as an organization.\n2i2c values organizational transparency and a willingness to be honest about where you’re struggling. Stress is a natural part of both individuals and organizations, and should be embraced with the goal of learning and improving. Moreover, as a young organization 2i2c has benefitted heavily from the documents and learning that other organizations have made publicly available. We wouldn’t be where we are without building on the backs of others who are willing to share what they’ve learned.\nSo, we are making this organizational audit and report public for anyone to see. We hope that it provides transparency into 2i2c’s current status, and that it serves as a useful resource for other non-profits that are growing and facing similar challenges.\nHere’s a link to the report on Zenodo .\nFor more background on this report, check out the short description below.\nIn April of this year we had our first in-person team meeting. We were excited and grateful to have the opportunity to speak to each other face-to-face. We also learned that many people on our team were stressed out! Our service had grown slow-but-steadily over the previous year, and we were feeling the tension that comes with growing your partnerships without significantly changing your team’s capacity or structure.\nSo, we decided to work with an organizational consulting group called makeadifference.digital to help us identify where we need to make improvements. They spent several weeks having one-on-one conversations with each member of the team, as well as doing a broader organizational analysis and comparison to other technical organizations at a similar stage of their lifecycle.\nThe result of this work was a report that outlines the major opportunities and strengths, as well as challenges and gaps in capacity, that our team currently faces. It makes a number of recommendations for how we should shift our practices, and importantly it also notes that the only way to gain that capacity is by hiring for new people and skills.\nHere’s a link to the report on Zenodo .\nThe immediate result of this work is that we currently have three jobs posted:\nA Product Lead role to help us build a “product function” within 2i2c’s team. A Delivery Manager / Chief of Staff role to oversee and manage 2i2c’s system of work. A cloud and operations engineering role to grow our cloud engineering team’s capacity in serving communities. Our next steps are to fill these positions, and to then begin the work of implementing many of the recommendations that are contained in the report. We’re confident that this is a natural part of being a small and growing organization, and we are grateful for the expertise of makeadifference.digital in guiding us through this work.\nNote: if you’d like to work with makeadifference.digital , you can reach out to them at hello@makeadifference.digital .\n💡 Follow our work! Sign up for our mailing list for updates about 2i2c. Send us an e-mail about collaborating or partnering on a project. See our Service Documentation or our Team Compass to learn about our service and organization.\n","date":1699401600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1699401600,"objectID":"59480fc276a9d788565555c7b0b50d1c","permalink":"https://2i2c.org/blog/2023/organizational-report/","publishdate":"2023-11-08T00:00:00Z","relpermalink":"/blog/2023/organizational-report/","section":"blog","summary":"Over the last several months 2i2c has been working with an organizational consulting group called Difference Digital to help us identify the major opportunities and challenges in our organizational structure and strategy.","tags":[],"title":"Open organizational report: Strengths and challenges for 2i2c's team","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"It’s been two quarters since our last major update - this isn’t quite as frequent as we’re hoping to post updates from our team, but we’re making adjustments to have more regular communication for reasons that will hopefully be a bit clearer below! In that time, we’ve been hard at work serving and growing our interactive computing service, as well as doing some introspection as a team and identifying major next steps moving forward. More on that in the following sections, but first a short service update.\nHow has our service evolved over the past few months? # New partnerships and service growth # Our service has grown several new partner communities over the last two quarters. A few notable communities are the NASA VEDA project , a team at the Smithsonian , a team at NCAR , and the U.S. Greenhouse Gases Center . We are running about 71 hubs across 24 clusters, with about 4000 weekly users ( more usage stats here ).\nWe also began operations on a major collaboration to serve communities in Latin America and Africa, called the Catalyst Project . This team met together for the first time in April, and we’ve been laying a foundation for service growth in the first several months. We are just onboarding our first communities and hope to grow that service in the coming year.\nFinally, we’ve been fortunate to receive some grants around creating content and designing workflows that utilize cloud infrastructure. For example, a NASA TOPS grant and an upcoming collaboration with Project Pythia around geospatial workflows.\nFinancial picture # At this point, we’re recovering roughly 40% of our operating costs through recurring fees of our managed hub service (making up the remainder in development contracts and grants), and we’ve currently got around 2 years of runway.\nHowever, both of these will be lowered soon because we are about to hire for several more positions. Improvements to our product model will allow us to estimate and recover our service costs more effectively, but we also intend to raise some funds next year to support our efforts in making our service more robust, sustainable, and valuable to communities.\nIt’s always difficult to strike a proper balance of team (and cost) growth against the financial buffer needed to assure your partners you’ll stick around, but we’re confident that the new hires described below will serve critical needs for our team and mission.\nFor more context on why and how we’re trying to make up that capacity, read on…\nHow service growth can lead to team stress # Over the past year we’ve had a slow-but-steady stream of new communities interested in working with 2i2c for managing cloud infrastructure for interactive computing. We’ve taken a “let’s make it work somehow” approach to all of our community partnerships thus far, with the idea that we must use these partnerships to learn what communities want and identify common patterns.\nThis is exciting, and we’re fortunate to see the interest and growth in our service. It suggests to us that something about our model is fundamentally right. Communities really love the Right to Replicate , and our participatory service model based around upstream contributions, transparency, and shared responsibility is attractive to many in research and education.\nHowever, each new community is also a new set of stresses on the technical and social infrastructure of our team. Without the capacity to manage the demands of the service, you run the risk of over-extending – and in a worst case scenario, burning out – your team.\nThis became clear in our first in-person team meeting last May. At that meeting, we realized that many on the team were spending too much of their time “reacting” to demands from the service. We also learned that the scope and complexity of our various workstreams had gotten to a size where our informal team structures of work prioritization were no longer adequate.\nGrowing the complexity of our team to match the complexity of our service # So, for the past several months we’ve been working on a plan to evolve 2i2c’s team structure in order to more effectively manage the complexity of our service, and balance long- and short-term thinking.\nThis began with an organizational audit carried out by makeadifference.digital , a consulting group that focuses on tech-for-good and non-profit products and services. They conducted interviews with everybody on the team, and concluded that we have a few key functions missing that were creating or compounding the stresses people felt.\nWe hope to make some of their key findings public soon (Update: this is now available at this blog post about the organizational report ), and in the meantime here is an overview of some highlights:\nWe need a dedicated product functionality # First, we realized that we have a number of new “signals” pushing our service in many different directions. Some are external - from communities we work with or from funders. Some are internal - from different team member visions …","date":1698710400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1698710400,"objectID":"56a2060396fd8fc0261559080a80c3b2","permalink":"https://2i2c.org/blog/2023/2023-q3-update/","publishdate":"2023-10-31T00:00:00Z","relpermalink":"/blog/2023/2023-q3-update/","section":"blog","summary":"It’s been two quarters since our last major update - this isn’t quite as frequent as we’re hoping to post updates from our team, but we’re making adjustments to have more regular communication for reasons that will hopefully be a bit clearer below!","tags":[],"title":"Community update Q3 2023: Service growth and growing pains","type":"blog"},{"authors":["Chris Holdgraf"],"categories":null,"content":"We’re looking for a Product Lead who will be instrumental in shaping 2i2c’s product vision, strategy, and execution. You’ll own the product vision, align it with user needs, and translate it into a clear product roadmap which defines cross-functional priorities and guides our partnerships and engineering teams, enabling efficient product delivery and continuous improvement.\nFor more information and to apply, see our Greenhouse application page for this job .\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $95,000-125,000 Location: Remote, preference for working hours that maximizes overlap in time zones with the existing team (currently distributed from UTC-7 through UTC+3) Deadline: We will begin reviewing applications around November 5th, and will accept them on a rolling basis until the position is filled. Major duties\nDefine and own the product vision and strategy assuming ‘the voice of the user’, and doing so collaboratively and inclusively.\nCreate a clear product roadmap that guides the engineering and partnerships teams.\nCollaborate closely with our engineers and users in partner organizations to translate the product roadmap into actionable plans and tasks.\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply ","date":1698537600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1698537600,"objectID":"736fcc5a2324d7fcb50c9ab3612b5455","permalink":"https://2i2c.org/jobs/2023/product-lead/","publishdate":"2023-10-29T00:00:00Z","relpermalink":"/jobs/2023/product-lead/","section":"jobs","summary":"We’re looking for a Product Lead who will be instrumental in shaping 2i2c’s product vision, strategy, and execution. You’ll own the product vision, align it with user needs, and translate it into a clear product roadmap which defines cross-functional priorities and guides our partnerships and engineering teams, enabling efficient product delivery and continuous improvement.","tags":null,"title":"Product Lead","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":null,"content":"Please see the Product Lead page .\n","date":1698537600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1698537600,"objectID":"35ad88621447764f761311ccc25df1ae","permalink":"https://2i2c.org/jobs/2023/product-operations-lead/","publishdate":"2023-10-29T00:00:00Z","relpermalink":"/jobs/2023/product-operations-lead/","section":"jobs","summary":"Please see the Product Lead page .","tags":null,"title":"Product Lead","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":null,"content":"We’re looking for a Delivery Manager who will serve as a key facilitator in ensuring the successful and efficient delivery of our product . Acting as a servant leader, you’ll guide our engineering team, promote collaboration, and eliminate obstacles to deliver high-quality results that are aligned with our mission and goals.\nFor more information and to apply, see our Greenhouse application page for this job .\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $85,000 - $107,000 Location: Remote, preference for working hours that maximizes overlap in time zones with the existing team (currently distributed from UTC-7 through UTC+3) Deadline: We will begin reviewing applications around October 23rd, and will accept them on a rolling basis until the position is filled. Major duties\nEnsure the successful and efficient delivery of our product ( https://2i2c.org/service/ )\nOrganize and oversee cross-functional work across the team\nDetailed planning and day-to-day management of engineering tasks\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply ","date":1697155200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1697155200,"objectID":"fcf8bb83f949901857455696d58d36bf","permalink":"https://2i2c.org/jobs/2023/delivery-manager/","publishdate":"2023-10-13T00:00:00Z","relpermalink":"/jobs/2023/delivery-manager/","section":"jobs","summary":"We’re looking for a Delivery Manager who will serve as a key facilitator in ensuring the successful and efficient delivery of our product . Acting as a servant leader, you’ll guide our engineering team, promote collaboration, and eliminate obstacles to deliver high-quality results that are aligned with our mission and goals.","tags":null,"title":"Delivery Manager / Chief of Staff","type":"jobs"},{"authors":["Damián Avila"],"categories":null,"content":"We are looking for an experienced Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on democratizing the design and access to cloud-based resources for research and education purposes. This engineer will be part of an awesome engineering team pushing forward the development and reliable operations of our cloud-based infrastructure.\nFor more information and to apply, see our Greenhouse application page for this job .\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $121,600 - $130,500 Location: Remote, required overlapping for US Pacific timezones Deadline: We will begin reviewing applications around October 16th, and will accept them on a rolling basis until the position is filled. Major duties\nCloud infrastructure management and operations\nSite Reliability Engineering\nDevelopment of open source infrastructure for hosted JupyterHub service\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply ","date":1696896e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1696896e3,"objectID":"6b65905fcd83c557ed5980f2cb93e8c8","permalink":"https://2i2c.org/jobs/2023/23qq4-open-source-infrastructure-engineer/","publishdate":"2023-10-10T00:00:00Z","relpermalink":"/jobs/2023/23qq4-open-source-infrastructure-engineer/","section":"jobs","summary":"We are looking for an experienced Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on democratizing the design and access to cloud-based resources for research and education purposes.","tags":null,"title":"Open Source Infrastructure Engineer","type":"jobs"},{"authors":["Chris Holdgraf","Zack Adell"],"categories":["updates"],"content":"We are thrilled to announce a revitalized visual brand for 2i2c. As we continue to grow and evolve, it’s essential that our branding communicates who we are, what we stand for, and how we envision our future. We hope that this new design will unify our visual style across the many places where 2i2c operates.\nIn pursuit of these objectives, we teamed up with Zack Adell , a designer based in Nairobi who has worked with several similar projects over the years (having most-recently overhauled the Invest in Open Infrastructure brand design ). After several rounds of brainstorming, design reviews, and fine-tuning, we’ve landed on a visual identity that resonates with our organization.\nMeet Our New Logo and design system # Zack has created a set of Brand Guidelines that will guide our use of color and visual style in 2i2c’s materials.\nBelow is our new logo in square and wide form:\nOur logo comprises the International Interactive Computing Collaboration wordmark, characterized by our interactive i. We can fly it just about anywhere. A mark of constant progress \u0026amp; community-driven technology, it isn’t stuck to the borders that separate people. It brings us closer together.\nOur primary and secondary color palette is below:\nColor is the first visual thing we remember and a powerful asset in building brand recognition. Our color is blue. Our community blue says the sky is not the limit. It’s energetic and vibrant, just like the community we serve. And it’s our primary colour, supported by a lively secondary palette that’s as at home on digital platforms as it is on billboards.\nWe’ve chosen two fonts to use in the majory of the text that we write. Poppins for big, bold sentences, and Work Sans for more versatile and everyday use.\nFinally, you might notice these curving, criss-crossing strands in some of our materials. For example, in our new social media header:\nThey’re the strands that intersect and show how our work and values are interconnected to our community. We like them because they represent 2i2c’s core mission, which is to build connections between people, computation, and data in order to share open knowledge. We’ll try and think of creative ways to incorporate them into our visual style.\nWe believe our new visual identity is more than just a fresh coat of paint. It’s a reaffirmation of our commitment to our stakeholders and an exciting milestone in our ongoing journey. We can’t wait for you to see it in action, and are excited to hear what you think about it!\n❗ Note\nIf you’d like to get in touch with Zack Adell, please reach out on his LinkedIn profile , or his Instagram account .\n","date":1694044800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1694044800,"objectID":"7f71c8ae3d34bd6f8c813b9ef11e46d4","permalink":"https://2i2c.org/blog/2023/new-design/","publishdate":"2023-09-07T00:00:00Z","relpermalink":"/blog/2023/new-design/","section":"blog","summary":"We are thrilled to announce a revitalized visual brand for 2i2c. As we continue to grow and evolve, it’s essential that our branding communicates who we are, what we stand for, and how we envision our future.","tags":[],"title":"A new design and logo for 2i2c","type":"blog"},{"authors":["James Munroe"],"categories":null,"content":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for a Technical Content Specialist that will create and curate documentation that supports interactive computing and cloud based open science. It intersects job titles such as “technical writer” and “content creator” while emphasizing previous experience working with open source science and related tools and a desire to share that knowledge.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $75,000 - $85,000 Location: Fully remote Deadline: We will begin reviewing applications around August 2, 2023, and will accept them on a rolling basis until the position is filled. Major duties\nCreate documentation for cloud-based interactive computing.\nCurate documentation and resources from open source and open science projects.\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply If you’re interested in advancing your career at an impact-driven non-profit that is dedicated to open communities and public knowledge, then read on…\nAbout you… # Below are several skills that will make somebody well-suited for this role. You should apply even if you do not have all of these skills. We expect any new hires to learn and grow into this role over time. If you aren’t sure whether you have the right skills for this job, you should just apply! This is a fully remote role with a preference for working hours that overlap timezones with the existing team (currently distributed from UTC-7 through UTC+3).\nNecessary qualities # Demonstrated excellence in communicating complex technical information to learners with a different levels of background and experience Demonstrated experience in using open-science tools (e.g. Python or R) in a scientific or scholarly domain Willingness to continually learn and share emerging technologies and techniques in the interactive computing and open science ecosystems Useful qualities # Experience with open source workflows, research and educational contexts, and an understanding of the value that cloud-based infrastructure provides Experience with the Jupyter ecosystem and other tools for interactive computing Experience working with distributed service teams that use asynchronous methods of communication Experience collaborating and coordinating work via online platforms and distributed revision control Ability to communicate in Spanish, Portuguese, or French What you’ll do… # As a Technical Content Specialist, you’ll be responsible for…\nWorking as part of the 2i2c Partnerships Team towards Community Success Creating documentation (tutorials, how-tos, explainers, and reference materials) that are shared across our communities using cloud-based interactive computing Curating documentation resources from open source and open science projects Developing training materials for communities such as Version control for collaborative cloud-based workflows Environment management for hub administrators Best practices for analysis-ready cloud optimized data Assisting the 2i2c Engineering Team by editing technical documentation and documenting solutions from our support desk Authoring content for 2i2c for use in marketing, blog posts, and website copy. Our benefits and compensation # We believe it is important for mission-driven non-profits to also provide competitive benefits and compensation packages. See our compensation philosophy page for more information about our compensation and benefits.\nHow to apply # 2i2c is committed to hiring processes that are inclusive of people with many lived experiences and qualities. We try to structure our hiring process so that it is predictable, doesn’t take too long, and doesn’t take too much effort.\nIf you’d like to apply for this position, please upload your resume and cover letter using this application form . We will begin reviewing applications after August 2, 2023 and will fill this position on a rolling basis once we find a candidate with the right fit for the job.\n","date":168912e4,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":168912e4,"objectID":"b55c651cd683fdce6e20940d91bbdaf8","permalink":"https://2i2c.org/jobs/2023/technical-content-specialist/","publishdate":"2023-07-12T00:00:00Z","relpermalink":"/jobs/2023/technical-content-specialist/","section":"jobs","summary":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for a Technical Content Specialist that will create and curate documentation that supports interactive computing and cloud based open science.","tags":null,"title":"Technical Content Specialist","type":"jobs"},{"authors":["Georgiana Dolocan"],"categories":["upstream"],"content":"","date":1688083200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1688083200,"objectID":"8c280e2adecd7cb1b2b85030e5aa725a","permalink":"https://2i2c.org/blog/2023/external-jupyter-georgiana-mentor/","publishdate":"2023-06-30T00:00:00Z","relpermalink":"/blog/2023/external-jupyter-georgiana-mentor/","section":"blog","summary":"","tags":[],"title":"On the Jupyter Blog: From intern to mentor.","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"It’s a month after the end of Q1 2023, and we’d like to share a belated update about what we were up to in the first quarter of this year (we have good excuses for being late, including new tiny humans, I promise).\nThis quarter we grew our engineering team significantly, and started to refine our team processes and structures to accommodate this extra complexity. We expanded our managed cloud service with new community partners, and made a number of improvements to our technical infrastructure and organizational processes for managing this service.\nRead on below to learn more about what we’ve been up to!\nNew community partnerships # We added several new community partnerships to our managed hub service. We’ve deployed new hub infrastructure for each of the following groups:\nOur University of Toronto Jupyter service now has a dedicated R hub. We ran an event hub for the Drakkar Ocean project We deployed a hub for the NASA Visuaslization Exploration and Data Analysis (VEDA) project . We deployed a hub for the QuantifiedCarbon organization. We ran an event hub for OceanHackWeek 2023 . We onboarded several new community colleges to our “JupyterHubs Education in Community Colleges” collaboration with CloudBank and UC Berkeley CDSS . Service improvements # Below are a few highlights for ways in which we improved our Managed Cloud Service for our partner communities.\nWe simplified our authentication workflow with CILogon # Authentication services allow us to identify a user when they log onto a hub, which determines their ability to access hub resources. Previously we had used a combination of Auth0 , CILogon , or GitHub for authentication.\nHowever, over the past year we’ve been happy with our use of CILogon so far, especially because of its non-profit status and alignment with many research and education institutions that we work with. This quarter, we decided to streamline our authentication process by dropping the use of Auth0 and grow our partnership with CILogon.\n💡 Learn more\nSee CILogon’s write up about it’s partnership with 2i2c See our blog post about our use of CILogon We exposed user activity dashboards in JupyterHub so communities know how many people are using the service # We tend to work with leaders of communities that utilize our service and infrastructure for many others in their network. For example, a teacher with a classroom of students, or a researcher with a global network of collaborators.\nIn these cases, it’s useful to track how many users are actively using a platform over various metrics of time. This can tell you whether your community finds a service useful, and whether this is growing or shrinking.\nWe use Grafana to automatically generate dashboards of activity for all of our community hubs and clusters. However, tracking daily, weekly, and monthly active users was not part of JupyterHub’s core functionality.\nSo, we decided to upstream this functionality into JupyterHub and expose it via the JupyterHub Grafana project . All 2i2c hubs now track daily, weekly, and monthly unique active users. And importantly, anybody else deploying the Zero to JupyterHub for Kubernetes can use this feature now too.\n💡 Learn more\nSee Yuvi’s blog post about this feature .\nWe made our support process more structured with a new support widget # We’ve added a support widget to our service documentation site . This will allow users to provide structured support requests directly to our team, allowing us to triage and respond more quickly.\nHere’s our support button and widget in action:\nOur fancy new support button! We upgraded Kubernetes across all of our AWS clusters # Kubernetes is at the core of our cloud infrastructure and scalability. We use either a shared or a dedicated Kubernetes cluster for each of our community partners, and it is the foundation upon which all of their Jupyter infrastructure rests.\nOne of the biggest challenges with managing an ongoing cloud service is keeping the underlying infrastructure upgraded. This brings in new stability and functionality, but also often involves manual steps and toil. This quarter, we upgraded each of our AWS JupyterHubs to Kubernetes 1.24 and will continue this effort with other providers in the coming quarters.\nWe streamlined our hub uptime checks to be more efficient # The best kinds of failures are ones that your operations team recognizes and solves before any users run into the problem themselves. We use the Google Cloud Platform HTTP uptime checker to run regular uptime checks for each of the community hubs that we use . This allows us to get quick alerts if any of our community hubs is down for some reason.\nWe made several optimizations to this process so that we can more efficiently monitor hub uptime and trigger alerts to our engineering team if action is needed.\nOrganizational updates # We made a number of broader improvements to our team processes and policies, and even got a shout-out from a few community partners!\nWe defined organizational …","date":168264e4,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":168264e4,"objectID":"837ca10f75690da78e1f6c20c1eef6d2","permalink":"https://2i2c.org/blog/2023/2023-q1-update/","publishdate":"2023-04-28T00:00:00Z","relpermalink":"/blog/2023/2023-q1-update/","section":"blog","summary":"It’s a month after the end of Q1 2023, and we’d like to share a belated update about what we were up to in the first quarter of this year (we have good excuses for being late, including new tiny humans, I promise).","tags":[],"title":"Community update Q1 2023: Growing our community partner network and our team","type":"blog"},{"authors":["Georgiana Dolocan"],"categories":["engineering","partnerships"],"content":" About CILogon # CILogon is an open source service provider that allows users to log in against over 4000 various identity providers, including campus identity providers. The available identity providers are members of InCommon , a federation of universities and other organizations that provide single sign-on access to various resources.\nCILogon and 2i2c # For the past year, 2i2c has been successfully using CILogon for more than fifteen of the hubs it manages.\nCurrently, most of the hubs that use it are hubs for communities in education that want to manage their hub access through their own institutional providers.\nWith using a tool like CILogon, we allow hub access to be managed both through the communities’ institutional providers, but also through social providers like GitHub and Google. Because both authentication mechanisms can coexist, there’s no need to provide specific credentials for 2i2c staff in order to have access to the hub. This reduces both the burden on institution’s IT departments, but also the complexity of a hub deployment.\nMoreover, as we migrate away from our current Auth0 setup, the number of hubs using CILogon will further increase in the following year.\nThe setup # The setup that 2i2c uses, is based on two important tools, the CILogon administrative client and the JupyterHub CILogonOAuthenticator.\nThe CILogon administrative client # The 2i2c administrative client provided by CILogon allowed us to automatically manage the CILogon OAuth applications needed for authenticating into the hub.\nFor each hub that uses CILogon, we dynamically create an OAuth client application in CILogon and store the credentials safely, using the script at cilogon_app.py . The script can also used for updating the callback URLs of an existing OAuth application, deleting a CILogon OAuth application when a hub is removed or changes authentication methods, getting details about an existing OAuth application, getting all existing 2i2c CILogon OAuth applications.\nThe JupyterHub CILogonOAuthenticator # For CILogon’s integration with JupyterHub’s authentication workflow, we’re using the CILogonOAuthenticator , which is part of the JupyterHub OAuthenticator project . This is what allows JupyterHub to use common OAuth providers for authentication, and it’s also a base for writing other Authenticators with any OAuth 2.0 provider.\nAs part of this 2i2c integration with the JupyterHub CILogonOAuthenticator some important upstream fixes and enhancements to the oauthenticator were identified and performed. For example, the GHSA-r7v4-jwx9-wx43 vulnerability was reported and fixed, and a migration guide containing a description of the breaking changes that were made, together with a step by step guide for the users on how to update their usage of JupyterHub CILogonOAuthenticator was provided.\nRead more about how CILogon is setup for use at 2i2c from the docs .\nCelebration # Thanks to the 2i2c - CILogon partnership, during this past year we were able to integrate CILogon into 2i2c’s infrastructure and to observe its importance, usefulness and great support for 2i2c and the communities we server.\nWe are now happy to announce that the 2i2c - CILogon partnership has been expanded to another year!\nAcknowledgements: The upstream jupyterhub-oauthenticator project mentioned in this post as being used at 2i2c is a JupyterHub package, kindly developed and maintained by the JupyterHub community and the 2i2c integration described was developed by the 2i2c engineering team . Also, this post was edited by Jim Basney .\n","date":1677196800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1677196800,"objectID":"ddff52adb91f9fcfcb7d4985bc349b33","permalink":"https://2i2c.org/blog/2023/cilogon-integration/","publishdate":"2023-02-24T00:00:00Z","relpermalink":"/blog/2023/cilogon-integration/","section":"blog","summary":"The following is a summary of how CILogon is used at 2i2c, how the integration works and a celebration of the partnership.","tags":[],"title":"CILogon usage at 2i2c","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["brainstorm"],"content":"This is a brainstorm to consider the principles and guidelines that 2i2c should follow in defining its strategy towards open source communities. See our open source policy documentation for the product of this brainstorm.\nOver the past year the 2i2c team has focused its efforts on deploying, configuring, running, and managing cloud infrastructure that supports open source workflows in research and education. We’ve also done a lot of upstream contribution as a part of our work.\nHowever, we have shied away from taking direct funding for direct development work in open source projects. This is for two primary reasons:\nOur focus has been on managing cloud infrastructure, not developing it. We want to facilitate access to open workflows in interactive computing, which is a different skillset and kind of work than creating those tools. While 2i2c is aligned with the interests of open communities, we are still a distinct organization with our own mission and strategy. We want to be conscious that 2i2c team members have more than one hat, and that their 2i2c hat is necessarily not the same thing as their open source hat. As such, we don’t want to leverage our “other hats” to drive resources to 2i2c without being thoughtful about it. In the last year we’ve found that running infrastructure for research and education gives us great visibility into the kinds of things that these communities want to do, and ways to improve the infrastructure. It also means we can potentially be a conduit of resources from those communities into open source development workflows. For example, we recently partnered with GESIS to make improvements in Binder and JupyterHub .\nSo, this post is a brainstorm to identify some of the major considerations that we should take before agreeing to this kind of work. Its goals is to drive policy that streamlines our ability to seek and accept funding for open source work. It tries to answer this question:\nHow can a stakeholder accept funding on behalf of an open source community in a way that is inclusive, equitable, and effective.\nSome assumptions # First off I want to note that this only applies to open source projects that I’d call “Open communities”. For example, those that follow the principles of open scholarly infrastructure . The ideas here don’t apply to open source projects that are run by single organizations or people. You can assume I’m talking about projects that:\nHave inclusive multi-stakeholder governance and operations. Care about having a broad contributor and leadership base, and want to follow best-practices in inclusive and equitable operations. Need funding to drive major new efforts, or to sustain pre-existing maintenance and community management work. Why is this important? In short, because open projects should care about good governance, and about building sustainable and diverse multi-stakeholder communities around their operations and strategy. While it’s easy to ignore these considerations and just bring in money however you can (open source is perpetually under-funded, after all), it’s crucial that we think about how to do so in a way that aligns with the values of open communities, and that doesn’t simply propagate a “rich get richer” dynamic. Ultimately, the unique value of open communities is not in the technology they create, but in the way that they create it.\ntl;dr: An overview of major considerations # After working with several open source projects over the years, there are a few issues that I’ve seen come up again and again. Here’s a quick summary and I’ll note each in more detail below.\nGovernance: funding should follow major decisions, not make them. It should represent the interests of the project rather than those of a single stakeholder or payer. Transparency: stakeholders that accept funding should be transparent in their accounting (the sources of funding, deliverables attached with it, and operational costs), their plans (the work they plan to do and how they want to do it) and in their strategy (the reason they’re applying for funding in the first place, and how the work fits in with their other operations). Accountability: stakeholders that accept funding should be accountable to the open communities that they are supporting. There should be mechanisms for open communities to provide feedback about and influence their operations, ideally in a powerful position like a board seat. Equity: funding should be shared with others in the project, particularly those that need it or that couldn’t get funding on their own. Moreover, people should be paid for their time - if funding requires work from others, they should be compensated somehow. Inclusion: funding opportunities should be shared with others in a project, particularly those from historically disadvantaged communities. Stakeholders with funding “connections” should use them to boost others in the community as partners, not just as contractors Here is a more in-depth discussion of each below. …","date":1673136e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1673136e3,"objectID":"cb1504c087ebf49007ba3a9d79b5b280","permalink":"https://2i2c.org/blog/2023/open-source-funding-principles/","publishdate":"2023-01-08T00:00:00Z","relpermalink":"/blog/2023/open-source-funding-principles/","section":"blog","summary":"This is a brainstorm to consider the principles and guidelines that 2i2c should follow in defining its strategy towards open source communities. See our open source policy documentation for the product of this brainstorm.","tags":["funding","community","open culture","sustainability"],"title":"Principles and considerations for ethically accepting funding for open source","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["brainstorm"],"content":"2022 was a busy year for 2i2c - we not only grew our operations as well as our organization, but also grew our understanding of our mission and where we can have impact. This is a brief reflection on this experience, and an attempt to identify our opportunities for impact and growth in 2023.\nOur major goals in 2022 # We wrapped up 2021 with two major new changes. We had just finished moving fiscal sponsors and had just finished a prototype of our alpha service offerings .\nOur 2x2 matrix of service offerings and prices created at the end of 2021. See the documentation for more details. Our biggest challenge in 2022 was to identify the bottlenecks in this service model, and to begin building the infrastructure to operate and scale it. This included team infrastructure, technical infrastructure, and administrative infrastructure.\nLet’s see what we did to accomplish this goal.\nHighlights from 2022 # In 2022, we thoughtfully grew the number of communities we worked with, and used this to make iterative improvements in our model. As a result, we learned some important things and made significant improvements to our service model and infrastructure. Here are a few highlights.\nWe grew the number of our partner communities # As noted above, we needed to grow the number and diversity of communities we worked with to understand where our model needed to change. At the end of 2022, we now have 43 community partner hubs across 17 clusters (and at least one on AWS, Azure, and Google Cloud). This amounts to roughly ~2,500 active users each week. We also ran more dedicated infrastructure for more than 11 workshops and events.\nWe grew our revenue from community partnerships # One of our goals is to reach self-sustainability without requiring grant funding for most of the communities we serve. In 2022 we built administrative infrastructure to more efficiently recover monthly costs, and were able to bring in funding for our team from community partnerships. Here’s a plot of our monthly non-grant revenue over the last several months:\nOur monthly non-grant revenue over the last several months. June is much larger because we filled a backlog of invoices from previous months that weren’t billed yet. We got grant funding to serve communities in Latin America and Africa # We also learned that some partnerships may require subsidization from a third party, such as historically marginalized communities and those without dedicated resources. To explore sustainable ways to serve these communities, we applied for and received a new grant to serve communities in Latin America and Africa! Here’s the blog post announcing this grant and our open grant narrative from the proposal .\nWe improved our continuous integration and deployment system # Our ability to sustainably grow our service requires being able to technically serve many communities from a relatively small team. We centralized and standardized configuration and operations of many community hubs in one transparent space for all of our partner communities. This allowed us to more easily grow the number of communities we served from one repository. You can read a write-up about these improvements in this blog post .\nWe defined a Shared Responsibility Model # Our goal is to frame each community hub as a partnership with a clear breakdown of responsibility to give communities more agency over the infrastructure and service. The Shared Responsibility Model provides a framework for assigning responsibility for various tasks with our partner communities. See our Shared Responsibility Model docs here .\nWe defined a formal Incident Response process # Cloud infrastructure inevitably degrades over time, and running ongoing services is largely about quickly responding to issues and resolving them quickly. To do so, we need clear processes to follow in order to quickly identify and respond to major incidents in the infrastructure. Our Incident Response process defines formal team roles and alerting mechanisms that are served by PagerDuty , following best-practices in industry. This will make our service more reliable and make our processes more transparent for our partner communities. Here’s our current incident response process .\nWe expanded our service offerings to include community and workflow guidance # We recognized that many communities need more than just infrastructure running in the cloud - they will also benefit from usecase and community guidance. We’re exploring a new range of roles that we could fill, starting with hiring a new team member to help us lead these efforts. Here’s a blog post about the Product and Community Lead .\nWe began a collaboration with GESIS to develop environment building in JupyterHub # This marks our first efforts into development-focused work as opposed to operating cloud infrastructure. We will use this experience to learn how to pair focused development with cloud operations (more on that below). It will also make it more likely that we can implement …","date":1672790400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1672790400,"objectID":"c0e3dbdaffd9239e9fd35b5e05629012","permalink":"https://2i2c.org/blog/2023/2022-year-in-review/","publishdate":"2023-01-04T00:00:00Z","relpermalink":"/blog/2023/2022-year-in-review/","section":"blog","summary":"2022 was a busy year for 2i2c - we not only grew our operations as well as our organization, but also grew our understanding of our mission and where we can have impact.","tags":["year-in-review"],"title":"2022 in review: growing our partner communities and expanding our operations","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["partnerships"],"content":"We are excited to announce that the team and proposal described in this blog post has been awarded funding by the Chan Zuckerberg Initiative !\nThis announcement may be cross-posted on the websites of several collaborating organizations of this grant. Para leer este post en español, vea el blog de MetaDocencia .\nOur goal is to create a collaborative cloud infrastructure service that enables community-based cloud-native workflows in the biosciences. We will promote values of open and inclusive community practices, infrastructure that enables these practices, and a “train the trainers” approach that empowers community leaders to share expertise in cloud infrastructure with others in their communities. Our focus will be on communities in Latin America and Africa, and we hope to learn how this model could be extended to other global communities that are historically marginalized from large-scale scientific infrastructure projects.\n2i2c will be providing cloud infrastructure operation and support for the communities that we partner with in this effort. We will also assist with creating content to teach cloud-native workflows and assist community leaders in learning this content so that they can share these skills with others.\nThis is a collaborative effort between 2i2c , The Carpentries , CSCCE , Invest in Open Infrastructure , MetaDocencia , and Open Life Science . For more detailed information, see the blog post with our full grant narrative .\nWe are hiring # As a part of this effort, we will also hire several new team members! There are currently two job postings open. Here are links for more information in case you are interested:\nCloud infrastructure engineer to join 2i2c’s Site Reliability Engineering team that will operate and support the cloud infrastructure in this project. Programme manager role to join Open Life Science and support this project via project management and operational support. We may be hiring other positions related to this effort, so please stay tuned for more information if you are interested.\nWhere to follow along # If you’d like to follow along with this work, please share your e-mail address in this short form . We’ll send updates as we work out longer-term spaces for communication or documentation.\n💡 Follow our work! Sign up for our mailing list for updates about 2i2c. Send us an e-mail about collaborating or partnering on a project. See our Service Documentation or our Team Compass to learn about our service and organization.\n","date":1671494400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1671494400,"objectID":"26124d90c14d8aa219d01a1a27ef7a9b","permalink":"https://2i2c.org/blog/2022/czi-global-communities-announcement/","publishdate":"2022-12-20T00:00:00Z","relpermalink":"/blog/2022/czi-global-communities-announcement/","section":"blog","summary":"We are excited to announce that the team and proposal described in this blog post has been awarded funding by the Chan Zuckerberg Initiative !\nThis announcement may be cross-posted on the websites of several collaborating organizations of this grant.","tags":[],"title":"New project: Open science cloud infrastructure and training for communities in Latin America and Africa","type":"blog"},{"authors":["Damián Avila","Arnim Bleier","Chris Holdgraf"],"categories":["partnerships"],"content":" Introduction # Mybinder.org enables researchers across the world to replicate computational environments in the cloud. It allows researchers to turn static code into interactive literate coding environments with a click of a button within seconds. The mybinder.org service is powered by BinderHub , an open-source tool developed by the Jupyter Project that many organizations have deployed for their own communities. It does this by _dynamically building _the software environment needed to reproduce a computation (using a tool called repo2docker ), and making this environment available to users.\nBinderHub was developed for use-cases that are temporary and fully open by design. BinderHub sessions are destroyed after a fixed amount of time and there is no persistent storage or authentication. However, many research institutions also need more “standard” service features like authentication and persistent storage.\nOver the past several years, the GESIS Notebooks team made the first steps towards bridging this gap through their Persistent BinderHub implementation. This was a modified and authenticated BinderHub that included persistent storage across sessions. The Persistent BinderHub service was very successful at GESIS and with its partner communities, and the team wishes to build this functionality into the JupyterHub community’s core technology so that these features can be enjoyed for more use-cases and by many communities.\nTo enable this vision, we have partnered with GESIS in cooperation with NFDI4DS (GAN: 460234259), CESSDA , and members of the JMTE project. This collaboration has three primary goals:\nGeneralize the Persistent BinderHub functionality/experience to run on cloud-agnostic infrastructure, so that other stakeholders in NFDI, CESSDA, and the broader scientific community may benefit from this functionality and experience. Upstream this functionality by making contributions into Jupyter community projects, so that it will be maintained and improved by a community moving forward, thus improving its reliability and sustainability. Improve the implementation and user experience around Persistent BinderHub, in order to make it more reliable, scalable, productive, and enjoyable to use. We began this collaboration several months ago, and have focused our efforts on exploring potential implementation pathways for this functionality. We believe that we now have a path forward for this functionality, and this blog post is a brief report of our efforts and future plans as we undertake this effort. See this GitHub Projects Board for issues that implement this effort .\nExploration 1: Adding persistent storage directly into BinderHub # Our initial intention was to incorporate persistent storage and authentication from the GESIS Persistent BinderHub into the BinderHub codebase . We began by holding a series of meetings to discuss technical requirements from our experience in the JupyterHub/BinderHub ecosystem, and also conducted an audit of the Persistent BinderHub codebase . The Persistent BinderHub implementation is a modified Helm Chart that configures a JupyterHub to expose its authentication and persistent storage functionality, overriding the BinderHub default behavior. We were concerned that building this functionality natively into BinderHub would be challenging given that the BinderHub codebase was designed for ephemeral user sessions.\nSo, we decided to take another approach:\nExploration 2: Add dynamic image building to JupyterHub # We realized that there is a way to make this functionality more broadly useful and more maintainable, while still achieving the end-user experience that the GESIS team needed. Instead of modifying BinderHub to incorporate JupyterHub’s storage and authentication features, we would give JupyterHub the ability do dynamically generate user environments using repo2docker .\nThis would give JupyterHub users more flexibility over the environments served by their hub, and expose Binder-style workflows to the “typical” JupyterHub workflow. BinderHub could then be simplified to re-use JupyterHub’s image building functionality as a part of its own service. We also identified a prototype of this functionality in the tljh-repo2docker project that QuantStack had built for the PlasmaBio project . This implementation was seen as successful, and something others in the community had wanted to generalize for some time.\nOur implementation plan # Two phases of implementation # With this alternative implementation route in place, we identified two major steps to accomplish this project:\nBuild a back-end for dynamic environment building. JupyterHub needs to understand how to call repo2docker’s image generation from a Docker-based environment. It needs to expose this ability via APIs that others can build interfaces on top of. **Build a front-end that is user-friendly and accessible. **Once the back-end is functional, we must build a front-end experience that feels familiar to BinderHub users and …","date":1669593600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1669593600,"objectID":"6a55a575b40906e55bc3821000992da8","permalink":"https://2i2c.org/blog/2022/gesis-2i2c-collaboration-update/","publishdate":"2022-11-28T00:00:00Z","relpermalink":"/blog/2022/gesis-2i2c-collaboration-update/","section":"blog","summary":"Introduction # Mybinder.org enables researchers across the world to replicate computational environments in the cloud. It allows researchers to turn static code into interactive literate coding environments with a click of a button within seconds.","tags":[],"title":"GESIS - 2i2c collaborate to build a persistent BinderHub experience","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"We recently completed a progress report for Year 2 of our primary CZI funding grant. This funding covers some core operations of 2i2c as well as engineering capacity to run our cloud infrastructure for JupyterHubs.\nBelow is a link to the 3-page grant narrative that summarizes some of our major progress and milestones from year two:\nhttps://zenodo.org/record/7319289 ","date":1668297600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1668297600,"objectID":"fdb1d1be20547d95ad76ddc8a5154853","permalink":"https://2i2c.org/blog/2022/czi-year2-progress-report/","publishdate":"2022-11-13T00:00:00Z","relpermalink":"/blog/2022/czi-year2-progress-report/","section":"blog","summary":"We recently completed a progress report for Year 2 of our primary CZI funding grant. This funding covers some core operations of 2i2c as well as engineering capacity to run our cloud infrastructure for JupyterHubs.","tags":[],"title":"Grant progress report: CZI Foundational grant year 2","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Quarter 3 of 2022 has wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.\nBelow we’ll provide a brief update about major developments this quarter, broken down by functional areas of 2i2c.\nThese are the main highlights from this quarter - if you’d like to check out more of the work that we’ve done, see:\nAll the PRs we’ve merged in Q3\nAll closed issues in Q3\nCommunity impact # These are a few ways in which we’ve collaborated with communities and demonstrated impact over the last few months.\nNew JupyterHubs for communities. We’ve deployed JupyterHubs for several new partner communities. Here’s a quick list:\nPaleoCube and PaleoHack Hubs infrastructure#1418 NeuroHackademy 2022 infrastructure#1505 Alabama Water Institute CIROH hub infrastructure#1444 OceanHackWeek 2022 infrastructure#1515 COESSING Pangeo-Style Hub infrastructure#1516 Temple University Education Hub infrastructure#1648 Callysto Hub infrastructure#1439 London Interdisciplinary School infrastructure#1485 We also ran hubs for several community events:\nNeuroHackademy: infrastructure#1300 OceanHackWeek 2022 infrastructure#1576 COESSING workshop: infrastructure#1516 Eddy Symposium: infrastructure#467 Allen Institute Summer Workshop on the Dynamic Brain infrastructure#1621 For a recap of one of these events, see our recent blog post on the Jack Eddy symposium .\nIf you are interested in partnering with 2i2c to have your own managed JupyterHub, please contact us at partnerships@2i2c.org. We have a shared cluster on Google Cloud, with plans to deploy one on AWS soon, and dedicated clusters can be run on any major cloud provider. Please see our service documentation for more details.\nOrganization wide updates # These are large-scale organizational and strategic efforts that impact all of 2i2c.\nWe applied for a CZI Grant: In partership with The Carpentries, CSCCE, MetaDocencia, Invest in Open Infrastructure, and OpenLifeScience, we applied for a CZI grant to provide cloud infrastructure services to global communities .\nWe grew our team: We’ve hired two new team members to lead new major efforts with 2i2c. James Munroe will lead efforts around community guidance and product design, and Jim Colliander will lead efforts around partnerships and sustainability. We also updated our Hiring and Candidate Search documentation in the process.\nWe’re refining our strategy: We’ve begun a process of revisiting and refining our strategy after a year of major operations, see our strategic update blog post for more information .\nWe completed the CSCCE community management training. Two of our team members (James and Sarah) both completed a several-week community management course that was offered in partnership with CZI .\nOur team member Sarah began a part-time role as the JupyterHub Community Strategic Lead. Sarah will be leading community strategy efforts within JupyterHub for the next two years thanks to a grant to the JupyterHub team from CZI. Check out this issue to follow our progress .\nService improvements # We made a number of improvements to our cloud infrastructure and the processes around our service. Here’s a brief breakdown:\nWe expanded our shared clusters to new cloud providers and regions. We now have shared clusters already deployed on Google Cloud Platform on us-central1-b and europe-west2.\nWe defined an incident commander process. This will allow us to coordinate and respond to major outages in our cloud infrastructure more efficiently. See our incident response documentation for more information.\nWe improved our cloud usage monitoring infrastructure. We’ve deployed a centralized Grafana Dashboard that aggregates cloud usage across all of our partner communities, and allows us to keep track of any unexpected behavior or outages across them all.\nWhere we’re focusing next # In the final quarter of this year, we’ve decided to focus our efforts on growing capacity across all of the aspects of our team. Now that we have brought on several more partner communities into our Managed JupyterHub Service, it has shown us where we have bottlenecks in our technology, process, and structure. In 2023 we hope to significantly grow the number of communities we work with, and so we must grow our capacity to be able to take on these new partnerships.\nWe aim to accomplish this in a few ways:\nMake technical improvements to our cloud infrastructure that reduces the amount of human labor associated with regular actions. This will make our cloud infrastructure more scalable and reliable. Improve our invoicing and partnership leads pipeline so that we can reduce the amount of administrative toil for ourselves and for the communities we work with in billing and cloud cost pass-through. Refine our organizational strategy and structure so that we are better-able to agree on our most …","date":1665878400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1665878400,"objectID":"034121fa0c6758b2d545cbf6ae5d813c","permalink":"https://2i2c.org/blog/2022/q3-update/","publishdate":"2022-10-16T00:00:00Z","relpermalink":"/blog/2022/q3-update/","section":"blog","summary":"Quarter 3 of 2022 has wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.","tags":[],"title":"Celebrating our progress in Q3 2022","type":"blog"},{"authors":["Damián Avila"],"categories":null,"content":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for an Open Source Infrastructure Engineer that will join our Site Reliability Engineering team and make our cloud infrastructure more reliable, scalable, and efficient. It will help build a future of data-intensive scientific research and democratize the design and access to cloud-based resources for research and education purposes.\nIf you’re interested, learn more about 2i2c at the links below, and more about this job posting on the rest of this page.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $120,000 - $135,000 Location: preferred at the US/Pacific time zone Deadline: We will begin reviewing applications around November 17th, and will accept them on a rolling basis until the position is filled. Major duties\nSite Reliability Engineering\nCloud infrastructure management, operations, and support.\nDevelopment of open source infrastructure for hosted JupyterHub service\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply Who we are # 2i2c is a non-profit organization with a mission to make interactive computing more accessible, scalable, and powerful for research and education: https://2i2c.org/organization/ .\nWe accomplish this mission by providing managed cloud services for interactive computing, by providing development and technical leadership to researchers and educators that utilize this infrastructure for specific communities, and by providing support for open source tools and communities in this ecosystem.\nWe have deep ties to the open source community, and have been leaders and core contributors across dozens of projects - in particular in the Jupyter ecosystem. We also have deep ties to research and education - our team has spent years deploying infrastructure for universities, community colleges, and research teams, and now we’re bringing this experience to a wider audience with 2i2c.\nWe believe strongly in communities that are inclusive, transparent, equitable, effective, and diverse, especially 2i2c itself. We believe that our values should permeate everything about 2i2c, including the work we do, the communities we serve, and our own organizational culture.\n2i2c is a fiscally sponsored project of Code for Science and Society , a registered US 501(c)(3) nonprofit corporation.\nWhat you’ll do # Ensure the reliable operation of the 2i2c infrastructure (leveraging production-ready cloud-based tools such as JupyterHub, BinderHub and Dask). Address support issues Explore emerging technologies in the Cloud / DevOps space, design and implement cloud computing architecture in partnership with our team. Participate in upstream open source communities we rely on (such as JupyterHub, BinderHub, Dask, etc) in partnership with the established leaders of those communities and collaborate with the Community Lead in the education and outreach around cloud computing. Work with a distributed and global team - team members are given a lot of autonomy, and expected to be proactive at communicating with one another and working with others to allocate effort that will maximize our impact. Essential requirements # Experience deploying applications on cloud infrastructure. Experience deploying and developing with Linux container-based technologies, such as Docker and Kubernetes. Experience with continuous integration services (e.g. Circle CI, GitHub workflows). Experience developing tools in a general purpose programming language (eg. Python). Experience collaborating and coordinating work via online platforms, such as GitHub, GitLab, or BitBucket, and distributed revision control. Experience working with distributed service teams that use asynchronous methods of communication Desirable requirements # Experience with major cloud providers. Experience in programming and software engineering with a track record of leadership in open, collaborative projects with broad community adoption. Experience working on geographically distributed open-source projects. Experience with the Jupyter ecosystem and other tools for interactive computing. Evidence of existing connections and relationships in the worldwide ecosystem of open source software for data-intensive research and ability to establish new ones. Experience with common data science methods, platforms, workflows, and infrastructures; with data management systems, practices, and standards; and the capacity to gain familiarity with new related topics. Experience engaging with highly technical researchers across a variety of methodological fields, research domains, and computational platforms. Experience building and maintaining continuous deployment pipelines. Interpersonal skills to work with researchers and …","date":1665705600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1665705600,"objectID":"fadeab2639f3679bd21677cc03d303a3","permalink":"https://2i2c.org/jobs/2022/open-source-infrastructure-engineer/","publishdate":"2022-10-14T00:00:00Z","relpermalink":"/jobs/2022/open-source-infrastructure-engineer/","section":"jobs","summary":"2i2c manages, supports, and builds community-centric infrastructure for interactive computing in the cloud with partner communities in research and education.\nWe’re looking for an Open Source Infrastructure Engineer that will join our Site Reliability Engineering team and make our cloud infrastructure more reliable, scalable, and efficient.","tags":null,"title":"Open Source Infrastructure Engineer: Site Reliability Engineering and Cloud Infrastructure","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":["brainstorm"],"content":"This post is an exploration of 2i2c’s current strategy and direction after a year of major operations. It is a brainstorm from the Executive Director, shared as a blog post to invite feedback and provide transparency into our current thinking. Its goal is to explore the context of 2i2c’s stakeholders and their needs, and identify an opportunity and plan for having a positive impact with these communities. It is not a concrete proposal but a snapshot of thinking in time meant to trigger reflection. Over time we will incorporate some of these ideas into our Team Compass .\nWhen we founded 2i2c, we largely did so from the “bottom up” - we identified several patterns around hosted infrastructure that were useful at UC Berkeley , Pangeo , and similar communities, and we wished to make them more generalized, accessible, and scalable.\nWe defined our mission as the following:\nOur mission is to make research and education more impactful, accessible, and delightful by developing, operating, and supporting infrastructure for interactive computing.\nAnd a description about our immediate activities to make things a bit more concrete:\n2i2c designs, develops, and operates JupyterHubs in the cloud for communities of practice in research \u0026amp; education. It builds and supports open source infrastructure that serves these communities.\nAround a year ago we began our pilot JupyterHubs project to learn more about our biggest challenges and opportunities in making interactive computing more accessible and useful for research and education. While both of these statements are still accurate, over the past year we’ve also learned more about the value that 2i2c provides. This post is an exploration of how these statements and our strategy may evolve in the near future.\nWhat did we miss with our original strategy? # In short: it is too-focused on actions rather than impact.\nWhile running JupyterHubs is a key part of what 2i2c does, it is a means to an end rather than our end-goal. Infrastructure is only useful if it changes workflows in a way that aligns with the goals and values that we wish to achieve. We’ve historically defined these in a few scattered places. For example, here are the values listed on our website:\n2i2c values fairness and justice as requirements for successful communities. 2i2c values learning and discovery for all people. 2i2c values collaborating and connecting to foster environments for learning and discovery. However, it is difficult to tie our operations directly to values and goals without making them concrete, and without defining a plan that ties them to our work.\nThrough our JupyterHubs pilot, we’ve learned how our actions-focused approach was missing some important aspects of these broader goals. For example, we came to understand that a big part of 2i2c’s value isn’t just providing a JupyterHub, it is de-risking cloud native workflows for communities that are inherently skeptical of what cloud infrastructure offers. Doing this entails many things: teaching, making decisions on behalf of others, supporting and answering questions, building trust, and yes, managing infrastructure.\nRefining our strategy # With this in mind, we’d like to make our strategy more clearly-defined and tied to our operational choices. Here are a few ways we’d like to do this:\nDefine our organization’s values and vision for the impact we wish to have. Define the key stakeholder communities that we wish to serve, the context of tools and services that are relevant to these stakeholders, and the assumptions we’re making. Define the problems these stakeholders have, the ways in which their current workflow could be improved, and the opportunity to help them. Describe our strategy to positively impact these stakeholders with our work. Define a collection of goals and objectives to carry out this strategy in the near-term. The rest of this post will take a crack at answering a few of these questions. It is intentionally messy, and meant both as a public snapshot of my thinking at this moment, and fodder for discussion and more specific proposals in the future.\nContext: Our key stakeholders and the impact we wish to have # 2i2c’s key stakeholders are communities of practice that are dedicated to creating and sharing public knowledge. These are primarily made up of researchers and educators in the global community.\nFor these stakeholders, we wish to catalyze and support a transformation in their data workflows that allows them to be more collaborative, inclusive, efficient, and powerful in the impact they wish to have.\nAssumptions we make about our stakeholders # There are a few unique things about these communities that are important for us:\nResearchers and educators see their job as creating and sharing knowledge with a heterogeneous and global community. They can’t make many assumptions about the organizational context or resources of this community, or their work will become inaccessible to others. They work at vertically-oriented …","date":1665273600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1665273600,"objectID":"6f97410cb47b43db748265b2c83455a3","permalink":"https://2i2c.org/blog/2022/strategic-update/","publishdate":"2022-10-09T00:00:00Z","relpermalink":"/blog/2022/strategic-update/","section":"blog","summary":"This post is an exploration of 2i2c’s current strategy and direction after a year of major operations. It is a brainstorm from the Executive Director, shared as a blog post to invite feedback and provide transparency into our current thinking.","tags":[],"title":"One year later: an update of 2i2c's mission, strategy, and impact","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["partnerships"],"content":"We recently submitted a grant to Chan Zuckerberg Initiative and wish to share some details about it as well as the grant narrative for others to read and re-use.\nGo to Zenodo record Read on for a quick overview of the proposal.\nCollaborators # This grant is a collaboration between several leading organizations in open infrastructure, community, and global leadership:\n2i2c The Carpentries Center for Scientific Collaboration and Community Engagement Invest in Open Infrastructure MetaDocencia Open Life Science Problem statement # Cloud infrastructure is a powerful way to broaden access to workflows and infrastructure across the globe. However, it is also inaccessible to many for a variety of reasons:\nThere is a large, diverse, and messy ecosystem of open source tools to facilitate cloud infrastructure. Most communities don’t already have skills in utilizing cloud workflows. Running infrastructure in the cloud takes dedicated time and expertise that many communities lack. Many communities do not have organized communities of practice around cloud infrastructure. These issues are true for most scientific communities, but they are exacerbated in countries that are often marginalized in the global scientific community.\nOur proposed work # For this reason, our goal in this grant is to provide human and technical services to facilitate learning and knowledge transfer of cloud workflows for communities in Latin America and Africa.\nIt defines four major areas of collaboration:\nCloud infrastructure management - to facilitate access to cloud resources via managed cloud services that integrate open source tools. Application guidance and training - to provide community leaders with the skills to utilize this infrastructure for their needs. This includes language-localized content and training materials. Training for trainers - to provide community leaders with skills to share these workflows with others in their communities. Community leadership and management - to provide community leaders with skills to sustain and grow healthy communities of practice. If this proposal is funded, over the course of two years the team will provide a combination of the services described above for communities in Latin America and Africa, with the goal of understanding how such services can be most useful for these communities, how we can structure them to provide community representation in the direction of these services, and how we can sustain and scale this model of community-focused services for a global community.\nImportantly, we wish to do this work in a way that centers the communities we work with as co-leaders and collaborators in these services. We will explore ways to run these services and workshops so that they are transparent, inclusive, and give agency to the communities they support. Ultimately, we hope that this can be an extensible model for many more communities in the future.\nIf you’re interested in this work, would like to discuss its ideas, or think something similar might be useful for your community, please reach out!\nSend us an email ","date":1661644800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1661644800,"objectID":"5ccaad99757bb2ca2ec3362260d77d89","permalink":"https://2i2c.org/blog/2022/czi-global-communities-proposal/","publishdate":"2022-08-28T00:00:00Z","relpermalink":"/blog/2022/czi-global-communities-proposal/","section":"blog","summary":"We recently submitted a grant to Chan Zuckerberg Initiative and wish to share some details about it as well as the grant narrative for others to read and re-use.\nGo to Zenodo record Read on for a quick overview of the proposal.","tags":[],"title":"Open grant narrative: A Collaborative Interactive Computing Service Model for Global Communities","type":"blog"},{"authors":["James Colliander"],"categories":["community"],"content":" Reflections on the Jack Eddy Symposium # 2i2c supported and participated in the 3rd Eddy Cross Disciplinary Symposium held recently in Vail Colorado. The event was hosted by the Cooperative Programs for the Advancement of Earth System Science ( CPAESS ) team at the University Corporation for Atmospheric Research ( UCAR ) with support from NASA.\nContext # The Symposium was framed by the interesting and interdisciplinary scientific career of the late Jack Eddy . Eddy’s legacy was highlighted and his influence has been extended by dynamic leadership from NASA Program Officer Madhulika Guhathakurta (Lika) . Lika helped launch and has sustained NASA’s Living with a Star (LWS) program over the past two decades. Prior to LWS, NASA had a variety of siloed efforts focused on near-Sun and near-Earth behavior. The LWS program led to an integration of these efforts under “system science” or “systems engineering” approaches and an expressed desired to connect LWS research activities with impacts on Earth (society, biology, culture, etc.). The program has expanded to include explorations of similar questions arising around other planets in our solar system and the recently discovered collection of exoplanets. Scientists from diverse disciplines (plasma physics, stellar evolution, atmospheric chemistry, space weather, planetary science,…) work together on “cross disciplinary” research that helps us understand our lives near our star.\nThe Symposium focused on three disciplinary areas (Exoplanets; Sun-Climate and Star-Climate interactions; Risk and resilience of space weather) unified under the cross-cutting thread of open science. Frequent references were made to the upcoming 2023 Year of Open Science and NASA’s Transform to Open Science (TOPS) mission . Symposium attendees listened to talks surveying the four areas in the morning and participated in hackathon-style breakout projects during the afternoons. Work on the projects launched at the Eddy Symposium continues . The space weather group is investigating ways to make the power grid more resilient. The Sun-climate group is exploring plans to establish an institute focused on Sun-climate interactions and improve connections between climate and heliophysics research communities. The exoplanets team is developing tools to programmatically compare Sun-Earth and star-exoplanet interactions.\n2i2c’s role # 2i2c, with input from Symposium CoChair’s Dan Marsh and Ryan McGranaghan , rapidly deployed a cloud-hosted JupyterHub for use during the event. The hub provided a shared space for participants to explore data, run analyses, and collaborate with one another using modern tools including Zarr, Xarray and Dask Gateway. Access to the interactive computing platform was granted to any member of the Symposium’s GitHub organization . The work to set up that hub, openly chronicled in this GitHub issue ( 2i2c-org/infrastructure#1329 ), included swapping out a Pangeo-style software environment for a heliophysics-specific resource developed by HelioCloud with special thanks to Brian Thomas !\n2i2c co-founder Fernando Pérez gave a talk on how he is “living la vida nube” . Fernando described the ways he, research collaborators, and students are using the Jupyter ecosystem. Diverse and curated tools in Jupyter hubs for the Jupyter Meets the Earth Project and Berkeley’s data science programs were highlighted. The talk showcased how these tools have been integrated to support individuals and communities of practice in data-driven research. In response to requests from the organizers and participants, Fernando gave a demonstration on how to use the hub 2i2c set up for the Symposium and an introduction to version control using git.\n2i2c co-founder Jim Colliander gave a talk titled Governing the Science Commons . Three key points from Jim’s talk were: the virtue that should guide the improvements to the scientific enterprise is intellectual generosity; implementation of intellectual generosity into science requires commons-based governance; the convergence of open source tools that support data-intensive collaborative research and learning (as showcased by Fernando) and agency interest ( NASA TOPS , UNESCO ) in open science is an inflection point for global change. The talk ended with a call to action for the diverse communities represented at the Symposium to improve the ways we do science.\nThings we learned # Our experience with the Symposium taught 2i2c a few things.\nWe learned that our engineering team can rapidly deploy interactive computing resources to support a research and education community. Along the way, we confirmed what we’ve been learning from Pangeo and the neuroscience communities: flexible methods to customize the software environment are necessary. We confirmed that our developing shared responsibility model , enabling domain-specific experts to provide curated toolchains for their communities while leveraging 2i2c’s infrastructure expertise, is the right approach.\nWe …","date":1657756800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1657756800,"objectID":"5d36d9cc84a68609f47fb32b7b8d0f39","permalink":"https://2i2c.org/blog/2022/eddy-symposium-report/","publishdate":"2022-07-14T00:00:00Z","relpermalink":"/blog/2022/eddy-symposium-report/","section":"blog","summary":"Reflections on the Jack Eddy Symposium # 2i2c supported and participated in the 3rd Eddy Cross Disciplinary Symposium held recently in Vail Colorado. The event was hosted by the Cooperative Programs for the Advancement of Earth System Science ( CPAESS ) team at the University Corporation for Atmospheric Research ( UCAR ) with support from NASA.","tags":[],"title":"Reflections on the Jack Eddy Symposium","type":"blog"},{"authors":["Sarah Gibson"],"categories":["engineering"],"content":"2i2c manages the configuration and deployment of multiple Kubernetes clusters and JupyterHubs from a single open infrastructure repository . This is a challenging problem, as it requires us to centralize information about a number of independent cloud services, and deploy them in an efficient and reliable manner. Our initial attempt at this had a number of inefficiencies, and we recently completed an overhaul of its configuration and deployment infrastructure.\nThis post is a short description of what we did and the benefit that it had. It covers the technical details and provides links to more information about our deployment setup. We hope that it helps other organizations make similar improvements to their own infrastructure.\nOur problem # 2i2c’s problem is similar to that of many large organizations that have independent sub-communities within them. We must centralize the operation and configuration of JupyterHubs in order to boost our efficiency in developing and operating them, but must also treat these hubs independently because their user communities are not necessarily related, and because we want communities to be able to replicate their infrastructure on their own .\nA year ago, we built the first version of our deployment infrastructure at github.com/2i2c-org/infrastructure . Over the last year of operation, we identified a number of major shortcomings:\nWithin a Kubernetes cluster, we deployed hubs sequentially, not in parallel. This grew out of a common practice of Canary deployments that allowed us to test changes on a staging hub before rolling them out to a production hub. We used a single configuration file for all hubs within a cluster, which led to confusion and difficulty in identifying a hub-specific configuration. Moreover, any change to a hub within a cluster caused a re-deploy of all hubs on that cluster. This is because we did not know whether a given change touched cluster-wide configuration or hub-specific configuration. Our goal # So, we spent several weeks discussing a plan to resolve these major problems - here were our goals:\nWe should be able to upgrade a specific hub alone, by inspecting which configuration files have been added or modified. Production hubs should be upgraded in parallel when they are effectively run independently. We should use staging hubs as “canary” deployments and not continue upgrading production hubs if the staging hub fails. An overview of our changes # To accomplish this, we needed to identify which hub required an upgrade based on file additions/modifications. This took a lot of discussion and iteration on design, and so we share it below in the hopes that it is helpful to others!\nImprovements to our code and structure # We made a few major changes to the infrastructure repository to facilitate the deployment logic described above. Here are the major changes we implemented:\nWe separated each hub’s configuration into its own file, or set of files. For example, here is 2i2c’s staging hub configuration . We created a separate cluster.yaml file that holds the canonical list of hubs deployed to that cluster and the configuration file(s) associated with each one. For example, here is 2i2c’s GKE cluster configuration , which contains a reference to the previously mentioned staging hub . We updated our deployer module to do the following things: Inspect the list of files modified in a Pull Request. From this list, calculate the name of a hub that required an upgrade, and the name of its respective cluster. Trigger a GitHub Actions workflow that deploys changes in parallel for each cluster/hub pair. In addition to these structural and code changes, we also developed new GitHub Actions workflows that control the entire process.\nA GitHub Actions workflow for upgrading our JupyterHubs # We defined a new GitHub Actions workflow that carries out the logic described above. These are all defined in this deploy-hubs.yaml configuration file . Here are the major jobs in this workflow, and what each does:\ngenerate-jobs: Generate a list of clusters/hubs that must be upgraded, given the files that are changed in a Pull Request.\nEvaluate an input list of added/modified files in a PR Decide if the added/modified files warrant an upgrade of a hub Generate a list of hubs and clusters that require upgrades, and some extra details: Does the support chart that is deployed to the cluster also need an upgrade? Does a staging hub on this cluster require an upgrade? This produced two outputs to be used in subsequent steps:\nA human-readable table including information on why a given deployment requires an upgrade (using the excellent Rich library ). JSON outputs that can be interpreted by GitHub Actions as sets of matrix jobs to run. Our staging and support hub job matrix tells GitHub Actions to deploy staging and support upgrades that act as canaries and stop production deploys if they fail. upgrade-support-and-staging: Update the support and staging Helm charts on each cluster. …","date":1650326400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1650326400,"objectID":"91264ab8963bcd7c30384d1bd6f92b1a","permalink":"https://2i2c.org/blog/2022/ci-cd-improvements/","publishdate":"2022-04-19T00:00:00Z","relpermalink":"/blog/2022/ci-cd-improvements/","section":"blog","summary":"2i2c manages the configuration and deployment of multiple Kubernetes clusters and JupyterHubs from a single open infrastructure repository . This is a challenging problem, as it requires us to centralize information about a number of independent cloud services, and deploy them in an efficient and reliable manner.","tags":[],"title":"Tech update: Multiple JupyterHubs, multiple clusters, one repository.","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":"Quarter 1 of 2022 just wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.\nThese are the main highlights from this quarter - if you’d like to check out more of the work that we’ve done, see:\nAll the PRs we’ve merged in Q1 All closed issues in Q1 Infrastructure improvements # This quarter we did a deep dive into a number of core infrastructure improvements for our Managed JupyterHubs Service . Here are a few highlights:\nInfrastructure reliability and efficiency. We improved the resiliency, reliability, and efficiency of our deployment infrastructure . For example, we refactored our hub configuration so that each community is better-able to track it, we implemented validation steps to ensure that we don’t accidentally push incorrect config to the hubs, and we’ve significantly improved our CI/CD pipeline to push deployments out to our hubs more efficiently. Automatic deployments to commercial cloud. With the ICESat hackweek as a test-case for AWS, we’ve finished automating the deployment of clusters and hubs to each major commercial cloud. (there’s not a specific issue for this as it has been a multi-month effort over many PRs and issues!) CILogon authentication. CILogon is a non-profit organization that provides “single-sign on” authentication services for the same communities that 2i2c serves. We’ve partnered with them to prototype using CILogon for 2i2c’s hubs , which should make it much easier for communities to user their own institutional sign-ons. Communities we’ve served and lessons learned # As described in our Managed Hub Services strategy , our goals for this phase of our organization are to balance serving communities of practice and learning where we can improve our infrastructure and practices. With that in mind, here are a few highlights of communities we’ve served, and what we’ve learned from it:\nWe grew a hub for the University of Toronto to around 4000 monthly users. This has taught us a lot about where our support and operations can and cannot scale, and where we have gaps in our sustainability / pricing model. We deployed CILogon on a hub for a class at Australian National University . This gives us an opportunity to work out any UX issues and improvements to be made before a deeper CILogon integration. We deployed a dedicated database per user for a databases course at UT Austin . This is helping us learn more about how to pair slightly more customized per-user infrastructure with our standard hub setups, as well as how our Right to Replicate model could be followed for more complex setups like a database. We ran an event hub for the ICESat2 HackWeek at the University of Washington. This helped refine our infrastructure and expertise with AWS, as well as improved our event “ready mode” practices. We deployed a new hub for the LEAP project . This has given us an opportunity to prototype new processes for pass-through cloud costs to simplify our deployments. Organizational improvements\nBeyond our technical and community impact work, we’ve made a lot of significant organizational improvements as well.\nWe designed a new role in Product and Community Management . We’re excited for this new hire to spearhead efforts in guiding and developing relationships with the communities we serve, as well as guiding and collaborating with our engineering team in developing our services. We designed a new Project Manager role . Our engineering team had been operating as a largely autonomous and independent group, but we’ve realized that we would benefit from someone to help coordinate our actions and plans, especially as we balance more operations/support issues in addition to new development. This new role is an experiment at growing this capacity within our team, in the hopes that we can dedicate a team member to it in the future. What’s next # We are still working out our major priorities for the oncoming quarter, but have a few major projects in the works that we’re hopeful to make progress on quickly. Here are a few major examples:\nImprove our process and operations around supporting our users. We are discussing first- and second-line support processes to make our team more responsive and effective at resolving incidents. Improve our invoicing and contracting process. We are discussing how to reduce toil associated with invoicing in order to make this practice more reliable and efficient, along with our fiscal sponsor Code for Science and Society . Improving our reporting and monitoring infrastructure. We’d like to boost our ability to monitor activity on each of our hubs in order to identify when something abnormal is happening and get ahead of any potential problems (e.g., to avoid unintentionally large cloud bills). We’d also like to improve our usage reporting to more create more accurate cloud bills …","date":1649030400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1649030400,"objectID":"454c4a8fe4f63e69b69c0d288694eaad","permalink":"https://2i2c.org/blog/2022/q1-update/","publishdate":"2022-04-04T00:00:00Z","relpermalink":"/blog/2022/q1-update/","section":"blog","summary":"Quarter 1 of 2022 just wrapped up, and the 2i2c team has been busy making improvements across our infrastructure, organization, and operations. This is a quick post to celebrate the work we’ve done over the past three months, and to briefly share what we’re working on next.","tags":[],"title":"Celebrating our progress in Q1 2022","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["people"],"content":"Yesterday we had a quick “drop-in” session to take questions about 2i2c’s job posting for a Product and Community Lead . We spent the hour discussing a number of questions that others had about the position. Below is a short overview of the questions and some responses, for those who were not able to attend. These responses are a bit rough, since they are mostly off-the-cuff based on the questions asked.\nUpdate 2022-03-24: We’ve added extra questions and answers below from our latest drop-in meeting.\nWhat does success look like in the short and long term? # This is an important question, with a few different kinds of answers.\nAs noted, this is the first hire of its kind inside of 2i2c, and it should bring a strategic and organization-building eye to the work that it does. To some extent, this role will be tasked with coming up with their own answers to these questions. This person should build a near- and long-term strategy for how Product and Community Engagement should evolve to be most-effective in accomplishing our mission. This will also mean defining goals and a strategy to meet these goals over time.\nWith that in mind, here are a few ideas we have in mind for goals that will drive this role:\n6 month goals for this role might be:\nBecome familiar with 2i2c’s organization, culture, mission, and team. Define an early strategy for how you’d like to incorporate Product and Community engagement into 2i2c’s operations, and set some Objectives or Key Results that we should use to measure success. This should include a plan for the two major objectives of this role: guiding and connecting with the communities we serve, and building design and planning processes that bring this perspective into our engineering and services. A few iterations on the execution of this strategy, with some demonstration of impact as well as some documented lessons learned. 2 year goals for this role might be:\nAn organizational strategy and structure has been created, defining the various roles that make up this division of 2i2c and their functions. Clearly defined team processes for major programs efforts that this role oversees, as well as interconnections with other major divisions of 2i2c (e.g. engineering or sales). For example, a framework for training community leaders and mechanisms or platforms for communication and engagement with our communities. A team exists that carries out these efforts, led by the Product and Community Lead. Clear demonstrated impact in the communities we serve, according to the OKRs and goals that have been set in this division. How does 2i2c provide mentorship/onboarding? # You can find our onboarding process in our Team Compass . This roughly comes down to choosing an “Onboarding Champion” for the new team member, to help walk them through our team processes and get them access to the right information and accounts. However, 2i2c is quite young, so has only had a few iterations in onboarding new team members. We look forward to improving this process further via this new hire.\nWhat are the largest challenges that someone might face in their first year in this position? # The largest challenge is largely related to ambiguity and fluidity of this role, due to the fact that 2i2c is small and relatively young. As noted above, this position will have a great deal of autonomy, and will be expected to show leadership in defining the nature of this work within 2i2c. This can either be exciting or scary depending on your comfort level with ambiguity! We recognize that it is an anti-pattern to have roles without clearly-defined measures of success, so we’re committed to defining this quickly in partnership with the new hire. However, we don’t want to be overly-prescriptive in this role, because we want it to have space to lead these efforts within 2i2c.\nHow do you hope to protect the “business” aspects of 2i2c, if all the tech is open source? # 2i2c is to some extent committing to a limiting business model: by respecting the Right to Replicate , we encourage other organizations to perform the exact same kinds of services that 2i2c offers. However, we believe this is in-line with 2i2c’s mission, and would consider this to be a measure of impact rather than a sustainability problem. In short: our goal is not to become a tech giant or start-up unicorn, we want to sustain a team with competitive pay, and we want to scale as there is more opportunity to serve new communities. We believe that the complexity of integrating tools and managing cloud services means that there will always be enough of an opportunity to bring in ample funding for this model. We also hope that our mission-driven nature and focus on research and education will bring in new kinds of funding opportunities that can sustain 2i2c and its mission.\nHow would applying the “1000 true fans” approach work in terms of advocacy? # The 1000 true fans approach suggests that it is enough to leverage the support of “1000 true fans” to sustain a product or …","date":1647907200,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1647907200,"objectID":"a610fec4ca5e5927b338d93661fa3039","permalink":"https://2i2c.org/blog/2022/product-community-lead-drop-in-notes/","publishdate":"2022-03-22T00:00:00Z","relpermalink":"/blog/2022/product-community-lead-drop-in-notes/","section":"blog","summary":"Yesterday we had a quick “drop-in” session to take questions about 2i2c’s job posting for a Product and Community Lead . We spent the hour discussing a number of questions that others had about the position.","tags":[],"title":"Notes from our drop-in meeting about the Product and Community Lead role","type":"blog"},{"authors":null,"categories":null,"content":"We are looking for a Product and Community Lead to ensure that the communities that 2i2c serves are empowered to have the most impact with our infrastructure.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $120,000 - $130,000 Location: anywhere (prefer a time zone between US/Pacific and Central European) Deadline: We will begin reviewing applications around March 21st, and will accept them on a rolling basis until the position is filled. Major duties\nGuide and learn from our user communities.\nGuide our team to build services and infrastructure for these communities\nLead strategic efforts to grow this work within 2i2c.\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply Position summary # This role will guide and empower the communities that we serve, learn from them, and bring their perspective to guide our service and product development. It is similar to a mixture of product management and community and developer advocacy in a tech firm, but adjusted for research, education, and open source contexts. It is also similar to a Research Applications Manager , but with a focus on using and developing infrastructure.\nThe skills required are a combination of communication, teaching, learning, service design and delivery, and technical acumen. The person that fills this role should feel comfortable learning and sharing ideas, empowering and guiding others, and communicating clearly and collaboratively with a variety of stakeholders including end-users and engineers.\nThis is a leadership role for a strategy-minded practitioner. 2i2c is a young organization, and this role will have a large degree of autonomy and flexibility. We have defined the starting point, but we seek someone who can bring a strategic eye to this position. Over time we hope that the role will grow to define and lead this style of work within 2i2c more broadly.\nWhat you’ll do # This role is a combination of connecting, guiding, leading, learning, communicating, and empowering stakeholders in the communities we serve, as well as the 2i2c engineering team. Here are some key focus areas with core responsibilities under each:\nGuiding and learning from communities we serve # Our users are often not “power-users” with Jupyter, open source workflows, or cloud-native workflows. This role should work with users of these communities to guide them in using our infrastructure for maximal impact. Below are a few example responsibilities:\nUnderstand the goals and needs of the communities we serve, as well as the major pain points and problems that they have. This understanding may not be directly communicated and will be gained through active observation. For example:\nCreate and engage in spaces for sharing information with users. For example, online forums and live community discussions. Engage in community-specific spaces. This role may monitor and participate in community spaces in either research or education (e.g., the Pangeo forum , the Jupyter forum , or forums for education communities) to track relevant conversation and provide guidance as-needed. Guide communities and their leaders for the use-cases that 2i2c wishes to enable, and how our infrastructure (Jupyter, JupyterHub, open source tools, etc) can be used to have the most impact. For example:\nDevelop user-facing materials (documentation, workshops, talks, etc) that demonstrate the basic use-cases that we support, and the best ways that the infrastructure can be used to accomplish community goals. For example “Teaching with Jupyter” or “An Introduction to Scalable Computing with Dask.” Provide one-on-one or group guidance to our user communities (particularly leaders in those communities) with the goal of transferring knowledge that they can then share within their peers. Foster deeper external relationships and engagements with key communities of practice and partners that are important for 2i2c’s strategy, such as the Pangeo Project (which is a key stakeholder for this role).\nEngage with potential communities and stakeholders, with a focus on demonstrating the use-cases we hope to support and generating new service contracts with these communities. Communicate externally to demonstrate impact. For example, by participating in meetings, conferences, and other events where we have an opportunity to highlight the work that 2i2c does. Interact extensively with open source communities that underlie our infrastructure, potentially serving in leadership roles and doing significant work to support these communities. There will be a particular focus on the Jupyter and PyData ecosystems. Guide product and service design and implementation # This role should understand the perspectives of our users and the use-cases we wish to enable, and bring this perspective to guide the evolution of our services and …","date":1646006400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1646006400,"objectID":"2ebe6e02e323565512fb237dc54713cb","permalink":"https://2i2c.org/jobs/2022/product-community-lead/","publishdate":"2022-02-28T00:00:00Z","relpermalink":"/jobs/2022/product-community-lead/","section":"jobs","summary":"We are looking for a Product and Community Lead to ensure that the communities that 2i2c serves are empowered to have the most impact with our infrastructure.\n❌❌❌\nThis posting is closed to new applications.","tags":null,"title":"Product and Community Lead","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":["people"],"content":"The 2i2c team is looking to hire a new team member! We are seeking a product and community lead with the following two goals:\nEmpower the communities we serve to have impact with our infrastructure. Guide our development and service design to reflect the needs of our users. This role will work alongside our engineering team as a partner, and will serve as a high-bandwidth interface to the communities that we work with.\nYou can find a link to the full job posting below, the rest of this post is a short rationale for this role, and how we hope it will fit within 2i2c’s team and strategy.\nLearn more and apply Why a new role? # When 2i2c began a year ago, we hired a team of engineers that had experience in cloud infrastructure, Jupyter, and open source ecosystems. In that time, we’ve built out the infrastructure foundation for scalable interactive computing environments that are customizable for the community, and respects their Right to Replicate .\nHowever, solely providing infrastructure is not enough. Working with the modern open source stack, using the cloud to its advantage, and bringing these tools into specific domains requires a lot of extra experience and expertise. We believe that 2i2c is in a good position to provide guidance and support to leaders in the communities that we serve, allowing them to get up-to-speed with the infrastructure more effectively so that they can have an impact.\nMoreover, we’ve also learned that it’s crucial to develop infrastructure in collaboration with the communities that we’re serving. A team of engineers tends to focus on code and infrastructure, and having a role that focuses on connecting with communities will give them an excellent perspective on what those communities need.\nWe hope that this role will combine these two aspects to create a culture of learning, sharing, and guiding between 2i2c’s team and the communities that we work with.\nWhat are similar roles? # We tried to find similar roles in the private and non-profit sector, but couldn’t find anything that was a perfect fit. However, there were a few close matches.\nThis role is kind-of like a product manager - their job is to understand the communities that we work with, and to use this to help us make decisions about what to build, how to present it, and how to engage with stakeholders. They will need to help us prioritize the work that is most impactful for our mission, and help us navigate trade-offs in the evolution of our services.\nThis role is also kind-of like a customer success manager or a developer advocate - they will guide and teach those in the communities we serve - particularly community leaders that go on to teach others - how to use our infrastructure most-effectively.\nIn fact, the closest role we could find is a relatively new one: the Research Applications Manager . This is a role that has been pioneered by the Turing Institute, and is similarly described as a connector that brings together many perspectives and encourages a participatory, team-based approach to research.\nHowever, the reality is that the person in this role will ultimately get to shape the nature of their work within 2i2c. As a young organization, there is a lot of flexibility for creativity and experimentation in bringing new skillsets into our organization. We hope that the person who fills this role will be excited about growing a culture of team-based approaches to our engineering and collaborations, and to share this culture with the communities that we serve.\nWhat’s next? # Effective today we are opening up applications for this position, and will begin reviewing them in 2 weeks on a rolling basis until the position is filled. For a more formal job posting, and instructions to apply, click the link below!\nLearn more and apply ","date":1645488e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1645488e3,"objectID":"9a790962fde35556190c78d24dace070","permalink":"https://2i2c.org/blog/2022/job-product-community-lead/","publishdate":"2022-02-22T00:00:00Z","relpermalink":"/blog/2022/job-product-community-lead/","section":"blog","summary":"The 2i2c team is looking to hire a new team member! We are seeking a product and community lead with the following two goals:\nEmpower the communities we serve to have impact with our infrastructure.","tags":[],"title":"New job posting: Product and Community Lead.","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"Now that 2021 has come to an end, this marks the end of 2i2c’s first year of operations. In this year we have grown, experimented, and accomplished a lot - we have also faced challenges and learned as a team. Our primary goal in 2021 was to build a strong foundation for 2i2c.\nTo reflect on our work thus far, we’re writing three blog posts that describe progress in major areas of work towards this foundation for 2i2c. These three areas are:\nCreating services for use-cases - these are our first managed infrastructure offerings for communities in research and education. Developing cloud infrastructure and tools - this is the technical backbone that makes these services possible, built entirely on open source tools. Building an organizational foundation - this is the creation of our team structures, processes, and culture that help us carry out our mission. This first post will focus on services that we’ve created in our first year.\nUltimately, 2i2c’s mission is to facilitate use-cases in research and education via open source development and services. Throughout 2021 we ran several pilots to learn more about the needs of communities in research and education, and how we could build sustainable services that meet these needs. Here are some highlights for each major use-case we have targeted thus far:\nEducational community hubs # A primary use-case that 2i2c seeks to enable is collaborative, distributed educational spaces for learning with data. In 2021 we ran several pilots with educational communities:\nA university-wide hub for the University of Toronto. This hub is used in a variety of classes throughout the university, and is made freely available to anyone with a UofT account. We hope to repeat this model for other university-wide communities, and have learned a lot about the challenges of working with particularly large educational communities.\nSeveral hubs for community colleges across California. In partnership with UC Berkeley and CloudBank, we’ve run several hubs for nearly a dozen small community colleges teaching the Data 8 curriculum for their students. These hubs are lightweight and offer standardized environments for their students to use, in order to lower the cost of deploying and maintaining the hubs over time.\nWhat we learned # The organizational context around educational use-cases is different from research communities. Compared with research groups, educucational groups have more variance in their size (classes as small as 10 people and as large as 500) and think about cost by the student, not as a lump sum. This means that our initial hub-based pricing model may not map cleanly onto educational contexts, and we need to improve the match of scalability and price to these communities.\nMoreover, we’ve learned that for these communities, navigating all of the open source tools that are available for pedagogy is confusing! Everybody wants auto-grading but it’s unclear what is the “right tool for the job”. Tools like nbgitpuller have heavy use at “power universities” like UC Berkeley, but many others don’t know that it exists! We will need to invest more time into building guides and documentation that help others leverage these tools.\nResearch in the cloud # In addition to educational use-cases, we ran several pilots for research communities in order to leverage cloud infrastructure for scaling their work or collaborating more effectively.\nWe migrated Pangeo’s cloud infrastructure to be run via 2i2c. The Pangeo Community had been operating and developing their own JupyterHub for several years, but were looking for another organization to provide more reliable/sustained operations and support for their Pangeo Cloud Service. This year we migrated the service to run off of 2i2c’s deployment infrastructure .\nA scalable cloud hub for a SWOT satellite team. The MEOM research group at Grenoble is doing work with the NASA SWOT satellite project . However, the datasets generated from this project are huge, and only storable via the cloud. We’ve set up a JupyterHub to provide cloud-based access to this data, running a Pangeo-like environment.\nWhat we learned # Research communities tend to have more usecase-specific needs than educational ones. While introductory courses in data science tend to be similar across institutions, research needs are much more unique to the problem and team at hand. Moreover, they tend to want infrastructure that runs via institutional cloud accounts. This is possible due to the flexible nature of Jupyter and JupyterHub, but brings extra challenges in bureacracy and access permissions, given that 2i2c engineers usually are not members of these organizations already.\nAdditionally, many research use-cases are based around the location of the data. This is because data is the hardest thing to move from cloud to cloud. For this reason, it’s important to bring interactive sessions to the data. Jupyter’s ecosystem makes this possible, but we’d like to do more to make this easier. For …","date":1643068800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1643068800,"objectID":"858b571dced8d12fbbf3c313fdb00006","permalink":"https://2i2c.org/blog/2022/2021-review-services/","publishdate":"2022-01-25T00:00:00Z","relpermalink":"/blog/2022/2021-review-services/","section":"blog","summary":"Now that 2021 has come to an end, this marks the end of 2i2c’s first year of operations. In this year we have grown, experimented, and accomplished a lot - we have also faced challenges and learned as a team.","tags":[],"title":"2i2c’s first year, part 1: exploring Jupyter services.","type":"blog"},{"authors":["Sarah Gibson"],"categories":["updates"],"content":" Pangeo Cloud is an experimental service providing public cloud-based data-science environments for data-intensive geoscience research. We have recently finished re-creating the Pangeo community JupyterHub hosted on GCP in the 2i2c-org/infrastructure repository. This is a huge milestone in our partnership with Pangeo to provide expertise and operations of cloud-based, vendor-agnostic Jupyter infrastructure and workflows.\nFor users of Pangeo Cloud, the switch should have been a smooth one! The new hub should behave nearly identically to the old one, and will be managed by 2i2c engineers moving forward, in partnership with the Pangeo community. It will be available at the same URL ( https://us-central1-b.gcp.pangeo.io ) and there’s no need to worry about your home directories, they were synced to the new hub only a few days before the migration took place. Development and operations on this hub will all be done in the open and we invite participation and feedback from others in our infrastructure work. Please see this Discourse thread as an initial place to provide feedback.\nOn 22nd November 2021, the old Pangeo GCP JupyterHub will be shut down, and the project will move forward on the new 2i2c Pangeo Hub. Moving forward, we plan to collaborate together in order to find new pathways for development in the Jupyter ecosystem - we will share more ideas of things we will work on soon!\nHistory of Pangeo Cloud Hubs # Pangeo has pioneered a new model in using open source and cloud-agnostic infrastructure to support scientific research in the cloud.\nThe first Pangeo cloud JupyterHub (pangeo.pydata.org; now defuct) was deployed for the 2017 American Meteoroligical Society Meeting ; since then, the Pangeo community has iterated through several different versions of prototype cloud-based hubs. This allowed for many new workflows that enabled a more open and collaborative pathway to doing world class research, and included access to datasets and computational resources that were previously unattainable. Pangeo achieved this by working in partnership with open source communities and building technology that leveraged modular open source components for their platform.\nIn the last several years, Pangeo have built a thriving community of practice around this infrastructure. However as the community has grown, so has the need for more reliable and dedicated operational and developmental support since parts of the Pangeo stack require dedicated expertise and attention to managed. Modern scalable cloud infrastructure is one example of this. Maintaining a complex JupyterHub with many users is a difficult task, and has required significant resources from the Pangeo Project up to this point.\nThe Pangeo-2i2c Partnership # 2i2c is a non-profit team that develops and operates cloud infrastructure for interactive computing workflows. We have extensive experience in Jupyter workflows in the cloud and a long history of contributions to projects in this ecosystem. We have built a cloud deployment management system that allows us to centralise and configure the deployment of many independent JupyterHubs, empowering communities to leverage the same infrastructure (and team!) for JupyterHubs running in the cloud.\nSimilarly to Pangeo, all of 2i2c’s core infrastructure is cloud- and vendor-agnostic, and follows a model of building open source tools and giving back to those communities. Our partnership with Pangeo began through 2i2c’s core competency in these areas and the similarity between the two project’s technical stacks.\nWe’ve begun a partnership whereby 2i2c will manage Pangeo’s cloud infrastructure and lead efforts to develop new features, in partnership with open source communities. We sketched out a few ideas to focus on in this kick-off thread on Discourse . This approach allows each community to focus on it’s core strengths: Pangeo will continue to grow an open community and scientific software ecosystem around geospatial analytics, and 2i2c will oversee the development and operations of the core cloud infrastructure stack that powers Pangeo’s workflows. In some areas we are still experimenting with different collaboration models to ensure that the needs of the Pangeo community are met in a way that is also sustainable for 2i2c. Over the coming weeks, you may see some conversations (and threads for feedback!) about different support and operations models that work best for the community. We are excited to use this as an opportunity to learn more about how to serve more complex and diverse communities like Pangeo.\nWe are extremely grateful to the Pangeo project for giving us the opportunity to serve their community, and we look forward to a long partnership ahead! 🚀\n","date":1637020800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1637020800,"objectID":"24f81ee8ba42c2db1774c4d417072c6f","permalink":"https://2i2c.org/blog/2021/pangeo-goes-live/","publishdate":"2021-11-16T00:00:00Z","relpermalink":"/blog/2021/pangeo-goes-live/","section":"blog","summary":"2i2c are pleased to announce that the first Pangeo JupyterHub is now live on 2i2c-operated infrastructure! :tada: ","tags":["2i2c","pangeo"],"title":"Pangeo Cloud goes live on 2i2c!","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["updates"],"content":" This is a (roughly) quarterly update for the 2i2c community, with the goal of providing transparency about what we’ve been up to, sharing what we are working on and where we have struggled, and discussing what we’re up to next. In addition, almost all of the work we do is public and discoverable across our GitHub repositories , and is tracked by GitHub issues. Here’s a list of issues we’ve closed in ~Q3 .\nIt is amazing how quickly 4 months goes by when you’re building an organization from scratch! It seems like only a few weeks ago that we were recapping the beginning of the year in our last community update . Since then, we have been hard at work to make 2i2c’s organizational and infrastructure more robust and sustainable.\nThere are several major strategic areas where 2i2c aims to have impact, and we’ve split this community update along each of these major areas below. We’ll cover major highlights, challenges we’ve faced, and where we’re going next.\nHighlights # Managed JupyterHub Service # Our Managed JupyterHub Service will be a sustainable, scalable, and participatory service to provide cloud-based DevOps around JupyterHub for communities of practice in research and education. For the past several months, we have been running individual JupyterHubs for many organizations as a pilot, in order to learn more about the challenges we’ll face, and give ourselves an opportunity to build centralized infrastructure around the service.\nWe focused on a few major areas for work, outlined below:\nAutomation across cloud providers. We wish to serve communities that run on any of the major commercial cloud providers. We can standardize some of our infrastructure through abstractions like Kubernetes, but must still create cloud-specific deployment infrastructure as well (that Kubernetes cluster has to come from somewhere first!). In the last four months we’ve worked on automating Kubernetes and JupyterHub deployments on AWS as well as Azure to complement our Google Cloud deployments. We would soon like to run more hubs on this infrastructure to test how well it scales. Monitoring and reporting infrastructure. We have worked on the JupyterHub grafana-dashboards project to improve dashboarding around JupyterHub deployments in general, and will soon automatically deploy Grafana dashboards for our hubs so that communities have insight into what is going on in their hubs. User environment management. We want communities to have control over the environments that are available on their hubs. We also want to encourage that our communities follow community standards for reproducible environments that can be re-used elsewhere. For this reason, we’ve improved the repo2docker GitHub action to work with more image registries, and created a 2i2c user image template repository for users to re-use for their hubs. See the User Environment docs for more information. Support and collaboration roles. In addition to technology changes, we have developed an alpha-level support and collaboration model for the communities we serve. Most relevant for our communities is the community representative role, who acts as the main point of contact with 2i2c engineers, and leads administrators on the hub to guide its customization for the community it serves. See the user roles documentation for more information. We have also begun prototyping a FreshDesk support model and team processes around monitoring our support channels and responding to requests and incidents. Pangeo # We are working with the Pangeo Community to migrate the Pangeo JupyterHub deployments to utilize 2i2c’s centralized infrastructure, with the goal of 2i2c taking over the development and operation of Pangeo hubs moving forward. We have spent the last few months re-creating the Pangeo hub environment from scratch on a new cloud project controlled by Columbia University, and are nearly ready to begin migration from the “old” Pangeo hub to the new one. After this, we will focus our attention on re-creating the Pangeo BinderHub and AWS hub. Follow along with this work in this GitHub Project .\nExecutable Books / Jupyter Book # We are nearing the final year of a grant from the Sloan Foundation to support development on the Executable Books Project . As such, we have begun shifting our attention to create a strategy for sustaining the project’s community beyond this grant . In the coming months we plan on prioritizing improving our documentation (both for users and developers), as well as improving the general maintainability and quality of our codebases.\nJupyterHub community support # We recently collaborated with the JupyterHub community to apply for two CZI EOSS awards . Last month, we were notified that our application to support a Community Strategic Lead was funded! This role will fund Sarah Gibson’s time to focus some of her thinking on building community structures and dynamics that are inclusive and sustainable. We’ll update with more information as this project starts moving. …","date":1633824e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1633824e3,"objectID":"eb8170fad0ccceb7840702fd5c2ef642","permalink":"https://2i2c.org/blog/2021/q3-update/","publishdate":"2021-10-10T00:00:00Z","relpermalink":"/blog/2021/q3-update/","section":"blog","summary":"This is a (roughly) quarterly update for the 2i2c community, with the goal of providing transparency about what we’ve been up to, sharing what we are working on and where we have struggled, and discussing what we’re up to next.","tags":[],"title":"Community update Q3 2021: A new fiscal sponsor, improving our infrastructure, nearing an alpha launch.","type":"blog"},{"authors":["Chris Holdgraf","Danielle Robinson"],"categories":["updates"],"content":"This post was originally written for the CS\u0026amp;S blog .\nCode for Science \u0026amp; Society is thrilled to welcome the International Interactive Computing Collaboration (2i2c, for short) as a fiscally sponsored project! After spending a year incubating in the International Computer Science Institute , where 2i2c received critical startup support , 2i2c now joins our fiscally sponsored project program to launch their next phase. 2i2c develops and operates cloud infrastructure for interactive computing, with a focus on the Jupyter ecosystem and cloud-native workflows in research and education. They will build a cloud services model that respects a community’s Right to Replicate their infrastructure by providing transparent and customizable JupyterHub deployments on cloud infrastructure that utilize community-driven open source tools. They aim to use the resources generated from this service in order to support the communities that underlie this infrastructure. Read on for more about 2i2c’s mission and how CS\u0026amp;S will support their team and vision.\n2i2c’s organizational mission is to develop and operate sustainable cloud services that provide interactive computing infrastructure with JupyterHub and an ecosystem of tools that support research and education. This model has been pioneered in the organizations that 2i2c’s co-founders have co-led for many years, including the Pangeo Project , the Syzygy Project , the Binder Project , and the UC Berkeley DataHub . These projects follow an “integrate, customize, and upstream” model. They integrate pre-existing open source tools, make necessary customizations to support their specific use-case, and make upstream contributions to extend the infrastructure beyond its current capabilities. This creates a virtuous cycle where tangible needs are met in research and education, while improvements are made to open source projects that benefit the broader community. 2i2c hopes to scale this model, and provide these JupyterHub-based cloud services available to the broader research and education community.\nCS\u0026amp;S is particularly interested in pursuing the opportunity to work closely with 2i2c as their team explores how to build sustainable, ethical services that support open scholarship as well as open source communities. The model that 2i2c will develop is different in many ways from traditional grant-based development, or service-based business, because it depends on running community-led infrastructure that 2i2c contributes to, but does not control or own. Both CS\u0026amp;S and 2i2c believe that this model is an opportunity to build more distributed, community-led infrastructure and services, as well aligning a sustainability model with both open source communities and the scholarly community. We hope that this work will also provide experience that helps improve CS\u0026amp;S’s other initiatives in this space, including CS\u0026amp;S’s other fiscally sponsored projects and participants in the Digital Infrastructure Incubator program .\nAchieving this mission will involve innovation at an infrastructure level, a business model level, and an open source community strategy level, and will be carried out over the coming years. 2i2c’s next steps are to run pilot JupyterHub infrastructure for select communities of practice in research and education, in order to better understand their needs and how these needs fit in with 2i2c’s developing sustainability model. They will also build infrastructure to deploy and customize a federation of JupyterHubs that are community-specific, and that run entirely on open source infrastructure.\nIf you believe that your community would benefit from a hub like this, please reach out to the 2i2c team , or join their mailing list . Stay tuned as 2i2c builds its sustainable, scalable, and community-driven platform for interactive computing in the cloud.\n","date":163296e4,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":163296e4,"objectID":"2a879062b3520ec9de025b6fcd6be1b1","permalink":"https://2i2c.org/blog/2021/css-announce/","publishdate":"2021-09-30T00:00:00Z","relpermalink":"/blog/2021/css-announce/","section":"blog","summary":"This post was originally written for the CS\u0026S blog .\nCode for Science \u0026 Society is thrilled to welcome the International Interactive Computing Collaboration (2i2c, for short) as a fiscally sponsored project!","tags":["2i2c"],"title":"2i2c launches next phase in partnership with CS\u0026S","type":"blog"},{"authors":["Damián Avila"],"categories":["upstream"],"content":"","date":1630713600,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1630713600,"objectID":"7129084e54d4bda7b3ec37c3b41dc2b3","permalink":"https://2i2c.org/blog/2021/myst-nikola-part-2/","publishdate":"2021-09-04T00:00:00Z","relpermalink":"/blog/2021/myst-nikola-part-2/","section":"blog","summary":"","tags":["jupyter","executablebooks"],"title":"A deep dive into MyST, Part 2: The MyST-Parser, Docutils and Sphinx","type":"blog"},{"authors":["Damián Avila"],"categories":["upstream"],"content":"","date":1629676800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1629676800,"objectID":"d6c2657172e1b9cf296716eda7200d3d","permalink":"https://2i2c.org/blog/2021/myst-nikola-part-1/","publishdate":"2021-08-23T00:00:00Z","relpermalink":"/blog/2021/myst-nikola-part-1/","section":"blog","summary":"","tags":["jupyter","executablebooks"],"title":"A deep dive into MyST, Part 1: The MyST-Parser Python API usage in Nikola","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"It has been about six months since 2i2c first began operations (after receiving funding from the Chan Zuckerberg Initiative ). In that time we’ve made progress along several directions, and wish to use this blog post to provide updates about the ways in which 2i2c has evolved over the first months of its existence.\nBelow are a few major updates from the 2i2c community - as always, if you want to learn more about 2i2c, keep an eye on our blog or subscribe to the 2i2c mailing list .\nEarly pilot JupyterHub infrastructure # First off - we have been making progress building out our JupyterHub deployment infrastructure for 2i2c. One of our major organizational goals is to build a sustainable service managing open source cloud infrastructure for interactive computing. This service will provide hosted, customized JupyterHubs for communities of practice in research and education. They’ll be built entirely with open source tools that are community-driven, and that respect the community’s Right to Replicate .\nIn order to accomplish this, 2i2c is running several pilots with partners and interested organizations, supported by our funding from CZI , as well as from the JROST rapid response fund . These pilots are meant to be learning opportunities to understand what kind of infrastructure and service it needs to build moving forward.\nThe documentation for our pilot hubs infrastructure contains information about our deployments and infrastructure. It is served from this 2i2c-org/infrastructure repository , a centralized location for configuring and deploying a federated network of JupyterHubs. Each JupyterHub is independent of one another, and could be spun out from the centralized repository with minimal extra work, giving hub users the ability to replicate their infrastructure, with or without 2i2c . We will continue refining the code in this repository as we learn more from our hub infrastructure pilots.\nJupyterHub for geospatial analytics - A collaboration with Pangeo # As originally announced on the Pangeo blog , 2i2c is forging a collaboration with the Pangeo project around operating and developing cloud infrastructure for large-scale geospatial analytics! This collaboration is funded through a grant from the Moore Foundation (via Pangeo investigator Ryan Abernathey).\nOver the coming months, 2i2c plans to assume operation of infrastructure underlying the Pangeo project, allowing the Pangeo team to focus their efforts on their core scientific and development missions. Because Pangeo’s infrastructure is already running on a fully open source stack with JupyterHub, our first step will simply be to shift control over this infrastructure to 2i2c engineers. We don’t anticipate needing to make major changes to their infrastructure and deployments (part of the benefits of using open, modular tools).\nOnce this is complete, we’ll next shift our attention to some new areas of development that support use-cases in the Pangeo community (and in the scientific community more broadly). There’s a lot of progress that we imagine making - such as supporting publishing pipelines via the Pangeo Gallery or improving tools for scalable computing with Dask Gateway . We’ll provide updates as we formally begin this collaboration and hash out a plan for our next steps.\nJupyterHub for education - A collaboration with CloudBank and UC Berkeley # In addition, we’ve begun a partnership with the UC Berkeley Data Science in Undergraduate Studies program , as well as CloudBank . This collaboration aims to provide hosted JupyterHub infrastructure for community colleges across the state of California. It is an attempt at providing vendor-agnostic and open-source infrastructure to several institutions who would otherwise not be able to deploy this infrastructure on their own.\n2i2c will provide the deployment and configuration architecture for this collaboration, working with Sean Morris in operating this educational infrastructure. All of the cloud infrastructure for this pilot will be funded via CloudBank. We will begin by offering environments that are modeled after the Data 8 course at UC Berkeley . This is part of an effort to build a community of practice around Data Science education using open source tools.\nNew team members # We’ve also welcomed two new members to the 2i2c core team! 🎉\nThese individuals will both work towards 2i2c’s major projects , and collaborate together on running our 2i2c Pilot Hub infrastructure. Here’s a bit about each new team member.\nDamián Avila . Damián has been a Jupyter core team member for many years now, and has done work across many different parts of the PyData stack (in particular, Jupyter , Bokeh , RISE , and Nikola ). Damián will focus his efforts on supporting JupyterHub infrastructure for the Pangeo project , as well as development across the Executable Books Project Sarah Gibson . Sarah will join 2i2c in June, after spending several years as a Research Software Engineer at the Turing Institute . She has …","date":1621900800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1621900800,"objectID":"dd8c28b4e191724ed9c1ebae27d1be38","permalink":"https://2i2c.org/blog/2021/six-month-update/","publishdate":"2021-05-25T00:00:00Z","relpermalink":"/blog/2021/six-month-update/","section":"blog","summary":"It has been about six months since 2i2c first began operations (after receiving funding from the Chan Zuckerberg Initiative ). In that time we’ve made progress along several directions, and wish to use this blog post to provide updates about the ways in which 2i2c has evolved over the first months of its existence.","tags":[],"title":"Pilot hubs, new collaborations, and new team members - A six month update","type":"blog"},{"authors":null,"categories":null,"content":"We are looking for an Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on important problems shaping society. This engineer will lead the development and operation of cloud-based infrastructure, focusing on the Pangeo Project - a community platform for big data geoscience.\n❌❌❌\nThis posting is closed to new applications.\nSee the jobs page for our open positions.\n❌❌❌\nAbout the position\nSalary: $110,000 - $130,000 Location: anywhere (prefer a time zone between US/Pacific and Central European) Deadline: Major duties\nCloud infrastructure management and operations.\nDevelopment of open source infrastructure for hosted JupyterHub service\nFor more general information about 2i2c, see the links below:\nOur Team Compass Our Code of Conduct Our Mission and Values What it’s like to work at 2i2c Click here to Apply Who we are # 2i2c is a non-profit organization with a mission to make interactive computing more accessible, scalable, and powerful for research and education. We strive to…\nSupport data workflows in research and education through infrastructure for interactive computing. Support open tools and communities that underlie this infrastructure. We accomplish this mission by providing managed cloud services for interactive computing, by providing development and technical leadership to researchers and educators that utilize this infrastructure for specific communities, and by providing support for open source tools and communities in this ecosystem.\nWe have deep ties to the open source community, and have been leaders and core contributors across dozens of projects - in particular in the Jupyter ecosystem. We also have deep ties to research and education - our team has spent years deploying infrastructure for universities, community colleges, and research teams, and now we’re bringing this experience to a wider audience with 2i2c.\nWe believe strongly in communities that are inclusive, transparent, equitable, effective, and diverse, especially 2i2c itself. We believe that our values should permeate everything about 2i2c, including the work we do, the communities we serve, and our own organizational culture.\n2i2c is a project of the International Computer Science Institute , a 501(c)(3) not-for-profit.\nWhat you’ll do # You will define the overall strategy and technical approach to cloud computing usage in Pangeo, and will interface with the Pangeo community on a frequent basis. You will help deploy, customize, and operate cloud infrastructure for research and interactive computing. You’ll use the experience operating this infrastructure to identify development opportunities, with the goal of minimizing maintenance time and toil - your goal will be to spend more time developing and less time operating. You will contribute to the general development and maintenance of open source software packages for the advancement of scientific objectives, and develop applications for extracting, transforming, loading, managing, and cataloging scientific data in the cloud. You will engage and interact with open source communities surrounding the tools that you use in serving the Pangeo community, and will represent 2i2c in these engagements. You will also collaborate with scientists to support research projects, and may conduct some education and training around scientific computing.\nResponsibilities # Develops strategy and technical design for cloud computing architecture within the Pangeo project and related projects with 2i2c. Assists with site reliability for Pangeo infrastructure, and uses experience operating this infrastructure to identify new opportunities for development. Ensures the reliable operation of production cloud-based tools including JupyterHub / JupyterLab and Dask. Participates in the upstream open source communities we rely on (such as JupyterHub, Dask, etc) by contributing code, documentation, etc as needed. Develops dashboards and reports to quantify system usage and costs. Helps to maintain and operate Pangeo Gallery , an interactive showcase for data science projects based on binder and github workflows. Conducts education and outreach around cloud computing. Explores emerging technologies in the cloud / DevOps space. Travels to conferences and workshops (once COVID-19 restrictions end). Will work with minimal supervision from leadership at 2i2c in partnership with collaborators at Columbia and the Pangeo project. Will work independently and make their own decisions about where to best allocate effort. Requirements # Familiarity with deploying applications on cloud infrastructure. Experience developing tools in a general purpose programming language (eg. Python) Experience deploying and developing with Linux container technologies, such as Docker and Kubernetes Experience with continuous integration services (e.g. Travis CI, GitHub workflows) Experience building and deploying backend web services. Experience collaborating and …","date":1607472e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1607472e3,"objectID":"0f43f426f967699a3f706a81695b7caa","permalink":"https://2i2c.org/jobs/2021/osie-pangeo/","publishdate":"2020-12-09T00:00:00Z","relpermalink":"/jobs/2021/osie-pangeo/","section":"jobs","summary":"We are looking for an Open Source Infrastructure Engineer who will help shape the future of data-intensive scientific research and make a big impact on important problems shaping society. This engineer will lead the development and operation of cloud-based infrastructure, focusing on the Pangeo Project - a community platform for big data geoscience.","tags":null,"title":"Open Source Infrastructure Engineer: Pangeo Project","type":"jobs"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"Last week we announced the creation of 2i2c , a non-profit initiative dedicated to improving and facilitating access to infrastructure for interactive computing workflows in research and education. Today we are thrilled to announce that 2i2c has received core support from the Chan Zuckerberg Initiative . You can find CZI’s announcement here .\nThis funding totals around $1.4m over three years. It provides crucial core support for 2i2c as it bootstraps itself into existence. We are so thankful to CZI for this support. 🎉🙏✨\nThe rest of this post is a short run-down of what we’ll use this funding for, and what we hope to accomplish.\nThe big picture # In recent years, several projects including Binder , Pangeo , Syzygy , and the Berkeley DataHubs have built atop the Jupyter architecture to support cloud-based infrastructure for reproducible research, large-scale scientific data analysis, national-scale infrastructure for researchers, and broad-impact educational programs based on freely available computational materials. These projects illustrate the transformative potential of the open Jupyter architecture, but they have also shown that unlocking this potential in service of scientists and educators requires continued development and resources beyond those of open source volunteers.\nIn order to deploy these resources at scale, manage and maintain them for large communities, and to continue developing the underlying technologies for scientific use cases, we need models to sustainably deploy and improve Jupyter technology. We also need capacity for thinking strategically and forging new partnerships to accomplish this goal. This funding will support 2i2c’s early strategic planning and partnership efforts, as well as technical development and operation of Jupyter infrastructure for research and education.\nBelow are two keys goals for this grant:\nGoal 1: Build capacity for Jupyter in research and education # The primary goal of this funding is to build more capacity for Jupyter’s engagement in research and education. This funding will primarily support Chris Holdgraf to build strategic partnerships and collaborations, find opportunities for Jupyter infrastructure to benefit research and education, coordinate activity in the Jupyter project that benefits these communities, and secure more funding for development, maintenance, and support for Jupyter technology.\nWe are grateful to CZI for this funding because strategy, leadership, and community support are often difficult to fund from grants that are focused on technical deliverables. By funding strategic growth and capacity building, CZI is helping 2i2c lay a strong foundation from which it can have a greater impact.\nGoal 2: Support hosted Jupyter infrastructure for research and education # 2i2c will offer hosted interactive computing infrastructure utilizing the Jupyter ecosystem. It will both deploy and operate this infrastructure for researchers and educators, as well as perform core development to ensure that it serves these communities well. Funding from this grant will support 2i2c’s first hire - Georgiana Dolocan as an Open Source Infrastructure Engineer. Georgiana has been the JupyterHub Contributor in Residence for the past year, and we are so excited for her to join 2i2c!\nGeorgiana will begin by supporting several pilot hubs that are run by 2i2c for community colleges, universities, and research institutions. She will help these organizations accomplish their mission through 2i2c infrastructure, and will develop these technologies so they are stable, scalable, and serve a diverse set of needs in research and education. This will hopefully set the foundation for 2i2c to sustainably offer this hub infrastructure to a wider audience in the future.\nThis is the next step in Georgiana’s journey through the Jupyter ecosystem that began with an outreachy internship followed by a term as Contributor in Residence . Both of these steps were made possible thanks to Jupyter stakeholders who invest their resources, time, and mentorship to grow Jupyter’s community beyond the people that have traditionally been involved in the project. It’s also possible because of funders committing resources to broaden participation and inclusion - in particular, the Berkeley Institute for Data Science and NumFOCUS for their original support of our Outreachy interns and the CZI EOSS grant series for funding the original Contributor in Residence.\nWhat’s next # With this core support, 2i2c turns towards its JupyterHub pilot deployments to build early prototypes that serve research and education, and to build organizational models that sustain these hubs and their development. If you or your organization think you’d be a good fit for these pilots, please reach out to 2i2c and let us know!\nMany thanks again to CZI for this support - we believe that it is an excellent investment in the Jupyter community and in open source communities more generally. We also believe it will lead to major …","date":1605744e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1605744e3,"objectID":"110ad797b7358afdff75f2722272af75","permalink":"https://2i2c.org/blog/2021/czi-core-support/","publishdate":"2020-11-19T00:00:00Z","relpermalink":"/blog/2021/czi-core-support/","section":"blog","summary":"Last week we announced the creation of 2i2c , a non-profit initiative dedicated to improving and facilitating access to infrastructure for interactive computing workflows in research and education. Today we are thrilled to announce that 2i2c has received core support from the Chan Zuckerberg Initiative .","tags":["meta"],"title":"2i2c receives core support from CZI","type":"blog"},{"authors":["Chris Holdgraf"],"categories":["organization"],"content":"👋 hey everyone!\nWe’d like to announce the creation of a new non-profit organization1 that we call 2i2c.\n2i2c stands for The International Interactive Computing Collaboration. It is a non-profit dedicated to making open tools for interactive computing more accessible and more powerful for the research and education communities.\nThis is a short post about why we created 2i2c, what we hope that it will do, and what we are up to next. If you’d prefer to watch a video instead of read a blog post, check out this talk about 2i2c at JupyterCon 2020:\nWhy create 2i2c? # The founding team of 2i2c has spent the last several years running projects that use interactive computing for research and education, including bringing data science education to thousands of students , connecting geospatial researchers with large datasets and computational resources in the cloud , and providing federated online environment hubs to schools across Canada , to name a few.\nOver time we realized that, while infrastructure for interactive computing could be a huge benefit to research and education, it also required a fair amount of expertise to configure, deploy, and develop. We wished for other organizations to enjoy the same success that we had found, but learned that for many, deploying their own infrastructure was a non-starter to adoption. Instead, many were turning to proprietary or vendor-specific tooling.\nWe created 2i2c so that these organizations can use entirely open-source tools without hiring and training their own dev-ops and infrastructure talent, and so that development and support of open tools for interactive computing continues to represent the interests of research and education.\nWhy a non-profit? # It may sound strange to create a non-profit initiative when there are many VC-funded startups and large tech companies offering notebook services these days. However, we think that a non-profit organization is the right approach to balance the interests of all the stakeholders that we wish to serve. We hope that 2i2c will be a partner to:\nResearch and educational communities, who can rely on 2i2c to provide them cutting-edge infrastructure for interactive computing that is 💯 open source. Researchers and educators who need development, who can rely on 2i2c as a collaborator that offers development and expertise in open-source infrastructure to push the cutting edge of interactive computing in the cloud. Open source communities, who can count on 2i2c support and grow the communities that underlie the tools that we deploy. Cloud providers, who wish to help the research and educational community via their infrastructure. Supporters of open source who wish to support interactive computing for research and education via a non-profit dedicated to exactly this mission. As a non-profit initiative, 2i2c is dedicated to supporting an ecosystem of tools and stakeholders across the open source community, and to ensuring that those tools are well-suited for research and education. We believe strongly in mission-driven work, and non-profit status will ensure that the work that we do is always aligned with our mission and values.\nWhat are we going to do? # With all of that in mind, what is 2i2c actually going to do? We are still working out the details, but here’s a rough picture:\nOffer hosted interactive computing environments on cloud infrastructure . These will be entirely open source and vendor-neutral, and customizable for the communities that are using them. They’ll be offered either as a fee-for-service model and/or subsidized through grants and donations. We wish to build upon the success of JupyterHub as a gateway to computational resources and environments, learning environments, and communities of users. For more information about the vision and values of our hosted infrastructure, see the 2i2c Right to Replicate document .\nProvide collaboration and development for interactive computing in research and education . Beyond providing hub infrastructure, there are many ways in which solving problems in research and education can lead to better tools, infrastructure, and workflows in the open source community. For example - how can we generalize a community’s solution to scalable computing so that it can be useful for other use-cases as well? We hope that 2i2c can be an aggregator and integrator of many perspectives in research and education, and build tools that are maximally useful across communities.\nProvide core development and community support for open source projects that we use. While many organizations use Jupyter technology in their projects, it is also crucial that they give back to those tools in order to keep the ecosystem healthy. As a mission-driven non-profit, 2i2c has a core goal in not only deploying and customizing open source tools, but also providing core support for them.\nNext steps # 2i2c is a young organization, but we already have a few exciting ideas to work towards in the coming months. Here’s an idea of …","date":1604966400,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1604966400,"objectID":"4fbd63f9efdd7c1913ddfa4eeef26698","permalink":"https://2i2c.org/blog/2021/hello-world/","publishdate":"2020-11-10T00:00:00Z","relpermalink":"/blog/2021/hello-world/","section":"blog","summary":"👋 hey everyone!\nWe’d like to announce the creation of a new non-profit organization1 that we call 2i2c.\n2i2c stands for The International Interactive Computing Collaboration. It is a non-profit dedicated to making open tools for interactive computing more accessible and more powerful for the research and education communities.","tags":["meta"],"title":"Hello World","type":"blog"},{"authors":null,"categories":null,"content":"The Right to Replicate gives communities the right to replicate their infrastructure in its entirety elsewhere, with or without 2i2c.\nThis document describes 2i2c’s commitment to a community’s “right to replicate”, and how this translates into specific infrastructure commitments from 2i2c. We make these commitments because we believe that using infrastructure that follows these principles will lead to a more fair, just, equitable world. We also believe they are the right foundation for more productive and impactful research and education.\n2i2c is committed to running its own infrastructure on open-source tools and vendor-agnostic infrastructure, though it does not force users to use only open-source tools in their own environments, code, and data. Below is a table describing how the Right to Replicate fits into 2i2c hub technology.\n(Definitions of MUST, MUST NOT, SHOULD, MAY, etc are defined in RFC 2119 )\nUser Code and Data May be Open Source We encourage adopting and producing open source code and data, but this is up to the user. e.g., licenses for user content/code User Environment Should be Open Source Strong preference for open source tools only, although in some cases user needs may override this. e.g., Python, R, PyData stack. 2i2c Infrastructure Must be Open Source Strong commitment to using only open source software. e.g., JupyterHub, Kubernetes, Postgresql Cloud Provider Infrastructure Must be Portable See this blog post for more information. Below we describe our commitments in our own infrastructure stack in more detail.\nHow 2i2c infrastructure ensures this right # 2i2c infrastructure and documentation for it MUST BE as transparent \u0026amp; accessible as possible, so communities can replicate our configuration without having to extract any ‘secret sauce’ from 2i2c. If they choose to, they can also inspect, audit \u0026amp; modify the infrastructure they are paying for and using.\nTo ensure the Right to Replicate to our communities, 2i2c makes the following commitments to infrastructure we build and operate:\nWe MUST use only open source software to run our infrastructure. By only using software that is available to everyone on the same terms, we can ensure that communities can replicate the infrastructure without having to negotiate licensing terms with proprietary software vendors. In addition, any changes we make to open source software will be made in public and/or contributed upstream, so communities continue to have access to them regardless of where their infrastructure is.\nWe MUST NOT directly depend on proprietary cloud vendor specific products or APIs. Instead, we use cloud-managed open source software, or hide the dependency behind a layer of abstraction. This ensures that communities can port their infrastructure to any cloud provider of their choice, or run it on their own hardware with purely open source software.\nThis set of commitments acts as a business continuity plan for our partner communities, ensuring 2i2c will follow best practices within the open source, open education and open research ecosystems.\n","date":1530144e3,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":1530144e3,"objectID":"f9d84027023bd7709772a71806b3aca9","permalink":"https://2i2c.org/right-to-replicate/","publishdate":"2018-06-28T00:00:00Z","relpermalink":"/right-to-replicate/","section":"","summary":"The Right to Replicate gives communities the right to replicate their infrastructure in its entirety elsewhere, with or without 2i2c.\nThis document describes 2i2c’s commitment to a community’s “right to replicate”, and how this translates into specific infrastructure commitments from 2i2c.","tags":null,"title":"The Community Right to Replicate","type":"page"},{"authors":null,"categories":null,"content":" ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"c2c20062023db009d767c2f4a7d38088","permalink":"https://2i2c.org/pilot-hubs/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/pilot-hubs/","section":"","summary":" ","tags":null,"title":"","type":"page"},{"authors":null,"categories":null,"content":" ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"74dcede968ab0952007871e9fa0da40e","permalink":"https://2i2c.org/pilot/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/pilot/","section":"","summary":" ","tags":null,"title":"","type":"page"},{"authors":null,"categories":null,"content":" ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"cbf2769f3919dc1ca746df7980be9eff","permalink":"https://2i2c.org/team-compass/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/team-compass/","section":"","summary":" ","tags":null,"title":"","type":"page"},{"authors":null,"categories":null,"content":"2i2c has expertise in cloud infrastructure and managed services for interactive computing in research and education workflows. We focus on the Jupyter ecosystem and adjacent open source communities (e.g., the PyData ecosystem), with a particular emphasis on JupyterHub.\nJoin our mailing list 📰 Send us an email ✉️ Our Team Compass contains all of 2i2c’s organizational strategy, policy, and team practices. Our updates blog series provides all major organizational updates for our community. Our Service Level Objectives describes our day-to-day goals running the service. Our Shared Responsibility Model describes how we collaborate with communities in this hub service. Our Infrastructure Guide describes all of our cloud infrastructure and engineering practices, with links to our codebase. Here are a few ways that you can connect with and collaborate with 2i2c.\nUse and support our managed JupyterHub services # 2i2c aims to provide Managed JupyterHubs in the cloud that are customized for communities in research and education. We are exploring sustainability and services models around this goal, and invite feedback and ideas for ways that we can improve this service. We are running JupyterHubs for many communities already, and are accepting new communities in batches as our capacity grows. If you are interested in having a managed JupyterHub for your community, check out our cloud service page for more information or send an email to partnerships@2i2c.org to discuss.\nPitch a project or grant # Our team is always looking our for opportunities to collaborate and learn from others in order to have an impact. Sometimes these can even lead to new grant ideas or ongoing projects. If you have an idea for collaboration that is aligned with our mission, and that would benefit from our skills and perspective, please send an email to partnerships@2i2c.org and we can discuss.\n","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"5fff794d732d0d9048992165a6c484a4","permalink":"https://2i2c.org/collaborate/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/collaborate/","section":"","summary":"2i2c has expertise in cloud infrastructure and managed services for interactive computing in research and education workflows. We focus on the Jupyter ecosystem and adjacent open source communities (e.g., the PyData ecosystem), with a particular emphasis on JupyterHub.","tags":null,"title":"Contact us to collaborate","type":"page"},{"authors":null,"categories":null,"content":" Brand guidelines # Our Brand Guidelines document describes 2i2c’s overall brand and visual style.\nLogos # Square logo (default) # Logo\nDownload SVG | Download PDF Logo light\nLogo black\nWide logos # Wide logo\nDownload SVG | Download PDF Wide logo light\nColors # Primary colors # Big Blue: #1D4EF5 Pale Blue: #F2F5FC Black: #000000 Secondary colors # Midnight: #230344\nMauve: #B86BFC\nForest: #057761\nLight Green: #0CEFAE\nMagenta: #C60A76\nPink: #FF808B\nCoral: #FF4E4F\nYellow: #FFDE17\nDesign assets # These two links are only accessible to 2i2c team members.\nFigma canvas with design assets Google Drive folder with design assets ","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"0cb45ec32ab674771091450a1bc1fdc4","permalink":"https://2i2c.org/brand/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/brand/","section":"","summary":"Brand guidelines # Our Brand Guidelines document describes 2i2c’s overall brand and visual style.\nLogos # Square logo (default) # Logo\nDownload SVG | Download PDF Logo light\nLogo black","tags":null,"title":"Design and brand guidelines","type":"page"},{"authors":null,"categories":null,"content":"Much of the work we do is supported by grants and donations from stakeholders in our community. These resources go towards things like new development of open source technology, maintenance for open source projects, community development efforts, sponsoring hubs for under-resourced communities, and general support for 2i2c in its mission.\nFill our the form below to make a donation to 2i2c via its fiscal sponsor, Code for Science and Society . If you’d rather have a conversation with us first about your donation, please send us an email .\n","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"ac26b9ca282f87df5d5ed826e374bb78","permalink":"https://2i2c.org/donate/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/donate/","section":"","summary":"Much of the work we do is supported by grants and donations from stakeholders in our community. These resources go towards things like new development of open source technology, maintenance for open source projects, community development efforts, sponsoring hubs for under-resourced communities, and general support for 2i2c in its mission.","tags":null,"title":"Donate to 2i2c","type":"page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"07777db7484439a4707d21d09c158fa2","permalink":"https://2i2c.org/mission/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/mission/","section":"","summary":"","tags":null,"title":"Mission and strategy","type":"widget_page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"6087c0ef875554f4409ac52928d79279","permalink":"https://2i2c.org/projects/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/projects/","section":"","summary":"","tags":null,"title":"Open Source","type":"widget_page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"8ab4338b5212831f3b729ac977000df4","permalink":"https://2i2c.org/founders/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/founders/","section":"","summary":"","tags":null,"title":"Our Founding Team","type":"widget_page"},{"authors":null,"categories":null,"content":"","date":-62135596800,"expirydate":-62135596800,"kind":"page","lang":"en","lastmod":-62135596800,"objectID":"6425ff024d90bbffa37d23fc4bf403ee","permalink":"https://2i2c.org/organization/","publishdate":"0001-01-01T00:00:00Z","relpermalink":"/organization/","section":"","summary":"","tags":null,"title":"Our organization","type":"widget_page"}]
\ No newline at end of file
diff --git a/index.xml b/index.xml
index afb64930a..274efdac3 100644
--- a/index.xml
+++ b/index.xml
@@ -39,7 +39,15 @@ loading="lazy" data-zoomable />&lt;/div>
 &lt;/div>&lt;figcaption>
 Login screen of the GHG hub showing the custom built SSIM-GHG image option.
 &lt;/figcaption>&lt;/figure>
-&lt;/p></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
+&lt;/p>
+&lt;h2 id="acknowledgements">
+Acknowledgements
+&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
+&lt;/h2>&lt;p>2i2c would like to credit the following individuals for their great efforts supporting this workshop:&lt;/p>
+&lt;ul>
+&lt;li>Sanjay Bhangar (Development seed)&lt;/li>
+&lt;li>Slesa Adhikari (NASA IMPACT)&lt;/li>
+&lt;/ul></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
 &lt;figure >
 &lt;div class="d-flex justify-content-center">
 &lt;div class="w-100" >&lt;img src="./cover.png" alt="Group selfie of Project Pythia Cook-off participants." loading="lazy" data-zoomable />&lt;/div>
diff --git a/tag/community/index.xml b/tag/community/index.xml
index e050f79c9..e190c957e 100644
--- a/tag/community/index.xml
+++ b/tag/community/index.xml
@@ -39,7 +39,15 @@ loading="lazy" data-zoomable />&lt;/div>
 &lt;/div>&lt;figcaption>
 Login screen of the GHG hub showing the custom built SSIM-GHG image option.
 &lt;/figcaption>&lt;/figure>
-&lt;/p></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
+&lt;/p>
+&lt;h2 id="acknowledgements">
+Acknowledgements
+&lt;a class="header-anchor" href="#acknowledgements">#&lt;/a>
+&lt;/h2>&lt;p>2i2c would like to credit the following individuals for their great efforts supporting this workshop:&lt;/p>
+&lt;ul>
+&lt;li>Sanjay Bhangar (Development seed)&lt;/li>
+&lt;li>Slesa Adhikari (NASA IMPACT)&lt;/li>
+&lt;/ul></description></item><item><title>Hacking the Project Pythia Cook-off with MyST Markdown</title><link>https://2i2c.org/blog/2024/project-pythia-cookoff/</link><pubDate>Tue, 18 Jun 2024 00:00:00 +0000</pubDate><guid>https://2i2c.org/blog/2024/project-pythia-cookoff/</guid><description>&lt;p>
 &lt;figure >
 &lt;div class="d-flex justify-content-center">
 &lt;div class="w-100" >&lt;img src="./cover.png" alt="Group selfie of Project Pythia Cook-off participants." loading="lazy" data-zoomable />&lt;/div>