First draft of TTW history page

[aleesteele]

Summary

Will close #1731 and close #2031

It has already been 4+ years since The Turing Way was founded! This chapter is being drafted here (also in pad form), and is aiming to collect testimonies about each stage of the project: https://hackmd.io/@turingway/cowriting-ttw-history

List of changes proposed in this PR (pull-request)

• Initial draft has been taken from onboarding documents for the Turing Way team: https://hackmd.io/pBysnLn2QxKMCHqPKvj9uA?edit
• What does this history exclude? Who does it exclude? How is it incomplete?
• Should this page be include as a separate sub page of the book?
• This would also be a great place to collect stories & experiences from the past year years of the project - as a means of writing a collective history of the project:

• What have your experiences been during X year of TTW?

What needs to be done?

• Draft Create history time line to add in the community handbook
• Draft timeline
  Invite people to add images and curate issues and quotes from past 2 years
  Highlight important milestones

Acknowledging contributors

• All contributors to this pull request are already named in the table of contributors in the README file.
• The following people should be added to the table of contributors in the README file:

[netlify]

✅ Deploy Preview for the-turing-way ready!

Name	Link
🔨 Latest commit	0e2cf9c
🔍 Latest deploy log	https://app.netlify.com/sites/the-turing-way/deploys/6470d69484b3b1000867b053
😎 Deploy Preview	https://deploy-preview-3159--the-turing-way.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[aleesteele]

Thanks for your feedback, @da5nsy! This is very much a work in progress, and the plan is to invite testimonies from every stage of the project - it's a work in progress! 😊

Adding here a screenshot from last year's Fireside Chat (June 2022):

• Caption: A screenshot of a powerpoint slide with a timeline on it, marked along four periods: 2018, 2019, 2020, and 2021. Each date features different visuals and descriptions.
  2018: Text says: "Proposal by Kirstie Whitaker approved.". Mozilla logo. The Alan Turing Institute logo. Scriberia illustration of Kirstie imagining project.
  2019: Picture of smiling Kirstie and others in office,. Text reads: "Book launched with 10 members, 3 chapters, many workshops, 2 Book Dashes. Year ended with Several chapters by 67 contributors."
  2020: Text reads: "Book Dash 2020, Project expanded to five guides, Community Handbook, social media, Translation started. 238 contributors."
  2021: Screenshot of Turing Way fireside chat logo, titled "What Exactly is The Turing Way?" Text reads: "Project growth, 134+ chapters, 1600 Twitter followers, 3000+ monthly visitors, citation in peer reviewed articles, government reports and policies, new projects emerged as extension. 309 contributors." Logo of HiddenREF.
• Documented as a tweet: https://twitter.com/turingway/status/1542862053739749379
• Documented as a google slide: https://docs.google.com/presentation/d/1qjBRS1-c41gLaf8kMm4pcwhoGLgHG-YrwTqrsEtn8pg/edit#slide=id.g13aa358dfea_0_1

[da5nsy]

Thanks for your feedback, @da5nsy! This is very much a work in progress, and the plan is to invite testimonies from every stage of the project - it's a work in progress! 😊

I'm drawn to the red cross of a CI failure like a moth to a flame... 🦋 🔥

[aleesteele]

Adding notes here from recent report:

• From 2018-2020, the project's foundations were established as a "Guide for Reproducible Research", with initial chapters, conceptualisations, and open source processes documented. A github repository was made for the project, and internal processes decided in how acknowledge of authorship works within the project (i.e. installation of Welcome bot, All-Contributors bot) and Collaborative spaces to contribute were created (i.e. Collaboration Cafe, Book Dash). In-person workshops were given in person on tools aligned with the project: particulary Binder and JupterBook, and the project was presented in many conferences across the UK.
• From 2020-early 2022: This period corresponded with the COVID-19 pandemic lockdowns, which transitioned many processes of contribution, collaboration, and documentation into remote ones. In part due to this, The Turing Way was able to expand greatly, from one guide on Reproducibility into five different guides related to project design, communication, collaboration, and research ethics. A global (and multilingual) community began to engage with The Turing Way, and the process of translation/localisation began informally. A Community Handbook was also established to document best practices that could be used by other communities. The Fireside Chat series was established in late 2021, facilitating shared spaces with networks and allies from across the open science ecosystem. The project received a few awards & citation in London Mayor report, HiddenREF Awards, Goldacre Report. Established Book Dash Planning Committee.
• From early 2022 onwards: Increased visibility of both The Turing Way project (public-facing book), and communities doing other kinds of work within the project (i.e. translation & localisation, infrastructure maintenance, accessibility). Incubation of 5 working groups: Editors & Reviwers, Trainers & Mentors, Accessibility, Environmental Data Science, Infrastructure Maintainers. The Turing Way organisational team has expanded from 8 to 30 people over the past year. Practitioners Hub has been established as of 2023, with addition of RPM (Research Project Manager). Project presented in in-person and remote contexts (50+) [citation 1], with growing number of citations. New workshops incubated, project contributors to broader movement building in open science by contributing to UNESCO Best Practices in Open Science, NASA TOPS, and other calls. Awarded "OpenUK" award for belonging.

