Book Dash Event Plans
Book Dash Event Plans¶
This subchapter provides information on the events that are organised for the book dash attendees. These events include a pre-event webinar for information, onboarding calls, GitHub introduction, development (coworking) sessions during the Book Dash and Community Share-Outs, which are explained below.
Webinar for Information¶
The planning committee members will host one webinar to share information about the Book Dash that can help interested members to plan their proposals for the event. These webinars will include a 10-15 minutes introduction talk followed by a session to address any questions participants may have. Recording and notes from this session will be published on the YouTube channel of The Turing Way.
Pre-event Onboarding Calls¶
The planning committee will host two onboarding calls, minimum of one week before the main event to ensure that all the participants are made familiar with the project, the format of the book dash, and how they can be contributing through their involvement at the book dash. It is an opportunity for the organising team and the selected attendees to get to know each other and discuss any concerns that they may have before the book dash.
Several participants often come to these calls with some plans and topics they would like to explore for their contributions in The Turing Way. Therefore, the host of this call facilitates a breakout session to allow attendees to draft their SMART goals for the Book Dash. These topics can be something that is either missing in the existing chapters or need to be updated in the project. We also discuss The Turing Way as a project in general and what the core team is working on to support the development of its guide on reproducibility, ethics, project design, collaboration, communication and a meta-book on the project itself. Most importantly, the core team goes through the contribution guideline and explain how attendees can effectively use their time at the book dash.
GitHub Introduction Session¶
One week before the Book Dash, 2-3 members from the planning committee will host a skill-up session for members who don’t have any prior experience with GitHub.
At this call, participants will learn how to:
create a new repository
create a (README) file: introduction to Markdown
submit changes (to The Turing Way) via Pull Request (PR)
see how to review PR or create issues
This session will help participants identify resources that they can use for self-paced learning. In the previous events, we have used the following materials:
During the Book Dash¶
On each day of Book Dash, we will hold three 2.5 hour-long development sessions, when hosting virtually each followed by a break or social event. When hosting an in-person Book Dash, four 75 minutes long development sessions will be facilitated, each separated by 15 minutes for report out followed by a break. Each development session will follow the Pomodoro technique that we also use for the coworking calls using the browser-based shared (cuckoo) clock to coordinate the time.
In the opening session of the first day, one of the planning committee members will provide an overview of The Turing way project and the resources that are available for the participants for their book dash contributions. Attendees will be then allocated in small groups with their collaborators based on their SMART goals. The collaborating groups will work together to build a roadmap and plans for their contributions as chapters, subchapters or other types of content. Participants are also encouraged to come up with the main sections of their contributions and collect their thoughts in bullet points on a GitHub issue.
The rest of the development sessions throughout the Book Dash will be facilitated in breakouts allowing members with similar ideas to collaborate. Participants can also work in self-organised groups or individually on their contribution ideas with the support of mentors. This is also a chance for everyone to meet the participants and helpers informally, learn about each other and connect with specific members who plan to work on the related topic during the book dash. Participants will be supported to collaborate in small groups, organising their thoughts and ideas for contributions during or after the Book Dash. Each development session will end with participants sharing their work with others and identifying new collaborators based on the similarity of their interests.
For participants who are unfamiliar with GitHub or would like a refresher (and did not manage to attend the GitHub introduction session), the planning committee members will guide them through the process of making their first pull request.
Reporting and Documentation¶
At the end of each day, participants can gather all their contributions on The Turing Way GitHub repository (issues, pull requests and notes) and add that in the shared notes. Specifically, during the last development session, they will be asked to add their details to the contributors file and provide anonymous feedback on a Pluses and Delta notes. This will help the planning committee to collect notes for their final report and improve future events.
Creating an environment for self-paced contributions¶
We acknowledge that everyone prefers different settings to work effectively and attentively. Therefore we create an environment for self-paced contributions to The Turing Way project.
Some recommendations to achieve this by managing the space at the book dash by:
set up shared notes for everyone to take notes together and draw inspiration from each other’s work (see template for notes).
offering a separate space (physical space or online breakout room) for open discussion for people who work better by discussing their ideas out loud.
when meeting in person, providing semi-quiet spaces or headphones for noise cancellation for people who don’t need active discussions.
Throughout the day, everyone is encouraged to ask for help, move around or change their position or group as needed. Participants are invited to offer feedback on other people’s work during the report out session.
Though there are designated breaks, participants are encouraged to take breaks whenever they need to decompress. A quiet room is arranged so that people can step back from the crowd as per their need for quiet time.