identify scribe

<Rain> scribe+ Eric_hind

<Rain> scribe+ Rain

<Rain> group generally acknowledging appreciation for Eric and scribing willingness

<Rain> Link to the version of the new pattern structure we are currently proposing: https://docs.google.com/document/d/1KHWpKAWOb6p7r-WdrdDUIqFB3BCVnLjRYVcEBM88hPQ/edit#heading=h.scqltz3rntje

Rain: From last week, broken up things categorically into 4 groups. But more granular consideration may be necessary (reviewing in this meeting).
... First; Title and subtitle of each grouping; short name and goal oriented subtitle (5 items; logical design, clear interactions, supportive functionality, understandable content, backup help)
... Row 2, role responsibility, when done, what phases typically done

<Rain> Eric_hind: does backup help mean internet connectivity independent

<Rain> Link to the version of the new pattern structure we are currently proposing: https://docs.google.com/document/d/1KHWpKAWOb6p7r-WdrdDUIqFB3BCVnLjRYVcEBM88hPQ/edit#heading=h.scqltz3rntje

John: Potential concern of too many categorization

Rain: This concern could be addressed by user testing (excessive categorization)

<kirkwood> rethinking, ignore my categorization comment.

Rain: Roles and phases commentary, reviews.

Jan: Potential acronym (CLUBS)!

Rain: Add consideration for 3P sourcing to phases

<Rain> Eric_hind: brought up that we also need to think about how 3P or low-code efforts that use other things might be included

Rain: Next steps, do lightweight user testing with prototype and identify other individuals who might be interested in materials and do a/b testing.
... Reviewed format of lightweight prototype, showed changes based on initial feedback (about 1 year ago)

<Jan_> +1 yes move forward

<Rain> Poll +1 for yes move forward with lightweight A/B testing to make sure this is the right direction

<Rain> -1 no, we need to do more work first

<Rain> 0 no opinion

+1

<kirkwood> +1

<DavidSwallow> +1

<Rain> +1 from Rachael as well

Structure V2 next steps

Rain: Looking for others to take up with the next steps; current group will stay as is (but others are welcome)

review current status of Images subgroup

<Rain> Figma file: https://www.figma.com/file/UTsZpFnA6Yf5jJBTz4FCTp/COGA-Illustrations-by-pattern?type=design&node-id=1844%3A11658&mode=design&t=epffj1pDhYUt90Dr-1

John: Images subgroup has a lot of core information that would be good as a leap off point.

Rain: Reviewed recent Figma designs for kinds of pages (by designers) that demonstrate different patterns - these will show examples that do things as per the updated criteria versus not.
... Reviewing and breaking down the designer provided 'pages' is allowing us to understand what needs to be done/compared going forward.
... Looking for volunteers to assist the breakdown
... Next steps, resetting the group, rebooting the pattern inventory and getting content back to the point of being able to bring back to task force.
... Added Tiffany to group

Jan: Potentially getting volunteer designers as well

Images subgroup next steps

This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: Eric_hind, kirkwood, Rain, tiffany, DavidSwallow, Jan_, Rachael
Present: Eric_hind, kirkwood, Rain, tiffany, DavidSwallow, Jan_, Rachael, Rain tiffany DavidSwallow, Jan_ Rachael
No ScribeNick specified.  Guessing ScribeNick: Eric_hind
Inferring Scribes: Eric_hind

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)