diff --git a/2021-04-20/audio.ogg b/2021-04-20/audio.ogg new file mode 100644 index 00000000..1e338646 Binary files /dev/null and b/2021-04-20/audio.ogg differ diff --git a/2021-04-20/group.txt b/2021-04-20/group.txt new file mode 100644 index 00000000..5bca5166 --- /dev/null +++ b/2021-04-20/group.txt @@ -0,0 +1 @@ +Credentials CG diff --git a/2021-04-20/irc.log b/2021-04-20/irc.log new file mode 100644 index 00000000..bddaee08 --- /dev/null +++ b/2021-04-20/irc.log @@ -0,0 +1,296 @@ +[2021-04-20T16:00:40.240Z] static as well +[2021-04-20T16:01:21.429Z] present+ +[2021-04-20T16:01:23.840Z] present+ +[2021-04-20T16:01:25.687Z] present+ +[2021-04-20T16:01:31.041Z] present+ +[2021-04-20T16:01:31.092Z] present+ +[2021-04-20T16:01:33.376Z] present+ +[2021-04-20T16:01:41.055Z] present+ +[2021-04-20T16:01:58.890Z] present+ +[2021-04-20T16:01:59.535Z] present+ +[2021-04-20T16:02:07.249Z] present+ +[2021-04-20T16:02:08.916Z] present+ +[2021-04-20T16:02:16.191Z] present+ +[2021-04-20T16:02:49.946Z] Agenda: https://lists.w3.org/Archives/Public/public-credentials/2021Apr/0109.html +[2021-04-20T16:02:52.946Z] https://www.w3.org/community/credentials/join +[2021-04-20T16:02:58.329Z] present+ +[2021-04-20T16:03:03.800Z] https://www.w3.org/accounts/request +[2021-04-20T16:03:15.454Z] https://www.w3.org/community/about/agreements/cla/ +[2021-04-20T16:03:31.520Z] https://w3c-ccg.github.io/meetings/ +[2021-04-20T16:03:50.599Z] present+ +[2021-04-20T16:03:51.185Z] present+ +[2021-04-20T16:03:59.525Z] present+ +[2021-04-20T16:04:07.927Z] q+ +[2021-04-20T16:04:11.140Z] ack Kim +[2021-04-20T16:04:58.857Z] i can scribe +[2021-04-20T16:05:12.475Z] thank you kim for your years of service to the community!! +[2021-04-20T16:05:16.363Z] scribe: pete_M +[2021-04-20T16:05:32.655Z] Topic: Introductions & Reintroductions +[2021-04-20T16:05:34.826Z] Thanks Kim. We'll miss your leadership and deep knowlege of github! LOL +[2021-04-20T16:05:40.396Z] Kim: Topic: Introductions and Reintroductions +[2021-04-20T16:05:41.444Z] present+ +[2021-04-20T16:05:42.346Z] Thank you Kim! May you Chair retire happily into the sunset! +[2021-04-20T16:05:46.146Z] q+ +[2021-04-20T16:05:59.697Z] ack kdenhartog +[2021-04-20T16:06:33.441Z] i knew it! +[2021-04-20T16:06:53.540Z] Juan knows the tech secrets... had no idea that Zoom stole the mic! +[2021-04-20T16:07:08.449Z] q? +[2021-04-20T16:07:17.979Z] (i was in the same IIW session so I had a hunch) +[2021-04-20T16:07:21.252Z] present+ +[2021-04-20T16:07:29.962Z] no mattr when you set a meeting, its a bad time for someone ; ) +[2021-04-20T16:07:30.101Z] present+ +[2021-04-20T16:08:43.907Z] Kim: Ive been CCG chair for a few years, about to move on from the position... I should also mention that we need a new chair +[2021-04-20T16:09:16.045Z] Kim: been working with Dept. Education for wallets and wallet interop +[2021-04-20T16:09:22.181Z] q? +[2021-04-20T16:09:39.792Z] Topic: Announcements & Reminders +[2021-04-20T16:10:06.459Z] Manu: do you want to announce the call later in the week? +[2021-04-20T16:10:13.879Z] yes, please. +[2021-04-20T16:10:16.390Z] q+ +[2021-04-20T16:10:26.566Z] Kim: IIW... its currently going on right now, where a lot of us will be. This is the weekly CCG call Tues 9AM PDT +[2021-04-20T16:10:39.708Z] FYI we told the IIW crowd that this call here is happening, so they are aware. +[2021-04-20T16:11:20.589Z] ack manu +[2021-04-20T16:11:23.098Z] q? +[2021-04-20T16:11:24.928Z] :-) +[2021-04-20T16:12:06.647Z] Manu_Sporny: today will be a quick overview of VC-HTTP-API, but we might need to continue Thursday +[2021-04-20T16:12:18.237Z] Announcement of the Special Topics Call: https://lists.w3.org/Archives/Public/public-credentials/2021Apr/0120.html +[2021-04-20T16:12:43.449Z] Kim: Topic: Progress on Action Items +[2021-04-20T16:12:45.638Z] Topic: Progress on Action Items +[2021-04-20T16:12:54.821Z] https://github.com/w3c-ccg/community/issues?q=is%3Aopen+is%3Aissue+label%3A%22action%3A+review+next%22 +[2021-04-20T16:13:37.944Z] Kim: Next steps from SOLID meeting, Heather would you like to speak for this? +[2021-04-20T16:14:28.006Z] heathervescent: the idea was we had 2 sets of SOLID meetings, an intro, and further discussions are still ongoing +[2021-04-20T16:14:36.145Z] Sarven +[2021-04-20T16:14:56.626Z] heathervescent: Sarven is the person I've been coordinating with for SOLID cohesion +[2021-04-20T16:15:27.932Z] q? +[2021-04-20T16:15:35.728Z] heathervescent: the community has a lot of interest, but we have been figuring out how to practically work together +[2021-04-20T16:16:20.376Z] heathervescent: there is group overlap, but the CCG has been really busy so the SOLID work items have been placed on the backburner +[2021-04-20T16:16:34.698Z] heathervescent: I'd welcome any additional help coordinating +[2021-04-20T16:16:52.409Z] +1, yeah, we've been encouraging the Solid CG to join the Conf Storage group +[2021-04-20T16:17:05.190Z] Kim: We might have an opportunity to work with Confidential storage... Dimitri are you here? +[2021-04-20T16:17:49.574Z] Kim: proposed to close this next week, if no objection? +[2021-04-20T16:18:05.642Z] heathervescent: im fine with closing, but this is the only place we are tracking it +[2021-04-20T16:18:23.194Z] (sorry, I didn't mean to skip the queue) +[2021-04-20T16:18:26.307Z] heathervescent: maybe mark it "low" priority for later instead +[2021-04-20T16:18:36.228Z] https://github.com/w3c-ccg/community/issues/181 +[2021-04-20T16:18:46.373Z] q+ +[2021-04-20T16:18:53.069Z] present+ +[2021-04-20T16:18:54.552Z] q+ +[2021-04-20T16:19:02.401Z] q+ +[2021-04-20T16:19:09.917Z] Kim: VC maintenence... who are the chairs of the VC maintenance group? +[2021-04-20T16:19:14.875Z] ack Wayne +[2021-04-20T16:19:15.343Z] q- +[2021-04-20T16:19:20.918Z] ack Man +[2021-04-20T16:19:46.127Z] q? +[2021-04-20T16:19:52.764Z] Wayne_Chang: once a merge happens we will be releasing the specs +[2021-04-20T16:19:54.446Z] q+ +[2021-04-20T16:20:09.111Z] ack heathervescent +[2021-04-20T16:20:16.544Z] heathervescent: wayne, do you have a time frame? can we get an update? +[2021-04-20T16:21:05.549Z] Wayne_Chang: do you mean a timeline for the PR or the 2nd spec? +[2021-04-20T16:22:04.149Z] heathervescent: this stems from February ... I'd appreciate a timeframe for when actions will be taken +[2021-04-20T16:22:13.819Z] Topic: Vc-http-api concerns and scope +[2021-04-20T16:22:21.575Z] Wayne_Chang: will do, thanks +[2021-04-20T16:22:26.279Z] https://github.com/w3c-ccg/community/issues/190 +[2021-04-20T16:23:20.369Z] refreshing the page periodically "resets" the memory leakage in Google Chrome, I find +[2021-04-20T16:23:21.263Z] https://docs.google.com/presentation/d/17FcR-KRv6klDff-A56nv7wz1OtcQDxvO4qosuQAmMRo/edit +[2021-04-20T16:23:31.861Z] ^ privvies? +[2021-04-20T16:23:39.103Z] jitsi screenshares spike CPU and fan for some (including me) but that shouldn't be a blocker on my account +[2021-04-20T16:23:41.622Z] lets just run the deck +[2021-04-20T16:23:46.590Z] Manu_Sporny: ive sent a PDF to the mailing list +[2021-04-20T16:23:55.925Z] I recently rebooted everything, so I'm probably fine. +[2021-04-20T16:23:57.447Z] we should reward folks who do work outside of meetings! thanks manu +[2021-04-20T16:24:05.336Z] Kim: maybe lets start there . . . +[2021-04-20T16:24:26.669Z] yees +[2021-04-20T16:24:32.627Z] i see the left half :D +[2021-04-20T16:24:50.490Z] nice! +[2021-04-20T16:25:08.588Z] Manu_Sporny: VC-HTTP-API is meant to enable system2system flows +[2021-04-20T16:25:38.827Z] ... we might only cover the first part, the proposal and challenges are meant for Thursday discussion +[2021-04-20T16:26:07.241Z] ... this is just my take on the problem statement, which came from a desire to issue and verify data in the VC ecosystem +[2021-04-20T16:26:14.864Z] q+ +[2021-04-20T16:26:23.458Z] ... not customer facing, Back of house server2server +[2021-04-20T16:26:32.181Z] I don't agree with the problem statement +[2021-04-20T16:27:00.177Z] ack Orie +[2021-04-20T16:27:01.188Z] ... there is disagreement with what this does +[2021-04-20T16:27:01.637Z] EU seems to have VC issuing API https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITALEBSI/Verifiable+Credential+API +[2021-04-20T16:27:10.701Z] though it returns un-signed VCs +[2021-04-20T16:27:21.642Z] +1 orie - this is part of the problem statement, but not the whole picture +[2021-04-20T16:27:41.240Z] q+ +[2021-04-20T16:27:55.840Z] Orie: i agree that this is an effective description for the community, but this API isn't only for internal use. That might be a bad description +[2021-04-20T16:28:14.885Z] Kim: maybe we can forward this discussion for later, but Manu please reply +[2021-04-20T16:28:56.880Z] Manu_Sporny: this diagram is only one iteration of architecture +[2021-04-20T16:29:26.455Z] ... this is where the disagreement is, "is it only a back end API, or should it be more in front?" +[2021-04-20T16:30:00.350Z] ... digital wallet, website has a credential, you authenticate, then you get a VC. We assume youre in a browser +[2021-04-20T16:30:11.730Z] ... in the backend, that website has to create the credential in some way +[2021-04-20T16:30:59.548Z] q+ re:Origin/Intent of this API from the DHS/SVIP Perspective +[2021-04-20T16:31:02.099Z] I will bring this up later, but I don't see why this work item should preclude external use, with appropriate auth or other prerequisites. +[2021-04-20T16:31:12.878Z] ack Manu_Sporny, +[2021-04-20T16:31:16.361Z] q? +[2021-04-20T16:31:17.156Z] Enterprise API integrations are not in the browser, supply chain EDI isn't done by hand clicking buttons in html... this is another challenge +[2021-04-20T16:31:17.978Z] Manu_Sporny +[2021-04-20T16:31:28.217Z] ... VC-HTTP-API would be used with the Issuer and Verifier +[2021-04-20T16:31:36.146Z] ack Anil_John +[2021-04-20T16:32:38.322Z] why a verifier would want to talk with to application backend? +[2021-04-20T16:33:35.701Z] Anil_John: in the past, we have been locked into an API. Internal vs External was not a concern. But for some use cases there might be exposure to the broader ecosystem +[2021-04-20T16:33:35.729Z] q? +[2021-04-20T16:33:38.936Z] @Nikos not sure I follow your question, but certainly some verifiers may want to have encrypted messages routed to them in back channel +[2021-04-20T16:33:41.277Z] @Nikos - it's optional. But some verifiers (in resource- or connection-restrained contexts) don't have the ability to verify stuff themselves. so they reach out to a backend +[2021-04-20T16:33:45.012Z] ack Manu_Sporny +[2021-04-20T16:34:06.887Z] Manu_Sporny: as Anil said, the origin of the VC-HTTP-API was to demonstrate true interop +[2021-04-20T16:34:47.122Z] ... we have run tests against multiple vendor platforms which helped us see the grand picture +[2021-04-20T16:35:08.854Z] Shout out to Anil for prompting this interop suite to happen, and to Orie for doing test suite heavy lifting (github activity tells me). +[2021-04-20T16:35:23.243Z] +1 +[2021-04-20T16:35:31.428Z] ... as Orie mentions, there are other use cases that vendors need to demonstrate, like Enterprise APIs +[2021-04-20T16:35:43.442Z] q+ +[2021-04-20T16:35:47.102Z] Interestingly on this previous slide... to see "signing presentations" grouped under issuance +[2021-04-20T16:35:58.148Z] thats another part of the troubles +[2021-04-20T16:36:03.216Z] This is the most valuable demonstration of interop of these standards I've seen to date, and sets a great precedent +[2021-04-20T16:36:08.925Z] q? +[2021-04-20T16:36:22.234Z] let's not call them "the troubles" no one's using carbombs +[2021-04-20T16:36:48.311Z] It is important to note that it is not just about interop testing... but about having API abstraction layer over a particular vendor implemenatation that ensures interop. +[2021-04-20T16:37:05.554Z] Amazing how easy it is to make fake certificates when there is no security turned on. +[2021-04-20T16:37:21.281Z] Having the this abstraction level API very much helps with Interop testing, as one may imagine! +[2021-04-20T16:37:23.042Z] +1 anil - this provides a common interface across implementations +[2021-04-20T16:37:25.700Z] +1 Anil, but I do want to call out what impressive work this is before we crap all over it +[2021-04-20T16:37:34.618Z] LOL +[2021-04-20T16:37:37.739Z] ... the API just started out as an OPEN API Spec, no uses cases, no spec documents, no documented data flows, no document structure agreement, no lead editor +[2021-04-20T16:37:54.192Z] q- +[2021-04-20T16:37:57.347Z] Yes! +[2021-04-20T16:37:59.456Z] q? +[2021-04-20T16:38:02.280Z] ... now, we need to make progress. +[2021-04-20T16:38:06.399Z] The SVIP demo day was impressive & I've been planning to bring some of those presentations to the CCG. +[2021-04-20T16:38:07.360Z] q+ +[2021-04-20T16:38:09.974Z] q+ +[2021-04-20T16:38:17.986Z] ack Juan_Caballero_(DIF/Spherity) +[2021-04-20T16:38:36.288Z] also, for folks who are not used to my humer, I am friendly, I think humor is motivating +[2021-04-20T16:38:37.941Z] Juan_Caballero_(DIF/Spherity): want to +1 that last slide, its really hard to know where to start +[2021-04-20T16:38:39.839Z] q+ +[2021-04-20T16:38:57.088Z] q+ +[2021-04-20T16:39:35.122Z] q+ +[2021-04-20T16:39:43.725Z] Kim: Manu you mentioned a call later in the week, we are not expecting a solution today. But is the idea to start a conversation here? +[2021-04-20T16:39:44.122Z] +1 to announcing the regular call time, and using the regular call to dive deep +[2021-04-20T16:39:55.672Z] airing of grievances! +[2021-04-20T16:39:56.441Z] open question - scope of VC-HTTP-API - is it just issue / verify? or is it all operations related to VCs? +[2021-04-20T16:40:05.742Z] Manu_Sporny: yes I think so. This is for concerns to be put on the table before the thursday call +[2021-04-20T16:40:25.291Z] ack markus_sabadello +[2021-04-20T16:40:28.587Z] ... community really needs to decide how they would like to work for these problems +[2021-04-20T16:40:59.297Z] q+ to suggest scope of VC HTTP API... +[2021-04-20T16:41:07.927Z] q- +[2021-04-20T16:41:21.886Z] q+ to discuss scope of VC HTTP API +[2021-04-20T16:41:45.355Z] ack heathervescent +[2021-04-20T16:42:00.764Z] heathervescent: we should look at the context of "how to solve this" +[2021-04-20T16:42:02.393Z] /me I just noticed Manu and MArkus have the same monogram +[2021-04-20T16:42:41.862Z] Twins, separated at birth... one growing up in the rough and rabble USA... the other in the cultured EU. +[2021-04-20T16:42:43.111Z] ... the work has been done in the open of the CGG but with another group +[2021-04-20T16:42:57.268Z] +q +[2021-04-20T16:43:06.210Z] ack man +[2021-04-20T16:43:16.522Z] q? +[2021-04-20T16:43:28.367Z] ... there have not been jumping off points which are easy for the community to join in on +[2021-04-20T16:43:35.650Z] q +[2021-04-20T16:43:37.116Z] +1 heather, there was essentially no way to engage the community on this work item. +[2021-04-20T16:43:42.306Z] q? +[2021-04-20T16:43:50.947Z] ... educating the broader community is important +[2021-04-20T16:44:06.008Z] huge thanks to mike prorock for starting the 101 ball rolling! +[2021-04-20T16:44:11.868Z] ack Kim +[2021-04-20T16:44:26.673Z] 101 is all heather :) +[2021-04-20T16:44:45.099Z] i imagine more useful edits will be made to that UCR straw man during next week's 101 session than in the last month combined :D +[2021-04-20T16:44:48.411Z] We've got like 3 101s in the planning +[2021-04-20T16:45:03.889Z] Thanks mprorock! +[2021-04-20T16:45:18.813Z] err, i meant for volunteering to 101 the trace-vocab +[2021-04-20T16:45:30.215Z] Kim: for the VC HTTP API work item, given what exists now how to make this more accessible? +[2021-04-20T16:45:35.732Z] ofc thanks to heather for the venue and the momentum more generally! +[2021-04-20T16:46:06.019Z] ... just for the community to think about for later, what else? +[2021-04-20T16:46:08.547Z] +1 to raising the bar for new work items +[2021-04-20T16:46:13.052Z] significantly +[2021-04-20T16:47:02.059Z] +1 Kim for bringing this up. I'd like to retroactively require the owners to add non-jargon details. +[2021-04-20T16:47:06.171Z] ... are there easy document clean ups we can do? One idea: for any work item that seems confusing, I like to see a 101 presentation for that +[2021-04-20T16:47:38.608Z] q? +[2021-04-20T16:47:42.999Z] ... writing / presentation / collaboration. The last thing is how we deal with PRs and other requirements for responses +[2021-04-20T16:47:50.580Z] heather, we might flag existing work items that fail to meet the bar, including codeowners from multiple companies, explainer in the readme, etc... +[2021-04-20T16:47:51.055Z] ack Manu_Sporny +[2021-04-20T16:48:00.033Z] Manu_Sporny: +1 to that, we can pause and document things better +[2021-04-20T16:48:12.271Z] Maybe survey other work, EU was mentioned earlier in IIW, Microsoft has one, I am sure there are many many more. State how this API relates to the prior work, will help make the scope more clear for newbies :) +[2021-04-20T16:48:21.745Z] ... Mike asked a good question, which is part of the conflict: "What's the scope of this thing?" +[2021-04-20T16:48:37.267Z] if its just internal, the way the tests are being used is fairly dishonest +[2021-04-20T16:48:37.467Z] ... it has become clear that many companies want there to be a "holder" API +[2021-04-20T16:48:39.347Z] @Orie, this has been on my chair todo list since July! +[2021-04-20T16:48:47.599Z] regaridng interop "proof" +[2021-04-20T16:48:55.505Z] Yes - we would like to have Holders and Mediators. +[2021-04-20T16:48:55.823Z] @Orie, wanna help me make those work items comply lol +[2021-04-20T16:49:20.841Z] ... there are tons of flows to manage when moving around the ecosystem. So do we want to open this up External/Internal APIs +[2021-04-20T16:49:23.552Z] sure, just need a process to make them visibly non formant +[2021-04-20T16:49:29.643Z] @heather ^ +[2021-04-20T16:49:45.238Z] then they will heal themselves naturally +[2021-04-20T16:49:51.818Z] q? +[2021-04-20T16:49:52.767Z] https://github.com/w3c-ccg/vc-http-api/issues/176 and https://github.com/w3c-ccg/universal-wallet-interop-spec/issues/84 +[2021-04-20T16:49:56.392Z] ... the scoping conversation is probably the biggest conversation we need to have +[2021-04-20T16:50:00.800Z] @orie, sweet. I'd sincerely appreciate some help, momentum & accountability. I've wanted to do this for a long time and cull the languishing work items. +[2021-04-20T16:50:11.806Z] we for instance require external exchange and operations using VCs far beyond issue / verify - so if vc-http-api does not support those use cases or external usage we need to create one +[2021-04-20T16:50:37.101Z] Bump PR: https://github.com/w3c-ccg/vp-request-spec/pull/9 +[2021-04-20T16:50:53.660Z] Anil_John: comments from Heather/Kim, I fully agree with the importance of fundamental process discussion +[2021-04-20T16:51:12.902Z] ... what is the value of VCHTTPAPI, multi vendor, multi platform, interop +[2021-04-20T16:51:44.902Z] ... everything we just talked about is the problem for this powerful technology +[2021-04-20T16:51:52.754Z] q+ +[2021-04-20T16:52:28.390Z] ack Anil_John +[2021-04-20T16:52:34.298Z] ... at the end, groups not in this community need to be able to use/understand this tech +[2021-04-20T16:52:49.967Z] ack Troy_Ronda +[2021-04-20T16:53:45.768Z] Topic: CCG work item / meeting requirements +[2021-04-20T16:53:53.927Z] +1 troy - similar support for broader scope from mesur.io +[2021-04-20T16:54:18.202Z] Kim: tracability work items brought up questions on how to work in the open +[2021-04-20T16:54:28.097Z] imagine even having calls! excited to have calls! +[2021-04-20T16:54:28.954Z] q+ to note who I gave rights to +[2021-04-20T16:54:37.206Z] Manu can also go +[2021-04-20T16:54:48.575Z] I can also comment +[2021-04-20T16:54:53.078Z] q+ +[2021-04-20T16:54:57.761Z] /give summary +[2021-04-20T16:54:58.312Z] q- +[2021-04-20T16:55:01.463Z] q+ +[2021-04-20T16:55:01.947Z] q+ +[2021-04-20T16:55:09.833Z] ack Manu_Sporny +[2021-04-20T16:55:25.547Z] ack Orie +[2021-04-20T16:55:27.176Z] q+ to close out on how to get your own meetings. +[2021-04-20T16:55:43.319Z] q+ +[2021-04-20T16:55:53.557Z] Orie: just to repeat my request to the chairs, if we have meetings, we need to make sure we are conforming to the rules +[2021-04-20T16:56:02.985Z] ... recording, notes, etc +[2021-04-20T16:56:26.264Z] ... the community should have explicit instructions on how to hold meetings that follow the rules +[2021-04-20T16:56:37.543Z] ... this will make it easier for everyone +[2021-04-20T16:56:58.895Z] is link to instructions ok? otherwise we're repeating a lot of info in each README +[2021-04-20T16:57:23.668Z] link to instructions is preferred by me if possible +[2021-04-20T16:57:33.539Z] heathervescent: work items can have a series of meetings, not sure if that's been noted in the CCG process documentation +[2021-04-20T16:57:47.244Z] +1 to instruction link +[2021-04-20T16:58:04.292Z] any instructions would be better than none, I would be happy to link to a single source of truth for running CCG meetings +[2021-04-20T16:58:06.338Z] ... maybe guidance on what work items that should not be recorded vs should be +[2021-04-20T16:58:07.907Z] q- +[2021-04-20T16:58:25.743Z] guidance on what to record sounds great +[2021-04-20T16:58:58.806Z] I'm writing some notes I'll add to a tracking issue +[2021-04-20T16:59:15.246Z] Minutes: https://w3c-ccg.github.io/publish_minutes.html +[2021-04-20T16:59:26.274Z] Github desktop interface: https://docs.google.com/document/d/1xsFZ6GKOHLsYwIN8DGYnVZRtxvx9eVZ4QQ6WJF6zgcI/edit +[2021-04-20T16:59:26.936Z] ... creating minutes has two separate documentations +[2021-04-20T16:59:30.006Z] Sorry .. Have to drop off for another meeting. Happy to chat directly if anyone has questions. +[2021-04-20T16:59:53.213Z] q? +[2021-04-20T17:00:00.013Z] ack heathervescent +[2021-04-20T17:00:14.261Z] q+ to suggest erring on the side of more (minutes, recording, etc.) -- overall better/safer in all cases to record than to not (even if the minutes/recordings are kept private in short term, when discussing something that happens to be sensitive in whatever way) +[2021-04-20T17:00:14.339Z] ack Wayne_Chang +[2021-04-20T17:00:29.183Z] Wayne_Chang: i support more permissive policy for calls for those in the community that want to participate +[2021-04-20T17:00:39.666Z] the easier it is to run and record meetings, the more often it will happen +[2021-04-20T17:00:49.091Z] q? +[2021-04-20T17:00:51.922Z] ... I'll be working on publishing these instructions, sometimes around mid May +[2021-04-20T17:00:57.574Z] ack Manu_Sporny +[2021-04-20T17:01:15.235Z] is there a place where i can find the list of scheduled meetings? +[2021-04-20T17:01:38.220Z] Manu_Sporny: +1 to refreshing the documentation. Tracability call seemed like they just needed a room, we appointed the people in charge, who now have Admin rights +[2021-04-20T17:01:47.564Z] Mahmoud: https://w3c-ccg.github.io/announcements/ +[2021-04-20T17:01:58.575Z] @mahmoud: we are trying to also add these meetings to a google calendar. +[2021-04-20T17:02:05.748Z] https://github.com/w3c-ccg/infrastructure/issues/11 +[2021-04-20T17:02:06.231Z] ... the infrastructure is there for the community to use, WITH Chair approval. This is rather easy to set up +[2021-04-20T17:02:18.140Z] and if you like @mahmoud, I can add the traceability meeting to the CCG calendar +[2021-04-20T17:02:23.625Z] @pete_M -- fantastic job scribing btw! +[2021-04-20T17:02:28.434Z] :D +[2021-04-20T17:02:35.198Z] how do we go about adding traceability call ot that list? +[2021-04-20T17:02:45.235Z] ... access is rather easy, the community simply should ask +[2021-04-20T17:02:45.740Z] ack TallTed +[2021-04-20T17:02:46.961Z] oh thanks heather thats my exact question! +[2021-04-20T17:03:13.720Z] Mahmoud - you can create a PR to that page I sent (it's a github pages site) +[2021-04-20T17:03:21.034Z] TallTed: its best to record more information rather than less. The culture is to do it in the open so everyone has access to work that is happening +[2021-04-20T17:03:23.528Z] @mahmoud: why don't you email me the details - heathervescent@gmail.com and I'll add it +[2021-04-20T17:03:23.771Z] thanks +[2021-04-20T17:03:24.219Z] It's been fun joining the CCG call this week! +[2021-04-20T17:03:25.579Z] yes, maximal transparency is very important! API design conversation makes everyone very nervous, getting this in the open ASAP will help calm all nerves +[2021-04-20T17:03:28.197Z] Kim: thank everyone. Call over! +[2021-04-20T17:03:29.244Z] see ya on github \ No newline at end of file