# Week 15: Group 2 - Looking for the note's link for the group 1: https://hackmd.io/@openlifesci/ols-2-week-15-gr1 ###### tags: `OLS-2` `cohort calls` `project-leads` :earth_asia: Cohort call --- **Call time** : 17:30 - 18:30 UTC ([see in your time](https://arewemeetingyet.com/London/2020-12-10/17:30/week-15-rehearsal-2)) **Hosts** : Malvika, Yo, Emmy **Syllabus** : [Week-15](https://openlifesci.org/ols-2/schedule/#week-15) <!---update this---> **JOIN THE CALL** (using Zoom): https://us02web.zoom.us/j/82819983583?pwd=Wk1MZVRKbkV5eW5WSjVnd29aTXpBQT09 Dial by your location +1 929 205 6099 US (New York) +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington D.C) +1 312 626 6799 US (Chicago) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) **Meeting ID:** 828 1998 3583 **Passcode:** 993801 Find your local number: https://us02web.zoom.us/u/kcsDRsVKNf - Please note that this call will be recorded - The video will be available on the [YouTube channel](https://www.youtube.com/openlifesci) in the next days - Turn on your webcam if you don't mind sharing your face (or off if you do!) ## Information **During this cohort call, we will:** - Start by introducing how to give and receive constructive feedback - Have the group-1 participants present their project through 5 minutes presentation - Share feedback on the project and presentation to help prepare for the final graduation call **Before this meeting** - Come prepared to share a 3 mins presentation of your project - it doesn't have to be a polished or finished. - Your presentation can be in the form of a demo, short 1-2 slides presentation or walk through your website - This should only be a highlight and not the entire presentation (your graduation presentation next week will be 5 minutes long) ### Sign up below - _Name / Project / social handles (twitter, GitHub, etc.) /_ [_emoji mood _](https://emojipedia.org/) - Joyce & Tina/ Open Innovation in Life Sciences/ T: @openlifescience/ 🎄 - Kendra Oudyk / Open Science Office Hours / T: @koudyk_ GH: koudyk / 🏃‍♀️ - Ismael, Laura and Sophia / Turing Way Guide to Ethical Research - Stephen Klusza/Synthetic Biology Chassis for Open Domain Use/ t: @codebiologist/ 🥱 - Malvika / OLS / malvikasharan / :zzz: - Paul & Neha / Embedding Accessibility in The Turing Way Open Source Community Guidance - Bailey Harrington / Chronic Learning / gh: @baileythegreen, tw: @ChronicLearning, @baileythegreen - Danny Garside/ [Registered Reports in Primate Neurophysiology](https://github.com/da5nsy/Registered-Reports-in-Primate-Neurophysiology) /gh:da5nsy t:@da5nsy / ✨ - Yo / OLS / <3 - Karega Pauline/The-Hub-Portal/ gh:@karegapauline / t:@KaregaP - Harriet Natabona /covid-19 immunology database/ gh:@natty2012/ t: @hnatabona :wave: Welcome --- Host: Emmy (3 minutes) **Icebreaker question** *What's the best piece of advice you've ever been given?* - _Name / answer_ - Malvika & Pauline: "Take one day at a time" - Lorena from OLS-2 mentor team - Kendra: "Slow is smooth and smooth is fast" (Navy SEALS, I thnk) and "Choose your own adventure" (outdoor leadership) - Laura: "if you want someone to do something for you, make it as easy as possible for them to do it" - my primary school music teacher (I think she was trying get us to get permission slips signed by our parents, but it's generally applicable!) - Sophia: “The only way to run a marathon is one step at a time” (which is along the same lines) - Bonus: “Best way to learn is to recognise that you always have something to learn.” - Danny: "When you're struggling to help yourself, help someone else." - Bailey: There is a lot of power in being the note taker. - Joyce: "Don't eat yellow snow..." - Neha : I should really make a note of these things, because I cannot remember! Whoa. Probably something along the lines of "if you have to troubleshoot code, it probably just a comma..." -- very encouraging when you're nervous :P - Stephen: "Wear latex gloves when cutting jalapeno peppers" - Danny: Haha I use a knife and fork! - Malvika: :laughing: - Joyce: habanero too... - ✏️ Giving feedback --- Malvika (⏰ 5 min) _Part of building a an open community is asking for & giving feedback to your contributors._ - Sometimes it can be hard to receive feedback, especially negative feedback. - Feedback is most effective when the people involved share ground rules and expectations. ![](https://i.imgur.com/IdLRJab.png) **We recommend using the 2x2 paradigm for feedback** - Provide at least one piece of constructive (not negative) and one piece of positive feedback each for content and delivery. | Aspects | Content | Delivery | | -------- |:------- | -------- | | Positive | | | | Negative | | | **Reference:** Suggested Rubric for Demonstrations from the carpentries Instructor Training](https://carpentries.github.io/instructor-training/demos_rubric/) ✏️ Silent GDoc-ing and +1ing (5 minutes) **Why is feedback important?** * It's impossible to learn if we don't know what our successes/failures are +2 * It helps you improve. It can also start a discussion and this can help you grow - it can be in your presentation skills, but also the content and other aspects. * it helps it helps it helps it helps it helps it helps it helps it helps it helps * To improve! There is always space to improve! * to be your best self * to put forth your best effort in communication and ideas in open science * * To know whether we are going in the right direction, or toward the correct end goal. * * * **What happens when we don't give feedback?** * It sends the message that we don't care +1 * In addition to the above, you may be left wondering if people don't care, or they didn't understand what you were trying to do/convey. You cannot further engage with the audience or content, nor can you improve yourself. * People are left not knowing whether there are issues they should address. * It think, feedback is around us all the time. Every time we speak to a person, employee, etc., we communicate feedback. In actuality, it’s impossible not to give feedback. * Laura: nothing gets improved and nobody learns anything * People can't improve (and we can't articulate where people need improving) * we lose direction or move around in circles * to resolve/prevent conflict **What happens if we only give critical feedback / areas of improvement?** * It can be demoralizing and doesn't acknowledge that work was done, regardless of the quality * It discourages participation and drive in individuals who may have obstacles that are not visible that could impact the quality of their work * People become overwhelmed * Fear and anxiety kick in so you don't share your work anymore * It can be demotivating, it creates more anxiety. You also don't get an idea of your strengths and what you did well and can count on/improve even further. * discouragement and nothing moves forward **What happens if we only give praise?** * People may think that everything is amazing and nothing should be changed, which may or may not be true. * It's hard to improve * It can be hard to believe! There's always _something_ to do better +1 (it doesn't feel genuine) * It makes people think you don't care enough to actually critically engage (it's easy to zone out for a presentation, and then just say nice general things after) * It's not helpful. * If there are mistakes and incorrect information, you're setting the person up for 'failure' * no-one learns anything and there’s a risk people get over-confident in their own abilities * It doesn't challenge you to do better. You might have a false sense of security about the quality of your work. Sometimes it also feels disingenuous -- like _fake_ praise which suggests people aren't that invested your content/efforts. * you become closed minded, not looking into how to make things better anymore **What does effective feedback look like?** * It is specific, clear, and there is often a concrete suggestion for improvement. * It takes into account how much time/resources the person has to implement suggestions * constructive, not critisizing - help to formulate better decisions to improve and increase performance * it should always be continued feedback - keep improving * Always constructive and with a touch of praise when things are going well - ah, and make it a conversation about things you've already discussed (never give surprise feedback) * There's the sandwich method? Start with something positive, then something constructive, end with something positive. * should always point out the silver linings whenever possible and acknowledge the effort that wa sput in * specific, delivered in a supportive and safe environment by someone I trust, room for clarification and discussion about how to incorporate that feedback into future activities * It's encouraging, it's clear, it's honest 👥 Warming-up --- Yo (⏰ 15 minutes) 👥 Vision and Value exchanges *What are you giving to your community, organization, or project (consider your OLS project for this activity)? What is it giving back? If there are gaps, how might you close them?* **Silent insights using prompts:** Your Vision and Project: (3 minutes) * Think about Why your project is important to you (your vision)? Why is it important for others? * What is the difference your vision will make for you, your community, the world? Value Exchange: (3 minutes) * What kinds of things do you give to others in your open leadership practices? * What kinds of things do you get back? * Does the balance seem right to you, or are there adjustments you’d like to make? * Does this fit with your plan as leader of your project? * Does this fit with your overall BIG vision (5/10/20 years)? If not, can how you improve them? Combining vision with value: (3 minutes) * What are 2-3 key activities or critical points people should know about your project? How would they find values in doing/helping/supporting that? **Notes:** You can add your response here for yourself and to share with others. *Copy this block for taking your notes* > [name=YOUR NAME]: > response line 1 > response line 2 > response line 3 > *Copy/edit this block for taking your notes* > [name=YOUR NAME]: > response line 1 > response line 2 > response line 3 > > [name=Laura C] > **Vision and Project**: > My project (Turing Way Guide to Ethical Research) is important as a contribution to the community of practice for ethics in data science > It's important for me to develop my own skills in community building, as well as to help me articulate my own ideas about ethics > **Value exchange**: > I can give: encouragement, time and space to discuss ideas about ethics and also about making progress in the project, extremely basic tech support (and signposting to less basic tech support). > I can get: sounding boards, encouragement, actual tech support, a sense of tangible progress, learning more about ethics. > I hope the balance is quite good at the moment: hopefully I would hear if I was expecting too much from people and not giving enough in return! I am more or less where I would like to be at the moment > I don't really have a 5/10/20 year plan :) suggestions for how to make one welcome! > **Combining vision with value**: > *Copy/edit this block for taking your notes* > [name=Ismael]: > Vision: The project (ethical guide to research) matters to me because I believe in an approach to knowledge that is more in-line with the world within which we conduct science, especially considering our work's impacts. With this, it should be important for all! > Value exchange: I can learn from contributors' scientific practices as a non-scientist myself and I am certain that my philosophical know-how can provide to their own reflections. This is one form of interdisciplinarity that is lacking in science education and which already plants the seed in our minds -- our contributors' minds -- that this reflection is crucial. > Combining vision with value: All the above, haha! > [name=Kendra]: > Your Vision and Project: Our vision is to great a space where grad students can get regular face-to-face help making their research more open. This is important to me because I went through a degree trying to do open science without support. I felt isolated and frustrated, and I wasn't very effective. I know there are other grad students in the same situation, and I want to help them feel empowered and included. > response line 2 > response line 3 *Copy this block for taking your notes* > [name=Danny Garside]: > **Vision** Increasing the efficiency of animal research, so that we can do less of it, and gain more from it. Because, fundamentally nobody likes the idea of doing animal research, but the benefits of it are huge, and so we need to focus on how to make it as efficient as humanly possible. Hopefully, it will mean that less animal lives are required, that scientific progress will happen faster, and that we can be more confident in the science that is published. > **Exchange** not sure... > response line 3 > *Copy this block for taking your notes* > [name=Neha]: > Vision: Our project was to make The Turing Way more accessible to contributors and readers alike. I think TTW is an incredible project and deserved Paul's (and mine!) efforts in improving the book's consistency and sustainability. TTW is also a wonderful project to learn about how to set up and maintain an open-source project/community, which is something I've been wanting to learn more about. > Values: I like to be helpful and team-oriented, if someone needs help/sounding board - I'll sit with them until we can crack it. I'm resourceful and can figure out some things pretty **Report out, shared insights, +1s:** (3 minutes) - What are your reflections? How can you apply this learning in your work and life? * * * 👥 Project demo -- *Breakout room with one host* Emmy (⏰ 25 minutes, 2-3 people per room) <--- If the room is smaller, we can close the room sooner and have an open discussion in the main room. **We recommend using the 2x2 paradigm for feedback** - Provide at least one piece of constructive (not negative) and one piece of positive feedback each for content and delivery. - You don't need to share this in this HackMD. | Aspects | Content | Delivery | | -------- |:------- | -------- | | Positive | | | | Negative | | | **For each group:** - 4-5 min presentation (use any mode of presentation) - 3 min feedback from group (1 min pp) - Presence - Clarity - Credibility - 1min closing / buffer - _Thank the person who presented for sharing._ - _If you presented, thank everyone for their feedback._ ✏️Feedback reflections [HOST NAME] (⏰ 5 minutes) Take a few minutes to reflect on the feedback you received. You can take private notes. - What did you hear? - What did you learn? - How can you apply this learning in your work and life? * * * * * 🗣️ Closing --- **Assignments** - Prepare for your graduation next week. - Take some time to finish or look through your assignments that you have not had a chance to work on yet. - Start documenting a micro-blog for your project that we would invite for publication on our website after your graduation: https://hackmd.io/@ols-2/speedblog-guide **Open Q&A time** - **Next calls** - **Feedback** _What worked?_ - - _What didn't work?_ - - _What would you change?_ - - _What surprised you?_ - - - - *Reference*: Open leadership Framework, Mozilla Open Leaders 6 & 7, Open Life Science 1 *License*: CC BY 4.0, Open Life Science (OLS-2), 2020
Last changed by  
 
