Merge policies repo into larger repo

CODE_OF_CONDUCT.md

@@ -1 +1,101 @@
-This project, as part of the **Open Life Science community**, is committed to providing a **welcoming, friendly, and harassment-free** environment for everyone to **learn and grow by contributing**. As a result, we require participants to follow our **code of conduct**, which may be found [in the policies repository]({{ site.github.owner_url }}/policies-procedures-and-docs/blob/main/CODE_OF_CONDUCT.md).
+This project, as part of the **Open Life Science community**, is committed to providing a **welcoming, friendly, and harassment-free** environment for everyone to **learn and grow by contributing**. As a result, we require participants to follow our **code of conduct**.
+
+This code of conduct outlines our expectations for participants within the
+community, as well as steps to reporting unacceptable behavior. We are committed
+to providing a welcoming and inspiring community for all and expect our code of
+conduct to be honored. Anyone who violates this code of conduct may be banned
+from the community.
+
+Our open source community strives to:
+
+- **Be friendly and patient.**
+
+- **Be welcoming**: We strive to be a community that welcomes and supports
+  people of all backgrounds and identities. This includes, but is not limited to
+  members of any race, ethnicity, culture, national origin, colour, immigration
+  status, social and economic class, educational level, sex, sexual orientation,
+  gender identity and expression, age, size, family status, political belief,
+  religion, and mental and physical ability.
+
+- **Be considerate**: Your work will be used by other people, and you in turn
+  will depend on the work of others. Any decision you take will affect users and
+  colleagues, and you should take those consequences into account when making
+  decisions. Remember that we're a world-wide community, so you might not be
+  communicating in someone else's primary language.
+
+- **Be respectful**: Not all of us will agree all the time, but disagreement is
+  no excuse for poor behavior and poor manners. We might all experience some
+  frustration now and then, but we cannot allow that frustration to turn into a
+  personal attack. It’s important to remember that a community where people feel
+  uncomfortable or threatened is not a productive one.
+
+- **Be careful in the words that we choose**: We are a community of
+  professionals, and we conduct ourselves professionally. Be kind to others. Do
+  not insult or put down other participants. Harassment and other exclusionary
+  behavior aren't acceptable. This includes, but is not limited to: Violent
+  threats or language directed against another person, Discriminatory jokes and
+  language, Posting sexually explicit or violent material, Posting (or
+  threatening to post) other people’s personally identifying information
+  (“doxing”), Personal insults, especially those using racist or sexist terms,
+  Unwelcome sexual attention, Advocating for, or encouraging, any of the above
+  behavior, Repeated harassment of others. In general, if someone asks you to
+  stop, then stop.
+
+- **Try to understand why we disagree**: Disagreements, both social and
+  technical, happen all the time. It is important that we resolve disagreements
+  and differing views constructively. Remember that we’re different. Diversity
+  contributes to the strength of our community, which is composed of people from
+  a wide range of backgrounds. Different people have different perspectives on
+  issues. Being unable to understand why someone holds a viewpoint doesn’t mean
+  that they’re wrong. Don’t forget that it is human to err and blaming each
+  other doesn’t get us anywhere. Instead, focus on helping to resolve issues and
+  learning from mistakes.
+
+### Diversity Statement
+
+We encourage everyone to participate and are committed to building a community
+for all. Although we will fail at times, we seek to treat everyone both as
+fairly and equally as possible. Whenever a participant has made a mistake, we
+expect them to take responsibility for it. If someone has been harmed or
+offended, it is our responsibility to listen carefully and respectfully, and do
+our best to right the wrong.
+
+Although this list cannot be exhaustive, we explicitly honor diversity in age,
+gender, gender identity or expression, culture, ethnicity, language, national
+origin, political beliefs, profession, race, religion, sexual orientation,
+socioeconomic status, and technical ability. We will not tolerate discrimination
+based on any of the protected characteristics above, including participants with
+disabilities.
+
+### Reporting Issues
+
+If you experience or witness unacceptable behavior, or have any other concerns,
+please report it by contacting the organisers - Bérénice, Malvika and Yo.
+(team@openlifesci.org).
+
+To report an issue involving one of the members, please email one of the members individually
+(berenice@openlifesci.org, malvika@openlifesci.org, yo@openlifesci.org).
+
+All reports will be handled with discretion. In your report please include:
+
+- Your contact information.
+
+- Names (real, nicknames, or pseudonyms) of any individuals involved. If there
+  are additional witnesses, please include them as well. Your account of what
+  occurred, and if you believe the incident is ongoing. If there is a publicly
+  available record (e.g. a mailing list archive or a public IRC logger), please
+  include a link.
+
+- Any additional information that may be helpful.
+
+After filing a report, a representative will contact you personally, review the
+incident, follow up with any additional questions, and make a decision as to how
+to respond. If the person who is harassing you is part of the response team,
+they will recuse themselves from handling your incident. If the complaint
+originates from a member of the response team, it will be handled by a different
+member of the response team. We will respect confidentiality requests for the
+purpose of protecting victims of abuse.
+
+### Attribution & Acknowledgements
+
+This code of conduct is based on the Open Code of Conduct from the TODOGroup.