[netlify]

✅ Deploy Preview for the-turing-way ready!

Name	Link
🔨 Latest commit	be53001
🔍 Latest deploy log	https://app.netlify.com/sites/the-turing-way/deploys/66bb9068e8696d0008a5076f
😎 Deploy Preview	https://deploy-preview-3159--the-turing-way.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[aleesteele]

After a conversation with @da5nsy - I'm switching this to a real PR! Adding this very basic version to TTW, with the idea of expanding it into more collective storytelling in the coming months. Can't let perfect get in the way of the good 😉

@malvikasharan @KirstieJane - I know there's some outdated language here around the core team, but are there any foundational edits, corrections and/or additions you would make to this basic skeleton version?

[aleesteele]

Adding breadcrumbs to #2080 - which includes a 'welcome' and 'history' page

[da5nsy]

After a conversation with @da5nsy - I'm switching this to a real PR! Adding this very basic version to TTW, with the idea of expanding it into more collective storytelling in the coming months. Can't let perfect get in the way of the good 😉

Woohoo! Well done 🎉

[jcolomb]

very nice, interesting to know the project is that young.
It would be easier to review if each sentence would end with a line break.

It may be interesting to write a section about the transformation of the turing way project into the turing way community.

I am also wondering if there is a relation between the rise of this community and the concomitant slow death of the openscienceMOOC project (2019-2020).

this file is probably something to link inside a organisation level readme #3282

[jcolomb]

Suggested change

	A github repository was made for the project, and internal processes decided in how acknowledge of authorship works within the project (i.e. installation of Welcome bot, All-Contributors bot) and collaborative spaces and events to contribute to the guides were created (i.e. Collaboration Cafe, Book Dash).
	A github repository was made for the project, and internal processes decided in how acknowledge of authorship works within the project (for instance the Welcome and All-Contributors bots were installed) and collaborative spaces and events to contribute to the guides were created (Collaboration Cafe, and Book Dash were organised).

[jcolomb]

some wording and questions

[malvikasharan]

That is not the entire truth.
The goal of The Turing Way is to provide a 21st-century book -- not static, and something that allows interactivity and creativity. JupyterBook at the time was the only option that allowed combining executable notebooks with flat MarkDown files.
JupyterBook has since inspired Quarto's development that offers this feature.

I suppose the other reason that you are highlighting ties to our commitment to build on existing open source technology and ensure that we have the opportunity to contribute back to the Jupyter system that is a critical open source infrastructure.

[jcolomb]

not sure it was the only option, bookdown (R package) date back to 2016, apparently 3 years before jupyterbook got its first release (?). I always wondered actually why jupyterbook was used (I find bookdown much easier to work with, probably because I only did small projects with it, though)

[malvikasharan]

That's true. I think there might be an issue somewhere. @sgibson91 can probably share here as she was involved in the early days.

[malvikasharan]

Ok, so speaking with Kirstie:

• 21st-century element was priority as well as ensuring upstream, contributions
• Bookdown was not executable - and Jupyter was offering that solution
• Also, we had a close connection with the Jupyter Book team which could offer advice and support

[EstherPlomp]

I think the overview looks complete! It does feel a bit like just facts are listed, so it is not super exciting to read. Perhaps add some quotes or a bit more personal story to the facts?

[EstherPlomp]

I'm not sure if this is the best sentence to start things with:

1. that wasn't the case in the beginning and
2. what does this tell anyone outside of the Turing?

[KirstieJane]

Yes - agree with @EstherPlomp - TPS came after The Turing Way!

[EstherPlomp]

There's a bit of a repeat with the expanding into the five guides with the next paragraph, and I think it can be more clearly explained that Malvika provided the capacity to do so and did not literally add the five guides herself - although almost of course :)

[malvikasharan]

Are you saying Malvika did not write all the 100s of chapters? 😆

[KirstieJane]

Yes - these two things are related but not causal - we got additional funding and hired @malvikasharan AND expanded because reproducibility on its own is not sufficient to address the major challenges (including incentive challenges!) faced by research data scientists.

[aleesteele]

Haha! Good catch - I'll make sure to edit this, it's very true that that wording might imply otherwise 😄

[EstherPlomp]

Maybe rewrite the next two sentences with The Turing Way as the main objective instead of the year. Now it looks like we're passively guided by time instead of via active thought/actions!

[aleesteele]

Very true Esther - and a lot has happened too! I'm updating this section to be more representative.

[KirstieJane]

