<div dir="ltr"><div>Here are the minutes from today's call.</div><div><br></div>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">12/16/2020 Minutes<span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Attendees:<span> </span>Corey
Bonnell, Jos Purvis, Ryan Sleevi, Ben Wilson, Wayne Thayer, Dean Coclin, Dimitris
Zacharopoulos, <span></span></p>
<p class="MsoNormal" style="margin:0in 0in 8pt;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">Antitrust Statement read by Jos<span></span></p>
<p class="gmail-MsoListParagraphCxSpFirst" style="margin:0in 0in 0in 0.0866in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><span><span>1.<span style="font:7pt "Times New Roman"">
</span></span></span>Meeting Series – Jos will send out a new series of calendar invites for
2021, starting with our next meeting on January 13, 2021<span></span></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:0in 0in 0in 0.0866in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><span><span>2.<span style="font:7pt "Times New Roman"">
</span></span></span>GitHub – Support for redlines has landed in
experimental mode. Ryan will work on Pandoc cleanup process. Action needed to
assign Forum and Server Cert code owners. Tooling is moving forward on
schedule. <span></span></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:0in 0in 0in 0.0866in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><span><span>3.<span style="font:7pt "Times New Roman"">
</span></span></span>Mailer migration issues?<span> </span>It seems like everything is working. Also, Jos was able to invite this list to the
meeting from the WebEx interface. (Meeting invites should be sent to management
lists and not be sent to a public lists).<span></span></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:0in 0in 0in 0.0866in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><span><span>4.<span style="font:7pt "Times New Roman"">
</span></span></span>Membership management – Wayne has developed a
Google form.<span> </span>He believes it is ready to
publish, but he needs to check on a few things first. <span></span>Q: How do we get this out and into
use? Where can a link to it be placed? Dean: What happens when it is completed? Wayne: It
goes to a database and could be emailed. Dean: there is a lot of backend work
for updating other data. Ryan: Some of these issues are discussed in the minutes from the meeting two meetings ago. We’ll
need to develop tooling to propagate the data to various locations, e.g., the
mailer, etc.<span> </span>Jos: For the mailer, the
authentication mechanisms aren’t the best. One possibility is to run scripts on
the common server. There are plug-ins for LDAP or Active Directory, too. Ryan:
Let’s see what we can do to keep it simple with the tooling we have using
scripts. Jos: We need to anticipate personnel turnover so tooling should be
tracked on GitHub. Ryan: Yes, but not the secrets. We can still manage the data
with clicks. Jos: Often the requests come in waves as new members join, and
changes also happen when one person leaves and is replaced by another person. Wayne:
The time-consuming part is managing the mailing lists – adding and removing
people from lists. Ryan: It would be good to have “sync” buttons. Wayne: Scripting
will help. Jos: And for some membership changes we currently have 4 or 5 people that have to interact with
the various resources.<span> </span>Dean: And remember
that we need to send out calendar invites, too.<span>
</span>Jos: I don’t know if there is an API for this. Ryan: This can be automated
with meeting invites. Wayne and Jos: New members can be directed to the wiki
for self-serve calendar invites. Jos: Stephen has a boilerplate template directing
new members of the SMIME WG on what they need to do.<span> </span><span></span></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:0in 0in 0in 0.0866in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><span><span><span style="font:7pt "Times New Roman""></span></span></span>NEXT ACTIONS: <span> </span><span></span></p>
<p class="gmail-MsoListParagraphCxSpMiddle" style="margin:0in 0in 0in 0.0866in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">1- Wayne will look at Google forms database
and email triggers (you’ll have to subscribe to follow changes to the data); <span></span></p>
<p class="gmail-MsoListParagraphCxSpLast" style="margin:0in 0in 8pt 0.0866in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif">2- Next Meeting - Organize to-do items (not
just in the minutes) structured for project management (for prioritization, who
is working on it, etc.) in a Google Doc with a link to it recorded
on the Wiki page (reference the management procedural guidance that Dimitris developed)
- <a href="https://wiki.cabforum.org/infra/member-rep-modification-request" style="color:rgb(5,99,193);text-decoration:underline">https://wiki.cabforum.org/infra/member-rep-modification-request</a>
and <a href="https://wiki.cabforum.org/infra/start#high-level_goals" style="color:rgb(5,99,193);text-decoration:underline">https://wiki.cabforum.org/infra/start#high-level_goals</a>.<span> </span>Meanwhile, we’ll use Etherpad to
collect our thoughts. <span></span></p><p class="gmail-MsoListParagraphCxSpLast" style="margin:0in 0in 8pt 0.5in;line-height:107%;font-size:11pt;font-family:"Calibri",sans-serif"><br></p>
</div>