-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Containing only the English version, for the moment
- Loading branch information
1 parent
ca18fcf
commit 436be2b
Showing
48 changed files
with
4,778 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
.Rproj.user | ||
.Rhistory | ||
.RData | ||
.Ruserdata |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
language: r | ||
cache: packages | ||
pandoc_version: 1.19.2.1 | ||
|
||
before_script: | ||
- chmod +x ./_build.sh | ||
- chmod +x ./_deploy.sh | ||
|
||
script: | ||
- ./_build.sh | ||
- ./_deploy.sh |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
# (PART) Version en Français {-} | ||
|
||
# Code de conduite | ||
|
||
La **série d’ateliers et le symposium R du CSBQ** ont l’objectif de fournir un environnement accueillant et favorable à toutes les personnes, indépendamment de leur origine ou de leur identité. | ||
|
||
Les participants, les présentateurs et les organisateurs de l'atelier et d'autres activités connexes **acceptent** le présent code de conduite lorsqu'ils sont présents à une activité liée à un atelier. | ||
|
||
Nous ne tolérons pas les comportements irrespectueux, intimidants ou gênants pour les autres. | ||
|
||
Nous ne tolérons pas la discrimination contre (y compris, sans toutefois s'y limiter) l'orientation sexuelle, le handicap, l'apparence physique, la citoyenneté, l'origine ethnique, la situation familiale, la religion ou les croyances (ou l’absence), l'appartenance à une minorité, l'âge, l'éducation et la situation socio-économique. | ||
|
||
Ce code s'applique à tous les espaces gérés par l'atelier ou affiliés à l'atelier, y compris, sans toutefois s'y limiter, les ateliers, les listes de diffusion et les forums en ligne tels que GitHub, Slack et Twitter. | ||
|
||
Les participants aux ateliers qui enfreignent ces règles peuvent être sanctionnés ou expulsés, sans remboursement, à notre discrétion. | ||
|
||
#### Comportement prévisible {-} | ||
|
||
Tous les participants et presentateurs doivent faire preuve de respect et de courtoisie envers les autres. Toutes les interactions doivent être professionnelles, quelle que soit la plate-forme: en ligne ou en personne. Afin de créer un environnement d'apprentissage positif et professionnel, nous encourageons les comportements suivants dans tous les ateliers et plateformes: | ||
|
||
* Utiliser un langage accueillant et inclusif; | ||
* Soyez respectueux des différents points de vue et expériences; | ||
* Accepter gracieusement les critiques constructives; | ||
* Concentrez-vous sur ce qui convient le mieux à la communauté; | ||
* Faites preuve de courtoisie et de respect envers les autres membres de la communauté. | ||
|
||
|
||
#### Comportement inacceptable {-} | ||
|
||
Les exemples de comportement inacceptable des participants et des presentateurs à tout événement / plate-forme d'atelier incluent: | ||
|
||
* les commentaires écrits ou verbaux qui ont pour effet d'exclure des personnes en raison de leur appartenance à un groupe spécifique; | ||
* amener une personne à craindre pour sa sécurité, par exemple par le harcèlement criminel ou l'intimidation; | ||
* menaces violentes ou langage dirigé contre une autre personne; | ||
* l'affichage d'images sexuelles ou violentes; | ||
* attention sexuelle importune; | ||
* contact physique non consensuel ou importun; | ||
* insultes ou rabaissements; | ||
* blagues sexistes, racistes, homophobes, transphobes, capacitables ou exclusives; | ||
* incitation à la violence, au suicide ou à l'automutilation; | ||
* continuer à initier une interaction (y compris des photographies ou des enregistrements) avec quelqu'un après avoir été invité à s'arrêter; | ||
* publication de communication privée sans consentement. | ||
|
||
Si un participant adopte un comportement harcelant, nous pouvons prendre toutes les mesures que nous jugeons appropriées, y compris avertir le délinquant ou l’expulser de l'atelier sans remboursement. Les participants à qui il est demandé de mettre fin à tout comportement de harcèlement doivent se conformer immédiatement. | ||
|
||
Si vous êtes harcelé.e ou remarquez que quelqu'un.e d'autre est harcelé.e ou pour toute autre question, veuillez contacter immédiatement l'un des organisateurs de l'atelier. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
# Préparation | ||
|
||
*Nous sommes en train d'ajouter des modifications à cette page. Veuillez revenir plus tard.* | ||
|
||
## Avant l'atelier | ||
|
||
*Nous sommes en train d'ajouter des modifications à cette page. Veuillez revenir plus tard.* | ||
|
||
## Pendant l'atelier | ||
|
||
*Nous sommes en train d'ajouter des modifications à cette page. Veuillez revenir plus tard.* | ||
|
||
## Après l'atelier |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Presentation | ||
|
||
*Nous sommes en train d'ajouter des modifications à cette page. Veuillez revenir plus tard.* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Recevoir votre prix | ||
|
||
*Nous sommes en train d'ajouter des modifications à cette page. Veuillez revenir plus tard.* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
# (PART) English version {-} | ||
|
||
# Code of conduct {#codeofconduct} | ||
|
||
The **QCBS R Workshop Series** and the **QCBS R Symposium** are venues dedicated to providing a welcoming and supportive environment for all people, regardless of background or identity. | ||
|
||
Participants, presenters and organizers of the workshop series and other related activities **accept** this Code of Conduct when being present at any workshop-related activities. | ||
|
||
*We do not tolerate behaviour that is disrespectful or that excludes, intimidates, or causes discomfort to others.* | ||
|
||
We do not tolerate discrimination or harassment based on characteristics that include, but are not limited to, gender identity and expression, sexual orientation, disability, physical appearance, citizenship, ethnic or social origin, pregnancy, familial status, religion or belief (or lack thereof), membership of a minority, age, education and socioeconomic status. | ||
|
||
It applies to all spaces managed by or affiliated with the workshop, including, but not limited to, workshops, email lists, and online forums such as GitHub, Slack and Twitter. | ||
|
||
Workshop participants violating these rules may be sanctioned or expelled from the workshop without a refund at our discretion. | ||
|
||
#### Expected behaviour {-} | ||
|
||
All participants and presenters are expected to show respect and courtesy to others. All interactions should be professional regardless of platform: either online or in-person. In order to foster a positive and professional learning environment we encourage the following kinds of behaviours in all workshop events and platforms: | ||
|
||
* Use welcoming and inclusive language | ||
* Be respectful of different viewpoints and experiences | ||
* Gracefully accept constructive criticism | ||
* Focus on what is best for the community | ||
* Show courtesy and respect towards other community members | ||
|
||
#### Unacceptable behaviour {-} | ||
|
||
Examples of unacceptable behaviour by participants at any workshop event/platform include: | ||
|
||
* written or verbal comments which have the effect of excluding people on the basis of membership of any specific group; | ||
* causing someone to fear for their safety, such as through stalking or intimidation; | ||
* violent threats or language directed against another person; | ||
* the display of sexual or violent images; | ||
* unwelcome sexual attention; | ||
* nonconsensual or unwelcome physical contact; | ||
* insults or put-downs; | ||
* sexist, racist, homophobic, transphobic, ableist, or exclusionary jokes; | ||
* incitement to violence, suicide, or self-harm; | ||
* continuing to initiate interaction (including photography or recording) with someone after being asked to stop; | ||
* publication of private communication without consent. | ||
|
||
If a participant or a presenter engages in harassing behaviour, we may take any action we deem appropriate, including warning the offender or expulsion from the workshop without a refund. Participants and presenters asked to stop any harassing behaviour are expected to comply immediately. | ||
|
||
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact one of the workshop organizers immediately. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,118 @@ | ||
# Preparation {#intro} | ||
|
||
Being a presenter for the QCBS R Workshop Series requires preparation and proactive communication with the participants registered for the workshops. Below, there is a list of points that will help you prepare for the workshops. We ask you to **carefully** read them. | ||
|
||
## Before the workshop | ||
|
||
### Two weeks before the workshop | ||
|
||
1. Obtain the list of registered participants to your workshop and determine the number of presenters that can be allocated to your workshop: | ||
|
||
Number of Participants | Number of Presenters | Payment per Presenter | Allocated funds to the workshop | ||
:-------------: | :-------------: | :-------------: | :-------------: | ||
1 to 5 | 1 | $125 | $125 | ||
6 to 14 | 2 | $125 | $250 | ||
15 or more | 3 | $125 | $375 | ||
|
||
> *If the number of registered presenters is lower than the number of presenters that can be allocated to your workshop, do not hesitate to invite other graduate students and post-doctorate fellows (members of the QCBS) that you think could instruct the workshop with you!* | ||
> *Note that the **maximum** payment per presenter is of 125$.* | ||
2. Familiarize yourself with the material available within the [wiki]() and the [presentation pages](). | ||
|
||
* **You must be *very* comfortable with the content and the presentation concerning the workshop as of the date of your presentation.** | ||
|
||
* It is **your responsability** to integrate be familiar with the material. | ||
|
||
* Use [wiki pages]() and RMarkdown [presentations]() as reference material for your workshop. Do not hesitate to complement your knowledge with other references and material. | ||
|
||
* The presentations come with a *presenter mode*, which allow for presenter notes and a more dynamic instruction. Go to our "[Using the presenter mode]()" section to learn more. | ||
|
||
3. Read the code of conduct (Section \@ref(codeofconduct)). | ||
|
||
### One week before the workshop | ||
|
||
1. Obtain the most [up-to-date list]() of registered participants for your workshop. | ||
|
||
2. Send the *standardized message* below to all participants, replacing the fields when required. | ||
|
||
* *NOTE:* Carbon-copy all your communication to the other instructors of your workshop. | ||
* *NOTE:* You must send the message below **at least** 7 days before the date of your presentation. | ||
* *NOTE:* You must **NOT** remove information from the following text. | ||
|
||
> Message subject: [QCBS R Workshop Series] Workshop #**X** – **Name of the Workshop** (Friday, **Month Day**) | ||
> Hello! | ||
> | ||
> You are registered for the QCBS R Workshop #**XXX** that will be given at **NAME OF THE UNIVERSITY** this coming Friday at **HH:MM** **PM or AM**. In preparation for the workshop please note the following: | ||
> | ||
> 1) The workshop will be given in **XXX** building, room **XXX**. | ||
> | ||
> 2) Please come with your laptop and the relevant programs (R and RStudio) installed. You can also download the script we will be using in this workshop at the following website: **https://wiki.qcbs.ca/r_workshopXX** | ||
> | ||
> We recommend that you execute the entire script at least once before coming to the workshop to make sure that everything works on your laptop and to download and install all the libraries we will be using during the workshop. | ||
> | ||
> 3) If you can no longer make it to the workshop, please advise us 5 days in advance by email, otherwise, you will receive a 100$ penalty which will be billed to your supervisor. | ||
> | ||
> 4) If you are not a member of the QCBS please bring receipt of payment to the workshop. | ||
> | ||
> 5) Internet access should not be necessary to follow the workshop if you executed the script before coming to make sure you had downloaded all the necessary R libraries. If you are taking the workshop at a different institution than your own and would like to have access to the internet during the workshop, please ensure that you can connect to the eduroam network (more info here: http://qcbs.ca/wiki/eduroam). If you do not have access to eduroam or to the university’s network, we may not be able to provide you with temporary access to the internet. | ||
> | ||
> 6) If you have any questions concerning this workshop or its venue, please reach one of the presenters so you can be helped to the best of our ability!. | ||
> | ||
> Thanks, and looking forward to Friday! | ||
> | ||
> **YOUR NAME(S)**. | ||
## During the day of the workshop | ||
|
||
1. Arrive *at least* 15 minutes before the beginning of your workshop to prepare the presentation room and project your presentation; | ||
2. Take attendance; | ||
3. Collect receipts from non-members; | ||
4. Start your presentation **on time**: | ||
|
||
* Start by introducing yourself (telling the participants who are you and what do you do); | ||
* Reassure attendants that they can raise their hands and pose questions to you during the workshop; | ||
* *More guidelines to come*. | ||
|
||
## After the workshop | ||
|
||
> We kindly ask you to do the steps below *immediately* after your presentation. | ||
1. Send the feedback form to the attendants of your workshop; | ||
|
||
> Message subject: [QCBS R Workshop Series] Evaluation Form for the Workshop #**X** – **Name of the Workshop** | ||
> Hi again! | ||
> | ||
> Thank you for coming to the workshop (#X) on **Name of the Workshop**. | ||
> | ||
> We kindly ask you to take a few minutes to [provide your feedback](https://docs.google.com/forms/d/12LiuK1hhCpuDULBYStlXoJi6K1sKTVeGzPiD5DVGdds/edit?urp=gmail_link) on the last workshop. | ||
> | ||
> This process is very valuable to us because we can understand where the workshop needs improvement. | ||
> | ||
> Your comments and suggestions are really appreciated and are read with attention. | ||
> | ||
> Thank you again! | ||
> | ||
> With our kindest regards, | ||
> YOUR NAMES | ||
2. [Provide your feedback](https://goo.gl/forms/85TXCiQ9tW9nvq922) on the workshop you have just instructed. | ||
|
||
3. Send the message below to the registered participants to the no-show participants (i.e. the participants that have not sent you a message cancelling their registration and that were absent during your workshop). | ||
|
||
* **NOTE**: Send **separate** messages to each one of the registered absences (i.e. do *not* include other participants in your communications). | ||
|
||
> Message subject: [QCBS R Workshop Series] Absence during the Workshop #**X** – **Name of the Workshop** | ||
> Dear **NAME OF THE REGISTERED PARTICIPANT**, | ||
> | ||
> I am contacting you because you were absent from today's workshop (#X) on **Name of the Workshop**, which was given at **Location**. | ||
> | ||
> According to the policy of the QCBS R Workshop Series, registered participants that do not cancel their attendance *at least* 5 days in advance by email incur a 100$ penalty that is billed to their supervisor's institutional account. | ||
> | ||
> We kindly ask you to contact us about your absence at your earliest convenience. | ||
> | ||
> With regards, | ||
> YOUR NAME(S) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Presentation | ||
|
||
*We are adding modifications to this page. We kindly ask you to come back later.* |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# Receiving your award | ||
|
||
All workshop presenters receive a **Learning and Development Award** from the **Québec Centre for Biodiversity Science (QCBS)**. | ||
|
||
You must follow these stepts to receive your award payment: | ||
|
||
1. **First, complete the [payment sheet]()**. You can refer to the [compensation standards]() section within this protocol to know the budget allocated to your workshop. *Remember that each presenter receives an award of a maximum of $125 per workshop instructed*. | ||
|
||
2. **Second, complete and sign this [form]()**. Note that you are considered as a “*Payee*” for the purposes of the development and instruction of a workshop belonging to the QCBS R Workshop Series. Name your file to "`YOURLASTNAME_PayeeForm.pdf`". | ||
|
||
3. **Third, fill out the attached invoice**. | ||
|
||
> You must write your *name*, *e-mail*, *phone number*, *complete address* (including postal code, city and province), *total balance* and *description of your work* (e.g., "Description: Lead presenter of workshops 1 and 2"; "Unit Cost: $ 125 per workshop"; "Total: $ 250"). | ||
> For the moment, do not write anything next to "P.O." (which stands for Purchase Order). | ||
> Name your invoice to "`YOURLASTNAME_RWorkshop_Invoice.docx`". | ||
4. **Fourth, send both the form and the invoice to [email protected]** (Helen Elina is the Administrative Associate of the QCBS). If you have already been registered as an employee or a self-employed, independent contractor for the McGill University, please indicate it within the message you send to Dr. Elina. You can use the following message model for your message: | ||
|
||
> Message subject: Learning and Development Award - QCBS R Workshop Series | ||
> Dear Dr. Elina, | ||
> | ||
> You will find attached to this message my payee form and the invoice concerning the workshop(s) that I instructed as part of the QCBS R Workshop Series. | ||
> | ||
> I HAVE NOT or I HAVE BEEN registered as an employee or a self-employed, independent contractor for the McGill University. | ||
> | ||
> I certify that the information attached to this message is true and correct to the best of my knowledge. | ||
> | ||
> With kind regards, | ||
> | ||
> YOUR NAME | ||
|
||
5. After a few weeks, McGill University's Procurement Services will send you an e-mail containing a purchase order. You must **copy the purchase order number** and paste it to the fields *Purchase Order* and *Invoice Number* of the invoice that you sent to Helen. | ||
|
||
6. **Export the invoice to PDF**, and send it to [email protected]. You should receive a check in the address you included within your invoice. | ||
|
||
To prevent any delays, please double-check your information and confirm that all fields concerning yourself are filled within both forms. | ||
|
Oops, something went wrong.