deploy: 8dca622

_preview/453/.buildinfo

@@ -0,0 +1,4 @@
+# Sphinx build info version 1
+# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
+config: 9bc8333b04b16a0c940e860c43b05d5d
+tags: 645f666f9bcd5a90fca523b33c5a78b7

_preview/453/_sources/about.md

@@ -0,0 +1,90 @@
+# About Project Pythia
+
+Project Pythia is the education working group for [Pangeo](https://pangeo.io)
+and is an educational resource for the entire geoscience community.
+Project Pythia is a home for Python-centered learning resources that are _open-source_,
+_community-owned_, _geoscience-focused_, and _high-quality_.
+
+## Why do we need Project Pythia?
+
+Scientists working in a multitude of disciplines rely heavily on
+computing technologies for their research. Numerical simulations
+run on supercomputers are used in the study of climate, weather,
+atmospheric chemistry, wildfires, space weather, and more. Similarly,
+a tremendous volume of digital data produced by numerical simulations,
+or observations made with instruments, are analyzed with the help
+of powerful computers and software. Thus, today’s scientists require
+not only expertise in their scientific discipline, but also require
+high-level technical skills to effectively analyze, manipulate, and
+make sense of potentially vast volumes of data. Computing environments
+change rapidly, and two technologies that have emerged and are being
+adopted by scientific communities relatively recently are Cloud
+Computing platforms and a software ecosystem of scientific tools
+built around the open source programming language called Python.
+Project Pythia provides a public, web-accessible training
+resource that will help educate current, and aspiring, earth
+scientists to more effectively use both the Scientific Python
+Ecosystem and Cloud Computing to make sense of huge volumes of
+numerical scientific data.
+
+## Why the name _Pythia_?
+
+In ancient Greek mythology, the god [Apollo](https://en.wikipedia.org/wiki/Apollo)
+is said to have slain the monstrous [Python](https://en.wikipedia.org/wiki/Python_(mythology)).
+Apollo's temple was later served by the [Oracle](https://en.wikipedia.org/wiki/Oracle)
+of [Delphi](https://en.wikipedia.org/wiki/Delphi),
+who was known as the [Pythia](https://en.wikipedia.org/wiki/Pythia).
+
+Like the Oracle of old, Project Pythia will help you make sense of things that seem mysterious.
+We will not, however, _slay_ your [Python](https://www.python.org),
+but instead help you _improve_ it -- and help you to help others do the same!
+
+## Who is Project Pythia?
+
+Pythia is an open and inclusive community! Look [here](index.md#join-us) for info
+on how to get involved.
+
+## Project Pythia Goals
+
+1. _The Pythia Portal:_ A searchable online portal that
+   provides scientists at any point in their career with educational
+   content and real-world examples needed to learn how to navigate and
+   integrate the myriad packages within the Python ecosystem for the
+   geosciences.
+
+2. _Cloud-Deployable Pythia Platforms:_ A light-weight,
+   Binder-based platform that will make it possible to launch portal
+   content in customizable executable environments in the Cloud with
+   only a “single click.”
+
+## Presentations about Project Pythia
+
+To learn more about Project Pythia and its history, see this list of presentations (listed in reverse-chronological order):
+
+| Forum | Date | Presenter | Format | Title (with link) |
+| ---   |  ---  |   ---   |  ---    |  --- |
+| Ocean Sciences | 2024-02 | Brian Rose | slides | [The Project Pythia Cookbook Initiative](https://docs.google.com/presentation/d/1tvABElX-0CgiuzMfY7XFY-gsXzGUXqWV6k2qJeTw5bk/edit?usp=sharing) |
+| AMS   | 2024-01 | Drew Camron | slides | [Project Pythia: Three Years of Community Building Through Open Source Technology and Education](https://drive.google.com/file/d/1nZfWWozBKQzVCYpKUqWPX51MEgSAhgfM/view?usp=sharing) |
+| AMS   | 2024-01 | Kevin Tyle | slides | [Cooking up a Storm with Project Pythia](https://docs.google.com/presentation/d/1zMsoCg1RMHGZDuLLV0QsZB6NwKE7CKo5_8iFAGDGj6o/edit?usp=drive_link) |
+| AMS   | 2024-01 | Brian Rose | slides | [Project Pythia's vision: Building an Inclusive Geoscience Community through Accessible, Reusable, and Reproducible Workflows](https://docs.google.com/presentation/d/1nG3iJr6Q7_ktKHg6PXzna7DMp4HDiFgS7scqjKLtXNA/edit?usp=sharing) |
+| AGU   | 2023-12 | Brian Rose | slides | [The Project Pythia Cookbook Initiative](https://docs.google.com/presentation/d/1J6wgvypXxYZ4uTQHsquyH_tlY6KiQXBcxb3cwdd3FUM/edit?usp=sharing) |
+| AGU   | 2023-12 | Julia Kent | slides | [Project Pythia: Empowering Geoscientists through Open-Source, Open-Science Collaboration](https://docs.google.com/presentation/d/1wm0RxaswVh_YJFcYsHduONsYiYNLc69f0XuHnP7Vfh8/edit?usp=sharing) |
+| SciPy | 2023-07 | Kevin Tyle / Drew Camron | slides | [Better (Open-source) Homes and Gardens with Project Pythia](https://drive.google.com/file/d/125Wk3TTImHqSYLkgPNsy4_M_w3aENgLr/view?usp=sharing) |
+| Pythia Cook-off 2023 | 2023-06 | Brian Rose / Drew Camron | slides | [Cook-off 2023 Introduction: All about Pythia, Cookbooks, and the Cook-off!](https://docs.google.com/presentation/d/1NUnkZLyf4HXkPfQATjoUAs1s9cQAAtTlmVUMwQQmvMg/edit?usp=sharing) |
+| CI2023 Reproducibility Challenge | 2023-05 | Brian Rose | slides | [Project Pythia: Learning Python Geoscience Software](https://doi.org/10.5281/zenodo.7915657) |
+| ISS   |  2023-04 | Julia Kent | slides | [How Project Pythia Leverages GitHub for Community Contributions](https://docs.google.com/presentation/d/13MH5968BAfR6IxplGVbM2bSJ6uRoa5Wkzk5axqvmCX4/edit?usp=sharing) |
+| ESDS forum | 2023-03 | Brian Rose | slides | [Project Pythia Cookbooks](https://drive.google.com/file/d/1goieS2kjajD93fPSKm6aP2GroNotV9zu/view?usp=sharing) |
+| AMS   |  2023-01  | Drew Camron | talk | [Project Pythia: A Community Update on Open and Sustainable Geoscientific Python Education](https://ams.confex.com/ams/103ANNUAL/meetingapp.cgi/Paper/421702) |
+| AMS   |  2023-01  | Max Grover | talk | [ARMing the Open Science Community with Radar Cookbooks: from the Colorado Rockies to the Gulf Coast and Beyond](https://ams.confex.com/ams/103ANNUAL/meetingapp.cgi/Paper/417388) |
+| AGU   |  2022-12  | Kevin Tyle | slides | [Project Pythia - Transforming Software Engineering Education for GeoScience](https://eppro01.ativ.me/src/EventPilot/php/express/web/planner.php?id=AGU22) |
+| AGU   |  2022-12  | Julia Kent | slides | [Project Pythia: A Pangeo Community Tool for Open-Source Education](https://docs.google.com/presentation/d/19oWV7LULijtIYObrNW3ccoRLNFV9lYA0APuPlXAx_z8/edit?usp=sharing) |
+| SciPy | 2022-07 | Kevin Tyle | slides | [A Community-built Training Resource for the Geoscientific Python Software Ecosystem](https://docs.google.com/presentation/d/1tyPkDVDKZX5BsWk9j-TTwiKT8mNQBBZG/edit?usp=sharing&ouid=114646835079460879999&rtpof=true&sd=true) |
+| ESDS forum |  2022-05  | Julia Kent | slides | [Project Pythia: A Community Learning Resource for Geoscientists](https://docs.google.com/presentation/d/1NGLFwqJdsu53CtsCqZLO3dxQtRcelOsm/edit?usp=sharing&ouid=107342162699810699865&rtpof=true&sd=true) |
+|  AMS  | 2022-01  | Drew Camron | slides | [Project Pythia: A community update](https://docs.google.com/presentation/d/1NuV5sI3oGhvuUt_s8hzmj0UA9MqCtlxWTADbJHjr9ow/edit?usp=sharing)     |
+|  AMS  | 2022-01  | Kevin Tyle | slides | [Leveraging Project Pythia in an Advanced Geoscience & Visualization Course](https://docs.google.com/presentation/d/1D8kkpsX4CE3rT5QQliH6JfKYeY76fT1gClIEzboxgko/)     |
+|  AMS  | 2022-01 | Max Grover | slides | [Rethinking CESM Diagnostics through the Lens of Earth System Data Science](https://docs.google.com/presentation/d/1aTw0DmaZ-7PQtWXxQqdik825r5mOoYRe/edit?usp=sharing&ouid=113419461755911727326&rtpof=true&sd=true) |
+|  AGU  | 2021-12 | Kevin Paul | e-poster | [Pangeo and Project Pythia: Helping Geoscientists Navigate the Scientific Python Ecosystem](https://agu2021fallmeeting-agu.ipostersessions.com/Default.aspx?s=CF-91-F4-F8-35-E4-B7-40-F2-8C-F6-86-76-97-11-02) |
+|  AGU  | 2021-12 | Kevin Paul | e-poster | [Project Pythia: A Resource to Help Geoscientists Navigate the Scientific Python Ecosystem](https://agu2021fallmeeting-agu.ipostersessions.com/Default.aspx?s=25-22-8E-6D-6E-CB-B4-E9-6D-08-78-2A-61-2F-62-09) |
+|  AGU  | 2021-12 | Julia Kent | abstract | [ESDS Educational Efforts](https://t.co/hQ1wGQZB18) |
+| Pangeo Showcase | 2021-06 | Brian Rose | video + slides | [Project Pythia: a community learning resource for Python-based computing in the geosciences](https://discourse.pangeo.io/t/june-23-2021-project-pythia-a-community-learning-resource-for-python-based-computing-in-the-geosciences/1601) |
+|  AMS  | 2021-01 | John Clyne | video | [Project Pythia: a community learning resource for geoscientists](https://youtu.be/_UxlrwB_evo)

_preview/453/_sources/blog.md

@@ -0,0 +1,3 @@
+# Blog
+
+This will be replaced by `ablog` so there's nothing here.

_preview/453/_sources/code_of_conduct.md

@@ -0,0 +1,55 @@
+# Code of Conduct
+
+## Our Pledge
+
+We, as contributors, creators, stewards, and maintainers (participants), of Project Pythia pledge to make participation in our software, system or hardware project and community a safe, productive, welcoming and inclusive experience for everyone. All participants are required to abide by this Code of Conduct. This includes respectful treatment of everyone regardless of age, body size, disability, ethnicity, gender identity or expression, level of experience, nationality, political affiliation, veteran status, pregnancy, genetic information, physical appearance, race, religion, or sexual orientation, as well as any other characteristic protected under applicable US federal or state law.
+
+## Our Standards
+
+Examples of behaviors that contribute to a positive environment include:
+
+- All participants are treated with respect and consideration, valuing a diversity of views and opinions
+- Be considerate, respectful, and collaborative
+- Communicate openly with respect for others, critiquing ideas rather than individuals and gracefully accepting criticism
+- Acknowledging the contributions of others
+- Avoid personal attacks directed toward other participants
+- Be mindful of your surroundings and of your fellow participants
+- Alert project administrators if you notice a dangerous situation or someone in distress
+- Respect the rules and policies of the project and venue
+
+Examples of unacceptable behavior include, but are not limited to:
+
+- Harassment, intimidation, or discrimination in any form
+- Physical, verbal, or written abuse by anyone to anyone, including repeated use of pronouns other than those requested
+- Unwelcome sexual attention or advances
+- Personal attacks directed at other guests, members, participants, etc.
+- Publishing others’ private information, such as a physical or electronic address, without explicit permission
+- Alarming, intimidating, threatening, or hostile comments or conduct
+- Inappropriate use of nudity and/or sexual images
+- Threatening or stalking anyone, including a participant
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Scope of this Code
+
+This Code of Conduct applies to all spaces managed by the Project whether they be physical, online or face-to-face. This includes project code, code repository, associated web pages, documentation, mailing lists, project websites and wiki pages, issue tracker, meetings, telecons, events, project social media accounts, and any other forums created by the project team which the community uses for communication. In addition, violations of this Code of Conduct outside these spaces may affect a person's ability to participate within them. Representation of a project may be further defined and clarified by project maintainers.
+
+## Community Responsibilities
+
+Everyone in the community is empowered to respond to people who are showing unacceptable behavior. They can talk to them privately or publicly. Anyone requested to stop unacceptable behavior is expected to comply immediately. If the behavior continues concerns may be brought to the project administrators or to any other party listed in the Reporting section below.
+
+## Project Administrator Responsibilities
+
+Project administrators are responsible for clarifying the standards of acceptable behavior and are encouraged to model appropriate behavior and provide support when people in the community point out inappropriate behavior. Project administrator(s) are normally the ones that would be tasked to carry out the actions in the Consequences section below.
+
+## Reporting
+
+Instances of unacceptable behavior can be brought to the attention of the project administrator(s) who may take any action as outlined in the Consequences section below.
+
+## Consequences
+
+Upon receipt of a complaint, the project administrator(s) may take any action deemed necessary and appropriate under the circumstances. Such action can include things such as: removing, editing, or rejecting comments, commits, code, wiki edits, email, issues, and other contributions that are not
+aligned to this Code of Conduct, or banning temporarily or permanently any contributor for other behaviors that are deemed inappropriate, threatening, offensive, or harmful. Project administrators also have the right to report violations to UCAR HR and/or UCAR’s Office of Diversity, Equity and Inclusion (ODEI), as well as a participant’s home institution and/or law enforcement. In the event an incident is reported to UCAR, UCAR will follow its Harassment Reporting and Complaint Procedure.
+
+## Attribution
+
+This Code of Conduct was originally adapted from the Contributor Covenant, version 1.4. We then aligned it with the UCAR Participant Code of Conduct, which also borrows from the American Geophysical Union (AGU) Code of Conduct. The UCAR Participant Code of Conduct applies to both UCAR employees as well as participants in activities run by UCAR. The original version of this for all software projects that have strong management from UCAR or UCAR staff is available on the UCAR website at [https://doi.org/10.5065/6w2c-a132](https://doi.org/10.5065/6w2c-a132). The date that it was adopted by this project was 20 December 2020. When responding to complaints, UCAR HR and ODEI will do so based on the latest published version. Therefore, any project-specific changes should follow the Process for Changes section above.