👋 Welcome! This is a dedicated space with information on the strategies, procedures, and activities of the Parsl community
This playbook is not intended to capture every process. Instead, it serves as a guide to our community by providing an overview of how we operate and pointing to ways and resources where you can learn more. It was developed in 2024 and is updated annually.
Our community playbook is licensed under CC BY 4.0
Components of our playbook are adapted from the Parsl Community Playbook (https://github.com/Parsl/community-playbook).
This README is set up as a resource hub, directing you to the necessary resources.
- Items that have the upward arrow icon (
↗️ ) signify that it's an external link. - Information regarding technical project activities live on our Github organization page
↗️ and in our project documentation↗️ .
| Resource Title | What's in This Section? |
|---|---|
| About Us | Provides an overview of our community, the motivation behind our project, and features a community sketch that offers a high-level view of how our community engages with each other. |
| Code of Conduct |
Describes the rules and policies for participating and contributing to our community, including our pledge, standards, and responsibilities to fostering a welcoming environment and the scope, enforcement, and attribution of our CoC. |
| Connect With Us | Describes how to connect with the community, including detailed information on our communications channels and platforms and where and when you can connect with fellow users, collaborators, and partners. |
| Funding and Support | Provides information on how Parsl is funded and supported. |
| Governance |
Describes how our community is governed, provides details on our committees' roles and responsibilities, and contributors. Our committees include Coordination, Code Maintenance, Training and Outreach, Communications, and Community Champions. |
| Project Roadmap |
Describes our planned activities and goals for our project, which includes code maintenance, new features and integrations, tutorials, training, and user support, and longer-term objectives. |
Items that are similar in purpose are organized into resource folders to make them easier to locate. Below, you will find an overview of these folders and the respective items that live in them.
This resource folder holds items that provide instruction, tutorials, etc., for community activities.
| Item Name | What's Included? |
|---|---|
| Community Blog | Describes the purpose of our community blog. It also provides an overview of content guidelines, the editorial review process, and instructions on how to contribute to the blog. |
| Contributing |
We welcome contributions to our project! This guide describes where to start, coding conventions, testing, development process, Git hooks, and project documentation. |
| Slack Quickstart | Describes how to join and use our Slack workspaces and channels. |
Our Open Community Calls are hosted on Zoom every two weeks @ 11 a.m. CST. These calls allow us to get together to share project progress, discuss challenges, troubleshoot technical issues, and provide community updates. These calls are mostly unstructured to allow space and time for people to drop by, ask questions, and provide input.
| Item Name | What's Included? |
|---|---|
| Meeting Notes | This subfolder houses our finalized meeting notes from our open community calls. |
| Recorded Talks | Provides info and links to recordings of talks and presentations from past open community calls. |
This resource folder is dedicated to holding general files, such as images. These files add context and additional content to our playbook sections and items. Since it's dedicated to holding general files, a breakdown of what items live in it is not provided.
We want to hear from you! If you have suggestions on resources you would like included in our playbook, please add a comment to our discussions thread to share your thoughts with us!