feat: reorg of org section

community/github/intro.md

@@ -1,11 +1,12 @@
+(github-intro)=
 # pyOpenSci GitHub Processes
 
 pyOpenSci has a suite of GitHub repositories (repos) that support pyOpenSci
-processes and content including:
+processes and content, including:
 
 * website content
 * tools that track contributors and keep the website up to date
 * peer review
 
-This section of the guidebook discusses our GitHub organization, and processes
+This section of the guidebook discusses our GitHub organization and processes
 for adding and managing content and infrastructure across the organization.

community/index.md

@@ -17,6 +17,7 @@ scientific Python community.
 
 Social Media <social>
 Slack <slack>
+Zenodo & Citation <zenodo>
 :::
 
 :::{toctree}

community/slack.md

@@ -1,3 +1,4 @@
+(pyos-slack)=
 # Slack - Day to Day communication
 
 We use Slack to communicate both as paid staff and within our community organization. Slack is a valuable tool for both asynchronous, synchronous, and remote communication.

community/social.md

@@ -1,25 +1,31 @@
+(community-social)=
+
 # pyOpenSci Social Media Platforms
+
 The 2024 North Star for pyOpenSci’s social media accounts is to raise general awareness of pyOpenSci in the broader open source community through both scheduled and ad hoc content that reflects our commitments to diversity and inclusion within the open source scientific Python community. Through these efforts we will also be supporting our mission of empowering scientists to create better software, thereby supporting more open and reproducible science.
 
 Until 2024, pyOpenSci has had an on and off social media presence since its inception in 2018. Although we’ve previously used Buffer to manage posting across platforms, we currently post directly on each individual site. Our current efforts are localized to [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci) (a Mastodon instance), although we are continuously evaluating other platforms and their compatibility with our community efforts.
 Social Accounts
 
 ## Social Accounts
