- From: sethi shivam <sethishivam27@gmail.com>
- Date: Mon, 5 Aug 2019 12:50:52 +0530
- To: Kim Hamilton <kimdhamilton@gmail.com>
- Cc: "Siegman, Tzviya" <tsiegman@wiley.com>, Markus Sabadello <markus@danubetech.com>, Manu Sporny <msporny@digitalbazaar.com>, "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-ID: <CAG7szRNo-iU1e49+0pyZG3+krH0LGtv_7n1vN2Qgtutx6BrkYQ@mail.gmail.com>
Ok, thanks for the update. On Mon, 5 Aug 2019 at 10:47, Kim Hamilton <kimdhamilton@gmail.com> wrote: > I think Tzviya identified the root of our scribing problems. We appear not > to be using RRSAgent correctly, or at least, not in a way that's consistent > with standard W3C procedures. > > I'd like us to revisit what we're doing, as it's causing several of us a > significant amount of time each week to handle, even with the time already > invested in automation. > > We'll use the current meeting minute backlog as test cases, so expect a > hold on minute publication until we get a handle on this. I'll reach out to > the folks Tzviya mentioned, and we'll come up with a plan for getting this > under control. This will likely require a bit of volunteer work, so stay > tuned if you'd like to help. > > On Mon, Jul 22, 2019 at 10:40 AM Siegman, Tzviya <tsiegman@wiley.com> > wrote: > >> Hi Markus, >> >> >> >> I am not sure what tooling you are using within IRC, but you might not be >> using RRSAgent correctly. Please see >> https://github.com/w3c-ccg/meetings/tree/gh-pages/2019-07-11-did-spec-and-resolution >> for a guide. If you encounter issues with it, open a chat in #sysreq on >> IRC. There is usually someone there who can help. >> >> >> >> Tzviya >> >> >> >> *Tzviya Siegman* >> >> Information Standards Lead >> >> Wiley >> >> 201-748-6884 >> >> tsiegman@wiley.com >> >> >> >> *From:* Markus Sabadello <markus@danubetech.com> >> *Sent:* Monday, July 22, 2019 11:28 AM >> *To:* Kim Hamilton <kimdhamilton@gmail.com>; sethi shivam < >> sethishivam27@gmail.com>; Manu Sporny <msporny@digitalbazaar.com> >> *Cc:* W3C Credentials CG (Public List) <public-credentials@w3.org> >> *Subject:* Re: Regarding Text to HTML conversion >> >> >> >> Kim and others, >> >> We've been using IRC for scribing and queuing for several months now on >> the Thursday DID meetings, however for some reason the automatic logs only >> seem to be available for download for some of the meetings, not all. >> >> Perhaps there is still something that needs to be done to trigger the log >> (besides joining IRC and calling in via SIP - I do that every time). >> I apologize if this has been explained in the past and I missed it. >> >> In cases when the logs were not available for download, I manually >> copied&pasted them out of my IRC client as a fallback. >> >> Example meeting where the logs were available for download: >> >> https://github.com/w3c-ccg/meetings/tree/gh-pages/2019-07-11-did-spec-and-resolution >> >> Example meeting where the logs were NOT available (and I had to >> copy&paste them): >> >> https://github.com/w3c-ccg/meetings/tree/gh-pages/2019-07-18-did-spec-and-resolution >> >> I think it's great if Sethi can convert them to HTML and add them to the >> repo via PR! >> >> Markus >> >> On 7/22/19 4:02 PM, Kim Hamilton wrote: >> >> Hi Sethi, >> >> Thanks for taking the initiative on this. Some notes: >> >> >> >> The tools in here (https://github.com/w3c-ccg/meetings) generate the >> individual index.html meeting files from the downloaded IRC log files. Note >> that no IRC log files will be available if the meeting didn't use it -- I >> thought that the thursday DID meetings weren't using IRC (or at least >> weren't scribing in IRC), which is why they weren't there. >> >> >> >> Perhaps they started doing this for last Thursday's meeting, in which >> case using the scribe tools (https://github.com/w3c-ccg/meetings) and >> instructions here (https://w3c-ccg.github.io/publish.html) should work >> as normal. >> >> >> >> Adding Markus and Manu because they may be able to answer this. >> >> >> >> Please go ahead and create a PR. Also, let us know how you created the >> index.html (if not through the above tool). There should be people >> available to help review I'm on vacation so may be slow responding). >> >> >> >> Thanks again for doing this! >> >> Kim >> >> >> >> >> >> >> >> >> >> On Sun, Jul 21, 2019 at 4:18 AM sethi shivam <sethishivam27@gmail.com> >> wrote: >> >> Hi Team, >> >> I have converted the conversation to HTML. For the meeting we had on >> 18th july 2019. >> >> But i have seen that are no index.html files present in the folders of >> thursday meetings. >> >> >> >> Shall I create a pull request for index.html. >> >> I am doing it first time. Please guide me if i am going worng. >> >> >> >> I shall be very thankful to you guys . >> >> >> >> Regards >> >> Sethi Shivam >> >> >> >
Received on Monday, 5 August 2019 07:21:29 UTC