# Week 15: Group 1 - Looking for the note's link for the group 2: https://hackmd.io/@openlifesci/ols-2-week-15-gr2 ###### tags: `OLS-2` `cohort calls` `project-leads` :earth_asia: Cohort call --- **Call time** : - 09:00 - 10:00 UTC ([see in your time](https://arewemeetingyet.com/London/2020-12-10/09:00/week-15-rehearsal-1)) **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 - 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/) - Kate S / Open access retrofit evaluation / t: @Dr_KateSimpson, g:@KateSimpson / 😮 (how quick this has gone!) S - Emma Karoune / Open Science in Phytolith Research / t: @ekaroune g:EKaroune / :smiley: - Beatriz Serrano-Solano / Growing the Galaxy Community / t: Birthae, gh: beatrizserrano - Cooper Smout / Free Our Knowledge / @coopsmout @projectFOK g:FreeOurKnowledge - Georgia Aitkenhead/Autistica-Turing citizen science project/GeorgiaHCA/🧑‍🎄 - Yo Yehudi / OLS ;) / :zzz: - Malvika / OLS / :zzz: (totally stealing this from Yo!) - Hilya / APBioNetTalks / Github:@hzahroh/ :dizzy: - Sophia / The Turing Way - Ethics / t: @brainonsilicon g: BrainonSilicon :wave: Welcome --- Host: Yo (3 minutes) **Icebreaker question** *What's the best piece of advice you've ever been given?* - _Name / answer_ - Yo / It's okay to stay quiet if you don't have anything constructive to say - Malvika / take one day at a time (by Lorena during OLS-2)! - Emma / Don't take on too much - obviously I don't actually listen to it. - Hans-Rudolf / talk to people - Bea / it might be overwhelming to start a new life abroad, but at a later stage of your life you will realise that it was the best moment of your life - Kate (S) / 'Self care is a political act' (via a colleague - a quote from Audre Lorde ;) - HIlya / You don't have to do everything, credit to OLS mentor (Patricia Herterich). This is a very good one, make me rethinking what are things that should be given priority and focus in life - Sophia | “The only way to run a marathon is one step at a time” & “Best way to learn is to recognise that you always have something to learn.” - ✏️ 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?** * Feedback allows us to learn and improve, but also gather a sense of how we might come across to others with different perspectives - important to get as diverse a range of feedback as possible * We learn from knowing our mistakes * For possible improvement based on awareness of others' perception * Collaboration and diverse idea makes everything better (both the thing we are asking feedback on and personal improvement) * Important to let others know if they are in the right direction. Acknowledge their work. - **What happens when we don't give feedback?** * People don't benefit from our suggestions and get better/improve * We may continue to make similar mistakes unaware that they may come across poorly; we may also end up speaking only to audience of people similar to ourselves * Ideas and approaches can become 'stuck' or progress more slowly * The others might think that we don't care * Nothing will change (lack/stagnation of project growth and individual growth) * No new ideas can come in - **What happens if we only give critical feedback / areas of improvement?** * We can get discouraged for not getting recognition for all the hard work we do. * The person can be left feeling discouraged and that their work has no value * The motivation is gone. * It can be very difficult to take pride in our work - it's hard to have a growth mindset - you need to have a sense of progess and possibility; without that nothing is distinguished, and the feedback is meaningless * It can be demotivating as it limits awareness of what went well (I had this conversation with my PhD supervisor as they only commented on what I needed to improve and it was always difficult to receive - then they added a few positives too) * People can focus on "fixing the negatives" and not realize that there were good parts/pieces, so those good pieces don't get carried into further iterations - **What happens if we only give praise?** * It has no meaning * It can have one of two effect: either the receiver believes everything and assumes that there is no area for imporovement, or they won't return to us for feedback next time. :grin: * The person will not work on their weaknesses and improve * The praise loses its value, because we cannot differentiate really good work from poor or average work; it becomes hard to improve, and to trust the person giving the feedback to be honest * It limits the opportunity to learn and improve * Can get blindsided by others (not realizing the "work on" areas) - **What does effective feedback look like?** * Using our empathy is key! * Supportive * Yo - mix of good and critical. I like to do it in a sandwich - something nice / something critical / something nice * Genuinely wanting someone to succeed and shine - the person receiving the feedback is gianing valuaable skills and support, and can feel their confidence grow as a result, instead of feeling put down. The pereson giving the feedback genuinely has the other's growth in their mind and is willing them and their work to be as good as it can be. - +1 * Good feedback, even negative feedback I've had has been accompanied by some excitement about what I'm doing or what I may do in the future * Feedback that poits out what can be improved while also acknowledging what are going great. * (+1) * I like the term 'constructive criticism' so it is positive and helpful, but highlights areas to improve - definitely highlighting what went well, as mentioned above :) * Contextualized (ie. "these were the goals of the project, and this current statement is not aligned with that goal") * Able to be acted upon (the life advice of "if they person couldn't fix it in 5 minutes, then don't mention it" eg. food in teeth vs different socks on/hole in shirt) * * 👥 Warming-up --- Yo (⏰ 15 minutes) 👥 Vision and Value exchanges (15 minutes) *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 > [name=Georgia]: > My project is important to me because I believe strongly in the benefits of neurodiversity and I'm motivated by the people I work with to do a good job for them. > It's important to others because it will make the world more accessible and also they can bbe part of th process and laern new things. > I do more facilitation and listening than leadership and direction, and this is part of the nature of participatory science - but I think I may have good the balance slightly wrong and in future I would want to be more precise and taake grater direction. > Every single aspect of the project is open to contributors, and this is a valuable step in progressing collaborative science. > [name=Cooper Smout]: > Vision and Project: My project is important to me because I want a more secure in academia moving forward. My project is important to others because early career researchers around the world are forced to choose between their careers and doing good quality science. I believe my project will help researchers cooperate, rather than compete, to create a future that supports their needs and desires to conduct good science > Value Exchange: I help other researchers connect with like-minded individuals and self-actualise their desires for a better future in academia. > Combining vision with value: > > [name=Emma Karoune] > Vision - for me this project is helping me move towards my research goals of developing reproducible methods. For my community - enable cultural change to open science in my field so that our discipline is brought into this new way of working. > Value exchange - I pass on skills to others and my vision of where the project needs to go. Others that I work with are giving me feedback and a bigger connection to the community as a whole. > [name=Hilya] > Vision - the project is important for me because I would love to see that people are sharing their expertise and skills with others, helping each others fixing scientific problems and making science more reproducible. For community - it enables people to get access to science and provides same opportunity to showcase their work. 👥 Project demo -- *Breakout room with one host* Malvika (⏰ 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 - _Thanks 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
730

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