W3C home > Mailing lists > Public > public-w3process@w3.org > October 2018

RE: Github minute bot

From: Siegman, Tzviya <tsiegman@wiley.com>
Date: Mon, 8 Oct 2018 15:50:19 +0000
To: "singer@apple.com" <singer@apple.com>, Léonie Watson <tink@tink.uk>
CC: Florian Rivoal <florian@rivoal.net>, W3C Process CG <public-w3process@w3.org>, "L. David Baron" <dbaron@dbaron.org>
Message-ID: <BL0PR02MB4820C3D47D6EB5D34E1038A0D5E60@BL0PR02MB4820.namprd02.prod.outlook.com>
RIchard Ishida also created a minute bot, which is a little easier to use https://r12a.github.io/mins2issue/. 

Tzviya Siegman
Information Standards Lead
Wiley
201-748-6884
tsiegman@wiley.com 

-----Original Message-----
From: singer@apple.com [mailto:singer@apple.com] 
Sent: Sunday, October 7, 2018 5:13 AM
To: Léonie Watson <tink@tink.uk>
Cc: Florian Rivoal <florian@rivoal.net>; W3C Process CG <public-w3process@w3.org>; L. David Baron <dbaron@dbaron.org>
Subject: Re: Github minute bot

I’d be up for it. we might need remedial training on IRC behavior.

> On Oct 6, 2018, at 5:23 , Léonie Watson <tink@tink.uk> wrote:
> 
> Thanks Florian. +1 to adopting the bot.
> 
> 
> On 04/10/2018 00:11, Florian Rivoal wrote:
>> Hi Chair and Process CG,
>> David Baron has written a very useful little IRC bot, that's been in use in a number of WGs, and that I have just configured to be usable in the Process CG as well.
>> It posts minutes from IRC directly into the relevant github issue, highlighting any resolution taken within these minutes. It does so based on existing minuting conventions plus one new command. As a side effect, if we make the bot a member of the group so that it has the necessary access rights, if the issue it posts minutes to has an Agenda+ label, it will remove it, since the existence of minutes proves that the topic has been discussed.
>> I suggest we adopt it.
>> == Minuting, before ==
>> scribe: Topic: Foo
>> scribe: someone: I suggest we should fizbuz the blah
>> scribe: sometwo: That sounds great
>> scribe: Resolved: Accept suggestion to fizbuz the blah
>> scribe: Topic: Bar
>> scribe: Somethree: I don't think we have quorum today to discuss this
>> scribe: Chair: sure, let's postpone to next call == Minuting, after 
>> ==
>> scribe: Topic: Foo
>> scribe: github: https://github.com/w3c/w3process/issues/1234
>> * github-bot OK, I'll post this discussion to 
>> https://github.com/w3c/w3process/issues/1234

>> scribe: someone: I suggest we should fizbuz the blah
>> scribe: sometwo: That sounds great
>> scribe: Resolved: Accept suggestion to fizbuz the blah
>> scribe: Topic: Bar
>> * github-bot Successfully commented on 
>> https://github.com/w3c/w3process/issues/1234

>> scribe: github: https://github.com/w3c/w3process/issues/5678
>> * github-bot OK, I'll post this discussion to 
>> https://github.com/w3c/w3process/issues/5678

>> scribe: Somethree: I don't think we have quorum today to discuss this
>> scribe: Chair: sure, let's postpone to next call then
>> scribe: github: none
>> * github-bot- OK, I won't post this discussion to GitHub.
>> ====
>> The result looks like this: 
>> https://github.com/w3c/csswg-drafts/issues/3020#event-1803071187

>> Full documentation: https://github.com/dbaron/wgmeeting-github-ircbot
>> —Florian
> 
> --
> @LeonieWatson @tink@toot.cafe Carpe diem

David Singer
Manager, Software Standards, Apple Inc.


Received on Monday, 8 October 2018 15:50:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:51:48 UTC