This meeting uses UnSync conventions and takes place on our Discord channel; transcript of actual meeting chat published here. [ charter | meeting archive | schedule ]
Nothing fancy needed; just a wave. This helps us tell whether we have a quorum, interpret silence, hold people accountable, and know who we're collaborating with.
@Brian and @James: Thank you for volunteering to be maintainers of repos. Can you confirm that you received the relevant github invitations, accepted them, and have read the docs about maintainer procedures for didcomm.org and for this repo?
If anybody else wants to volunteer to be a maintainer, please feel free.
I (Daniel H) have been announcing this meeting in DIF, TOIP, and Hyperledger Aries. I also did preliminary announcements in the W3C CCG mailing list. Questions:
- Who attends other meetings (e.g., DIF interop group, WACI/PEx, Human Colossus, OIDC, IETF work on KERI, etc) that can socialize more broadly?
- How do we feed updates to Identosphere, DIF and TOIP's regular newsletters, etc?
- Should we should be socializing at conferences or groups that are outside the SSI orbit? LinkedIn? RSA conference? If so, where and how?
- How can we make sure that our UG announcements are on autopilot, so it doesn't require unsustainable heroics to get the word out?
- Are we all subscribed to the mailing list?
Proposed closure: Please make concrete proposals on chat about how to answer these questions. Volunteers appreciated.
@Brian raised a PR that adds some links to the main page. Since this was cosmetic, I just merged it. If you object, please note your concerns in the chat.
We have a PR for the outline and some initial content for the DIDComm Guidebook. Any content in this PR comes directly from the DIDComm WG repo, where efforts on an Implementer's Guide began but have been stalled a bit. As discussed in our last meeting, we are taking over maintainership of the resource.
I'd like to get this PR merged asap. The point is not to make the content great (yet), but to create a permalink for the resource, and to get the WG's github repo cleaned up. We can improve the content later. Current content includes everything we brainstormed in our last meeting.
Proposed closure: Please review the PR in Github and give an approval (in Github, not in Discord) for it to be merged (or itemize things that need to be fixed before you're comfortable). I propose that we try to merge the PR immediately after this meeting closes, unless requests for changes cause a delay.
Is anybody interested in volunteering to write a section of the book? Could be a tiny section, or something more ambitious. See outline in the PR above.
Proposed closure: Please volunteer in chat.
Did you think this meeting was effective? How could we improve?
Proposed closure: Please leave your ideas in chat.