Re: Materials from 2019-07-02 DID Working Group Charter meeting

Hi Rhiaro,
Well I am planning to sit this weekend and go through all the tutorials and
videos shared by Kim.
As this is the first time I will be doing such stuff. This could take me a
longer time than usual.

There could be a situation where I may need you to help me.

Will that be ok?

Regards
Sethi Shivam


On Wed, 10 Jul 2019 at 16:53, rhiaro <amy@rhiaro.co.uk> wrote:

> Hi folks, I've actually had convert the log files into html on my
> personal for-fun todo list for a little while, I just didn't get around
> to it yet. (Also because I keep missing meetings due to travel and
> reading the log files is not as nice as html.)
>
> So unless someone (Sethi?) replies to me to say they plan to do or have
> already done all of the historic ones by this weekend, I'll do them then.
>
> Markus, I'm also happy to get on top of doing the conversions after each
> meeting, once you've posted the log files.
>
> Cheers,
>
> Amy
>
> On 10.7.19. 10:57, Markus Sabadello wrote:
> > On 7/10/19 7:00 AM, Manu Sporny wrote:
> >> On 7/9/19 5:07 PM, Markus Sabadello wrote:
> >>> The meeting notes and recording are not in Google doc, but in
> >>> Github:
> >>>
> >>>
> https://github.com/w3c-ccg/meetings/tree/gh-pages/2019-07-02-did-wg-charter
> >>>
> >>>
> >>>
> >> You can see that there's a ".log" file and a ".mp4" file in the
> >>> repository.
> >> Yeah, but that requires a bit of insider knowledge to understand... and
> >> I expect that many don't click through.
> > I just expanded all the READMEs to list individual meeting files:
> >
> https://github.com/w3c-ccg/meetings/commit/4192bd74f9fcd6dc5811a713e9bdc4990fa47729
> >
> >
> > So e.g. the most recent one now has links to the recording and chat log:
> >
> https://github.com/w3c-ccg/meetings/tree/gh-pages/2019-07-02-did-wg-charter
> >
> >> For the more recent meetings we have logs, yes... wondering if we can
> >> pull some of the older meetings from Google Docs into some
> >> publicly-readable format... there were a few in the beginning that
> >> didn't make it over to .logs.
> > I did some digging and found out out:
> >
> > - The 2019-03-21 DID Spec meeting had notes only in Google Docs.
> > - The 2019-03-21 DID Resolution meeting had notes only in Google Docs.
> > - The 2019-02-07 DID Resolution meeting had notes only in an email on
> > the list.
> >
> > I just added those in PDF format:
> >
> https://github.com/w3c-ccg/meetings/commit/a42bec989fdb6f6fc17ac5ef54ecc7e611fbebfc
> >
> > With this, unless I'm missing anything, I believe that all notes, logs,
> > recordings, slides etc. are now in Github.
> >
> >> We should probably also convert these .log files into our standard
> >> Web/email readable format here:
> >>
> >> https://w3c-ccg.github.io/meetings/2019-06-25/
> >>
> >> and post them to the mailing list as we do for our regular calls:
> >>
> >>
> https://lists.w3.org/Archives/Public/public-credentials/2019Jun/0044.html
> >>
> >> ... and I say this knowing full well it's more work to do that and we're
> >> all really pressed for time. Publishing .log files is the bare minimum
> >> that we need to protect ourselves from future IPR concerns (and it's
> >> good CG hygiene to publish in a way that is accessible to all --
> >> including those behind a firewall and those using screen readers -- the
> >> log files are pretty terrible for that).
> >>
> >> The good news is that we have the raw source files (.log and .mp4) to go
> >> back and generate the minutes retroactively... now all we need is a
> >> volunteer to do that. :)
> >>
> >> So... any volunteers want to learn how to publish the groups minutes so
> >> we can start doing that for Task Forces? It will only hurt a little bit,
> >> I promise. :)
> > Since I've been the one recording and uploading notes for these calls,
> > I'm probably also the natural choice for doing this additional
> > conversion/publishing work.
> > I'd just need some instructions and then I'd be happy to do it for past
> > and future calls.
> > Note that we have been using Zoom, not sure if/how that would fit in
> > with the process?
> >> -- manu
> >>
> >
> >
>
>