openseeds/ols-5/cohort-emails/README.md

@@ -0,0 +1,3 @@
+# Cohort emails
+
+Emails sent on a weekly basis to cohort members sharing what's happening in a given week. 

openseeds/ols-5/cohort-emails/graduations.md

@@ -0,0 +1,27 @@
+[rest of this mail in English] 
+
+Hi all!
+
+We're heading towards the end of OLS-5 and that means it's time to start planning for graduations! Here's what you need to know. 
+
+We have five graduation slots coming up in June and July. In order to get an OLS-5 certificate, you must participate in a graduation. 
+- Registration: https://www.eventbrite.com/cc/ols-5-graduations-432229 <-- PLEASE REGISTER FOR A SLOT ASAP SO WE CAN PLAN
+- Time zones: https://pad.sfconservancy.org/p/ols-5-graduations 
+
+If you **have been able to attend/watch calls** (cohort calls, mentoring calls, etc.) and complete some assignments: Please register for whichever graduation slot works best for you! 
+
+If you **haven't attended/watched many calls** and/or are missing some assignments: Don't worry, you can still graduate! We are hosting several catch-up sessions over June and early July. Please come to at least two sessions (time/dates here: and in the OLS calendar https://pad.sfconservancy.org/p/ols-5-catchup-sessions ) and be prepared to work on (or discuss) assignments. These will be very loosely structured calls, giving you a chance to chat to OLS community members, including cohort members and OLS organisers, and catch up on OLS things in a low-pressure way. 
+
+View all the session dates / times in the OLS calendar or this etherpad: https://pad.sfconservancy.org/p/ols-5-catchup-sessions Still can't attend? email te...@openlifesci.org or y...@openlifesci.org and we'll help out. 
+
+**¿Habla español? (Speak Spanish?)** - if you can, please register for graduation 5. We're in the process of arranging two translators, one English -> Spanish, and one Español -> Ingles. English speakers are welcome to present at this call too, but priority will be given to Spanish speakers if needed. <-- PLEASE REGISTER ASAP SO WE CAN GIVE DETAILS TO OUR TRANSLATORS
+
+We will have limited slots for the presenters at each call, therefore, please register as a presenter (choose the “Presenter (OLS-5 project leader” option) for one call only where you will share your work and graduate from the cohort. 
+
+Would you like to invite anyone outside of OLS to join and watch your graduation? Please share the above registration page links with them - they can register (as viewers) to participate in the call(s). We’ll also invite all OLS-5 mentors and experts! 
+
+If you’ve experienced a delay or impact of any kind, from COVID or any other life events affecting the wellbeing of you, your family, or your friends - let us know (te...@openlifesci.org or a DM on Slack), and we’ll put things on pause and arrange to wrap up graduations when things are a bit calmer. 
+
+## What do I do at a graduation?! 
+We have a grad guide - check it out here: https://github.com/open-life-science/policies-procedures-and-docs/blob/main/cohort-procedures-and-templates/graduation-guide.md - and you can admire previous graduations on YouTube: https://www.youtube.com/c/OpenLifeSci/playlists - there are four graduation playlists from OLS-1 to OLS-4. 
+

openseeds/ols-5/cohort-emails/week-05.md

@@ -0,0 +1,33 @@
+# Subject: [OLS-5 week 5] Mentor call and optional GitHub training
+
+---------------
+
+Hey all!
+
+## Last week: 
+
+We had a cohort call (notes), with Mayya Sundukova co-hosting the call, and guest speakers Hao Ye on open licensing, Raniere Silva on READMEs, and D Sarah Stamps on contributing guidelines and codes of conduct. If you were unable to attend, please review the notes, and make sure to watch the recording on YouTube - it should be on our YouTube channel by the end of Monday 28 April. 
+🎉 We also voted on a cohort name: OLS-5 is cohort “Hope” - in your language it might be  cohort “Asha”/”आशा“ (Hindi), “Hoffen”/”Hoffnung” (German), "Esperanza"/”ilusión” (Spanish), "Tikva" תִקוָה (Hebrew), “Speranza” (Italian), “надежда”/”Nadezhda” (Russian), “ITXAROPENA” (Basque), “Hopen (Dutch), "희망"/”Hui-mang” (Korean), “希望”/”Hei Mong” (Chinese/Cantonese) and “Espoir” (French) (did we miss your language? Let us know in Slack).
+
+## Next week - Everyone:
+
+Meet with your mentor! Spend a few minutes chatting with your mentors about inviting an expert to a mentor meeting in week 7 or 9 to offer advice and insights - this could be someone from the OLS expert list or someone you or your mentor knows.
+
+## Next week - Optional:
+
+Monday 28th GitHub Training: We have an optional GitHub training cohort call. Come along if you are new to GitHub, if you’d like to learn about social and collaborative aspects of GitHub, or if you’d like to share your expertise with others! As usual, we will record the call for those who can’t make it.
+
+- Notes with joining link: https://bit.ly/ols-5-week-05 
+- Time zone: https://arewemeetingyet.com/Berlin/2022-03-28/18:00/week-05 
+- Website: https://openlifesci.org/ols-5/schedule#week-05 
+
+### Before this meeting:
+Create a GitHub account (if you don’t have one already) - https://github.com/
+
+Finally, don’t forget there are a few more changing clocks/timezones over the next few days. 
+
+Questions, worries, concerns, ideas? Email team@openlifesci.org or book in a few minutes to chat (open equally to project leads/mentees/experts/mentors).
+
+Your Open Life Science Team,
+
+Bérénice, Emmy, Malvika, Yo

openseeds/ols-5/cohort-emails/week-06.md

@@ -0,0 +1,24 @@
+# Subject: [OLS-5 week 6] Cohort call Open Science I: project development
+
+---------------
+Hello Cohort Esperanza!
+
+## Next week: 
+
+We will have our Open Science I: Project Development cohort call, with several experienced guest speakers. We will discuss agile project development/management plans (Renato Alves) and introduce different practices in open-source hardware (Hong Phuc Dang), open-source software (Andrew Stewart), and open data (Lilly Winfree).
+
+- Notes with joining link: https://bit.ly/ols-5-week-06 
+- Time zone: https://arewemeetingyet.com/Berlin/2022-04-04/18:00/week-06 
+- Website: https://openlifesci.org/ols-5/schedule#week-06 
+
+## This week:
+
+We hope that you had a great time catching up with your mentors, discussing your assignments, and sharing your understanding of how the assignments apply to your community!
+We also had a GitHub skill-up training call ([syllabus](https://openlifesci.org/ols-5/schedule#week-05), [notes](https://bit.ly/ols-5-week-05), and [video](https://www.youtube.com/watch?v=90BOler9hqI)) for folks who are new to GitHub. Please use Slack (#technical-help or #ols-5-general) to ask questions and receive help in troubleshooting.
+
+Start getting ready to bring your project online in the next few weeks through GitHub, [GitHub Pages](https://pages.github.com/), [WordPress](https://wordpress.com/), [Google Sites](https://sites.google.com/), or other suitable ways (if you haven’t done that already). If you need help with this, connect with us on Slack.
+
+Feeling lost, need some more personal discussion, or want someone to listen to your ideas/plan/concerns? Email team@openlifesci.org or [book in a few minutes to chat](https://calendly.com/yo-yehudi/ols-chat-with-yo?month=2022-04) (open equally to project leads/mentees/experts/mentors). 
+
+Your Open Life Science Team,
+Bérénice, Emmy, Malvika, Yo

openseeds/ols-5/cohort-emails/week-07.md

@@ -0,0 +1,29 @@
+Subject: [OLS-5 week 7] Mentor call and an optional Q&A call!
+---------------
+
+Dear cohort [आशा / Asha](https://dict.hinkhoj.com/shabdkhoj.php?word=%E0%A4%86%E0%A4%B6%E0%A4%BE&ie=UTF-8),
+
+This week:
+
+We had a cohort call: “Open Science I: Project Development and Introduction to Working Open”. Guest speakers Renato Alves, Andrew Stuart, Lilly Winfree and Hong Phuc Dang shared their experience in applying iterative project management methods, and managing and developing open software, data and hardware. If you were unable to attend, the recording will be on YouTube by end of day Monday 11 April. In the meantime you can review the [notes](https://bit.ly/ols-5-week-06) (thank you Festus for co-hosting this call!)
+
+To help you break down your project’s milestones using agile development and management methods, [we have an assignment for you](https://docs.google.com/document/d/1FFU3ZngDl_Rh1V979qvnKMQSgyAZ0VnvPhCBcu7CSL8/edit?usp=sharing) (make a copy for your project). 
+
+Next week - everyone: Meet with your mentor! 
+You should invite an expert to this week’s call and/or prepare to invite another one for week 9. If you are not sure who to invite, please contact us (team@openlifesci.org) so that we can help you identify one from the OLS expert list or someone we may know in our network. 
+
+Prepare to meet an expert: We have a guide to help you prepare notes that you should share with the invited expert in your invitation email. This will allow the experts to assess what to expect at the call and how best they can share their skills and insights with you: https://github.com/open-life-science/policies-procedures-and-docs/blob/main/cohort-procedures-and-templates/expert-guide.md 
+
+Next week - optional: Open Q&A call
+We’re now almost in the 7th week of the program! We have discussed many topics and open science concepts and imagine that you have many questions, and ideas that you might want to discuss. Come along to our open Q&A call to share those with the OLS team:
+
+- Notes with joining link: https://bit.ly/ols-5-week-07 
+- Time zone: https://arewemeetingyet.com/Berlin/2022-04-13/11:00/week-07 
+- Website: https://openlifesci.org/ols-5/schedule#week-07
+
+Questions, worries, concerns, ideas? Email team@openlifesci.org or [book in a few minutes to chat](https://calendly.com/yo-yehudi/ols-chat-with-yo) (open equally to project leads/mentees/experts/mentors). 🌻
+
+Your Open Life Science Team,
+Bérénice, Emmy, Malvika, Yo
+
+

openseeds/ols-5/cohort-emails/week-08.md

@@ -0,0 +1,57 @@
+Subject: [OLS-5 week 8] Cohort call, Community design for inclusivity
+
+---------------
+
+TO: OLS + SPEAKERS:
+-------
+
+Hello Tikva/תִּקְוָה Cohort!
+
+Last week was a mentor call. Hopefully, you’ve had the chance to talk about how progress is going and discuss questions regarding assignments or your project.
+
+## Next week:
+
+Next week on Wednesday 20 April is our cohort call: Community design for inclusivity. Guest speakers Chad Sansing and Anelda van der Walt will be talking about Mountain of engagement, community interactions, Personas and pathways, and welcoming new contributors. 
+
+
+- Notes with joining link: https://bit.ly/ols-5-week-08 
+- Time zone: https://arewemeetingyet.com/Berlin/2022-04-20/11:00/week-08 
+- Website: https://openlifesci.org/ols-5/schedule#week-08 
+
+As usual, if you’re unable to make this call we’ll upload the recording to the OLS YouTube channel by end of day Monday 25 April. .
+
+## 📚 Assignments so far
+We hope you are making time to do your assignments in the context of your projects. Please update your issues (https://github.com/open-life-science/ols-5/issues) to ask for feedback, question or support as needed. We encourage you to also connect with others on our Slack workspace.
+If you’ve been having trouble keeping up with the assignments, don't worry. You can always go back and reflect upon the assignments in the next weeks or in the future - it may surprise you how often we refer back to these lessons! Please remember that the main goal here is to learn and understand the wider application of open science concepts.
+
+## Before this cohort call:
+
+- Create a project development plan for your project: Assignment to help you use Agile methods to break down your milestones into smaller tasks and define a timeline for your milestones.
+- You can explore how to manage your tasks using project management or kanban tool like GitHub projects (short intro), Trello, Asana or Zenhub in GitHub
+- Make sure that by now you have added a license, contribution guideline, and selected a Code of Conduct in your GitHub repository. If you feel stuck and don’t know where you start, take a look at this repo to see a basic recommended structure of an open-source project.
+- Look up two other projects and comment on their issues and share feedback on their Open Canvas and README
+
+Feeling lost, need some more personal discussion, or want someone to listen to your ideas/plan/concerns, book in a few minutes to chat 🗣 (open equally to project leads/mentees/experts/mentors).
+Questions, worries, concerns, ideas? Email team@openlifesci.org. 📢
+
+Your Open Life Science Team,
+
+Bérénice, Emmy, Malvika, Yo
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+