<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Global Team :: R-Ladies organizational guidance</title>
    <link>https://guide.rladies.org/global-team/index.html</link>
    <description>Guidance for global team volunteers supporting and coordinating chapters. 🚋</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://guide.rladies.org/global-team/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Onboarding new chapter organizers</title>
      <link>https://guide.rladies.org/global-team/onboarding/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/onboarding/index.html</guid>
      <description>Goal The goal of this activity is to start a conversation with prospective organisers, answer any questions and send information on how to get a new chapter started. This activity can be carried out by a team of 2 people, to split the workload and guarantee requests are addressed timely.&#xA;What to do Monitor the email: chapters@rladies.org. As part of the Onboarding Team, the messages to this account are forwarded to the email address you provided during your own onboarding process.</description>
    </item>
    <item>
      <title>Editing and publishing the Code of Conduct</title>
      <link>https://guide.rladies.org/global-team/code-of-conduct/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/code-of-conduct/index.html</guid>
      <description>The Code of Conduct would only be edited with the agreement of the global leadership.&#xA;Now, technically, its source including translations live at https://github.com/rladies/.github/blob/master/CODE_OF_CONDUCT.md&#xA;How to use the Code of Conduct Linking to it Link to either the Code of Conduct on the R-Ladies website or the source on GitHub (if you want to refer to a translation that isn’t on the R-Ladies website yet).&#xA;Reproducing it within your website If you use the Code of Conduct somewhere that’s supposed to be long-lived, be careful to have a process in place to ensure that the Code of Conduct rendered on your thing keeps in sync with the code of conduct source.</description>
    </item>
    <item>
      <title>General Airtable guide</title>
      <link>https://guide.rladies.org/global-team/airtable/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/airtable/index.html</guid>
      <description>The R-Ladies Global team uses Airtable for a lot of internal project tracking, from the Rotating Curation on Bluesky, to Directory management, the Abstract Review programs, as well as other internal processes. This document is intended for our team members to learn some general tips about Airtable, and more project specific documentation is elsewhere.&#xA;A really nice introduction to Airtable can be found on youtube.</description>
    </item>
    <item>
      <title>Directory management</title>
      <link>https://guide.rladies.org/global-team/directory/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/directory/index.html</guid>
      <description>The R-Ladies directory source data is in a private repository containing potential personal information. If you have a local clone of this, please ensure it is stored securely.&#xA;Notes to Self Entries from Males: Consider how to handle entries submitted by males. Should we delete these files during editing/reviewing? Previewing Updated Files: Ensure a method to check updated previews once files are changed.</description>
    </item>
    <item>
      <title>Meetup account management</title>
      <link>https://guide.rladies.org/global-team/meetup/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/meetup/index.html</guid>
      <description>Goal The goal of this activity is to create and monitor chapters on the meetup.com platform. The person in charge needs to be able to commit a few hours weekly. Ideally, this will become a team of at least 2 people, to split the workload and guarantee requests are addressed any time of the year.&#xA;What to do Monitor the notifications of @rladies/meetup-pro on GitHub. You were added to that team during your onboarding process to R-Ladies Global. The Chapter Onboarding team will mention @rladies/meetup-pro in the issue of the new-chapters-onboarding repository where the prospective chapter is being created.</description>
    </item>
    <item>
      <title>Monitoring chapter activity</title>
      <link>https://guide.rladies.org/global-team/monitoring/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/monitoring/index.html</guid>
      <description>Goal The goal of tracking chapter activity is to identify inactive chapters and help them to get started. If nothing can be done for a particular chapter, the chapter should be retired within 9months/1 year of inactivity.&#xA;Background Chapters can be divided into 3 categories, according to the frequency of their events:&#xA;Unbegun (created in the past 6 months, no events yet)&#xA;Active (have run an event in the past 6 months or have an upcoming event in the near future)</description>
    </item>
    <item>
      <title>Social Media Management</title>
      <link>https://guide.rladies.org/global-team/social-media-management/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/social-media-management/index.html</guid>
      <description>This section covers the tools, templates, and guidelines used by the RLadies+ communications team to manage social media across platforms.&#xA;Platforms RLadies+ maintains official accounts on:&#xA;Platform Handle Primary use Bluesky @rladies.org Primary social media Mastodon @RLadiesGlobal@fosstodon.org Fediverse community LinkedIn RLadies+ Professional network Instagram @rladies Visual content YouTube RLadies+ Global Recorded talks The WeAreRLadies rotating curation runs separately on Bluesky.&#xA;Brand voice We sound like a friend who’s excited about what the community is doing — not a corporation issuing announcements. Our voice is direct, warm, and grounded. We’re a movement but we don’t take ourselves too seriously.</description>
    </item>
    <item>
      <title>R-Ladies chapter mentoring program guidelines</title>
      <link>https://guide.rladies.org/global-team/mentoring/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/mentoring/index.html</guid>
      <description>Objective 🎯 The main objective of the R-Ladies chapter mentoring program is to help organisers conduct successful meetups and keep their chapters active.&#xA;Organizing an R-Ladies chapter involves a series of non-trivial tasks that can feel overwhelming to a new organiser. However, a number of experienced R-Ladies organisers are willing to mentor new ones, and can provide great advice.&#xA;For mentors, this is an opportunity to help to build community, learn about the realities of other chapters, gain experience as a mentor and contribute to R-Ladies as an organisation.</description>
    </item>
    <item>
      <title>Managing R-Ladies Finance</title>
      <link>https://guide.rladies.org/global-team/finance/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/finance/index.html</guid>
      <description>Donations When someone sends an email inquiring about larger donations, offer to&#xA;provide them the routing/account number for a direct wire transfer,&#xA;or if they are in the US and prefer to send a check, we can provide them our non-profit HQ address in Oakland, California.&#xA;How to acknowledge the donation?&#xA;Of course, thank the donator in the email communication.&#xA;If the donator is comfortable with a public acknowledgement, add their name to our future website.</description>
    </item>
  </channel>
</rss>