OLS-2
690

Read more

Lens Protocol Subgraph - Manual Testing (SG HACKATHON)

Resources: Hosted Service: https://thegraph.com/hosted-service/subgraph/mike-data-nexus/lens-sg-hack This covers contract that emit events for the Lens Protocol Tests Test 1 ✅ User Account

4/28/2023
TU-Delft celebrates a year of Open Science Course: Share your research with the world

Project background The Delft University of Technology (TU Delft) in the Netherlands runs once a year a Massive Online Open Course (MOOC) on Open Science on the edX platform => Open Science: Share your research with the world. Our primary target is PhD candidates but the MOOC is meant also for MSc students, researchers, support staff, policy makers that want to learn the basic principles of and motivations behind Open Science. The OSMOOC has been running for multiple years with a decreasing number of enrollments and varying levels of engagement. We have high dropout rates and we do not know if the participants practice Open Science later on. Our project goal was to improve the engagement by creating a community around the MOOC participants. _Figure1: _Logo of the Open Science MOOC and titles of the six modules contained in the course. Image by TU Delft and licensed under CC-BY-NC-SA 4.0 International License. Expectations from this program Since we had both just started in our jobs as open science teachers, the first thing we hoped to learn was more about the different themes within Open Science. We also hoped that through our participation in the OLS program, we would learn more ways to engage our MOOC’s participants and build a solid community, as well as workflows and processes to make our own work more open.

