Meeting minutes
New Business
Jeff- email to the group to discuss support dimension today
Support Dimension
is that dimension too big/catch-all? Things that belong in other places? Needs some editing for consistency and make sure the right things are in there (key important/not too granular for every task)
Turn the comment into an editor's note- aware needs xyz, need your comments to edit and update in the working draft.
Jeff: email to the group to discuss support dimension today
… is that dimension too big/catch-all? Things that belong in other places? Needs some editing for consistency and make sure the right things are in there (key important/not too granular for every task)
janina: Turn the comment into an editor's note- aware needs xyz, need your comments to edit and update in the working draft.
… put it in the 2.4.1 section
we agreed at last meeting section that will point to the spreadsheet, 2.4.1 section for editor's note
janina: we agreed at last meeting section that will point to the spreadsheet, 2.4.1 section for editor's note
CharlesL: testing this at Benetech, made changes and made some updates..I have time to make changes...Today Susan sent an updated set of changes to the dimensions in the excel spreadsheet
… this morning I was able to add 2.4.1 section that points to the current maturity model spreadsheet, it's in Github in same directory and links to it
… there is an editor's note in that section that basically says final format is TBD, can add Jeff's note here
sheribyrne: want doc and excel in sync, while I created and maintained original file I appreciate Charles picking this up
CharlesL: we need to say we agree, update excel to match, and make same changes in proof points to match. To Jeff's point this is getting to be a very long section. Do we not worry about Susan's current edits and make sure docs are in sync? What do we use as the master?
David: we're past due for updating, TPAC in three weeks and we need to get an update published. Save the rest for the next update
Janina: yes we need to take this up, put on the list post publication
David: OK to publish as-is?
sheribyrne: should acknowledge it's not in sync and make sure we do that next
CharlesL: happy to make that note in 2.4.1 where we link to spreadsheet. We know out of sync, work in progress and we'll address this
Jeff: put some of the examples in there but not all of them?
David: let's put these in the notes.
CharlesL: I'll do after the call
Discuss TPAC Breakout
Janina: have several volunteers from corp participants, but not just corporate...a few panelist for breakout would be important. I can work with David on proposal, or Sheri. We have a few weeks left. Due Sept 3, but get done in the next week in proposing the breakout
Fazio: Can virtuall get Jonathan Town Lane, joined last year and can maybe share the experience using it without talking about name of the company
… Charles, Brian, Jonathan...Sheri?
Sheribyrne: yeah, we can talk about that
… I'll be available virtually
janina: we'll be requesting afternoon time so we can include North America comfortably
Fazio: I can write up narrative and send to Janina
Janina: need to be ready to answer why a W3C maturity model
… bears repeating, people might have forgotten
Fazio: Irfan too maybe?
Janina: some corporate feedback experience with the W3C maturity model, become a standard show wherever we can put this on at conferences in the future, we have a good story
Jeff: will there be call in info for TPAC?
Janina: Open to public for breakout sessions, with questions and comments
… need people tracking the comments in chat, Zoom call? Don't expect everyone to be IRC enabled.
update on GitHub/New Working Draft Readiness
CharlesL: I think it's just fixing the items from this discussion? Some wording issues in the dimensions, customer support team went through and some items weren't applicable to them and a few questions on understanding the proof points. We can address these later. 172 proof point discrepancy, and everything else looks like are good, add last editor note in new section.
… will be done after this call
Fazio: how should we publish?
Janina: Tell Roy to update current version on editor draft. Some parallel activity on homepage. Latest excel spreadsheet link, homepage under APA to show more things but doesn't affecxt publication
Fazio: once Charles gives confirmation, we give to Roy and we all promote
Janina: Yay!
Janina: you can ask Roy directly or ask me to do it, just put me in the loop
Follow up on Task Force Page replacing Wiki
Janina: whether we keep a wiki or not, W3C or github or keep in old silver or point to historic or say we don't use it...can change our minds later. But we are under advertised on the homepage.
… top page that describes what we do was something Roy put together when became part of APA, most discoverable thing and should be more specific than it currently is. Need 2.4.1 for latest spreadsheet find it here
… may be other things we want to change. Make a list of edits for Roy, at least that one change done before TPAC. Maybe some other ones, it's our opening homepage for the world
Janina: relatively permanent, just a set of updated information we can give to Roy. If we want to update continuously update then a wiki
Fazio: who wants to get to work on this?
Mark: keep wiki but make static. Took a look at it and have a list of recommendations, and a few things that are a question. Word doc for us to consider. Do I put this into an email for everyone?
Fazio: Yes and no. But we're on the call, so what questions do you have?
Mark: What should we get rid of? First thing was github issues assigned, github comments from first working draft, it didn't contain anything when I clicked into it.
… maturity modeling was the anchor text for the link
Janina: left over from silvers. Delete
Mark: Maturity model draft working doc. Is this used?
Janina: Ancient, take it out
Mark: draft of maturity model note didn't seem current version
Fazio: Delete
Mark: going to delete the old google docs that predate...are older versions. Next steps thought remove, but it's static so we won't have next steps
… participants, remove or update
Fazio: going to have participant list elsewhere
<janina> https://
Janina: would have to move it either way, now part of APA not silver. Need to look at that one and should update is the link (posted above)
… that's our opening face to the world, what do we want to say in here, what should people see when they first find us?
… who are we, what are we doing, our docs, how to get involved?
<sheribyrne> need to drop to put out a fire
Fazio: who wants to volunteer to get the notes together?
sheribyrne: if someone handles the github I can do it or work with Mark? Just providing the text to Roy?
Mark: happy to work on it with you
sheribyrne: I'll reach out to you
<CharlesL> The proof-points of each dimention may not be in sync between this document and what is in the latest excel Speadsheet template. We are experimenting on how detailed do we want to be and if this document only shows a sample of all the proofpoints for a dimension or if the complete list of proof-points should be identical.
CharlesL: proposed wording for the new editor's note (above)
Janina: not sure about the last sentence.
… can say we're still experimenting and are works in progress and may not be in sync
Jeff: might say, for most detailed info use the spreadsheet
Fazio: we can go through it in email
… Anything else?
… we'll be published in the next week or so and get ready for TPAC!