From 91643ada5e758ec586116b1f3774b6196a7d4b74 Mon Sep 17 00:00:00 2001 From: Jesse Mostipak Date: Fri, 24 May 2024 15:44:56 -0500 Subject: [PATCH 1/7] Update README.md clarified governance to be governance handbook, and corrected the link to point to the new handbook URL (was pointing to /governance) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 1c58e2e..6fc3f7c 100644 --- a/README.md +++ b/README.md @@ -35,7 +35,7 @@ you are working through the content! ## How to setup -This repository contains the source files for the [pyOpenSci governance](https://pyopensci.org/governance). +This repository contains the source files for the [pyOpenSci governance handbook](https://pyopensci.org/handbook). ## Build the governance document locally From afdc053e7c6f58cf031c0c4f6fa37a6dbc83e085 Mon Sep 17 00:00:00 2001 From: Jesse Mostipak Date: Tue, 9 Jul 2024 10:45:27 -0500 Subject: [PATCH 2/7] external comms - email --- organization/external-communications.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 organization/external-communications.md diff --git a/organization/external-communications.md b/organization/external-communications.md new file mode 100644 index 0000000..0dbb25d --- /dev/null +++ b/organization/external-communications.md @@ -0,0 +1,22 @@ +# External Communications + +pyOpenSci uses a multitude of platforms for external communication, in order to both maintain communication with our current community, as well as grow our community. Our external communications fall under the broad categories of email, the pyOpenSci blog, pyOpenSci newsletters, and social media platforms. This section details each of those broad categories, as well as the specific platforms used within each, and provides relevant links and insights into the purpose, strategy, and associated processes for each platform. + +## Email +pyOpenSci does not send unsolicited bulk emails, and all emails contain an unsubscribe link. Emails from pyOpenSci are sent to communicate with potential volunteers, share the monthly version of the newsletter, and to keep registered event participants up-to-date on logistics. pyOpenSci will also reach out to event attendees with pre- and/or post-surveys, along with follow-up reminders, as needed. + +### Mailchimp + +pyOpenSci uses [Mailchimp](https://mailchimp.com/) as a catch-all bulk emailing service. Anyone interested in subscribing to the pyOpenSci mailing list and receiving our monthly newsletter can do so by [signing up here](https://eepurl.com/iM7SOM). We also use Mailchimp to communicate with individuals who have signed up to volunteer as a [reviewer](https://forms.gle/Mps4UsRHTyF66cdg7) and/or [editor](https://forms.gle/aFAMBjrdU7f7zMP89) as part of our [open software peer review process](https://www.pyopensci.org/about-peer-review/index.html). + +### EventBrite + +pyOpenSci uses [EventBrite](https://eventbrite.com) to manage event sign-ups. Anyone who has registered for a pyOpenSci event through EventBrite will be contacted through the EventBrite service regarding event updates and logistics. pyOpenSci may also upload EventBrite contacts to Mailchimp or SurveyMonkey for the purposes of sending out pre- and/or post-surveys. + +### SurveyMonkey + +[SurveyMonkey](https://www.surveymonkey.com/) is used to send out pre- and/or post-surveys to attendees of pyOpenSci events. This can include in-person or online events such as workshops, talks, and sprints. SurveyMonkey is used due to its ease of use, integration with HubSpot, and ability to send out survey reminder emails. + +### HubSpot + +[HubSpot](https://hubspot.com/) is pyOpenSci's customer relationship management (CRM) platform. Although HubSpot has email capabilities, pyOpenSci does not currently use this functionality. From fc68dbf4e2dd76862b8e685dc2beadf7d1e50dea Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 9 Jul 2024 15:46:46 +0000 Subject: [PATCH 3/7] =?UTF-8?q?'[pre-commit.ci=20=F0=9F=A4=96]=20Apply=20c?= =?UTF-8?q?ode=20format=20tools=20to=20PR'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- organization/external-communications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/organization/external-communications.md b/organization/external-communications.md index 0dbb25d..516016c 100644 --- a/organization/external-communications.md +++ b/organization/external-communications.md @@ -1,6 +1,6 @@ # External Communications -pyOpenSci uses a multitude of platforms for external communication, in order to both maintain communication with our current community, as well as grow our community. Our external communications fall under the broad categories of email, the pyOpenSci blog, pyOpenSci newsletters, and social media platforms. This section details each of those broad categories, as well as the specific platforms used within each, and provides relevant links and insights into the purpose, strategy, and associated processes for each platform. +pyOpenSci uses a multitude of platforms for external communication, in order to both maintain communication with our current community, as well as grow our community. Our external communications fall under the broad categories of email, the pyOpenSci blog, pyOpenSci newsletters, and social media platforms. This section details each of those broad categories, as well as the specific platforms used within each, and provides relevant links and insights into the purpose, strategy, and associated processes for each platform. ## Email pyOpenSci does not send unsolicited bulk emails, and all emails contain an unsubscribe link. Emails from pyOpenSci are sent to communicate with potential volunteers, share the monthly version of the newsletter, and to keep registered event participants up-to-date on logistics. pyOpenSci will also reach out to event attendees with pre- and/or post-surveys, along with follow-up reminders, as needed. From daf132be1cd605c0ac0ce0cdc35892d2ae8b8c35 Mon Sep 17 00:00:00 2001 From: Jesse Mostipak Date: Tue, 9 Jul 2024 10:52:28 -0500 Subject: [PATCH 4/7] updated index toc for external comms --- organization/index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/organization/index.md b/organization/index.md index 9eec44a..c5c8143 100644 --- a/organization/index.md +++ b/organization/index.md @@ -1,3 +1,10 @@ # Organization In this section we will add organizational processes. + +:::{toctree} +:hidden: +:caption: External Communications + +Email +::: \ No newline at end of file From 8c7d68890bb28a9ef6e010a536f4ebee93ebc6f1 Mon Sep 17 00:00:00 2001 From: Jesse Mostipak Date: Tue, 9 Jul 2024 10:56:42 -0500 Subject: [PATCH 5/7] removed extraneous text --- organization/index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/organization/index.md b/organization/index.md index c5c8143..571104f 100644 --- a/organization/index.md +++ b/organization/index.md @@ -1,7 +1,5 @@ # Organization -In this section we will add organizational processes. - :::{toctree} :hidden: :caption: External Communications From df98196eb39927fe957b8f36a168bd899d38d2c9 Mon Sep 17 00:00:00 2001 From: Jesse Mostipak Date: Tue, 9 Jul 2024 10:57:29 -0500 Subject: [PATCH 6/7] toc fix --- organization/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/organization/index.md b/organization/index.md index 571104f..c2ec180 100644 --- a/organization/index.md +++ b/organization/index.md @@ -4,5 +4,5 @@ :hidden: :caption: External Communications -Email +External Communications ::: \ No newline at end of file From 22647b0d8074a5b5a5386c61627236233c42e896 Mon Sep 17 00:00:00 2001 From: Jesse Mostipak Date: Tue, 9 Jul 2024 11:14:30 -0500 Subject: [PATCH 7/7] linktree and blog added --- organization/external-communications.md | 55 +++++++++++++++++++++++++ 1 file changed, 55 insertions(+) diff --git a/organization/external-communications.md b/organization/external-communications.md index 516016c..92ceb61 100644 --- a/organization/external-communications.md +++ b/organization/external-communications.md @@ -20,3 +20,58 @@ pyOpenSci uses [EventBrite](https://eventbrite.com) to manage event sign-ups. An ### HubSpot [HubSpot](https://hubspot.com/) is pyOpenSci's customer relationship management (CRM) platform. Although HubSpot has email capabilities, pyOpenSci does not currently use this functionality. + +## Linktree + +All of our active sites, platforms, and social media accounts are located in a Linktr.ee account, which is shared in the Description of our social media sites where applicable. + +Accessing and editing Linktr.ee: +* Login at linktr.ee (credentials are in Bitwarden) +* Click on “Admin” +* Add new links by clicking on the “Add link” button, or edit existing links by clicking on the pencil next to the title and//or URL +* Current linktr.ee: https://linktr.ee/pyopensci + +## Blog + +Our [blog lives on our website](https://www.pyopensci.org/blog), which is driven by Jekyll and hosted currently on GitHub pages. [The repo url is here](https://github.com/pyOpenSci/pyopensci.github.io). + +### Blog goals + +The goals of our blog include: +* Writing for the broader open science community +* Sharing news and updates related to pyOpenSci +* Build domain authority through SEO strategies + +### How to add a new blog post + +There are two main groups of people who submit blog posts to the pyOpenSci blog: pyOpenSci employees, and package authors/maintainers for packages that have been accepted into the [pyOpenSci ecosystem](https://www.pyopensci.org/python-packages.html). If you are not in one of these two groups, but would like to submit a blog post to pyOpenSci, please reach out to us at [media@pyopensci.org](mailto:media@pyopensci.org) to discuss your post prior to writing it and submitting a PR. + +**Writing a blog post** + +The following processes for writing a blog post should be used by both pyOpenSci employees as well as guest posts: +1. Fork the pyOpenSci website repo: https://github.com/pyOpenSci/pyopensci.github.io. +2. Work on your blog post locally. Be sure to include alt text as needed, and create an author page if you do not already have one. +3. Submit a pull request from your fork of the website repo to https://github.com/pyOpenSci/pyopensci.github.io. +4. Make sure that the blog post passes CI checks that look for spelling errors, broken links and more. Please note that occasionally the `htmlproofer` check will fail because the URL does not exist yet. We have implemented a fix for this, but it occasionally does not work. +5. Request review of the blog post. A member of the pyOpenSci staff should always review any new content being added to the website. +6. Once you have an approving review, the pull request can be merged. In the case of guest blog posts, a memember of the pyOpenSci team will merge your post. + +pyOpenSci has GitHub organization-wide policies in place that ensure all pull requests are generally reviewed prior to being merged. In some instances we may bypass those if the PR is a small fix or critical update. In most cases a review is preferred. Please contact the Executive Director and Founder, Leah Wasser, with any questions or needs for clarification. +{: .notice } + +**A note on guest blog posts** + +Anyone who has had their package accepted into the pyOpenSci ecosystem is encouraged to submit a blog post (or series of blog posts) about their review experience and/or their package. When reviewing a guest blog post, pyOpenSci staff will only make necessary edits for: +* pyOpenSci branding +* post clarity + +### Promoting blog posts + +All blog posts should be promoted, regardless of whether or not they were written by a guest or a pyOpenSci employee! For promotion, coordinate with the Community Manager to ensure that there’s a tailored message for each of the following platforms: +* Slack +* Discourse +* BlueSky +* LinkedIn +* Fosstodon + +In addition to pyOpenSci promotions, we monitor social media for any personal posts authors have created to promote their post, boost accordingly.