-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First draft of TTW history page #3159
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for the-turing-way ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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):
|
I'm drawn to the red cross of a CI failure like a moth to a flame... 🦋 🔥 |
Adding notes here from recent report:
|
Co-authored-by: Danny Garside <dannygarside@outlook.com>
Co-authored-by: Danny Garside <dannygarside@outlook.com>
❌ Deploy Preview for the-turing-way failed.
|
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? |
Adding breadcrumbs to #2080 - which includes a 'welcome' and 'history' page |
Woohoo! Well done 🎉 |
very nice, interesting to know the project is that young. 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 |
book/website/history.md
Outdated
The project was incubated during Kirstie's time as a [Mozilla Open Leader](https://mozilla.github.io/leadership-training/), and was funded by a grant within the Turing. | ||
|
||
Due to close relationships with the Jupyter Project, the book was written in JupyterBook. | ||
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some wording and questions
book/website/history.md
Outdated
The project has its roots in the [Mozilla Open Leadership](https://mozilla.github.io/leadership-training/), a programme that led to Kirstie's Mozilla Fellowship in 2016, which influenced her as a researcher and strengthened her commitment to working open. | ||
|
||
*The Turing Way* has been funded by The Alan Turing Institute since the very beginning. | ||
Due to close relationships with the Jupyter Project, the book was written in JupyterBook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's true. I think there might be an issue somewhere. @sgibson91 can probably share here as she was involved in the early days.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
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? 😄 |
book/website/foreward/history.md
Outdated
The project has its roots in the [Mozilla Open Leadership](https://mozilla.github.io/leadership-training/), a programme that led to Kirstie's Mozilla Fellowship in 2016, which influenced her as a researcher and strengthened her commitment to working openly. | ||
|
||
*The Turing Way* has been funded by The Alan Turing Institute since the very beginning. | ||
Due to close relationships with the Jupyter Project, the book was written in JupyterBook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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!
|
||
*The Turing Way* has been funded by The Alan Turing Institute since the very beginning. | ||
Due to close relationships with the Jupyter Project, the book was written in JupyterBook. | ||
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). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to flag - the use of "i.e." here is causing CI to fail
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edited to "for example"
In 2022, Malvika and Kirstie became co-leads of *The Turing Way*, and welcomed Anne Lee Steele as the new community manager. | ||
|
||
As the number of contributors to the project has grown to over 400 people, *The Turing Way* has also developed into a kind of ["community of communities"](https://ben.balter.com/2019/07/18/a-community-of-communities-oscon-2019/). | ||
Many ongoing projects have been developing alongside the expansion of the guides, demonstrating the need for internal systems that enable the sustainability and maintenance of the project more broadly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
Co-authored-by: Arielle-Bennett <74651964+Arielle-Bennett@users.noreply.github.com>
The directory introduced here seems to be misspelled ("foreward" rather than "foreword") which is tripping up CI. I'm cautious to change it because I'm not certain it won't mess up the currently open review suggestions, so just flagging it here so that it can be cleaned up before merge. |
Sorry @da5nsy - accidentally requested your review again! Thanks for flagging the misspelling 😅 , I'll make sure to investigate. |
23 April 2024: I am adding this timeline, first drafted for governance-related work in 2022 and 2023 (formatting is a little distorted, as this was copied over from another document!). This could be added here or separately in a timeline page, perhaps in the foreword. After discussing with @malvikasharan at a coworking this week, we saw that this this is something that would be good to integrate either in this foreword section here, or in the Afterward. I'll make sure to draft an issue with a larger structure or draft to make this more clear – for now, adding this as a comment!
|
Summary
Will close #1731 and #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)
What needs to be done?
Invite people to add images and curate issues and quotes from past 2 years
Highlight important milestones
Acknowledging contributors