coordinate on proposed resolution on FPWD

[ghurlbot]

due 16 Feb 2023

[pchampin]

As a first step, I set up a dashboard with the specprod status of all publications:

https://www.w3.org/2023/02/pub-rdf-star.html

Clicking on a badge, you get a link to the log of the corresponding github jobs.

cc @rdfguy @ktk @gkellogg @afs

[pfps]

Cute, and useful.  I particularly like the current passing-failing demarcation. When I click on a "badge" I see a new link "check results" but this link appears to be to the results for sparql-update no matter which badge I clicked on.  I'm also not sure why two clicks are required to get to the result instead of having clicking on the badge just taking you to the results. peter

…

On 2/10/23 04:19, Pierre-Antoine Champin wrote: As a first step, I set up a dashboard with the specprod status of all publications: https://www.w3.org/2023/02/pub-rdf-star.html Clicking on a badge, you get a link to the log of the corresponding github jobs. cc @rdfguy <https://github.com/rdfguy> @ktk <https://github.com/ktk> @gkellogg <https://github.com/gkellogg> @afs <https://github.com/afs> — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSPY63XZQGKX4VJ5PNBUITWWYB3RANCNFSM6AAAAAAUW3CPAA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[pchampin]

On 10/02/2023 13:18, Peter F. Patel-Schneider wrote: Cute, and useful.  I particularly like the current passing-failing demarcation.

RDF 1.1 are more recent

When I click on a "badge" I see a new link "check results" but this link appears to be to the results for sparql-update no matter which badge I clicked on.

ooh, Javascript rookie mistake! (/never**/define a closure inside a loop... I should know better). Thanks for pointing that out, this is now fixed.

I'm also not sure why two clicks are required to get to the result instead of having clicking on the badge just taking you to the results.

Generating the link requires to requests to Github's REST API, so I prefer to do this lazily, otherwise I very quickly reach the limit imposed by Github on how many requests I can do. Then I found  it unintuitive and frustrating to click on the badge and have to wait for ~1s before the link actually "worked". I found it more convenient to reveal the link and then click on it. Note also that it also allows more flexible uses: you can click on multiple badges to generate all links, then right-click on each link to open it in differen tabs... But of course, all this can be changed or improved.   best

…

peter On 2/10/23 04:19, Pierre-Antoine Champin wrote: > > As a first step, I set up a dashboard with the specprod status of all > publications: > > https://www.w3.org/2023/02/pub-rdf-star.html > > Clicking on a badge, you get a link to the log of the corresponding github jobs. > > cc @rdfguy <https://github.com/rdfguy> @ktk <https://github.com/ktk> > @gkellogg <https://github.com/gkellogg> @afs <https://github.com/afs> > > — > Reply to this email directly, view it on GitHub > <#18 (comment)>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABSPY63XZQGKX4VJ5PNBUITWWYB3RANCNFSM6AAAAAAUW3CPAA>. > You are receiving this because you are subscribed to this thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#18 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKLZBWGESX3ET6IGBWQC3WWYWZXANCNFSM6AAAAAAUW3CPAA>. You are receiving this because you were assigned.Message ID: ***@***.***>

[gkellogg]

Cool use of the API! We should put a link to this either on the W3C group page, or somewhere in this repo, although API limits could get in the way of doing this, I suppose.

[pchampin]

I don't think that the badges count in the API limit. We only "consume" it when we click on the badge. So this should be safe enough.