[Infrastructure] Draft Minutes of Today's Meeting 2021-Aug-25

[Ben Wilson]

Draft Minutes of Infrastructure Committee

August 25, 2021

Attendees: Ben Wilson, Jim Gorz, Corey Bonnell, Jos Purvis, Shelley Brewer,
Mike Min, Ryan Sleevi, Wayne Thayer, Dean Coclin

Antitrust statement was read by Jos

Minutes of August 11, 2021, meeting were approved.

GitHub:

   -

   We have tagged the last few ballots up to the current release and are
   working on SC 48
   -

   Jos has tagged the issues list. Should we create common tags and rules
   like a style guide and provide guidance to chartered working groups? Ryan
   suggested that we take a hands-off approach. The downside of the
   style-guide process for this would be that everyone would have to learn it.
   We haven't done it for the Face-to-Face minutes, and they have worked out
   well, even though the styles are all over the place. We should leave it to
   the chartered working groups to adopt their own tagging, labeling and
   styles. They can reference the approach used by the Server Certificate
   Working Group. Later, we can adjust tags, etc., if and when we begin work
   on tooling for any automation.
   -

   We had an issue with smart ligatures. For example, the definition of
   punycode uses an x followed by – –.  Many systems convert the two dashes to
   an em-dash. Jos has wrapped that notation in code markers in markdown.
   Corey requested that whatever is in markdown on Github should be in the PDF
   and vice versa. Ryan noted that the Github markdown remains the canonical
   version of the guideline documents.
   -

   For Ballot SC47 we had to perform a date fix. We should provide guidance
   on what to do when a working group needs to reopen a branch and fix
   it--what is the best way to do it. In this case, we created a new “SC 47
   date-fix” branch, and then we changed the pointers to that branch. We also
   added tags to help navigate to the relevant SC47 changes.

Website: We received several suggestions on how to improve the ballot
tables.

   -

   One suggestion was to add ballots that had been withdrawn or abandoned.
   One approach would be to alert the reader with a notice that any missing
   ballots are due to them having been withdrawn or abandoned. The other
   approach is to create a new post for each missing ballot (because the table
   is based on Wordpress posts). Wayne agreed that this would be a good idea.
   We could come up with boilerplate language to use in each of the posts.
   -

   Some code signing ballots are missing from the table, and Ben will work
   with Bruce to create posts for those ballots.
   -

   Another suggestion was to add guideline versions to the ballots table so
   that we would have another way to correlate ballots with changes to the
   guidelines. The guidelines pages already indicate which ballots made the
   changes to the guidelines. This effort would involve adding a new field for
   posts and then populating that field in each of the ballots with the
   relevant guideline version number.
   -

   We will work on creating multiple tables and webpages for ballots and
   minutes. The Forum and Server Certificate Working Group minutes are already
   tagged, and tables can be created for those relatively easily. Also,
   separate pages will be created for each ballot table for each of the
   working groups.

DMARC:

Dean, Jim, and Jos have worked on DMARC. (DMARC will prevent people from
sending spam from a spoofed CA/B Forum email address.)  Now we only need to
add text records to enable reporting, and then we will move to a quarantine
status. After moving to quarantine for DMARC, we will move records to Route
53 and cut over. We can go back to Go Daddy if necessary.

Membership Spreadsheet:

Jos has worked on new membership spreadsheets using the CA/B Forum Gmail
account. Dean and Wayne will take over work on the spreadsheets and adjust
them to their needs. The spreadsheets are very similar to a database
structure. There are tables for organizations, people, and working groups.
The tables correlate people to their organizations and organizations to
their working groups.

We need to update the information on the spreadsheet. We will likely
contact each member organization and ask them to provide updated
information for their representatives--likely using the membership
modification form.

The goals of these efforts are to simplify processes, including updating
subscriptions to the mailers, and to have fresh data that we can rely on.
Jos mentioned that this is not an end state, but an interim step toward
better automation.

Meeting adjourned
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/infrastructure/attachments/20210825/707807d8/attachment.html>