7/18/2022
Speed Blog: Project name, team members

THIS PAGE IS OBSOLETE. NOTES MOVED TO: https://github.com/open-life-science/policies-procedures-and-docs/blob/main/cohort-procedures-and-templates/speedblog.md ==This document provides guidance for you to summarize your OLS journey so far and the project you worked on during the entire period of OLS-2 in a speedblog. Please draft your speedblog in your 'mentor-mentee hackMD notes' and share with the OLS team.== Ideally your speed blog will be a written piece with a picture (max 2) and contain some links and references. In terms of word count you are aiming for between 500 and 1200 words. We will post your speedblog on OLS website: openlifesci.org/posts See this post for guidance on speed blogging: https://software.ac.uk/speed-blogging-and-tips-writing-speed-blog-post Example you can draw from: https://openlifesci.org/posts/2019/10/21/culture-track Here are a few questions to help you generate ideas and content for your speedblog:

6/1/2022
Week 10

:earth_asia: Cohort call Schedule: Open Science III: Next steps - applying FAIR research principles Date and time: 05 November 2020, 09:00 - 10:30 LONDON, Duration: 90 minutes Video on YouTube :house: Before this meeting After this meeting: Think about and plan to apply FAIR principles to your project in your own time. Resources for more information have been linked in the notes.

3/9/2021
Read more from OLS-2
Published on HackMD