I gave it a try and succeeded :)

https://github.com/rubys/whimsy-board-agenda-nodejs/commit/e5bbdb763739d8f0b658a0f7af790c3bbd798b31
 

At first I thought I was going to be overwhelmed but in the end it was quite 
easy to convert from
the current board agenda to the Node.js solution.

- Roy

On 2020/05/06 11:50:43, Sam Ruby <ru...@intertwingly.net> wrote: 
> I'll lob up an easy one, let's see if there are any takers.  The task is 
> to update the node.js version of the board agenda tool to add a new feature.
> 
> If you look at the current board agenda, the HTTP server team has posted 
> an early report, and mentioned two resolved CVE's.  CVE numbers are in a 
> well known format, and if a string that matches that format is found in 
> a report, it is highly likely to represent a CVE.
> 
> The code that renders a report passes the text through a number of 
> filters to augment the HTML that is generated.  It is easy to add a filter:
> 
> https://github.com/apache/whimsy/commit/1316a898d5e8c91e8a33d89565d12efc4842dd56
> 
> Whimsy already converts the code to JavaScript to send to the browser. 
> Go to 
> https://github.com/apache/whimsy/commit/1316a898d5e8c91e8a33d89565d12efc4842dd56
>  
> and search for "// hotlink to CVE" and a few lines later, "// determine 
> what text filters to run".
> 
> The code that would need to be changed can be found here:
> 
> https://github.com/rubys/whimsy-board-agenda-nodejs/blob/master/src/client/pages/report.js
> 
> The README for that project should contain enough information on how to 
> get started, but if it helps, I have a video walkthrough:
> 
> https://youtu.be/Bps7yQOYMEE
> 
> https://lists.apache.org/thread.html/rc68eb76ab9298e3b103e7782d05474dc9272c9c7820d642f4401449c%40%3Cdev.whimsical.apache.org%3E
> 
> - Sam Ruby
> 
> 

Reply via email to