<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=en-SE link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal style='margin-bottom:8.0pt;line-height:106%'><b><span lang=en-SE>Infrastructure Committee Meeting of </span></b><b><span lang=EN-US>2022-03-23</span></b><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><b><span lang=en-SE>Attendees: <o:p></o:p></span></b></p><p class=MsoNormal><span lang=en-SE>Ben Wilson<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Corey Bonnell<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Daryn Wright<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Inigo Barreira<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Jos Purvis<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Joseph Ramm<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Kiran Tummala<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Martijn Katerbarg<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Tyler Myers<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Wayne Thayer<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:8.0pt;line-height:106%'><b><span lang=en-SE>Antitrust Statemen</span></b><b><span lang=EN-US>t:</span></b><span lang=EN-US> </span><span lang=EN-US>R</span><span lang=en-SE>ead by Jos<o:p></o:p></span></p><p class=MsoNormal><b><span lang=en-SE>Updates on the new membersh</span></b><b><span lang=EN-US>ip</span><span lang=en-SE> tool:<o:p></o:p></span></b></p><p class=MsoNormal><span lang=en-SE>Source code is checked into a CA/B Forum private GitHub repository. If anybody needs access, please let Jos know. Jos is currently working on hosting part. This is pending on DNS changes at the moment. <o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>The DNS cutover to Route 53 scheduled for next Monday, after which this can be completed.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US>The </span><span lang=en-SE>IPR agreement URL can now be added to </span><span lang=EN-US>a member organization record</span><span lang=en-SE>. In the future we may look into allowing the tool to host the files, but for now we will keep them in the wiki.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-SE>Discussion on which Forum Groups to add and how to differentiate. There was agreement to add a column specifying the type of Forum Groups, such as WG or subco</span><span lang=EN-US>mm</span><span lang=en-SE>ittee</span><span lang=EN-US>s</span><span lang=en-SE>. On</span><span lang=EN-US>c</span><span lang=en-SE>e we're online we can look at integrating these groups with the mailing lists.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-SE>The V2 Registry import mechanism </span><span lang=EN-US>has been </span><span lang=en-SE>completed, there are however a couple of issues with the current list. Wayne will set these straight in the existing list.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Decision was made to add a "Interested Party - Private People" Member organization in which any private people that are registered as an interested party will be added.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-SE>Since the tool may give access to some private details, such as full membership information, names and email addresses there was agreement to not let members that are registered only as interested parties login to the new system.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>They at current also should not have access to the V2 Registry.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><span lang=en-SE>Corey suggested adding a function to copy the attendees list of a meeting so it can be pasted directly into meeting minutes and will have the same format every time. A Git</span><span lang=EN-US>Hu</span><span lang=en-SE>b issue to track this will be opened.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Corey also suggested to utilize the WebEx API to automate meeting details and attendee registration even more. We will need to investigate how this works, but since the current Attendee report from WebEx has some encoding difficulties, this would be preferred in the long run.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=en-SE>DNS change</span></b><b><span lang=EN-US>over</span><span lang=en-SE>:<o:p></o:p></span></b></p><p class=MsoNormal><span lang=en-SE>As mentioned, the DNS cutover to Route 53 is scheduled for next Monday.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=en-SE>Website update: <o:p></o:p></span></b></p><p class=MsoNormal><span lang=en-SE>Ben: Working on moving menus around, seems like it should work. Ben has sent an email with the details to limit the number of items in the top menu.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>There's agreement on not making the top menu too complex and crowded.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Ben will go ahead with re-organizing the main website's menu<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=en-SE>Other business</span></b><b><span lang=EN-US>:<o:p></o:p></span></b></p><p class=MsoNormal><span lang=en-SE>Corey</span><span lang=EN-US> mentioned that we</span><span lang=en-SE> as </span><span lang=EN-US>a </span><span lang=en-SE>group should come up with manuals and workflows for GitHub use. This might be useful</span><span lang=EN-US> and there have been several requests made for this since not everybody has experience with GitHub, raising ballots, etc.</span><span lang=en-SE>.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Jos</span><span lang=EN-US> agrees, and mentions that there is also a s</span><span lang=en-SE>econd request: It would be helpful if there was some kind of style guide on what to do and not do with MarkDown</span><span lang=EN-US>.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Ben</span><span lang=EN-US> suggest putting these documents in the </span><span lang=en-SE> We should probably </span><span lang=EN-US>add this information to the wiki start page under Instructions.<o:p></o:p></span></p><p class=MsoNormal><span lang=en-SE>Corey Ben and Martijn are willing to work on that</span><span lang=EN-US>.<o:p></o:p></span></p></div></body></html>