<div dir="ltr"><a href="https://archive.cabforum.org/pipermail/infrastructure/2020-May/000223.html">https://archive.cabforum.org/pipermail/infrastructure/2020-May/000223.html</a> for the instructions<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 17, 2020 at 11:48 AM Ryan Sleevi <<a href="mailto:sleevi@google.com">sleevi@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Let me dig out the previous e-mail from our discussions about this.<div><br></div><div>The answer is "No, it won't work", and I was offering to get to it once I'm nearer to a computer that can do that.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jul 17, 2020 at 11:43 AM Dimitris Zacharopoulos <<a href="mailto:dzacharo@harica.gr" target="_blank">dzacharo@harica.gr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div> <span>That's fine.<br><br></span> <span>Do we have the artifacts from the current official master branch? I can create a PR on our official repo, that contains the commits of both ballots if that automatically creates new artifacts. Then, I can use MS word to compare the display the changes, thus creating a redline.<br><br></span> <span>Would this work?<br> <br><br></span>
<div>
<p dir="ltr">DZ. </p>
</div>
<div>
<p>Jul 17, 2020 18:32:10 Jos Purvis (jopurvis) <<a href="mailto:jopurvis@cisco.com" target="_blank">jopurvis@cisco.com</a>>:</p>
<blockquote lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-family:Georgia,serif">Hmmm. So I know we’ve never produced uploaded artifacts from PRs <i>from other people’s forks</i>, which makes sense—I thought that was the discussion. We’ve been producing artifacts from PRs of branches actually on the cabforum repo, though, because a quick peruse of the S3 bucket contents shows a folder for each cabforum/documents branch up through pandoc-travis-changes.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:Georgia,serif">
<u></u>
<u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9pt;font-family:Consolas;color:black">
<u></u>
<u></u></span></p>
<p class="MsoNormal"><span style="font-size:9pt;font-family:Consolas;color:black">-- <br>Jos Purvis (</span><a href="mailto:jopurvis@cisco.com" target="_blank"><span style="font-size:9pt;font-family:Consolas;color:rgb(149,79,114)">jopurvis@cisco.com</span></a><span style="font-size:9pt;font-family:Consolas;color:black">)<br>.:|:.:|:. cisco systems | Cryptographic Services<br>PGP: 0xFD802FEE07D19105 | Controls and Trust Verification</span><u></u><u></u></p>
</div>
<p class="MsoNormal"><span style="font-family:Georgia,serif">
<u></u>
<u></u></span></p>
<p class="MsoNormal"><span style="font-family:Georgia,serif">
<u></u>
<u></u></span></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12pt;color:black">From: </span></b><span style="font-size:12pt;color:black">Ryan Sleevi <<a href="mailto:sleevi@google.com" target="_blank">sleevi@google.com</a>><br><b>Date: </b>Friday, July 17, 2020 at 11:07 AM<br><b>To: </b>"Jos Purvis (jopurvis)" <<a href="mailto:jopurvis@cisco.com" target="_blank">jopurvis@cisco.com</a>><br><b>Cc: </b>"Dimitris Zacharopoulos (HARICA)" <<a href="mailto:dzacharo@harica.gr" target="_blank">dzacharo@harica.gr</a>>, "<a href="mailto:infrastructure@cabforum.org" target="_blank">infrastructure@cabforum.org</a>" <<a href="mailto:infrastructure@cabforum.org" target="_blank">infrastructure@cabforum.org</a>><br><b>Subject: </b>Re: [Infrastructure] Preparation of review period for SC30 and SC31
<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"> <u></u>
<u></u></p>
</div>
<div>
<div>
<p class="MsoNormal"> <u></u>
<u></u></p>
</div>
<p class="MsoNormal"> <u></u>
<u></u></p>
<div>
<div>
<p class="MsoNormal">On Fri, Jul 17, 2020 at 10:50 AM Jos Purvis (jopurvis) <<a href="mailto:jopurvis@cisco.com" target="_blank">jopurvis@cisco.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Hi Dimitris,<br><br>For the current version in Word format, you can fetch it from this link:<br> <a href="https://cabforum-travis-artifacts.s3-us-west-2.amazonaws.com/builds/master/BR.docx" target="_blank">https://cabforum-travis-artifacts.s3-us-west-2.amazonaws.com/builds/master/BR.docx</a><br><br>That's the same link as the PDF from the front page of the CABF repository, but with the extension changed to docx (we need to update the README on the repository to reflect the new formats and whatnot!).<br><br>For the SC30 and SC31 ballots, the Travis build completed successfully, but it doesn't look like it uploaded the resulting artifacts to S3. Ryan, is that something we need to fix? (Looks like that used to be the default and isn't anymore?)<u></u><u></u></p>
</blockquote>
<div>
<p class="MsoNormal"> <u></u>
<u></u></p>
</div>
<div>
<p class="MsoNormal">I think there's some confusion. It was never the default to upload artifacts for PRs. This is the whole discussion about the need to create a dedicated branch within the main CABF repository, then create a PR using that, to have the artifact produced. I'll see about doing that later today. <u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote></div>
</blockquote></div>