link to #2 and its spreadsheet

README.md

@@ -24,6 +24,8 @@ Examples of communication tools that support the SLOPI style include:
 - public roadmaps
 - public kanban boards
 
+(As part of [issue #2][] we are gathering examples in the wild in a [spreadsheet][].)
+
 While open source projects should endeavor to communicate in the SLOPI style whenever possible, this style is inappropriate for security, code of conduct violations, and telling co-workers on your floor that you brought in donuts.
 
 The SLOPI style can take some getting used to if you are new to open source culture. It's ok to be a little sloppy. Please don't worry if the message you send isn't perfect. The fact that you sent it in the open is appreciated. Open source is getting friendlier. A thick skin isn't as necessary as it was in the past.
@@ -34,4 +36,6 @@ We love contributors! Please see our [Contributing Guide][] for ways you can hel
 
 [discussion]: https://github.com/coreinfrastructure/best-practices-badge/commit/65ebe74d7bfdf661502978311200d0c32f7b8be8
 [Core Infrastructure Initiative (CII) Best Practices]: https://bestpractices.coreinfrastructure.org
+[issue #2]: https://github.com/good-labs/slopi-communication/issues/2
+[spreadsheet]: https://docs.google.com/spreadsheets/d/1wvG3XTd5YwA-SliOUCavQgqfK1jLVnlL9tuUsjHR0Ik/edit?usp=sharing
 [Contributing Guide]: CONTRIBUTING.md