support agenda as well as topic

[jnurthen]

We prefer to use zakim (in combination with agendabot) for the agenda in our meetings. Would it be possible for a new agenda item to act exactly like a new topic for github-bot?

[jnurthen]

so when we move between agenda items we use
zakim, next item/agendum (or zakim, take up item x)

so for example

18:21:22 [chlane]
Zakim, next agendum
18:21:22 [Zakim]
agendum 4 -- -> Step 2E isn't used for form field + name-from-label when it is the current node in an aria-labelledby traversal https://github.com/w3c/accname/issues/179 -- taken

We would like the line agendum X -- -> to be equivalent to a new Topic (both in terms of posting to a github issue AND closing the previous issue)

[dbaron]

This is somewhat related to the feature I recently added in #45. (See the output of github-bot, help for documentation.)

I'm curious how what you currently do integrates with scribe.perl minutes generation, which depends on Topic: (and Subtopic:). Does it?

[jnurthen]

scribe.perl works just fine with an agenda (assuming scribe.perl is what rssagent uses when creating the minutes). See aria minutes for examples.

[dbaron]

OK, I checked the IRC log for one such meeting -- I suppose the request is that a line like:

<Zakim> agendum 8 -- TPAC Announcement - Sep 11-15 Sevilla, Spain -- taken up [from jamesn]

be treated the same as:

<any_user> Topic: TPAC Announcement - Sep 11-15 Sevilla, Spain

It looks like it would also optionally need to strip off an initial -> because agendabot adds that.

Does that seem about right?

[jnurthen]

@dbaron Yes.

If it makes things simpler I'm happy to file a bug against agendabot to NOT add the -> as this seems at first glance redundant (and also causes extra verbosity for screen readers). The ' -> ' seems come from https://github.com/w3c/AgendaBot/blob/fa418c18ae38e6c33bc1f861faf37a578bb2650d/agendabot.pl#LL1440-L1446C6

I have no idea what an "Ivan Link" is. @bert-github do you know what these are and why it is added?

[bert-github]

On Wednesday, January 18, 2023 7:22:00 PM CET James Nurthen wrote: @dbaron Yes. If it makes things simpler I'm happy to file a bug against agendabot to NOT add the -> as this seems at first glance redundant (and also causes extra verbosity for screen readers). The ' -> ' seems come from https://github.com/w3c/AgendaBot/blob/fa418c18ae38e6c33bc1f861faf37a5 78bb2650d/agendabot.pl#LL1440-L1446C6 I have no idea what an "Ivan Link" is. @bert-github do you know what these are and why it is added?

Back in 2005, Ralph Swick suggested a way to add anchor text to links in IRC minutes: precede the URL by ‘->’ and follow it by the desired text. This convention became known as a "Ralph link’. David Booth implemented that in scribe.perl, the program that RRSAgent uses behind the scenes to format minutes as HTML. Later, I noticed that people made mistakes in the order of the arrow, the URL and text text; and some people also suggested that a different order would be more convenient. And thus when I made scribe.perl version 2, I added those alternative syntaxes and named them after the people who suggested them: the Ivan link (‘-> text URL’), the Xueyuan link (‘text -> url’) and the Inverted Xueyuan link (‘url -> text’). A similar syntax also lets you add ALT text for an image that way: If you use a long arrow (‘-->’), scribe.perl assumes that the URL points to an image and it will insert that image and the given ALT text. As for agendabot: When it finds an agenda and the agenda is in HTML, it has to convert the HTML to plain text before printing it on IRC. If there is a link in the agenda, it then tries to print not just the text, but also the URL of that link. And for that it uses the syntax of the Ivan link. That way, when the IRC minutes are converted to HTML by RRSAgent, the agenda topic will again have its link.

…

-- Bert Bos ( W 3 C ) http://www.w3.org/ http://www.w3.org/people/bos W3C/ERCIM ***@***.*** 2004 Rt des Lucioles / BP 93 +33 (0)4 92 38 76 92 06902 Sophia Antipolis Cedex, France

[jnurthen]

Thanks @bert-github
@dbaron stripping off the -> for posting to github seems reasonable.