Merge branch 'main' into values

.github/workflows/add-help-wanted.yml

@@ -14,6 +14,7 @@ jobs:
         uses: actions/[email protected]
         with:
           project-url: https://github.com/orgs/pyOpenSci/projects/3
-          github-token: ${{ secrets.GHPROJECT_TOKEN }}
-          labeled: help-wanted, sprintable
+          # This is a organization level token so it can be used across all repos in our org
+          github-token: ${{ secrets.GHPROJECT_HELP_WANTED }}
+          labeled: help wanted, sprintable
           label-operator: OR

.pre-commit-config.yaml

@@ -23,7 +23,7 @@ repos:
 
   # Misc commit checks
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.5.0
+    rev: v4.6.0
     # ref: https://github.com/pre-commit/pre-commit-hooks#hooks-available
     hooks:
       # Autoformat: Makes sure files end in a newline and only a newline.
@@ -34,6 +34,6 @@ repos:
       - id: trailing-whitespace
 
   - repo: https://github.com/codespell-project/codespell
-    rev: v2.2.6
+    rev: v2.3.0
     hooks:
     - id: codespell

community/events/intro.md

@@ -0,0 +1,56 @@
+# Meetings & Events
+
+## pyOpenSci meetings
+
+pyOpensci staff regularly attend community meetings (e.g. SciPy meeting, PyCon US, etc). If the meeting is in person, some of the staff may be in person at the event while the community manager / others might be supporting the event remotely.
+
+In these instances, asynchronous communication and sharing of documents in an organized way is critical.
+
+### Event documents
+
+For every meeting, pyOpenSci staff should create a Google Drive folder, located in our pyos-shared drive, where meeting documents will be stored. These documents may include talk and workshop proposals, attendee signup lists, graphics used in social media and outreach posts and more content related to the event.
+
+Before an event, pyOpenSci staff will make sure this folder is shared and supporting documents are added to it. Often the folder will be created prior to the event to store talk, BoF (birds of a feather), Townhall and workshop proposals.
+
+:::{admonition} Team check in prior to an event
+:class: note
+
+Staff should also have a short check-in prior to an event to ensure that all documents, and elements needed for the event, are shared in the right place, appropriate permissions are granted, remote support needs for the event are clarified, etc.
+
+Because the internet might be an issue sometimes at an event, whomever is leading the event should always bring a pen and paper.
+:::
+
+## Event social media and graphics
+
+The community manager will manage online “comms” and social media during an event. However, it is important for whomever is attending the event in person to be in asynchronous communication via the pyOpenSci Slack about key activities, findings, new cool things, etc. to be posting about, promoting and highlighting.
+
+In some cases, an event might “pop up” last minute--such as an Open Space at PyCon. In this case, the person attending the event may want to modify and reuse graphics posted on social media to publicize the event.
+
+To support this case, an event folder in our online graphics platform, Canva, should be created prior to the event and shared with the pyOpenSci team. This event-specific folder will be where all graphics used to promote an event, both before, during and after, are stored. Using Canva as a central location for graphics makes it easier for the person at the event to make a quick change to a graphic, add a room number or a time for a pop up event, notify of any change in plans, etc. as needed.
+
+:::{admonition} Share the Canva folder with the pyopensci-canva-team
+:class: important
+
+Be sure to share the Canva folder with the `pyOpensci-canva-team` on Canva to ensure that the entire team has edit access to the graphics and can make last minute changes as needed!
+Please also be sure to name files using expressive words that make them easy to find / use / reuse.
+:::
+
+### Preparation prior to an event
+
+Prior to an in-person sprint, the following items should be created:
+
+1. A template "sign up" form, created in HubSpot and shared via a bit.ly shortlink, with data fields that we collect from participants. This allows us to track who attends and event and to followup with them after (if they wish to have communication with us after)
+1. A tabletop “card” that says pyOpenSci. You will need 2-3 cards on hand for any event in case participants are spread across a few tables. This card will be important for events like sprints, workshops and open spaces where pyOpenSci has one or more tables in a large room. It will signal to contributors that we are there and help people quickly find us.
+
+* The card should have a qr code that is dynamic (so we can update the url that it points to and reuse the cards). This will allow us to have participants scan the code using their phones, and add their names as participants in the event. Following the event we can then send a thank you message to each participant using MailChimp or HubSpot.
+
+:::{todo}
+will this work for events as we will want an event name associated with it but it would be annoying to make a new card for every event? UNLESS we make a bunch at once for all events for the year?
+
+We are currently pricing out a travel banner, to be used outside a space where pyOpenSci is running a workshop.
+An example of the [base/holder for the table top card](https://www.officedepot.com/a/products/5760240/American-Metalcraft-Stainless-Steel-Harp-Style/). We'll initially test out metal, as they will be less likely to break in transit, however acrylic options are also available.
+
+Cards will be designed and printed, all of which will contain, at minimum, the pyOpenSci logo, website address, and a QR code that links to all of our socials/mailing list. this way it'll give people a visual cue as to where pyOS is congregating, as well as the option to interact with us directly.
+
+Cards will be designed to be printed out on a home printer, or through MOO, and laminated when non-glossy paper is used.
+:::