Meeting minutes
<Lisa> Order is 2, 1, 3
<Lisa> close item 5
+present
I think I am scribing?
<Lisa> yes, thank you!
<Lisa> next item
Reminder from rashmi Mental health meeting Thursday at a later time 11am Boston time
<Lisa> next item
Trigger warning issue paper on the Agend
<Lisa> close item 9
<Lisa> next item
Survey discussed last week - is it open?
Julie - open and closed several times... Julie checking
<Lisa> close item 8
<Lisa> next item#
<Lisa> next item
How can people engage with Coga- helping people to get involved. Notes were put together - has it been useful? Sharing screen ...
Link above in IRC
New people or those involved less frequently may need help where the group has got to - orientation - documented issues around the process - proposal about re-arranging the subroups and processes between subgroups.
<julierawe> Lisa Re the WCAG 3 survey: The survey was re-opened and then closed again. It is still closed. The AG chairs will make an announcement about the status of the survey at tomorrow's AG meeting at 11am ET.
Issues around technical items such as subject lines in emails and problems with technology. Suggestion of a buddy system
<julierawe> I will send an update to the COGA task force after tomorrow's AG meeting when I have more information about the WCAG 3 survey, which is currently closed but may re-open soon.
<julierawe> I'll be right back...
<Lisa> next item
Lisa has provided context about the issues arising for people wishing to be part of Coga - will go on to discuss what is needed
Looking at Action items. Lis added some more tabs including orientation and training
List went through the expectations if you join coga.
<Zakim> Charli, you wanted to ask about another issue
Charli mention where she finds it hard trying to find out which document is being reviewed. Need provide a link and then to pause before starting to review the contents
Lisa aims to do this on all occasions and the links may be repeated but this issue has been added to the Actions doc.
Justine wondered if it would help to give an overview before going through the document.
Added issues around subgroups
Lisa asked if there were any other queries
Charli and Gareth are going to take look at the document
Lisa asked about the use of 'tabs'
Was it helpful to have all the documents linked as tabs
<EA> +1 with tabs
<Gareth> +1 with tabs
Tiffany +1 with tabs
<Justine> +1 to tabs
Lisa felt it was going in the direction of tabs similar to GitHub
<tiffanyburtin> I really like that we essentially have a manilla folder of a collection of related documents. Very helpful.
Charli was worried that she might be finding the tabs could confuse when the pointing is happening to a different document - but actually it is just that a different tab is being used.
<Jan> If we are going to use tabs, can we keep them in alphabetical order in case the list gets longer?
Is there a problem with them being alphabetical as it is a concertina?
<tiffanyburtin> We could add a numbering of importance if that would help
<LenB> +1 for order of importance
Julia add the levels of importance
<Lisa> next item
May need to re-visit some of the ideas next month
Helping people engagin with coga has a suggestions section - may add ideas to this document
Went through the tasks being worked on. Updating Content Usable, research, advice and support work of parent groups
Divide coga into giving advice... Monday meeting - working on structure and internationalisation etc. and then once a month those working on research join the groups.
The Thurday call could be more about research - working on particular topics. Have a regular all on their own topics - only join the Monday calls when there is a link up.
David mentioned that so much is going on - confusion sets in so try to split up with work.
However, there can be so may overlaps that people joining and groups can become harder to organise.
Would the overall gathering once a month make the involvement less challenging. So two main focus topics - advice and research? Then have the other subdivsions
Len felt that might well work with a division of effort but concerned that bottle necks may occur and it could be that just the sheer workload is an issue rather than the way time is spent on it all
Exeternal factors may also have an impact - such as WCAG 3 taking up more time.
Jennie suggested that maybe there could be breakout rooms for speedy comments about specific subgroups
Lisa mentioned that they had tried breakout rooms with some subgroups. Not easy with managing many people with overlapping membership
Julie suggested that leaders of task could use a Google doc to put in one sentence about what has been discussed in the previous week. The list would be short and skimable. This would provide the Monday meeting with a quick overview of what needs to be discussed or actioned
<Lisa> do we like the direction?
Lisa asked about the idea of dividing time into two groups - advice guidance group Monday and Research on Thursday
days not important re meetings more the general idea
<Lisa> +1
<Gareth> sorry, undecided as had to drop out
<Jan> 0
<Charli> leaning towards +1
<LenB> 0
<Becca_Monteleone> +1
<tiffanyburtin> Trying to encode what you said
Could you guess how many would go to research v general advice?
Tempted to say +1
<tiffanyburtin> I almost see three groups. Giving Advice, Research, Editors
<Jennie_Delisi> How would we measure success of this proposed approach?
Julie mentioned the editorial reviews and would probably in the research group, however the new structure and patterns and GitHub Issues but this might be more complicated as once again you have overlaps!
Lis wants people to feel interested in the calls their join
<julierawe> I'll be right back
Reducing cognitive load would be the measure of success.
Where subjects are related it could be people are working on both aspect - advice and research
Lisa suggested there needs to be time to think about the logistics - maybe wait and see whether people will like the idea more when talking about the practicalities.
<Lisa> next item
Action tabs has subject lines for emails - Jenni suggested a section about email etiquette.
The advice can all be found under 'Working with coga' tab in the Action document
Jennie suggested offering examples
<Jennie_Delisi> Good example: action needed by Friday: please thumbs up this link in Github
<Charli> +1 to put COGA at the beginning of subject lines!
Julie liked Jennie's example but suggested that you add 'coga' to the beginning of the subject line. Len added a document topic... so getting things in the right way is very important
<tiffanyburtin> COGA: Action Needed [Date]: Subject
<tiffanyburtin> Please don't just put day of the week alone.
<Lisa> Good example: COGA: supported desion making - action needed by Friday: please thumbs up this link in Github
Maybe need several examples and date is important rather than day
<Jan> Sorry - I have to drop
<Gareth> Sorry, i need to drop too
date important with time lines etc
<Jennie_Delisi> Reminder: use words for date - month/day in reverse order in different countries when using numbers