+
 * **[LinkedIn:](https://www.linkedin.com/company/pyopensci)** LinkedIn is our primary social media platform as of 2024, as it is the place where the majority of the pyOpenSci community can be found. In addition to posting regularly on LinkedIn, we send out a weekly newsletter on LinkedIn that has shown a promising amount of growth its first few weeks of publication.
 * **[Fosstodon:](https://fosstodon.org/@pyOpenSci)** the pyOpenSci Fosstodon account is active, and generally has the same information as what’s posted on our LinkedIn account (albeit in a truncated form). We continue to grow our community on Fosstodon, and intend to keep investing in it as a social media platform.
 * **[Bluesky:](https://bsky.app/profile/pyopensci.bsky.social)** we posted consistently on Bluesky during the first quarter of 2024, however were ineffective at growing a community on the site. We plan to keep the account active with occasional posts, but Bluesky is not a current priority for our social media outreach efforts.
 * **[X:](https://twitter.com/pyopensci)** although we maintain an account on X, we do not actively post on the platform at this point in time due to both the lack of inclusivity on the platform, as well as community members moving elsewhere.
 
 ## Post types: evergreen vs. *ad hoc* content
+
 pyOpenSci will run both evergreen content campaigns as well as ad hoc campaigns. One of the major keys to success on social media is publishing on a regular cadence across a series of platforms. Evergreen content allows pyOpenSci to be in constant dialogue on social platforms, in turn generating larger interest in ad hoc posts.
+
 * Evergreen content is any content that can be prepared well in advance and does not have a timeframe for posting. Examples of evergreen content include:
-    * Volunteer spotlights
-    * Package showcases
-    * Information about pyOpenSci
-    * Python packaging
+  * Volunteer spotlights
+  * Package showcases
+  * Information about pyOpenSci
+  * Python packaging
 * *Ad hoc* content is any content that has a timing element to it, in that the content is only relevant for a specific amount of time. Examples of ad hoc content include:
-    * Calls for volunteers
-    * Live-posting at an event
-    * pyOpenSci content and event launches
+  * Calls for volunteers
+  * Live-posting at an event
+  * pyOpenSci content and event launches
 
 It’s important to note that *ad hoc* content can become evergreen content! For example, when the Python Packaging Guide was released, we did a full social media product launch (*ad hoc*), and throughout the year we plan to also spend time highlighting various parts of the guide (evergreen).

community/zenodo.md

@@ -0,0 +1,25 @@
+# Zenodo
+
+:::{admonition} How to cite pyOpenSci
+:class: tip
+
+pyOpenSci doesn't yet have an organization-level citation, but all of our resources and GitHub repositories are citable. To find a citation for a specific pyOpenSci resource, go to the repository in our GitHub organization and look at the top of the README.md file.
+:::
+
+Zenodo is a general-purpose research repository where anyone can publish outputs and receive a citable DOI (digital object identifier).
+
+pyOpenSci uses Zenodo to create citable entries for:
+
+* GitHub software repositories
+* Presentations by pyOpenSci staff and community members
+* Online educational resources, like our [Packaging guide](https://www.pyopensci.org/python-package-guide/)
+
+For GitHub repositories, pyOpenSci includes a Zenodo citation badge at the top of the README file, linking directly to the citation page. pyOpenSci also encourages all its software packages to use Zenodo to create a DOI for their Python packages.
+
+When major updates are made to resources, such as the Packaging guide, pyOpenSci creates a new release. Zenodo then generates an updated DOI specific to that release, allowing users to cite the latest version.
+
+## pyOpenSci Zenodo Community
+
+pyOpenSci maintains a [community group](https://zenodo.org/communities/pyopensci?q=&l=list&p=1&s=10&sort=newest) on Zenodo where both staff and community members can share content related to pyOpenSci, including presentations, blog posts, open education resources, software, and other materials. This allows contributors to receive a citable DOI while retaining ownership of their submissions.
+
+The pyOpenSci Zenodo community is moderated by pyOpenSci staff, who review and approve all suggested additions to ensure relevance and quality.

organization/branding.md

@@ -1,10 +1,11 @@
 # The pyOpenSci brand
 
 The pyOpenSci brand is playful and curious. It integrates a calm, gender-neutral color palette with illustrations and abstract primary shapes that are soft, round, and flowing.
+All of the elements that support our brand can be found in our Canva organization.
 
 ## Logos, colors, and fonts
 
-pyOpenSci stores its logos, brand colors, and font information in [Canva](https://www.pyopensci.org/handbook/organization/canva.html). However, we also store some of our logos and brand assets in a [publicly-shared Drive folder](https://drive.google.com/drive/folders/1m4cG3JLonP0mQ8y3pBaULMulpja-As0l?usp=drive_link) for community members to use as needed.
+pyOpenSci stores its logos, brand colors, and font information in [Canva](pyos-canva). However, we also store some of our logos and brand assets in a [publicly-shared Drive folder](https://drive.google.com/drive/folders/1m4cG3JLonP0mQ8y3pBaULMulpja-As0l?usp=drive_link) for community members to use as needed.
 
 ### pyOpenSci logos
 

organization/canva.md

@@ -1,4 +1,5 @@
-# pyOpenSci uses Canva as a shared graphic platform
+(pyos-canva)=
+# pyOpenSci uses Canva
 
 pyOpenSci has a nonprofit Pro license for [Canva](https://www.canva.com/), and uses the platform for:
 

organization/employee-onboarding.md

@@ -0,0 +1,38 @@
+# New Hire Onboarding
+
+The following needs to happen when a new team member joins pyOpenSci’s staff as core staff.
+
+## Community Initiatives Onboarding
+
+The new hire needs to meet with Community Initiatives HR and complete any training, fill out any paperwork that is required by Community Initiatives.
+
+## pyOpenSci onboarding process
+
+* **Create Employee Google Workspace Account:** An email should be created with the new hire's <name@pyopensci.org> should be created using the Google Workspace admin console.
+* **Add staff to shared Google Drives:** Within our workspace, the new hire should be added to: `pyos-shared`.
+
+* **Add the employee to email groups as needed**
+  * [admin@pyopensci.org](mailto:admin@pyopensci.org): used for administration tasks such as calls for hiring.
+  * [media@pyopensci.org](mailto:media@pyopensci.org): used for general social media work.
+
+### Provide permission to access
+
+* **Our pyOpenSci GitHub organization** In some cases the new hire may already have a GitHub account. So on the first day, ask what account they prefer to use for pyOpenSci work. You can filter notifications by organization repo and email so it could be that some wish to use their personal profile so activity profiles are concentrated. The email can be modified easily on an account.
+* **Add to [Asana](https://asana.com/)** - added to the pyOpenSci Operations team on Asana: we have a paid plan for Asana and it’s linked to GitHub issues. This is a great way to keep track of tasks (see more below on using Asana and tracking tasks).
+* **Invite to Slack:** Slack is our primary mode of communication day to day. Learn more about [how we use Slack](https://www.pyopensci.org/handbook/community/slack.html).
+* **Social media and content platform access as needed**
+  * Login credentials for LinkedIn, Mastodon, and BlueSky
+  * Added to YouTube channel at appropriate level
+
+### Announcing the new hire to the community
+
+* **Announce in Slack:** New staff will be introduced in the `#pyos-updates` slack channel and asked to share a bit about themselves.
+* **Add to website:** Update the data file with the new hire's name and information and add them as "staff". This will update them on the “Our pyOpenSci” community page.
+* **Introductory blog post:** New hires write brief blog posts introducing themselves to the community. The post can include topics such as: their work background, hobbies, why they joined pyOS, and what they’ll be doing with pyOS.
+* **Social media:** Post the announcement of the hire on social channels.
+
+## Staff check-ins
+
+When new members join the pyOpenSci team, they may need more up-front meeting time to adjust to the organization and our work environment. As such, when an employee starts, a standard weekly check-in time will be scheduled with their manager to discuss current tasks and how things are going.
+
+These meetings are a good time to ask for help or guidance, discuss challenges, and suggest ways to improve our workflows. The meeting cadence can be flexible, accommodating each employee's needs. We will move to that if we find that a bi-weekly meeting might be more productive. If weekly meetings continue to be useful, then we will stick to that schedule.