# Week 6 ###### tags: `OLS-2` `cohort calls` `project-leads` - Schedule: [**Open Science I: Project Development**](https://openlifesci.org/ols-2/schedule#week-06) - Date and time: [08 October 2020, 09:00 - 10:30 LONDON](https://arewemeetingyet.com/London/2020-10-08/09:00/week-6-cohort-call), Duration: 90 minutes - Link to the shared notes: https://hackmd.io/@ols-2/week-06 - Zoom call joining link: <this meeting has concluded, please watch the call on YouTube: https://www.youtube.com/watch?v=fyz4gB4XPJk> **Before this meeting:** - Look up two other projects and comment on [their issues](https://github.com/open-life-science/ols-2/issues) with feedback on their Open Canvas and README *OLS progress assessment: Week 1 - Week 5* *You have been working on the following assignments and tasks to understand and use Open Science concepts introduced in the last 2 cohort calls (if you haven't worked on them, please create a plan so that we can advance our projects without having too much workload later):* - [x] Create a GitHub/online repository for your project - [x] Create an [OLS-2 issue](https://github.com/open-life-science/ols-2/issues) with this [issue checklist](https://raw.githubusercontent.com/open-life-science/ols-2/master/.github/ISSUE_TEMPLATE/project.md) for your project and add your project's online repo link - you can cross what you have done each week - [x] Create and share links to your assignments in your OLS-2 issue: - [x] Create an [open canvas](https://docs.google.com/presentation/d/1aWbD7rLCQ5fvjUuT8lPGlD4mj8WAKR_oXDB_8jDxJTU/edit?usp=sharing) - [Make a copy of this TEMPLATE](https://docs.google.com/presentation/d/1cqZ1oKVA8szXPoT_n0z_5tpAOVQ9qlOPLUQ69okMD20/edit?usp=sharing) - [x] your project [vision statement](https://mozilla.github.io/open-leadership-training-series/articles/introduction-to-open-leadership/stating-your-project-vision/) - [ ] [compare/contrast table](https://docs.google.com/document/d/1sVuFTh_YMfLzxx8gkp7Oc3mHGjRP6bmQiipUfhxGNog/edit?usp=sharing) for your community’s current and desired value exchange, and establish [milestones through your roadmap](https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/start-your-project-roadmap/#assignment--make-a-project-roadmap) - [ ] Using your canvas, vision and [roadmap](https://docs.google.com/presentation/d/17JbIvsXpSEZ82FYzpf63CuR1LJoICJ8lOSUdN0BpYjM/edit?usp=sharing) - [start writing a README](https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/write-a-great-project-readme/), or landing (web)page, for your project - [ ] Select an [open license](https://mozilla.github.io/open-leadership-training-series/articles/get-your-project-online/sharing-your-work-in-the-open/) to your repository as a file called LICENSE.md **Table of contents** [TOC] :earth_asia: Cohort call --- **Call time**:08 October 2020, 09:00 - 10:30 London time, [see in your time zone](https://arewemeetingyet.com/London/2020-10-08/09:00/week-6-cohort-call) **Hosts**: Emmy, Malvika, Yo **Syllabus**: [OLS-2 Week-6](https://openlifesci.org/ols-2/schedule/#week-06) **This week** During this week's cohort call, we will learn about: - Project development plan - Open Software - Open Hardware - Open Data :wave: Roll call --- please add :writing_hand: to be allocated to **Written Discussion Breakout Room** or :speech_balloon: for **Spoken Discussion Breakout Room**, or both if you are happy to be assigned to any breakout room. - *we will explain this in the beginning of the call, so it's ok if you want to wait to add this later.* [More info](https://hackmd.io/Rxv59dqAQ1C7gnHz5P-5PQ) *Examples:* - Yo Yehudi (they/them) / OLS / t: yoyehudi / :writing_hand: :speech_balloon: - Malvika Sharan (she/her) / OLS / t+gh: malvikasharan / :writing_hand: - Emmy Tsang / TU Delft, OLS-host / t: emmy_ft / :speech_balloon: *Name (pronouns - optional) / Project / social handles (twitter - t, GitHub - gh, etc.) / breakout room preference: :writing_hand:, :speech_balloon:, both.* - Sophia Batchelor / Ethical Guide - The Turing Way / t: brainonsilicon / :writing_hand: :speech_balloon: - Renato Alves / EMBL - [Bio-IT](https://bio-it.embl.de) Community Manager - t: @renato_alvs gh: @unode :speech_balloon: - Pradeep Eranti/Open platform for Indian Bioinformatics community / t: [@pradeeperanti](https://twitter.com/pradeeperanti)/ :writing_hand: - Kate Simpson/ open energy retrofit protocol/ t:Dr_KateSimpson/ g: @KateSimpson, :writing_hand:, :speech_balloon:, both! - Markus Löning / sktime / He/him / gh: @mloning, t: @mloning_ / :writing_hand: :speech_balloon: - Laura Carter (she/her) / Ethical Guide - The Turing Way / :bird: @LauraC_rter / :speech_balloon: - Arielle Bennett (she/her) / Cambridge Neuroscience / t: biotechchat / :writing_hand:, :speech_balloon: - Piv Gopalasingam (he/him) / European bioinformatics institute / t: cascade21 / cannot attend breakout (meeting clash) - David Beavan / The Alan Turing Institute / @DavidBeavan / He, Him / :writing_hand: :speech_balloon: - Aleksandra Nenadic / The Software Sustainability Institute / t: aleks_nenadic / gh: anenadic - Beatriz Serrano-Solano / Growing the Galaxy Community / gh: beatrizserrano / t: @Birthae / :writing_hand: :speech_balloon: - Bailey Harrington / Chronic Learning / gh: baileythegreen :speech_balloon: - Kirstie Whitaker / Alan Turing Institute t: @kirstie_j gh: @KirstieJane / she/her/hers / :speech_balloon: - Camila Rangel Smith / Alan Turing Institute / t: @CamilaRangelS/ :writing_hand: :speech_balloon: - Karega Pauline/ The Hub Portal / gh:karegapauline /t: @KaregaP / :speech_balloon: :writing_hand: - Ismael Kherroubi Garcia / Ethical Guide - The Turing Way / t: [@IsmaelKherGar](https://twitter.com/IsmaelKherGar); gh: @Ismael-KG / :writing_hand: :speech_balloon: - Jez Cope / Mentor / t/gh/gl: jezcope - Georgia Aitkenhead / Alan Turing Institute / GeorgiaHCA / :writing_hand: :speech_balloon: - Sarah Gibson / Alan Turing Institute / gh: sgibson91 t: drsarahlgibson - Emma Karoune- Emma Karoune/Open science in phytolith research/ :writing_hand: :speech_balloon: :smiley: - Teresa Laguna / Science for All / t:@teresa__laguna g:@tlaguna :writing_hand: :speech_balloon: - Peter van Heusden / RSSE Africa / t:@pvanheus g:@pvanheus :writing_hand: :speech_balloon: - Harriet Natabona / covid19 open science communication / gh: @natty2012 / :speech_balloon: :writing_hand: - Eva Herbst (she/her) / Finite Element Zurich / G: @evaherbst / Twitter: @EvaCHerbst :writing_hand: - Paula Andrea Martinez / Carpentries, UQRUG, RLadies Brisbane / @orchid00 :writing_hand: - Paul Owoicho / Embedding Accessibility in the Turing Way Open Source Guide / g: @paulowoicho :writing_hand: - Hilyatuz Zahroh / APBioNetTalks /gh: @hzahroh t:@hilyatuz_zahroh/ :writing_hand: :speech_balloon: **Icebreaker question** --- What is your recent favorite tool or app or software? - [name=Sophia] NOTION!! Once you get to know me, you'll learn how much I love, use, and rave about [Notion](https://www.notion.so). You can also view my template homepage [here](https://www.notion.so/Home-1c2a17e01e1347d98b8cd48871aef9f4) if you're wondering how I use it - 😅😍 - [name=Kate]Github! I never knew I could host such a great website from there! 😍 - [name=Bailey] The **Atom text editor** (from the people behind GitHub!). I recently converted after downloading it just to see how easy it would be for students to use (though I also still use vim on command line). - [name=Aleks] Need to try **atom**, people say it is great - [name=Kirstie] **Whatsapp**, honestly, its let me stay in touch with SO many people. My dad was in hospital for 8 days a couple of weeks ago and it was his (and our) absolue lifeline given that we couldn't go an visit him :phone: - [name=Arielle] ToDoist! I use it to keep track of all my tasks, including long term projects and daily reminders +1 - [name=Piv] not recent but LifeRPG - since the pandemic started I've added tiny tasks to add structure to my day. small walks, listening to podcasts, etc. - [name=Laura] **Borrowbox** for fiction books while the library has been closed :books: - [name=David] Headspace, for that feeling of chill when your daily commute is a walk from one room to another - :+1: - Kirstie: I just signed up for the Turing's paid subscription. Interested to see where I can fit it in :relaxed: - David: Some are good for walkies, easy to zone out (not fallen over yet) - Camila: I also started using it with the Turing subscription, I love it. Having a session at the end of the working day helps me a lot to transition. - Jez: I subscribed for a about a year and while I found it a bit samey after a while and unsubscribed it was definitely worth it, I learned a lot and I'll probably go back to it at some point - [name=Jez] [GNU Emacs](https://www.gnu.org/software/emacs/) text editor (+ [spacemacs](https://www.spacemacs.org/) configuration) with [org-mode](https://orgmode.org/) for note-taking, planning & project management, knowledge management, document writing, ... all in plain text - [name=Aleks] OBS for recording videos, Clemetine for managing a music library - [name=Renato] :+1: for OBS! - [name=Renato] [GitPod](https://www.gitpod.io/) - amazing tool for co-working on text/coding open source projects - Great integration with GitHub/Lab - [name=Sarah] My new Google Nests - really enjoying controlling the "mood" of my music and having it follow me around my flat (spying microphones in my flat aside :grimacing: but they do have hardwired mic off switches) - [name=Pauline] Pomodoro focus app. Managed to focus and complete tasks despite the distractions :-) :+1: - [name=Emma] - Git hub and making emojis in markdown!:smiley: - [name=Paula] Github - [name=Teresa] HackMD! I find it massively useful for every project I work on, with or without coding. - [name=Paul] VSCode! I feel it makes writing code so much easier. It also makes working with GitHub very easy as well. - [name=Peter] VSCode! I like how it has "language engines" for Python and CWL that provide useful hints on variable and function name and formatting 🗣️ Welcome! host: Malvika Sharan (4 mins) [⏰ 4] **Call recording reminder:** - Please note that this call will be recorded - The video will be available on the [YouTube channel](https://www.youtube.com/c/OpenLifeSci) in the next few days - Turn on your webcam if you don't mind being in the video (or off if you do!) **Participation reminder:** - [Code of conduct & community participation guidelines ](https://openlifesci.org/code-of-conduct) - If you experience or witness unacceptable behaviour, or have any other concerns, please report it by contacting the organisers - Bérénice, Malvika and Yo. ([team@openlifesci.org](mailto:team@openlifesci.org)). - To report an issue involving one of the organisers, please email one of the members individually ([berenice@openlifesci.org](mailto:berenice@openlifesci.org), [malvika@openlifesci.org](mailto:malvika@openlifesci.org), [yo@openlifesci.org](mailto:yo@openlifesci.org)). Breakout room description --- host: Yo Yehudi (3 mins) [⏰ 7] - Link to the post: https://hackmd.io/Rxv59dqAQ1C7gnHz5P-5PQ - :writing_hand: Written Discussion rooms - :speech_balloon: Spoken Discussion rooms **We have a cohort name:** "The Masked Cohort" ![A screenshot from https://poll.ly/#/LBNe74g0 with 11 votes from The Masked cohort, other options are Winged Lion, El Zorro and Anti(corona)virus](https://i.imgur.com/45iV3SZ.png) ✏️ Open Science I: Using project management skills during development stage --- Host: Emmy (3 min) [⏰ 10] Open science has many aspects, so we'll be covering this over two separate cohort calls. This week, we're looking at different aspects that open science projects may have, across a few main areas: - Iterative project management - Open Source Software (reproducible, peer-reviewed code!) - Open Source Hardware (affordable, maintainable equipment!) - Open Data and sharing research outputs! In the next cohort call (week 8), we'll cover open dissemination - open access, preprints, citizen science and open education. 🖥 Agile and iterative project management methods --- Host: Emmy (10 minutes + 5 for questions) [⏰ 25] **Guest speaker: Renato Alves** - Bioinformatics Community Manager - EMBL Bio-IT, Germany - Email: renato.alves@embl.de, twitter: @renato_alvs, github: @unode - [Slides](https://docs.google.com/presentation/d/1CWnHXZHFDYFTqE2KKgZ8R5i_46XqAqnjy12gYSDESxk/edit?usp=sharing) - Agile methodology - Iterative design - Break tasks into manageable chunks - Use-case links: [OLS-2 OSUM](https://github.com/orgs/osumontreal/projects/3) - [OSL demo board](https://github.com/open-life-science/demo-project-board/projects/1) - Notes: - Combination of different topics that help plan and strategise project management - Agile software development: [agilemanifesto.org](https://agilemanifesto.org) - stemmed from the need to respond to changes - Waterfall: higher time/ risk trade off - product requirement document - software design - implementation - verification - maintenance - Iterative: Plan - collaborate - deliver - Daily review allows to clean your backlogs and gain feedback regularly - Using Agile for MY project - Using GitHub project board - Think of post it based small tasks - different columns for different status/stages (todo, planned, ongoing, done) - You can automate this process - The automation can be managed from the ••• in the top right corner of a column, then going to ‘Manage Automation’. - It has options to ‘Move issues here when…’ and then some things that can be checked for when you add a new issue, or when something is done related to it. - breaking down of tasks: you can use issues in GitHub, writing issues in bullet points is recognised in the project board of GitHub - [name=Renato] Try to keep a balance and the tasks manageable, too many tasks can feel overwhelming and become a serious problem. Milestones can help reducing this feeling. Closing tasks as abandoned is fine if it seems unlikely something will ever get done/completed. - Questions / comments - Name / Question - Sarah / I’m interested in the word “Collaborate” in the Agile diagram. Is collaboration intrinsic to Agile or can I agilely managed myself on my hobby project? :D - Perhaps you are collaborating with past-Sarah and future-Sarah? - [name=Laura] SG: I think you are right there! - [name=Sarah] Follow-up Q: are iterative work and small-chunk work two separate thing? Both agile? - [name=David] I'm really interested in the psychology and motivation of 'assigning' people to tasks. Do people self-assign, get asked, or someone just assign another without discussion. I've seen it all, what works in the real world best for you(s)? - [name=Renato] I maybe missed the main point of your question but answering here. If you have a contributor guide you should state this there. The success of the approach depends on the commitment of individuals. A compromise is to allow self assigning with occasional reviews on progress to avoid "someone else working on it but nothing happening" situations. If communication is fluid "ownership" of issues is, in my experience, rarely an issue. - Kate/ How often do you tend to log on? Eg. everyday or once week? - daily, weekly, monthly depending on the project - [name=Renato] The approach I mentioned [Getting Things Done (GTD)](https://en.wikipedia.org/wiki/Getting_Things_Done) provides some thoughts and ideas on how to manage such list of task introducing different "phases" that you *should* do on a daily basis. - Checkboxes! Use `- [] item 1` (and `-[x] item 1` for the checked box) - [ ] Like this one - works here too :smile: - [name=Arielle] I think one of the most important concepts in Agile project methodology is the use of reflection sessions after specific periods of time or when tasks are completed/milestones hit. Building non-judgemental reflection in *throughout* is really important to project development! - [name=Emmy] A friend of mine recently shared this idea of [fractal boards](https://workflowy.com/post/fractal-boards/) :shocked_face_with_exploding_head: 🖥 Open Source Software --- Host: Emmy (10 minutes + 5 for questions) [⏰ 40] **Guest speaker: Aleks Nenadic** - Training Lead at Software Sustanability Institute, UK. - [Slides](https://docs.google.com/presentation/d/1uZuqgoJp67uRB6t0LCZJ06V8YYyff9-iqrv6zfqtOhk) - **Notes:** - Open source != Free - open source is about allowing your work to be reused and remixed - Open source research code allows code to be peer-reviewed and reused: this means folks don't have to reinvent the wheel, and you can share and collaborate with more people from all around the world, and vice versa - No code is bug-free and comment/critic on your code is not a critic on you - or blame on your ability - If you release early, and release often: you can get more eyes on your code who can help you make your code better - If source code is available but no license if associated with it, it's not legal 'yet' to be reused: putting a license makes people aware how they will use your code. - Open Source makes it available (and legal) for others to reuse, remix and share - Publishing and sharing your open code: first step is Version Control - Enables you to publish and share your code - Backup and version control - It helps you recover your mistake - makes collaborating on your code and resources easier - git is one version control system - this allows you to synchronise your code from local system to GitHub - Ready to share? - Have a README - Consider having a roadmap - Contribution guideline so others can help improve - Code of conduct - Issue tracker - Citation: use others work with clear citation, and consider getting DOI for your code/resource (Zenodo, FigShare) - [Citation File Format](https://citation-file-format.github.io/) - add your contact - Ultimate goal is to have full reproducibility - Checkout [Binder](https://mybinder.org/) to allow people to launch/test your code in browser - You can publish your code on JOSS - Check [The Turing Way](https://the-turing-way.netlify.app/welcome) - Questions / comments? (5 minutes) - Name / Question - Arielle/ Is there much difference between Git/GitHub and Mercurial/BitBucket? - Yo (and Aleks): Git and Mercurial are version control systems that don't have to tie in to things like GitHub or BitBucket. They have different commands but basically do the same thing, backing up versions of what you do. GitHub and BitBucket are both web interfaces and community interfaces that provide a skin over Git or Mercurial (which are essentially command line tools). These user interfaces make it easier to start using version control under the hood, before descending into command line, and are a great way to overcome any fear or aversion to version control. And user interfaces like GitHub have been improved a lot over the years and many more functionalities of the underlying tool (in this case Git) have been made available in point+click fashion - lowering the barrier for people to start using them. - Principle is the same, commands remain different - Go with what your community and group is using - so it is easier for you to gain help and communicate your work - Jez: Mercurial is more user friendly but suffers from a small user base compared to git (Aleks: I'd agree with that) - Kate / Does anybody know a tool to quickly convert MATLAB code to Python or R? A student I was just working with was working in MATLAB but could benefit from this. - Emmy - i'd love to know this toooo - Aleks: never used it myself but maybe check **libermate** for Matlab to Python conversion: https://github.com/awesomebytes/libermate - Aleks: also check out this thread, seems to have a few usefull pointers: https://www.mathworks.com/matlabcentral/answers/426258-how-to-convert-the-matlab-code-into-the-python 🖥 Open Data --- Host: Yo (10 minutes + 5 for questions) [⏰ 85] **Guest speaker: Paula Andrea Martinez** - Twitter: [@orchid00](twitter.com/orchid00/) - [slides DOI: 10.6084/m9.figshare.13065308](https://doi.org/10.6084/m9.figshare.13065308.v1) ## What is open data? - Open Data is data that is made available for others to reproduce your work - Kate: Open data is data that is publicly available at the lowest bar. It doesn't have to have documented metadata (however it would be better!) so that people can _effectively_ reuse it (which generally is the purpose of making the data open in the first place :wink:) - Accessible to everybody - Sharing data in an open repository, in an ethical and accessible way. - Data that you can use for other purposes? - Data freely available for anyone to use, under open licenses / copyleft - [name=David] Data that we can share, build upon and point others towards, so we can have more trust in what's based upon it - Data that can be publicly, freely accessed, used, and reused - Open data is available to everyone - Reusable - Much like code, [Low WTF/minute](http://3.bp.blogspot.com/-ilMjE1Gh3Yg/VpUAmd-6TWI/AAAAAAAAAbg/-FJ08zxN42s/s1600/WFTPM.png) - good metadata - **Notes:** - Open data definition as per Open Data Handbook: Can be freely used, reused and redistributed by anyone - This allows us to build upon other people's work and improve it - Check out this step by step guide for opening you data: https://5stardata.info/en/ - Data Ethics: Goes across the data life cycle - who is funding it - What is your motivation - Project design - Data collection and sourcing - Analysis - Interpretation - Communication and distribution - Linking you data: Linked data > the reason that Open data exists - is to create knowledge - for that you need a standard (vocabulary/ontology), see [w3c guide](https://www.w3.org/standards/semanticweb/ontology) - FAIR Data Principles: Findable, Accessible, Interoperable and Reusable - There are many works that are invisible and FAIR can allow us to enhance the value of that work - check FAIR guiding principles, Go-FAIR FORCE11, FAIR4RS (for research software) and Research Data Alliance - Open Data is part of the road to Open Science - Questions / comments? - Name / Question - Muhammet Celik: "I understand, reusing and accessing the data but when the data is open to modify, does not it make it less reliable? I understand it can get improved but on the other hand it might just get ripped, no?" - Open Data has a concept call data transformation: it means that with a license and a DOI you allow others to improve your work by citing your work (it's not being ripped :D) - Emma Karoune: Where do you suggest putting links to old data to make your data 5 star? in a separate file of your repo or in a research paper/data paper? - I recommend seperate file - but be aware of journal-specific guidelines. The most important thing is to make sure to link it somewhere visible! - Yo: Bigger datasets should ideally go in an appropriate open repository - also git-lfs and git-annex to manage large files in git - Peter: "Data benefit sharing is a big worry for researchers in Africa where often we are the "sample collectors" and analysis happens elsewhere. How can benefit sharing be maintained with open data?" - Attribution licences can help to make sure you still have benefits from data re-use - Kate: If data is collected from homes (temperature/humidity/building performance) and was not originally planned to be made open, do you think opening it up anonymously, so the householders cannot be traced, it is okay, or unethical practice? - This touches upon sensitive data. Use specific guideline and ethical framework/process (your institutions) - anonymise or de-identify personal information data, also get consent from people before sharing their data - This is the kind of thing we are hoping to discuss/address in the Turing Way Guide to Ethical Research! Please come get involved - [name=Laura] +1 👥 Breakout discussion: Iterative project management and design --- Host: Yo (15 minutes) [⏰ 70] **Breakout room reminder:** if you need assistance in your breakout room, please click the ' **Ask for Help**' button at the bottom of your screen _Instructions: Try to break down your first milestone into achievable chunks, and share what you found interesting and challenging._ 👥 Break-out room 10 minutes, ~3-4 rooms: we will have some written discussion and some spoken discussion room: - First 5 minutes: Work silently on breaking up and taking notes below. - It's okay to talk and bounce ideas off your group if needed in the 'Spoken discussion rooms' - Last 5 minutes: Share with your group & get feedback. - *Written discussion room:* Read through what others have written, +1 or comment where needed. - *Spoken discussion rooms:* Take turn to share your ideas 1 minute each and capture the main insights in your notes - Room 1 - Written: (Pradeep, Muhammet, Hilyatuz) - [name=Muhammet] The key goal in our project is making a tool that will simplify the metagenomic classification, these days metagenomics analysis has been a boom and a simple classification analysis requires users to use the command line which frustrates non-IT people. The biggest challenge in this is after we come up with the pipeline its gonna require some computational power which not everybody has it. Or not everybody uses the same OS. So we are thinking about how to represent the pipeline in a way so people do not need to worry about their computational power nor OS. - [name=Hilya] The key goal to this project is to create an open source platform to stream bioinformatics talks, tutorials ans trainings. Among the key milestones are to finish the website development [APBioNetTalks](https://apbtalks.apbionet.org) and then stream our first talk. - Room 2 - Spoken: (Harriet, Markus, Kate, Laura) - [name=Markus] a key goal of our project is to better integrate other package developers and users into our project, I find it hard to break this down into milestones because I'm not sure how to best measure success - identify success criteria - identify ways how to approach other package developers (for example, raising issues, joint presentations) - [name=Laura]: a key milestone opportunity for our project is the Turing Way BookDash in November: we want to use this as an opportunity to create lots of content and also identify barriers to contributing. So our more detailed plan looks a bit like: - identify what we want BookDash participants to get done during the week - break that down into discrete issues on github that are open and ready for +1 - make sure the contributor guides are up to date and provide information that we think will be needed - ...other prep things that we haven't thought of yet... - [name=Kate]: 1. Review existing post occupany evaluation data via:Universities; Individual researchers; Web portals; Github. Create table and add web links: Add columns for data types, for tick boxes; Make the table easy to read; Format the data in Markdown (is this even possible??), or similar 😊. Share via Github: Add issue/section on website; Invite collaborators to add more; Continue to add to this over time - Room 3 - Written: Bailey - [name=Bailey Harrington]: I am creating a website for my first main milestone. I am debating between Wordpress (which I actually started with) and GitHub Pages (which will allow me to do more of the things I want to do). Broken down parts of this include: - figuring out how/whether I can use a modified verison of a GitHub pages theme (I need to check their licenses to see what type of modification is allowed) - writing content for the static pages: About, Contact, Home, et cetera - finding a way to allow people to submit contributions that does not require them to interact with the GitHub interface if they find that uncomfortable or unintuitive - Room 4 - Spoken: Georgia, Karega, Ismael, Arielle - [name=Georgia]: I have a tricky milestone for my project which is working out the moderation process for online platform. The steps to do this are: running focus groups to gather different people's opinions, collating and analysing the focus groups, researching other moderation processes and creating a scaffold, co-designing a code of conduct to support moderators, choose and recruit moderators, and design a data-flow/communication process. - [name=Ismael] I'm in a group (of 3) project and one of the biggest challenges is building a community. For this, we have agreed to share our discussions more widely and transparently. Which we have then whittled down to streaming our discussions on Twitch! (Yet to be done). So a milestone is to have one of our meetings over Twitch. And a simple task we all have is to open Twitch accounts! We are now using Asana to keep track of milestones and tasks. - [name=Arielle] I use workback plans to set milestones and then breakdown the steps needed to reach milestones. One of my main projects at the moment is organising a workshop for mid-November - [name=Karega] I'm woring on a backend database and a frontend platform. First time after having a call with my collaborators my vision became less clear, this was when we were supposed to develop a roadmap. So we have broken it down to two parts, bakend and frontend. Step one is just gathering all sorts of data we'll put in there. Made Notion account and have a slack channel where everyone can throw in their ideas. - Room 5 - Written: (Eva, Paula, Paul) - [name=Eva]: For us one of the biggest challenges was trying to figure out how to get contributors to add their workflows to our database. For this, we had several steps: 1) figure out a platform to share the resources (Github repo or github org?) 2) recruit potential collaborators 3) make a template and guide for submitting resources 4) make Slack channel to start building community - [name=Paul]: I find that when breaking down milestones, it can be too easy to not break them down thoroughly. This leaves room for ambiguity, and you may end up not being as productive as you should. - [name=Paula]: Set a deadline, set the schedule to go through the proposals, review the guidelines, add comments to each, do last review and send all the feedback back. - Room 6 - Spoken: Emma, Aleksandra, Camila & Teresa - [name=Emma] problems of getting other to interact with gitbhub as can be seen as scary by researcher that are not used to it. Using issues and then breaking these down into smaller achievable tasksable to tick things off! having short-, medterm goals Using issues and then breaking these down into smaller achievable tasksable to tick things off! having short-, med- and long-- and long-- and long-- and long-term goals Using issues and then breaking these down into smaller achievable tasksable to tick things off! having short-, medterm goals Using issues and then breaking these down into smaller achievable tasksable to tick things off! having short-, medterm goals - [name=Camila Rangel Smith] Breaking up a big milestone into smaller pieces is very useful to get progress on a project. It stops the process from being abstract. - [name=Teresa] Because I have not started my roadmap yet, I was listening to the other "roommates". We were also talking about the usefulness we think github has on project management even for the projects whih do not involve coding. Nice talk by the way :wink: **share-out (5 minutes)** - What did you find very interesting about this process? - Kate: Breaking work down into manageable steps always feels quite satisfying, but I rarely do it! - It's interesting to see the solutions people have to different problems: it creates a nice, problem-solving atmosphere! - What was challenging? - We did not pay attention to time and only left ourselves 60 seconds for discussion +1 :face_palm: +1 - Malvika: We will send a time reminder next time. You can also go back and +1 of written comments from your room. 🖥 Open Hardware --- Host: Yo/Malvika (a video will be played by one of them, whoever can :D) (10 minutes) [⏰ 80] **Guest speaker: Julieta Arancio** (video) Email: jarancio@unsam.edu.ar, Twitter: https://twitter.com/Cassandreces - Slides / notes: [https://youtu.be/BtUNjoTr5eg](https://youtu.be/BtUNjoTr5eg) - Notes: - Poeple who wants to make science needs tools to make science, but currently a lot of these tools are blackboxes - we may know the principles, but not the details of the processes, nor could we investigate them - Scientists need to be able to adapt tools to solve their specific scientific questions; another example in the pandemic is ventilators - it would be very nice to be able to adapt it to specific needs (of patients, etc); finally - a lot of existing tools are produced/supplied by a few companies, this creates restrictions and barriers to acccess for many - Open Science hardware tools: makes use of open-source software, designed by the community, making use of 3D printing - this means everyone from around the world can learn and build on the work of everyone else! - A wide range of open science hardware: standard lab equipment, sensors to reagents- all developed following best open practices to allow people to easily contribute and reuse/remix the work - Open science hardware is crucial for open science - hardware is integral to the collection of data, scientific analysis, etc - access and the ability to innovate in hardware determines who can do science and whose scientific questions are being answered. - How to get involed: - journal of open hardware - the GOSH forum to collaborate and get feedback - Questions / comments? (will be shared with the speaker on Slack to be addressed after the call, in their time zone) - Name / Question - - - :writing_hand: Silent Reflections and main takeaway (5 minutes) [⏰ 85] - Name / comments or notes and '+1's - [name=Teresa] I love this initative, great way to democratize Science +1 +1+10000 - - 🗣️ Closing & Assignments --- Malvika (⏰ 2 minutes) - **Assignments** 1. Prepare to share your project online through Git Pages, Google Site, Wordpress or other option. - Check the [GitHub Intro notes](https://hackmd.io/@ols-2/week-05), [learning resource](https://malvikasharan.github.io/developing_collaborative_document/) and [video](https://www.youtube.com/openlifesci) from last week - A GitHub repo with detailed README, LICENSE and CODE OF CONDUCT files without a webpage are great too! 2. Create a project development plan for your project - [Assignment to help you use Agile methods](https://docs.google.com/document/d/1bn4qR9b3XmAYXT8GZK9yI1xI3GE71GBMQ0ySkXtba4o/edit?usp=sharing) to breakdown your milestones into smaller tasks and define a timeline for your milestones 3. If you haven't yet already, please select and start adapting a [code of conduct](https://docs.google.com/presentation/d/196NOwvIx2A_cSOKE7YEyDvww7lehxBmef9O4B_FLodc/edit?usp=sharing) for your repository in a file called CODE\_OF\_CONDUCT.md **After these assignments:** - Start creating a contribution guideline for your community: _we will revisit this next week so no need to rush!_ - You can transfer your tasks to a project management or kanban tools such as GitHub projects ([short intro](https://unito.io/blog/github-projects-agile/)), [Trello](https://trello.com/templates/project-management), [Asana](https://asana.com/uses/kanban-boards?msclkid=c0e51366148511fc77394d30727faada&utm_source=bing&utm_medium=cpc&utm_campaign=NB%7CUK%7CEN%7CBoards%7CEX&utm_term=kanban%20board&utm_content=Kanban%20Board), [Zenhub in GitHub](https://www.zenhub.com/) **Next cohort call:** October 22, 17:30 - 19:00 pm London time ([see in your time zone](https://arewemeetingyet.com/London/2020-10-22/17:30/OLS-2%20Cohort%20Call%20(Week%208))) - We will discuss Open Science II: Project Dissemination Plan - Open Q & A time - 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