Meeting minutes

We're moving our meeting minutes to this Google doc!

Kick off meeting 21 March 2021

Attendees: Alyssa, Erin, Felicity

• We talked about the reasons why having an example project is good and what we want to be able to do with it. See About Chronologue
• We talked about the idea of Chronologue and whether it will fit our needs. We decided that it will. See About Chronologue
• Logistics:
  • We're going to keep our core working group small to start with.
  • We'll create something that show the shape and intention, then we can open it up to invite contribution from others.
  • To keep overhead light, we'll work in the wiki of the Chronologue repo until we outgrow it.
  • We'll communicate via Slack. We'll work asynchronously. We'll meet monthly and can meet ad-hoc if the need arises.
  • We imagine our deliverables will emerge like any typical OS project. We'll probably start with the ReadMe and then whatever makes sense next like an issue template, contributor guidelines, whatever.
  • We decided we won't necessarily start with finalized Good Docs Project templates. We'll use what we need to make sense for the project and clearly label any template is still in draft. Any work we do on templates for Chronologue can be used to seed/feed templates in The Good Docs Project.
• Double docs:
  • Because this is a fake open source project, all docs will be doubled. We're going to need a ReadMe about Chronologue, and a ReadMe about contributing to the Chronologue project.
  • We decided the docs are parallel, and internally consistent. We're using the paradigm of onstage (for Chronologue) and backstage (for everything to do with the planning and working with Chronologue project). We might have parallel repos.
  • We'll make sure any links in an onstage doc that need to link 'out of world' go to the parallel backstage doc.
  • For us world-builders, and any contributors, we'll need to have a very clear boundary of where on-stage ends, and backstage begins. Perhaps this will be obvious? We'll find out in time.
• We will want a web component.
  • Erin owns chronologue.dev. Let's also get chronolog.dev and setup a redirect.
  • We could have a Docsy site inside a folder inside the existing Chronologue repo.
  • We'll need a way to signal that this is fake. Something obvious in the footer and any links should pop-up a 'this is fake' message or go to ReadMe which explains the fakeness of Chronologue.
  • Building a fake project and fake community docs could be risky. We don't want a War of the Worlds situation happening. We'll make sure any links to emails or pages show an auto message "example purposes only - check out our real README over here". So that means as part of our MVP, we'll need an 'About the Chronologue' page so that all links can point to it.