<div dir="ltr">
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>Meeting of 7-April-2021<span></span></b></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>Present:</b> Ben Wilson, Jos Purvis, Ryan Sleevi, Dean
Coclin, Shelley Brewer, Dimitris Zacharopoulos, I<span>ñ</span>igo Barreira, Corey Bonnell, Don
Sheehy, and Jeff Ward<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>Antitrust Statement</b> read by Jos.<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>Minutes</b> of 24-March-2021 were approved. <span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>GitHub Updates<span></span></b></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Ryan – There were intermittent issues with the build
guidelines tool where work on a local branch or pull request would fail. Those
are sorted out now. It had to do with the Latex publishing to PDF. We made it
download less. We performed GitHub integration so that the steps are published
as a docker image which reduced random downloads necessary to build PDFs. <span> </span>There are minor changes left for the working
groups. <span> </span>Ryan has already worked on the Server
Cert WG issue, and other working groups should be able to copy from the Doc
GitHub directory to use the new tooling. Related to that, Ryan cleaned up
artifacts from the old infrastructure now that SC41 has landed (there shouldn’t
be any weasyprint or kramdown bits left over). Ryan is not aware of any
remaining action items on the automated building part, although he is still working
on the HTML output, which will help with the redlines.<span> </span>We are stable now on Github.<span> </span>Ryan will still be working on formatting to
support the Validation Subgroup’s certificate profiles (fonts, page sizes, and
margins).<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>Style Guide, List Formatting and Other Infrastructure
Committee Issues<span></span></b></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Jos – We have talked about style guidelines and improving
the list formatting.<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Ryan – The Style Guide would be useful. It is being tracked along
with other issues.<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Other issues related to the build guidelines action
repository include:<span> </span>improving HTML
output and plaintext presentation of tables, adding a markdown linter, and from
2016, build instructions for MacOS. So, with the new docker image those are ready
to close out.<span> </span>On the other side, there
is the Forum Infrastructure list on GitHub.<span>
</span>See the list below of items that are on the backburner and not being
actively worked on:<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Markdown Style Guide - <a href="https://github.com/cabforum/forum/issues/11" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/forum/issues/11</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Automation of Ballot e-mail: <a href="https://github.com/cabforum/forum/issues/9" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/forum/issues/9</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Release tagging: <a href="https://github.com/cabforum/forum/issues/8" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/forum/issues/8</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">IPR policy agreement enforcement: <a href="https://github.com/cabforum/forum/issues/7" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/forum/issues/7</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Weekly summaries of GitHub activity: <a href="https://github.com/cabforum/forum/issues/5" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/forum/issues/5</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">On the last item, we are making progress, but we need to work
through some problems to finish setting it up. <span> </span>Jos has the credentials, but we are struggling
on how to do this in mailman. What we’ll have is a private list where anyone
can post, archives not visible, which would receive mail.<span> </span>The Amazon account would send the weekly
summaries as mail, and then we’d need to configure it, so members could receive
mail from the GitHub bot account.<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">The GitHub Issues List is good place to track Infrastructure
Committee tasks/projects – see <a href="https://github.com/cabforum/forum/issues" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/forum/issues</a>.<span> </span>Or we can also use the Project Board – <a href="https://github.com/cabforum/forum/projects/1" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/forum/projects/1</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Other links in chat:<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Markdown Linter - <a href="https://github.com/cabforum/build-guidelines-action/issues/18" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/build-guidelines-action/issues/18</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Table presentation: <a href="https://github.com/cabforum/build-guidelines-action/issues/17" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/build-guidelines-action/issues/17</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Generate HTML output: <a href="https://github.com/cabforum/build-guidelines-action/issues/16" style="color:rgb(5,99,193);text-decoration:underline">https://github.com/cabforum/build-guidelines-action/issues/16</a><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>WebSite </b><span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">We still use GoDaddy for our website.<span> </span>Contact Jim Gorz to have him help create a
clone of the existing WordPress site for <a href="http://test.cabforum.org">test.cabforum.org</a>.<span> </span>Changes will be easier to examine using a
test website.<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Jos noticed when he tries to upload a ballot that it is
getting longer and longer to parse through the media. We should consider moving
older content to an archive outside of WordPress.<span> </span>One possibility is to move older content to <a href="http://archive.cabforum.org">archive.cabforum.org</a>.<span> </span>Also, we should ensure that we are periodically
backing up content. We should check with GoDaddy to ensure that is being done.<span></span></p>
<p class="gmail-MsoListParagraphCxSpFirst" style="margin:0in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>Membership
Management</b><span></span></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:0in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><span> </span></p>
<p class="gmail-MsoListParagraphCxSpLast" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Member
list still lives in Google Sheets. We need to create a new spreadsheet and make
sure there is a CA/Browser Forum account that is the owner and that it is
backed up regularly. Currently, spreadsheets are all owned by an individual, and
access is granted to editors.<span> </span>There should
be a Google account for managing the documents.<span>
</span>We can create a plain vanilla Google account, a G-Suite org or a bot
account that owns these. One issue with a plain vanilla account is that there might
be account protection monitoring issues if the same user is logging in from multiple,
geographically diverse locations. Jos will create a Google account. Backing up locally
is still a good idea. <span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><b>Meeting adjourned.<span></span></b></p>
</div>