From 82cae7826d5070ed35f660ad6d4ae227bfce722f Mon Sep 17 00:00:00 2001 From: Sean Madsen Date: Tue, 6 Feb 2018 16:28:17 -0500 Subject: [PATCH] Touch up meeting notes --- meetings/notes/2018-02-06.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/meetings/notes/2018-02-06.md b/meetings/notes/2018-02-06.md index e24e0e4..9169027 100644 --- a/meetings/notes/2018-02-06.md +++ b/meetings/notes/2018-02-06.md @@ -20,13 +20,13 @@ We want to have another remote docs sprint. We did some work at this meeting to * We will focus on the **User Guide** because it's the guide that has now gone the longest without the type of attention that a sprint would bring. * Within the User Guide... - * Currently [23 open issues](https://github.com/civicrm/civicrm-user-guide/issues). We c + * Currently [23 open issues](https://github.com/civicrm/civicrm-user-guide/issues). * Also, this is probably not reflected in the issue queue, but there are a lot of places in the User Guide that could use additional links, for example internal links to other chapter and also external links to other guides. * Would be good to create new tickets for tasks as needed ### Schedule -* Will be **March 22nd, 23rd, and 24th** +* Will be **March 22nd, 23rd, and 24th**, 2018 * This is a Thursday, Friday, and Saturday, which sounded like a good idea to everyone. * We'll want to pick a 72 hour block of UTC time that roughly corresponds to these days, but also that doesn't leave AU/NZ stuck with too much weekend time during the sprint. * Last time we did a remote docs spring we picked one 12-hour period. A number of people planned to participate in the sprint but ended up being busy that day. So we figured that it would be nice to try having a longer time window to see if that makes it easier for folks to plug in. @@ -40,6 +40,7 @@ We want to have another remote docs sprint. We did some work at this meeting to ### Coordination * Sean will coordinate the sprint and do the following: + * Identify a specific 72 hour time window for the sprint that makes sense * make a blog post soon about it and get it into the events calendar on civicrm.org * make a follow-up blog post after the sprint is completed to announce its progress * make a GitHub milestone for the sprint and use it to track our progress on tickets -- GitLab