Capturing a few notes from the Turing Way core team co-working!

I'll add a full review soon!

[KirstieJane]

Yes - these two things are related but not causal - we got additional funding and hired @malvikasharan AND expanded because reproducibility on its own is not sufficient to address the major challenges (including incentive challenges!) faced by research data scientists.

[KirstieJane]

Yes - agree with @EstherPlomp - TPS came after The Turing Way!

[KirstieJane]

This really needs to be more nuanced about how Open Life Science AND The Turing Way are inspired by the Mozilla Open Leadership training programme.

Both @malvikasharan and I credit Mozilla Open Leadership with transformational mentorship that has led us to contribute to changing the world through open and inclusive science practices.

OLS and TTW had parallel development rather than one coming before the other... I don't think OLS needs to be specifically mentioned in the history of The Turing Way project page.

@malvikasharan - what do you think?

[EDIT: I'm in a call with Malvika now - she agrees 😅]

[aleesteele]

Very true! I think this was something that was visible to me when I joined the team - but might be confusing for people who are just looking to learn about the project's history in a specific, contained way!

[KirstieJane]

Technically the funding came through in 2018 and then we launched at the SSI Collaborations Workshop in 2019.

[aleesteele]

Adding this in - thought maybe it should be moved further up?

[aleesteele]

Folks (particularly @da5nsy @jcolomb @EstherPlomp @KirstieJane @malvikasharan who have commented and reviewed here), I'm so sorry for my late response to this pull request!! I was on annual leave for the past few weeks, and am finally getting caught up on your thoughtful comments. Just wanted to flag that I am working on an updated draft throughout this week, and will add more responses to your comments here too! Thanks again. ❤️

[aleesteele]

Alright! Finally finished another review of this draft, apologies folks that it's taken a bit longer than expected!

• Added a bit more context to the founding section about the context, funding, and use of Jupyter Notebooks - nuanced by Kirstie and Malvika's comments (thank you!)
• Also added in a bit more: particularly removing OLS, and adding in the statement (that we always use in presentations!) about how the guides expanded also because of the wider needs of research data scientists (used your wording in particular - Kirstie!)
• Added a bit more to 2022 as well
• In general I agree with Esther's point about it not being the most exciting (mostly factual) read – but I'm hoping that this can be a starting point, where we can bring in people's quotes after it's up! 😄

[kallewesterling]

Just wanted to drop a comment here to say that this is SUCH an interesting and important page to have as part of The Turing Way. I'd love to see this merged soon so we can bask in all your glorious work over the past few years! 🎉

Btw, looks like the CI fails only because book/website/history.md isn't included in the book/website/_toc.yml file, so should be an easy fix, which would enable previews of the commits :)

/home/runner/work/the-turing-way/the-turing-way/book/website/history.md: WARNING: document isn't included in any toctree

[aleesteele]

Thank you so much @kallewesterling! Can't believe I forgot that - great catch! ❤️

I made a few changes to this pull request: pulling in some text from #2033 to create the forward section where this text can be embedded. I'm still facing build breaks though - no-bad-latin.py? Hmmm

@da5nsy - if you want to review these changes, perhaps we might even be able to get this merged by the end of Book Dash? 😄

[Arielle-Bennett]

Didn't Kirstie and Malvika explain previously that it wasn't just that there was a close relationship with JupyterBook but that the book was also open source, executable, and a prior relationship existed?

[aleesteele]

Good point! It's true that this phrase emphasises the relationship above the toolkit - edited this to better reflect that. Thank goodness for first drafts!

[Arielle-Bennett]

Suggested change

	A GitHub repository was made for the project, and internal processes decided in how to acknowledge authorship works within the project (i.e. installation of Welcome bot, All-Contributors bot) and collaborative spaces and events to contribute to the guides were created (such as the Collaboration Cafe and Book Dash).
	A GitHub repository was made for the project, and internal processes decided how to acknowledge authorship works within the project (for example, the installation of Welcome bot, All-Contributors bot) and collaborative spaces and events to contribute to the guides were created (such as the Collaboration Cafe and Book Dash).

We can point specifically to the Authorship chapter in the community handbook here - we should probably also be clearer on the "internal processes", was it Kirstie or the original project team who made the authorship decisions?

[da5nsy]

Just to flag - the use of "i.e." here is causing CI to fail

[aleesteele]

Edited to "for example"

[Arielle-Bennett]

I think it would be helpful to name some explicit examples here - from this sentence it's not clear what is meant by "many ongoing projects have been developing alongside the expansion of the guides"

Do you mean that the project is providing the community infrastructure to support smaller scale, or offshooting collaborations?

It's also not clear why this in itself demonstrates the need for internal systems around maintenance, I think those are two separate things so should be in two different sentences.

[bsipocz]

Also, cleaned up (rebased this) in the hope of getting a passing CI.