Skip to content

Commit

Permalink
Merge branch 'main' into moon-rlady-patch-1
Browse files Browse the repository at this point in the history
  • Loading branch information
moon-rlady authored Oct 23, 2024
2 parents 2dcdda9 + 5be4182 commit 86d8b82
Show file tree
Hide file tree
Showing 8 changed files with 54 additions and 35 deletions.
3 changes: 2 additions & 1 deletion .zenodo.json
Original file line number Diff line number Diff line change
Expand Up @@ -99,7 +99,8 @@
"orcid": "0000-0001-8016-1469"
},
{
"name": "Columbus, Alyssa"
"name": "Columbus, Alyssa",
"orcid": "0000-0002-5510-8364"
},
{
"name": "Ravi, Janani",
Expand Down
2 changes: 2 additions & 0 deletions config.toml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ defaultContentLanguage = "en"
enableEmoji = true
pygmentsUseClasses=true
ignoreFiles = ["\\.Rmd$", "\\.Rmarkdown$", "_files$", "_cache$", "index\\.html", '\.knit\.md$', '\.utf8\.md$']
enableGitInfo = true

[module]
[[module.imports]]
Expand All @@ -17,6 +18,7 @@ home = [ "HTML", "RSS", "JSON"]

[params]
editURL = "/~https://github.com/rladies/rladiesguide/edit/main/content/"
githubsource = "/~https://github.com/rladies/rladiesguide/blob/main/content/"
description = "R-Ladies Organizational Guidance"
author = "R-Ladies Global Team"
showVisitedLinks = true
Expand Down
4 changes: 2 additions & 2 deletions content/about/datacamp/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ We also do not promote the use of DataCamp or offer its products (even if they a

For more context on the disapproval of DataCamp by the R-Ladies organization, please refer to the two statements on our blog.

* [R-Ladies Global's disapproval of DataCamp](https://blog.rladies.org/post/statement-about-datacamp/)
* [R-Ladies Global's disapproval of DataCamp](https://rladies.org/news/2019-04-08-statement-about-datacamp/)

* [R-Ladies Global's response to the DataCamp Assessment Report](https://blog.rladies.org/post/datacamp-third-party-review/)
* [R-Ladies Global's response to the DataCamp Assessment Report](https://rladies.org/news/2019-10-22-datacamp-third-party-review/)

{{< tweet 1114507499728769024 >}}

Expand Down
4 changes: 2 additions & 2 deletions content/comm/blog/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,10 +109,10 @@ the post series of the 2018 IWD project. It shows in the posts list and in the
post page.
- **Tags**: Post tags. They should include meaningful information; for recurrent
posts please follow previous tags. 4 or 5 tags is a good number.
[Tags](http://blog.rladies.org/tags/).
[Tags](https://rladies.org/tags/).
- **Categories**: Post categories. Like tags but the theme is more general. This
field is currently not visible and is optional.
[Categories](http://blog.rladies.org/categories/).
[Categories](https://rladies.org/categories/).

All of the information will be shown in the post yaml, and can also be edited later.

Expand Down
4 changes: 2 additions & 2 deletions content/comm/iwd/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,9 +16,9 @@ The goals of this chapter is to document our previous efforts for folks who migh

## Information about previous campaigns

* [Behind the scenes of R-Ladies IWD2018 Twitter action!](https://blog.rladies.org/post/ideation_and_creation/) -- tweets featuring all R-Ladies from the R-Ladies directory. Take-home message: sign up in our directory.
* [Behind the scenes of R-Ladies IWD2018 Twitter action!](https://rladies.org/blog/conclusion/) -- tweets featuring all R-Ladies from the R-Ladies directory. Take-home message: sign up in our directory.

* [IWD 2019 Twitter Action](https://blog.rladies.org/post/blog_iwdtwitter_2019/) -- tweets featuring all R-Ladies chapters. In Spanish [Acción de Twitter para el IWD 2019](https://blog.rladies.org/post/blog_iwdtwitter_2019_es/). Take-home message: how to create an R-Ladies chapter.
* [IWD 2019 Twitter Action](https://rladies.org/blog/2019-03-25-blog_iwdtwitter_2019/) -- tweets featuring all R-Ladies chapters. Take-home message: how to create an R-Ladies chapter.

* IWD 2020 had [tweets featuring R-Ladies lessons](/~https://github.com/rladies/IWD#catalog-the-meetup-material-in-github-from-the-chapters-and-tweet-this-material-during-the-campaign). [Shiny app](https://yabellini.shinyapps.io/RLadiesLesson/). Take-home message: share and re-use (depending on the licence) materials from R-Ladies meetups.

Expand Down
56 changes: 29 additions & 27 deletions content/organization/events/online/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,52 +88,54 @@ At the very bottom you should see some buttons -- click on the 'Claim Host' butt

{{< figure src="enter-key.png" alt="Screenshot of the 'enter key' form in the Zoom interface" >}}

### Tips for Running the Zoom meeting
### Tips for running the Zoom meeting
{{% notice note %}}
These guidance has been updated based on experiences from the Baltimore, Irvine, NYC, and Santa Barbara chapter guidelines, specifically to address issues with trolls in zoom meetings.
{{% /notice %}}

:eyes: After becoming Host, we suggest that you:

:eyes: After becoming the Host, we suggest that you:
- Enable the waiting room.

- Admit your co-organisers (if they are still in the waiting room) and
make them co-host so that they can manage bad actors with you if
necessary. **Being several to run an online meeting makes things easier (e.g. one organizer can keep an eye on the chat).**
- Admit your co-organizers from the waiting room and
make them co-hosts so that they can manage bad actors with you if
necessary. **Having multiple co-organizers run an online meeting makes things much easier (e.g., one organizer can keep an eye on the chat).**
It also makes it possible for your co-host to claim host if you for some reason disconnect or experience other technical difficulties.
We recommend being at minimum one co-host to help you.
We recommend having (at a minimum) one co-host to help you. For larger events, you may consider three to four co-hosts.

- Cross-reference the Meetup RSVP list with names of folks in the waiting room before admitting them into the meeting. (Before this step, encourage all members of your Meetup group to add their real first and last names to their profiles along with a profile picture.)

- Make organizers easy to recognize.
Introduce yourselves at the beginning, add "Organizer - " to your name.
This is important for participants for different requests for help and for being able to report incidents related to the code of conduct.
Introduce yourselves at the beginning, and add "Organizer - " to your name.
This is important, as it helps participants more easily request assistance and report incidents related to the code of conduct.

- Do the same for your presenter so that they can share their screen
- Make your presenter a co-host as well so that they can share their screen
even if regular participants cannot.

We have set the meeting options to prevent trolling as best as possible
(e.g., *participants are muted on entry, participants who have been
removed from the meeting can't rejoin, and we've disabled file
transfers, screen sharing for participants, and also virtual
backgrounds*). With the latest version of the zoom client, the host has
an extra security control menu where they can adapt a lot of these
settings during the meeting (e.g., *turning on/off the waiting room,
chat, and screen sharing*).

- Enable Close Captions: On the Zoom Rooms controller, tap the Captions icon (a square with the text _CC_). You may need to tap the More (...) icon first to see the option.

:zombie: If you do have to deal with trolls:
:zombie: We have set the meeting options to prevent trolling as best as possible
(e.g., *enabling the waiting room feature by default; participants are muted on entry and must request permission to unmute; participants who have been
removed from the meeting can't rejoin; disabling participant file
transfers, private messages (only messages to everyone or to the hosts only are allowed), screen sharing, profile pictures, and virtual
backgrounds*). With the latest version of the Zoom client, the Host has
an extra security control menu where they can adapt a lot of these
settings during the meeting (e.g., *turning on/off the chat and screen sharing*).

- Mute everyone and don't let them unmute (uncheck "allow participants
to unmute themselves" when muting all).
However, if you do have to deal with trolls:

- Remove the participant (hover your mouse over their name, click
"more" and click "remove").
"more," and then click "remove.")

- Lock the meeting so no one can come in (select "more" under
participants and "lock meeting").

- Email our code of conduct team (reporting [at] rladies [dot] org) after the meeting to let us know what happened. By reporting incidents like these to us, we can better prevent them in the future.

Lastly, the link to book the online meetup is **not to be shared
publicly** as it's only intended for organisers.
publicly** as it's only intended for organizers.

{{% notice warning %}}
**Like for in-person event, be respectful of participants' privacy.**
**Like for in-person events, be respectful of participants' privacy.**
If you want to save the Zoom chat, ask participants for their permission at the beginning of the event.
Advise participants to not take photos of the Zoom screen to publish on social networks unless permission is collected from all people appearing in the screenshot.
{{% /notice %}}
Expand Down Expand Up @@ -182,7 +184,7 @@ but the stream won't be publicly listed and there won't be notifications sent to

Running an event (or part of an event) especially dedicated to socializing might be great for everyone in these difficult times!

Here are some tips mostly from R-Ladies NYC.
Here are some tips mostly from R-Ladies NYC:

* Dedicating an entire event to "virtual social networking" help make it clear that the event is about getting to know each other.

Expand Down Expand Up @@ -224,7 +226,7 @@ Outside of Zoom you could try out platforms such as [gather.town](https://gather

{{< tweet 1299296290266849281 >}}

* [How to organise and run an awesome deaf accessible virtual event?](https://hearmeoutcc.com/deaf-accessible-virtual-events/)
* [How to organize and run an awesome deaf accessible virtual event?](https://hearmeoutcc.com/deaf-accessible-virtual-events/)

### Tooling

Expand Down
2 changes: 1 addition & 1 deletion content/organization/events/speakers/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ weight: 53

* Remember the [rules about Prioritization of Underrepresented/Minority Genders](/about/mission/#r-ladies-rules--guidelines).

* In line with R-Ladies’ Mission Statement and with our [Black Lives Matter Statement](https://blog.rladies.org/post/2020-06-06-blm/)
* In line with R-Ladies’ Mission Statement and with our [Black Lives Matter Statement](https://rladies.org/news/2020-06-06-blm/)
to achieve participation and representation in our events of generally excluded groups, taking into account the intersectionality of gender, race, language and geography; for these reasons we request:

- In chapter events, invite speakers of diverse race, language and geography (i.e., avoid a one year period with all white speakers at the chapter events).
Expand Down
14 changes: 14 additions & 0 deletions layouts/_default/single.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
{{ partial "header.html" . }}

<div class="notices info"><p>Last modification: {{ .Lastmod.Format "2006-01-02" }} (<a href="{{ .Site.Params.githubsource }}{{ .File.Path }}" target="_blank">View source</a>)</p></div>

{{ .Content }}

<footer class="footline">
{{with .Params.LastModifierDisplayName}}
<i class='fas fa-user'></i> <a href="mailto:{{ $.Params.LastModifierEmail }}">{{ . }}</a> {{with $.Date}} <i class='fas fa-calendar'></i> {{ .Format "02/01/2006" }}{{end}}
</div>
{{end}}
</footer>

{{ partial "footer.html" . }}

0 comments on commit 86d8b82

Please sign in to comment.