- From: Pierre-Antoine Champin <pierre-antoine@w3.org>
- Date: Wed, 20 Nov 2024 09:58:43 +0100
- To: Decentralized Identifier Working Group <public-did-wg@w3.org>, RDF-star WG <public-rdf-star-wg@w3.org>, JSON-LD Working Group <public-json-ld-wg@w3.org>
- Message-ID: <b3035dcf-a81d-49ef-8508-13d14df2fb1f@w3.org>
Dear all, I confirm that the IRC bot is now installed. 🎉 It is called m2gbot (minutes 2 github bot). It can be /invite'd on any channel. Basic use is: after the minutes have been generated by RRSAgent, type in IRC: m2gbot, link issues with transcript and it should do the magic. best On 15/11/2024 12:42, Pierre-Antoine Champin wrote: > > Dear WG participants, > > the DID WG, RDF-star WG and JSON-LD WG have been early adopters of my > "minutes_to_gh" script, > to include fragments of meeting minutes in the issues and PRs that > were discussed during meetings. > > I wanted to inform all of you of a significant change in how the > script works: > from now on, the script will *only* comment an issue/PR if it appears > as a topic or subtopic in the minutes. > Issues/PR simply mentioned in the discussion will *not* receive a > comment with a link to the minutes, as was the case before (but see > below). > > Experience showed that the previous behavior was creating a lot of > noise, some of which could not even be fixed by editing or removing > the spurious comments. So I decided to be more conservative. Using > issue/PR links in (sub)topic is already a largely adopted practice, so > I don't expect this to be too disruptive, but be aware that this is > now the only way to have the discussion reflected in the minutes. > > Please also note that issues simply mentioned in the discussion will > still be indirectly affected, as github adds a comment of sorts in an > issue conversation when that issue is mentioned somewhere else. You > have an example of this in > https://github.com/w3c/did-extensions/pull/593, where github added this > > > pchampin mentioned this pull request XXX ago > > Should there be a registry? Process to migrate to a W3C Registry? > #565 <https://github.com/w3c/did-extensions/issues/565> > > which was caused by a mentioned of this pull request in the transcript > inserted at > > https://github.com/w3c/did-extensions/issues/565#issuecomment-2476989295 > > There are cases where this cross linking maybe undesirable, but it > would be really hard to prevent (github is quite smart at recognizing > issue mentions). > Furthermore, those automatically-added cross-references do not > disappear when the comment which caused them is edited or deleted... > So please keep this in mind and do not mention issues or PRs lightly > on IRC (or do it off-the-record, using the "/me" command). > > best > > > [1] https://github.com/pchampin/minutes_to_gh >
Received on Wednesday, 20 November 2024 08:58:45 UTC