Add retro notes from new contributors ensemble

doc/retro/2021/07/17.md

@@ -0,0 +1,46 @@
+# 2021-07-17
+
+This retrospective was from the first [new contributors mob/ensemble]. Sadly [@mattwynne] failed to record the stream, so there's no video from this session.
+
+## Who
+
+* [@artismarti]
+* [@16sheep]
+* [@eoola]
+* [@mattwynne] (taking these notes)
+
+## What happened?
+
+* We read the issues at https://github.com/cucumber/cucumber-js/contribute
+* We decided to tackle one
+* We discussed how contributing to the repo worked
+* We changed what to tackle and tackled something simpler
+* We made a [PR](https://github.com/cucumber/cucumber-js/pull/1734).
+
+## What worked? What do you appreciate?
+
+* I learned general concepts that I could use in other open source projects
+* The issues were good for first timers. I'm keen to explore more now I've looked through them!
+* It was so much fun! All the intimidation I had about starting to do this vanished. Low stakes way of learning new things. A nice way of learning new stuff!
+* The team gelled almost instantly
+
+## What was puzzling or frustrating?
+
+* Why did the tests pass on your device but not mine?
+* Live Share vs Screen Share it was a bit confusing
+* Would it be easier to just run it locally on one of our machines? More realistic.
+* Twitch setup (Matt heard his own voice the whole way through, and we started late)
+
+## What should we decide / change for next time?
+
+* Do this regularly but on any codebase, not just Cucumber
+* Would it be easier to just run it locally on one of our machines?
+* Matt do more homeowrk on twitch setup
+* Let's do this again!
+* Update CONTRIBUTING.md guide to include pointers to basics about forking, how to name your branch etc., and some words of comfort and encouragement to make mistakes, ask for help etc.
+
+[@artismarti]: https://github.com/artismarti
+[@mattwynne]: https://github.com/mattwynne
+[@16sheep]: https://github.com/16sheep
+[@eoola]: https://github.com/eoola
+[new contributors mob/ensemble]: https://cucumber.io/blog/open-source/tackling-structural-racism-(and-sexism)-in-open-so/

doc/retro/2021/08/06.md

@@ -0,0 +1,38 @@
+# 2021-08-06
+
+This session was streamed live and recorded. Watch the video [here](https://www.twitch.tv/videos/1110016952).
+
+## Who
+
+* [@artismarti]
+* [@16sheep]
+* [@mattwynne] (taking these notes)
+
+## What happened
+
+* Discussed what to do.
+* Worked from Marju's fork, using our own local machines and VSCode each time we switched driver.
+* Re-did the work we did last time on the mobbing machine, using Marju's machine to submit a new PR ([#1764]) cleanly. We learned about `git cherry-pick`.
+* Started working through the pre-prepared issue [#1136] in a [branch on Marju's fork](https://github.com/16sheep/cucumber-js/tree/opt-out-print-attachments-1136)
+* Arti had to leave a bit early
+
+## Insights
+
+* Preferred working on own machine, not using the live share / mobbing machine.
+* Good to prepare. But, wonder if you over-prepare, it doesn't leave space for people to explore and learn.
+* Good to have an issue to focus on, and perhaps a failing test (but we could also write this ourselves).
+  * It would help to share what we're goin g to work on beforehand so people watching can also know ahead of time. Decide now for next session?
+* Matt didn't like being in charge of the timer.
+  * Could use different mechanism for changing turns, like when we make a commit, or when a test is passing?
+* More people would be nice. Should we make it easier for people to join? How? How often can we run it?
+
+### Actions / decisions
+
+* Next time, continue with fixing [#1136]
+
+[@artismarti]: https://github.com/artismarti
+[@mattwynne]: https://github.com/mattwynne
+[@16sheep]: https://github.com/16sheep
+[#1764]: https://github.com/cucumber/cucumber-js/pull/1764
+[#1136]: https://github.com/cucumber/cucumber-js/issues/1163
+

doc/retro/README.md

@@ -0,0 +1,13 @@
+# Retrospective notes
+
+From time to time, we run a mobbing/ensemble session on this codebase. At the end of each session., we 
+run a brief [retrospective] conversation in an effort to "turn up the good" – Woody Zuill.
+
+Each retro we run is recorded in this folder as a dated Markdown file.
+
+e.g. To find the retrospective for 23rd May 2020 you would look in the file `2020/05/23.md`
+
+We use [retro-tools] to help manage these files.
+
+[retrospective]: https://www.agilealliance.org/glossary/heartbeatretro/
+[retro-tools]: https://github.com/tooky/retro-tools