# Book Dash, 30 Oct 2023 - Pre-Book Dash onboarding Sessions *tags: bookdash 2023 Nov event* --- https://pad.sfconservancy.org/p/ttw-bookdash-nov2023-onboarding * Date: 30 Oct 2023 * Call 1: 9:00 - 10:00 London time * Call 2: 17:00 - 18:00 London time * Hosts: * 9:00 am session: Batool, Saranjeet, Emma, Anne, Alex * [https://turing-uk.zoom.us/j/98164513009?pwd=eThWR1FZRkVYVm1TdVp3aHBBMkY3dz09]([]https://turing-uk.zoom.us/j/98164513009?pwd=eThWR1FZRkVYVm1TdVp3aHBBMkY3dz09[]) * Meeting ID: 981 6451 3009 * Passcode: 446126 * 17:00 session: Arielle, Anne, Alex * [https://turing-uk.zoom.us/j/94806111976?pwd=THBuTUtGb01HQW81Z0xpampvU0NhQT09\&from=addon]([]https://turing-uk.zoom.us/j/94806111976?pwd=THBuTUtGb01HQW81Z0xpampvU0NhQT09\&from=addon[]) * Meeting ID: 948 0611 1976 * Passcode: 204444 * Slides: [https://docs.google.com/presentation/d/1i1BWL4j8BmpmF32JxcB1i1xx9J\_W1bod75GFjY0pzNQ/edit#slide=id.gda155644db\_0\_1581](https://docs.google.com/presentation/d/1i1BWL4j8BmpmF32JxcB1i1xx9J\_W1bod75GFjY0pzNQ/edit#slide=id.gda155644db\_0\_1581) * Slides are available for download on Zenodo: [https://zenodo.org/records/10054798](https://zenodo.org/records/10054798) --- If you can't make it, please let the Book Dash committee know, so that they can work with you outside this call. ## 👋 Welcome! Save this link!: [https://ttw-book-dash.start.page/](https://ttw-book-dash.start.page/) This call is scheduled for the invited participants of the next Book Dash event hosted by The Turing Way taking place from 13 to 17 Nov 2023 online. Please note that everyone who participates in *The Turing Way* project is expected to abide by our Code of Conduct. Please see more details on the project, Book Dash and logistics details (shared by email before the event) for the upcoming book dash below the notes. ### 📝 Agenda * Introductions (get to know each other): 10 minutes * About the Book Dash (logistics, accessibility support, socials): 10 minutes * SMART Goal setting exercise in breakout (or quiet writing): 15 minutes * Report out and general discussion: 10 minutes * Wrap up and final words: 5 minutes * Reminder Scriberia artist on Thursday ### Call 1: 9:00 - 10:00 London time Chairs: Saranjeet and Batool. Backup: Anne and Ale Registered attendees for morning session: Richard Acton, Cari Hyde-Vaamonde, Sarah Gibson, David Sarmiento, Ceilidh Welsh, Eriol Fox and Mike Nolan *Name (optional: pronouns) - “icebreaker: your favorite collaborative project or tool” - you can also share a 'current favorite' * * Batool Almarzouq * Mike Nolan (he/him) - PenPot is very cool! * Susana (she/her): favourite collaborative project has to be TTW book!! * Ceilidh (sher/her): have to agree, it's the Turing Way 🙌 * Richard J. Acton - Renku (renkulab.io)r * Sarah Gibson (she/her) - mybinder.org! * Emma Karoune, she/her, well Turing way of course! * David Sarmiento, he/him, * Alexandra AA, she/her, The Turing Way, * Anne (she/her) - (aside from The Turing Way of course), penpot, are.na, miro * * * * * ### Call 2: 17:00 - 18:00 London time * Chairs: Arielle Bennet and Johanna Bayer. Backup: Anne and Ale Registered attendees for afternoon session: Gigi Kenneth, Jen Ding, Eriol Fox, Kalle Westerling, Maria Nanton, Fran Gomez, Patricia Loto *Name (optional: pronouns) - “icebreaker: your favorite collaborative project or tool” - you can also share a 'current favorite' * * Francisco GĂłmez Medina (he/him) - I love using Miro, the flexibility it gives for collaborative brainstorming is something I haven't been able to replicate anywhere else * Gigi Kenneth (she/her) - Miro * David Llewellyn-Jones (he/him): everything text files + git! * Kalle Westerling (he/they): It has got to be Miro for collaboration across Teams and doing it online especially * MarĂ­a Nanton (she/her) | Miro + Github! * Jesica Formos (She/her) | Github * Anne (she/her) - digital gardens! github! pads like this one! * Alexandra (she/her): one week ago I used Kumu and I loved it * Arielle (she/her) - GitHub * Johanna Bayer(she/her) - Git * Liz Hare she/her, just learned that Framapad is a great place towork together on documents that is also screen reader accessible * Patricia Loto(she/her): Padlet * Cari Hyde-Vaamonde (she/her): miro / padlet! * Jen (she/her) ### Overview of Book Dash Event: *1 week long, 5 contributions sessions, 1 social session per day - *You don’t have to attend them all, select 1-2 per day that works for you * **Slides**: [https://docs.google.com/presentation/d/1i1BWL4j8BmpmF32JxcB1i1xx9J\_W1bod75GFjY0pzNQ/edit#slide=id.g2946b76a5e8\_0\_29](https://docs.google.com/presentation/d/1i1BWL4j8BmpmF32JxcB1i1xx9J\_W1bod75GFjY0pzNQ/edit#slide=id.g2946b76a5e8\_0\_29) * See the index Etherpad index: [https://pad.sfconservancy.org/p/ttw-bookdash-nov2023-index](https://pad.sfconservancy.org/p/ttw-bookdash-nov2023-index) * We will have one** local hub**, in London available on Monday 13, Wednesday 15, Thursday 16 and Friday 17 from 9:30 - 17:00. If you're joining in-person please register by Thursday 09 November here: [https://docs.google.com/spreadsheets/d/1KGNc8nPCBv5nBrtsm0DfTfx6a8M4NRid/edit#gid=1815997574](https://docs.google.com/spreadsheets/d/1KGNc8nPCBv5nBrtsm0DfTfx6a8M4NRid/edit#gid=1815997574) * We offer ÂŁ50 subsistence cost for meals (online participants), and ÂŁ75 for any accessibility requirements - anything that will make it easy for you attend. All guidance can be found here: [https://docs.google.com/document/d/1STIXpGM1Wh4J\_1y85-hOCAmwKmPmQtFB/edit](https://docs.google.com/document/d/1STIXpGM1Wh4J\_1y85-hOCAmwKmPmQtFB/edit). if you have any questions please contact Alexandra at aaraujo.alvarez@turing.ac.uk - due by 30 November!! ***All the activity times and slots are provided in London time (UTC). See in you time here ***[https://arewemeetingyet.com/](***https://arewemeetingyet.com/***) * **Social event Monday 13 November**: Adding Scriberia illustrations to the Book (Emma) - Check out previous illustrations: [https://zenodo.org/record/3332808](https://zenodo.org/record/3332808) at 14:00 UTC * **Social event Tuesday 14 November**: We will have two ‘Show and tell’ sessions. One session led by Kirstie at 11:00 am (in English) and other session led by Susana at 17:00 (in Spanish) * **Social event Wednesday 15 November**: Creative Writing Workshop with JonnyWritesWords at 14:00 * **Social event Thursday 16 November**: A Scriberia artist will be there on Thursday - would you like to get some illustration? (Check out previous illustrations: [https://zenodo.org/record/3332808](https://zenodo.org/record/3332808) ) * **Friday 17 November**: On day-5 we have community share out: [https://www.eventbrite.co.uk/e/the-turing-way-book-dash-community-share-outs-and-celebrations-nov-2023-tickets-735396419487?aff=oddtdtcreator](https://www.eventbrite.co.uk/e/the-turing-way-book-dash-community-share-outs-and-celebrations-nov-2023-tickets-735396419487?aff=oddtdtcreator) 11 UTC + 5 UTC <-- **this is public, invite friends, family, peers, colleagues ** * Working Group Share-outs: [https://www.eventbrite.co.uk/e/the-turing-way-working-group-and-collaborator-celebrations-nov-2023-tickets-744284564167?aff=oddtdtcreator](https://www.eventbrite.co.uk/e/the-turing-way-working-group-and-collaborator-celebrations-nov-2023-tickets-744284564167?aff=oddtdtcreator) About *The Turing Way* and the Book Dash * Detailed Presentation about the project (slides: [https://zenodo.org/record/3615259](https://zenodo.org/record/3615259) / video: [https://www.youtube.com/watch?v=dlycvMU45ek](https://www.youtube.com/watch?v=dlycvMU45ek) ) * GitHub: [https://github.com/alan-turing-institute/the-turing-way](https://github.com/alan-turing-institute/the-turing-way) * There's a Github introduction Session on Monday 06 Nov, 17:00 London time ([https://pad.sfconservancy.org/p/ttw-bookdash-nov2023-github](https://pad.sfconservancy.org/p/ttw-bookdash-nov2023-github) * If you can’t join us for this GitHub session, please use this video to get familiar with the GitHub: [https://www.youtube.com/watch?v=lRW8mlpTw5M](https://www.youtube.com/watch?v=lRW8mlpTw5M) ## Goal setting exercise: Breakout We would like to help create some plans and topics they you would like to explore for your contributions in *The Turing Way*. This will help us assign some groups and help find collaborators in your work. * Please note that this goal setting can relate to the suggestions made by the reviewers based on your application (see your acceptance email). * We will be delighted to work with you to make sure that you are excited about your contribution to the Book Dash event. * These topics can be something that is either missing in the existing chapters or need to be updated in the project. * You personal motivation could also be to collaborate with others at the event to work on and support what they are working on * We also recognise - and celebrate the fact - that plans may change once you meet the other participants! Setting our personal goals will help us prepare better for your participation: * Specific: They precisely spell out what you want to accomplish and usually answer the 5 Ws (Who? What? Where?) * Measurable: They provide a specific indicator of success. * Attainable: They are realistic. * Relevant: They are important and practical. * Time-bound: They specify a deadline for when the goal will be met. *We are using this template by Danielle R. Schultz (2015). * *You can use the Etherpad of Zoom chat to share your SMART goals.* ### — Template— Name: <add your name> Specific: What do I want to accomplish?: Measurable: How will I measure my success?: Attainable: Can I realistically achieve this goal? What steps will I take? Relevant: Does this goal meet a specific need?: Time-bound: What is my target deadline? (potentially between 14-18 Nov): Goal statement: ### Group GOALS Previous Example Name: <Emma> Specific: What do I want to accomplish?: - Clear plan/structure of Community Management paper and some parts drafted. - CM case study? for TTW Measurable: How will I measure my success?: - Clear plan/structure written down. Attainable: Can I realistically achieve this goal? What steps will I take? - Gather reading and resource materials - Meet with Arron and Malvika to work on clear plan/structure of article. - Start drafting my sections of the paper. Relevant: Does this goal meet a specific need?: - Yes - the paper will help others to understand the specific role of CMs at Turing. Time-bound: What is my target deadline? (potentially between 14-18 Nov): - 18 Nov - plan complete and my sections drafted. Goal statement: By the end of the bookdash week, I want to have a clear idea of the structure of the paper and made progress on drafting specific sections. Name: Richard * *Specific* – target a specific area for improvement. * Restructure the Licencing chapter to group aspects of different licening areas into a common introduction with specific sub-chapters for different areas, e.g. software, hardware * Include the concepts of use restrictions on tools in the case of conventional software 'ethical source' and in the case of AI/ML models RAIL * New graphics for * copyright/patent/trademark * proprietary/permissive/copy left * Update the checklist page - how to do this well, compicated decision tree * *Measurable* – quantify or at least suggest an indicator of progress. * New introcution section the the common area covered is introduced at the beginning of the chapter * Each existing sub-chapter is reworked to removed duplications from the shared intro * *Assignable* – specify who will do it. * Input on the new flow / from the writers of the exising sub chapters to make sure we don't loose anything that they considered important in the new structure * Getting review from some people with relevant legal expertise would be great * Illustrations would require some help - scriberia * *Realistic* – state which results can realistically be achieved, given available resources. * New 'common' introduction has substancial work done on it from the previous book dash along with some content on use restrictions so this is fairly achevable * Going sub-chapter by subchapter to rework the redundant sections, is also I think acheivable but might not need to be completed entirely within the book dash * *Time-related* – specify when the result(s) can be achieved. * Name: Susana \& Ceilidh Specific: What do I want to accomplish?: 1 - look at at what we did in May 2 - focus on write up for main chapter of data hazards 2.1 - organize, clean (links to point below) 2.2 - see what we can take away/not urgent to include in write-up. 3 - clean up symposium write up: 3.1 - go through it 3.2 - cut it down 4 - submit pull request Measurable: How will I measure my success?: - By crossing each bullet point off. Attainable: Can I realistically achieve this goal? What steps will I take? * - asking other members for feedback * - maybe set and plan some times for working "alone", and other sessions open to discussion with other participants - yes đŸ’Ș-woop * - focused writing periods during the book-dash (no distractions with other tasks 😂) Relevant: Does this goal meet a specific need?: * - yes, this goal looks to use the use-case of the symposium to highlight the importance of data hazards Time-bound: What is my target deadline? (potentially between 14-18 Nov): - the week of the book dash (18th Nov) - write by Thursday, pull request on Friday Goal statement: - By the end of the Book Dash, we will have a ready to publish chapter on Data Hazards including a use-case on for the Data Ethics Symposium Name: Sarah Gibson Specific: What do I want to accomplish?: - Investigate methods to locally render the book in multiple languages Measurable: How will I measure my success?: - A workflow will be developed to render the book in different languages - Documentation is developed/published that allows others to follow the same process Attainable: Can I realistically achieve this goal? What steps will I take? - Investigate what steps the localisation WG are currently taking - Investigate current best practices from Sphinx and Jupyter Book communities - Scoped to local-only deployment. Getting it onto the internet and automating it are future tasks. Relevant: Does this goal meet a specific need?: - Yes. The localisation WG has done a lot of great work and we need to make it usable and visible! Time-bound: What is my target deadline? (potentially between 14-18 Nov): 17th Nov Goal statement: By the end of the Book Dash, I will understand how to locally render the book in languages other than English and write down/publish this workflow for others to work from. Name: Mike Nolan Specific: What do I want to accomplish?: 1. Develop section on CARE principles and relevant information about when they are relevant \& how to utilize them. 2. Provide additional resources towards Guide for Project Design related to evidence based community building including the following * a. Interview guides for gathering data from stakeholders on contribution process b. Methods for identifying contribution barriers \& designing solutions Measurable: How will I measure my success?: - Ideally, by the end of the book dash I will have two PRs open as an initial draft but might requrie feedback from others Attainable: Can I realistically achieve this goal? What steps will I take? - I have no idea :) I hope to acheive both! I have plenty of content for Goal 2 but will want to ensure I am not duplicating information already in the guide. Relevant: Does this goal meet a specific need?: - Goal 1: Yes, the need is discussed here [https://github.com/the-turing-way/the-turing-way/issues/3223](https://github.com/the-turing-way/the-turing-way/issues/3223) - Goal 2: Have not created a tracking issue for this need but have had conversations about it in previous community calls. Time-bound: What is my target deadline? (potentially between 14-18 Nov): - Hopefully have initial PRs submitted by Nov 18 but expect to have further edits and feedback for several weeks after to get feedback from other community members Goal statement: By the end of the bookdash week, I will have some language written for Goal 1 \& 2 that will somewhat resemble coherent ideas in the english language Name: David S Specific: What do I want to accomplish?: I want to write the Data Safe Haven ways-of-work into a TTW usecase * - Bonus if: laying out how to adapt to each project (going from usecase to guide) * - Bonus Bonus: contribute to data ethics by either finishing my draft subchapter or joining Susana and Ceilidih Measurable: How will I measure my success?: I produce a PR with all content ready for full review Attainable: Can I realistically achieve this goal? What steps will I take? - It is a lenghty writing exercise but achievable in a week - I have blocked time and will be the priority of my week Relevant: Does this goal meet a specific need?: Would say so, but this is a question for others, I think it will help have better tools for project management that also have a strong focus in team care and building Time-bound: What is my target deadline? (potentially between 14-18 Nov): 16 Nov Goal statement: By the end of the bookdash I want to have written a ways of work usecase that serves for others to adapt agile principles to research Name: Patricia **Specific: ** What do I want to accomplish? - I'll translate material about accesible events from Metadocencia and I'll add it to the WIP inclusive events chapter (initiated by Sophie Batchelor) **Measurable:** How will I measure my success?: - I will add material through a PR to the developing chapter on inclusive events for further review. **Attainable**: Can I realistically achieve this goal? What steps will I take? - Yes, I think so. Some steps to accoomplish to my goal: 1) Review the available material and collect the most relevant points, 2) translate them into English, 3) add this content to github and 4) finally, obtain some feedback for other participants. **Relevant:** Does this goal meet a specific need?: Yes, totally. Because I believe that accessibility cuts across all disciplines and having clear guidelines on accessibility will help to include more people in the TTW community. **Time-bound: **What is my target deadline? (potentially between 14-18 Nov): - Tentative Pull request on Thursday 16 or Friday 17 Nov. **Goal statement: ** - At the end of the bookdash week, I want to make material available to guide you in organising more inclusive and accessible events. **Name**: Jesica Specific: - Review the available materials on acces Measurable: Attainable: Relevant: Time-bound: Goal statement: **Name: Kalle** **Specific:** - Develop a chapter introducing formal project management methodologies for research software engineers (RSE) and research infrastructure roles (RIR). - Provide a foundation for researchers to design project infrastructure for coordination/collaboration with RSEs, Research Application Managers, and Community Managers. - Highlight project management generally, and delve deeper into specific methodologies/frameworks. **Measurable:** - Complete a draft of a main chapter/section introduction of a "Project management for research teams" section - Complete a draft of at least one subchapter on a specific project methodology/framework, e.g. agile/scrum/kanban **Attainable:** - I will prioritise writing the main intro and the chapter on agile - I will engage with community members via TTW Slack to gather insights and feedback in this process (and anyone interested is invited obv!) - Incorporate any feedback and contributions received through the above bullet point. **Relevant:** - The chapter will address a need and interest in the research community for "best practice" examples of project management in research projects - The idea is to bolster the Project Design section of The Turing Way, reinforcing the values of openness, transparency and reproducibility Time-bound: I aim to have a finalised draft and pull request by November 20. **Goal statement:** I will work collaboratively on a new section + one detailed chapter for The Turing Way, focused on formal project management methodologies/frameworks, suitable for research teams (with RIR roles, in particular). By the 20th of November, I will have finalised the main chapter and agile methodologies, incorporating any community insights and feedback. Name: Fran Specific: - Contribute a subsection to Academic and Industry Collaborations titled “Shaping industry-academia collaborations for open science” focused on best practices, lessons learnt, and case studies in successfully shaping ad navigating Academia-Industry collaboration. Measurable: - Complete the foundational structure of the chapter that future participants will be able to contribute to. - Contribute a first case study of best practices for successful industry-academia collaborations that lead to open science. Attainable: - I will identify collaborators and previous contributors to this section of TTW ahead of the book dash - Help conduct highly focused and agile discussions to structure the subchapter (“Shaping industry-academia collaborations for open science”) and begin contributing content to it. Relevant: - This is a very common issue for researchers that work with industry. - As a DCE RAM, I have to navigate the academia and industry tensions and ecosystems on a daily basis! Time-bound: - Aim to have a finalised draft and pull request by 18th November. Goal statement: -Contribute a subsection that will consist of an initial library of best practices and lessons learnt for achieving open science from at least one case study of industry-academia collaboration. Name: Jen Specific: Initial chapter framework for how open \& distributed AI collaboratives form - capture: [https://github.com/the-turing-way/the-turing-way/issues/3269](https://github.com/the-turing-way/the-turing-way/issues/3269) - wrap in this outdated PR: [https://github.com/the-turing-way/the-turing-way/tree/dingaaling/bigcodecasestudy](https://github.com/the-turing-way/the-turing-way/tree/dingaaling/bigcodecasestudy) Measurable: How will I measure my success?: Feedback from 2-3 people in the #open-source-ai group, PR with first page Attainable: Can I realistically achieve this goal? What steps will I take?: Get a first draft in a branch ASAP to solicit feedback, so potentially doing some pre-writing before the week and focusing on community feedback/conversation during the week Relevant: Does this goal meet a specific need?: Capturing info from TTW convos over the past year Time-bound: What is my target deadline? (potentially between 14-18 Nov): PR by Tuesday 15 Nov Goal statement: Create an initial PR on open source AI capturing convos/with feedback from the Slack group. Name: MarĂ­a Nanton Specific: - I would like to set a specific goal with the translation \& localization team. I haven't been able to join one of their coworking calls, but I plan to do so on november 9th so we can discuss some goals for the sprint. - The goal would be materialized in a **PR in the translation handbook, or a specific configuration for the infrastructure of the translation project** Measurable: - Feedback from the translation team (and others at TTW) Attainable: - Go over the translation team's call minutes - Do some translations on CrowdIn to get more familliar with the platform - Go over the translation handbook carefully to detect opportunities for adding or improving content, think of questions to ask the team, etc Relevant: - The goal will be aligned with the roadmap the translation team set up for the project's progress in 2024 Time-bound: Goal statement: Name: David L-J **Specific: What do I want to accomplish?:** 1. Updated references to Twitter so that they reference X and/or Mastodon 2. Contribute to the Code Review sections to introduce more material about how to handle code review respectfully and avoiding the pitfalls of power inbalance inherent in the process. **Measurable: How will I measure my success?:** 1. All references to Twitter are gone. Create a PR that removes references to Twitter. 2. Start a separate PR to discuss Mastodon, just as a skeleton. 3. A PR that introduces - at a minimum - a new section on code review power dynamics; within the Recommendations and Best Practices section: [https://the-turing-way.netlify.app/reproducible-research/reviewing/reviewing-recommend](https://the-turing-way.netlify.app/reproducible-research/reviewing/reviewing-recommend) **Attainable: Can I realistically achieve this goal? What steps will I take?** 1. The switching from Twitter to X is somewhat mechanical so should be a quick win. 2. The aim to create a PR related to Mastodon only needs to be a skeleton, but can be more fully realised if there's time. There's a lot of good material and expertise to draw from, from the Turing Way community. 3. Creating the text on Code Review is more of a challenge, but I'm highly motivated to get something done. The hardest challenge will be understanding the text that's already there and aligning what I'm hoping to include with it. **Relevant: Does this goal meet a specific need?:** 1. The shift away from Twitter - both the name and platform - I believe makes this timely. 2. On a personal level I continue to find code review challenging in spite of the existing good material written about it. It also remains a really important part of the development process, so I hope any improvements that can be made in the sections of the Turing Way would remain relevant. **Time-bound: What is my target deadline? (potentially between 14-18 Nov):** 1. I'm aiming for a simple Twitter/X PR before the end of Tuesday 15th. 2. The remaining days I'll dedicate to the Code Review changes, ideally a PR before the end of the 18th. **Goal statement:** 1. My goal is to ensure no reference to Twitter goes unchallenged, and to capture my thoughts on the challenges of code review in a way that will be beneficial to others. Name: Johanna Specific: Go through the RSE pull request, make sure it's reviewed and ready, look what oi missing Measurable: have the PR in a reviewable state Attainable: 1. identify gaps in the chapter 2. review the PR and add missing bits 3 identify reviewers Relevant: long needed Chapter on RSE, finally closing this PR Time bound: The worklaod is not too big- after the bookdash I should have a PR Name: Gigi Kenneth Specific: What do I want to accomplish?: * Edit drafts for the Data Feminism chapter. * Include relevant links to the draft. * Collaborate with Maya and anyone else who's interested in joining on how to make the chapter awesome. * Pull request for this chapter Measurable: How will I measure my success?: * Number of revised chapters/ sub topics per day. Attainable: Can I realistically achieve this goal? What steps will I take? * Split the chapters I'm going to be working on into the number of available days and see how that goes. Relevant: Does this goal meet a specific need?: * Yes, working on a chapter that addresses how data governance and ethics are important especially for underrepresented groups. Time-bound: What is my target deadline? (potentially between 14-18 Nov): on or before 17 Nov. Goal statement: Wrap up the edits with on the Data Feminism chapter. Name: Arielle Specific: What do I want to accomplish?: * Continue working on revamping the Project Design guide with best practices from Turing - I want to split out the project design checklist from project planning and propose a new structurd for the guide * Also want to get more images into the guide overall! Measurable: How will I measure my success? * PR merged to break out the checklist to a separate subchapter * Issue updated with new proposed structure, PR under review for new structure * 5 images added to chapters that previously did not have an image added Attainable: Can I realistically achieve this goal? What steps will I take? * Images and checklist are achievable and will be done on Monday/Tues * New guide structure will take longer and may stretch beyond the end of the Book Dash Relevant: Does this goal meet a specific need?: * Yes, we need to better incorporate the images into the guide * Also the project design guide hasn't been revised in some time, so is due for a refresh! Time-bound: What is my target deadline? (potentially between 14-18 Nov): 16 Nov Goal statement: Name: Cari Specific: What do I want to accomplish?: - Clear plan for chapter regarding use of algorithms / automation / AI in the justice system and the particular challenges of this task - Seek out collaboration with relevant people in the Turing working in associated fields - draft chapter Measurable: How will I measure my success?: - Clear plan/structure written down. Attainable: Can I realistically achieve this goal? What steps will I take? - Check previous correspondence from the last book dash. - Meet with relevant people to work on clear plan/structure. - Start drafting my sections of the paper. Relevant: Does this goal meet a specific need?: - Yes I can share my domain specific knowledge as a former lawyer and current visiting lecturer in King's College London. Time-bound: What is my target deadline? (potentially between 14-18 Nov): - 14 Nov - If not before, make contact with the relevant people in the Turing - 15 Nov - clear plan drafted - 18 Nov - plan complete and my sections drafted. Goal statement: By the end of the bookdash week, I want to have a clear idea of the structure of the chapter and made progress on drafting specific sections. Name: Anne Specific: - Reviewing material about running inclusive events - Cross-referencing material between Metadocencia and TTw - Landing page for Accessibility Guide landing page Name: Liz Specific: Review accessible events guidelines and accessibility policy, collaborate on policy and Accessibility Guide Landing Page: Measurable: I will complete reviews of the accessible events guide and accessiblyilty policy and collaborate on the landing page with the Accessibility Working Group.: Attainable: I will have time during the week to forcus on reviewing Relevant: Yes, the Accessibility Working group has goals to produce material to help plan inclusive events, set up an accessibility policy, and lay the foundation for the Accessibility Guide. Time-bound: What is my target deadline? Nov 17 Goal statement: Name: Emma Specific: What do I want to accomplish?: - Add more scriberia images to the book. - Facilitate a session about adding images to the book . Measurable: How will I measure my success?: - Ran the session on monday. - More images are now now the book! Attainable: Can I realistically achieve this goal? What steps will I take? - Make an issue about how to add images. - Where are images * Where do you add them in the the github repo * Finding a place in the book * Code to add to pull image into book * Adding alt text * Make slides for session. * write about workflow for adding images. Relevant: Does this goal meet a specific need?: - Yes - we need to add more new images. Time-bound: What is my target deadline? (potentially between 14-18 Nov): - 18 Nov - session run and lots of images added. Goal statement: By the end of the bookdash week, I want lots of images to be added and lots of people to know how to do this. Name: Sara Specific: What do I want to accomplish?: * Getting a nice outline to the Mental Health in Data science chapter. * do a bit of research to add nice and helpful material to the chapter * Check and create a to-do list to curate chapters for the health scientist path Measurable: How will I measure my success?: * - Make an issue with Mental Health outline * -Getting reviews/ideas on teh content * -Make an issue about the curation for specific path Relevant: Does this goal meet a specific need?: - Yes. Mental health chapter was highlighted as a need in the last book dash; same with curated paths Time-bound: What is my target deadline? * - to make an outline of both Mental health and curation: done within book dash week * - Chapter won't be done within the week, but I'd love to get some content done * -To-do list ready to review for curated chapters: end of the week. Goal statement: By the end of the boook dash week, I want to have a clear working outline for the Mental Health chapter so people can review and contribute and I can start developing content. I also want a clear and real to-do list for path-related chapter curation so I can keep working on it during next collab cafes Name: Esther Specific: I want to work on inclusive/open/engaging events Issues/PRs ([https://github.com/the-turing-way/the-turing-way/issues/3279](https://github.com/the-turing-way/the-turing-way/issues/3279), [https://github.com/the-turing-way/the-turing-way/issues/3307)](https://github.com/the-turing-way/the-turing-way/issues/3307)), follow the license chapter changes and the CARE section. If any time left I want to work on my PR review for the RDM chapter, but I should prioritise the events one. Measurable: How will I measure my success?: Contributed to the text / had a discussion with Sophia (if Book Dash participant), Review licence chapter changes / discuss things with Richard, review CARE section or discuss things with Nolan Attainable: Can I realistically achieve this goal? What steps will I take? Keep an eye out of any PR reviews on those topics + work at least an hour a day during the Book Dash on the event section Relevant: Does this goal meet a specific need?: Yes - addresses 2 existing issue + contributions from other community members Time-bound: What is my target deadline? (potentially between 14-18 Nov): This book dash! Goal statement: By the end of the bookdash there is a new section on inclusive/open events to the Turing Way + a section on CARE + changes to the license materials ## Planning Your *Turing Way* Contributions Based off of the SMART Goals that people have listed above, this ongoing list is being created with ideas, projects, and themes that we will have ongoing rooms made for during the Book Dash. **Applied Projects** There are a few projects and people that have applied to work with already at Book Dash. We are gathering information about people's interests and proposed projects, based off of the goals listed above. * Data Hazards * *Reach out to Susana Roman Garcia if you're interested in getting involved* * Licensing * *Reach out to Richard Acton if you're interested in getting involved* * Accessibility * *Reach out to the Accessibility Working Group (#accessibility channel on slack) if you're interested in getting involved* * Infrastructure * *Reach out to Sarah Gibson (join the #infrastructure channel on slack) if you're interested in getting involved* * Project Management and Project Design * *Reach out to David Sarmiento-Perez if you're interested in getting involved* * Governance * *Reach out to Alejandra Araujo Alvarez if you're interested in getting involved* * Data Feminism * *Reach out to Gigi Kenneth if you're interested in getting involved* * Algorithmic Justice * *Reach out to Cari if you're interested in getting involved* * Research Software Engineering * *Reach out to Alejandra Araujo Alvarez if you're interested in getting involved* * Translation and Localisation * Code Review **Other Project Ideas and Project Needs** We're starting to log project needs and other tasks that people can gte * Adding Scriberia images to the Book (session planned for Day 1) * * ## Open questions: * *If you are a returning member, and would be interested in helping us chair a session (there are 12 sessions throughout the week) -- please write down your name below! We will be in touch with you with details.* * * * * * Closing: * * * ### ### Wondering where to start? Here are a few suggestions for a good first contributions: * Start page for Book Dash: [https://ttw-book-dash.start.page/](https://ttw-book-dash.start.page/) * Start with the GitHub: [https://github.com/alan-turing-institute/the-turing-way](https://github.com/alan-turing-institute/the-turing-way) * README page: [https://github.com/alan-turing-institute/the-turing-way/blob/main/README.md](https://github.com/alan-turing-institute/the-turing-way/blob/main/README.md) * Contribution guideline: [https://github.com/alan-turing-institute/the-turing-way/blob/main/CONTRIBUTING.md](https://github.com/alan-turing-institute/the-turing-way/blob/main/CONTRIBUTING.md) * Style guide: [https://the-turing-way.netlify.app/community-handbook/style.html](https://the-turing-way.netlify.app/community-handbook/style.html) * Explore the Book's 5 guides: [https://the-turing-way.netlify.app/welcome](https://the-turing-way.netlify.app/welcome) * Make your first contribution with Good first issues: [https://github.com/alan-turing-institute/the-turing-way/labels/good%20first%20issue](https://github.com/alan-turing-institute/the-turing-way/labels/good%20first%20issue) * See this link for all relevant links and tips: [https://the-turing-way.start.page/](https://the-turing-way.start.page/) * Review an existing chapter by suggesting a few changes in the book and/or repository. * Flag the unclear or duplicated information in the book by opening an issue on the GitHub. * Fix an old issue or comment on the the pull requests. * Write your personal experience of reproducible research in this google form. * See more info on the GitHub: [https://github.com/alan-turing-institute/the-turing-way/blob/master/project\_management/online-collaboration-cafe.md](https://github.com/alan-turing-institute/the-turing-way/blob/master/project\_management/online-collaboration-cafe.md)