Meeting minutes
<Lisa> meetings this week
<Lisa> is anyone on zoom?
<Lisa> next item
Lisa: Review actions with people who are here.
Eric_hind: Will jump into the github issues resolved with Lisa to present a week from Monday.
Jennie: No updates for today
Jan: Translation update, looking for editors note November time-frame - work with Lisa to get ready.
DavidSwallow: No new updates
julieawe: Conversations are continuing.
Lisa: Upcoming, Next-gen content usable next, changes to github, working on next issue of issue papers. Looking for contributors.
<Lisa> next item
Lisa: Update on clock changes. Currently we base our meetings on EST(Boston). Be aware that outside of the US, there's a week window where calls are early in those time zones.
<Lisa> next item
<Lisa> next item
Lisa: Will not be available for editors meeting but line will be open.
<Lisa> close item 3
<Lisa> next item
Rain: Update on structure - status. Qualitative content was overwhelming, and there will be some scheduled sessions to help push forward the analysis
Rain: Realized that much of the (good) qualitative feedback was more generic to all documents, but we do need to focus on our specific document.
Rain: Focus on triage to ensure we aren't missing major feedback components.
Rain: Proposed schedule from doc link; takes through to December. In December, synthesize new patterns, final design recommendations by end of November
Rain: Two working sessions, one this week for triage only, working as individuals but cooperating online. The other way to review the triage and make design decisions. Then Rain to clean up the designs next week. The next week, we figure out what does and doesn't work. Then Rain updates and shares with Task Force week of Nov 11. Nov 18 task
force meeting to bring forward near final updates. Then update after that discussion and bring back to Nov 25 meeting to review final designs.
Lisa: Findability review may have to wait until January.
<tiffanyburtin> I can help
Rain: Scheduling triage, this week
I can help depending on the day
Frankie: Can help too
Lisa: Using Editors meeting window might make sense
Rain: Will review and send a calendar invite for all volunteers
Rain: Synthesize on week of 28th - early in week if possible. 9-1030 am EST on Monday the 28th?
<tiffanyburtin> Earlier in the morning is harder for me, but I can try.
<Jan> Rain - I can also help on Thursday.
Rain: Will propose the next meeting to figure out when and how to get the next meeting after that to work for everyone. Will prep on Friday for the next week's meeting
<tiffanyburtin> I can Rain, I have flexibility during the day. Early morning are a bit more difficult, but if that is the only time, let me know.
Jennie: Advance reading before meetings would be appreciated
<EA> I agree with Eric - thank you for the suggestion of advanced copies.
Rain: Biggest outcome, pros and cons related to single/two documents. Either everything into Technical report style document (more official with TR style), or a pared down TR style report with supplemental guidance which is referenced from the main document. We know that some people need it all in one place, one TOC, one view. But we do need a
way to get around the wall of text - the existence of a scroll bar showing a LOT of content can overwhelm.
Rain: There is an expectation around the document being friendly as a COGA lens consumable
Lisa: Concern on following our own guidance; we may be able to imply understanding of underlying concepts; e.g. neurodivergent, other words common in context
Rain: We can control the words but we can't control the visual styling - e.g. accordions to collapse sections.
<julierawe> +1 to Rain on sharing publicly what you've learned
<Jennie> +1
<julierawe> And many thanks for leading this terrific work!