<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 2020-07-22 6:59 μ.μ., Ryan Sleevi
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACvaWvY7MJLqw=25EZymaZXX7HsCXVkVp+E=r=CiWHvdtJwhJw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Yes, I'm aware you changed it.
<div><br>
</div>
<div>I originally had it like that when I updated, but then
reverted it (as you can see in the edit history), because it's
inconsistent with the other links on the page - e.g. the
GitHub redline. I was trying to prioritize consistency within
the instructions (e.g. look at Compare Changes)</div>
<div><br>
</div>
<div>I don't care one way or the other, but think we should at
least be consistent. If you prefer the <code> block
style, which forces a newline, would you please correct the
other instances?</div>
</div>
</blockquote>
<br>
I see what you mean. I didn't notice the other cases. In any case,
since I will probably be the one going over these instructions, I
think I will revert to what you had :)<br>
<br>
<br>
Thanks,<br>
Dimitris.<br>
<br>
<blockquote type="cite"
cite="mid:CACvaWvY7MJLqw=25EZymaZXX7HsCXVkVp+E=r=CiWHvdtJwhJw@mail.gmail.com"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jul 22, 2020 at 11:40
AM Dimitris Zacharopoulos (HARICA) <<a
href="mailto:dzacharo@harica.gr" moz-do-not-send="true">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> <br>
<br>
<div>On 2020-07-22 6:02 μ.μ., Ryan Sleevi wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Eh, that's no more broken than our existing
sections on that page. I intentionally mirrored that, as
opposed to forcing it not to be a hyperlink, so that the
styles would be consistent.
<div><br>
</div>
<div>This definitely fits with Jos' remarks about our
wiki stack ;)</div>
</div>
</blockquote>
<br>
It's not broken because I fixed it :-)<br>
<br>
This is how it's displayed now.<br>
<br>
<img src="cid:part2.6A14A8BC.D9FCE7FD@harica.gr" alt=""
class=""><br>
<br>
This was the previous version<br>
<br>
<img src="cid:part3.083EDF30.0FD6FC6C@harica.gr" alt=""
class=""><br>
<br>
Dimitris.<br>
<blockquote type="cite"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jul 21, 2020
at 1:06 PM Dimitris Zacharopoulos (HARICA) <<a
href="mailto:dzacharo@harica.gr" target="_blank"
moz-do-not-send="true">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> <br>
<br>
<div>On 2020-07-21 7:27 μ.μ., Ryan Sleevi wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Made edits and added screenshots.
It looks like several steps had been omitted
from my previous mail, so hopefully that helps.</div>
</blockquote>
<br>
It sure does. Some text is broken under step 8,
probably because they are partially converted to
hyperlinks.<br>
<br>
<br>
Thanks,<br>
Dimitris.<br>
<br>
<br>
<br>
<blockquote type="cite"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jul
21, 2020 at 12:42 AM Dimitris Zacharopoulos
(HARICA) <<a
href="mailto:dzacharo@harica.gr"
target="_blank" moz-do-not-send="true">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> <br>
I would appreciate a review of the last two
sections added in <a
href="https://wiki.cabforum.org/github_redline_guide"
target="_blank" moz-do-not-send="true">https://wiki.cabforum.org/github_redline_guide</a>
before removing the "under construction".<br>
<br>
<br>
Thank you,<br>
Dimitris.<br>
<br>
<br>
<div>On 2020-07-20 9:32 μ.μ., Dimitris
Zacharopoulos (HARICA) wrote:<br>
</div>
<blockquote type="cite"> <br>
I was out of office today so apologies for
replying late. The result of the process
is very good and I plan on adding specific
instructions on <a
href="https://wiki.cabforum.org/github_redline_guide"
target="_blank" moz-do-not-send="true">https://wiki.cabforum.org/github_redline_guide</a>.
Until we reach the next milestone of
automatically creating a red-line, we can
create a final version in the Pull
Request, and compare against the existing
main branch.<br>
<br>
I have attached the resulting docx redline
BRs between 1.7.0 and ballots SC30+31
using the two docx versions I got from the
links provided by Jos and Ryan.<br>
<br>
Does this look good to everyone? I will do
a more detailed review myself tomorrow
morning (Greek time) before posting to the
public lists.<br>
<br>
Once again, a big thanks to Jos and Ryan
for working on this automation.<br>
<br>
<br>
Best regards,<br>
Dimitris.<br>
<br>
<br>
<div>On 2020-07-20 8:40 μ.μ., Ryan Sleevi
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Dimitris: Did that work
for you? I didn't hear back so wasn't
sure if you were sorted now with <a
href="https://github.com/cabforum/documents/pull/203"
target="_blank"
moz-do-not-send="true">https://github.com/cabforum/documents/pull/203</a></div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On
Fri, Jul 17, 2020 at 3:09 PM
Dimitris Zacharopoulos (HARICA) <<a
href="mailto:dzacharo@harica.gr"
target="_blank"
moz-do-not-send="true">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> Thank you both for the quick
response. I recall the
instructions posted by Ryan;
unfortunately I am not so familiar
with these processes. I will read
them more carefully during the
weekend. In the meantime, if you
succeed in getting a combined
SC30/SC31 docx against the BRs
1.7.0 sent by Jos earlier today,
that would save me a lot of time.<br>
<br>
<br>
Dimitris.<br>
<br>
<br>
<div>On 17/7/2020 6:59 μ.μ., Jos
Purvis (jopurvis) wrote:<br>
</div>
<blockquote type="cite">
<div>
<p class="MsoNormal"><span
style="font-family:Georgia,serif">Sounds
good, Ryan! Dimitris, the
link I provided is the
official DOCX from the
official master branch:
that’s the 1.7.0 version
of the current
master-branch BRs. So
that’s the current clean
master version, against
which you can compare
something from the ballot
outputs to create a binary
redline. The trick is
getting you something from
the SC30/SC31 branches to
create that redline
against. </span><span>😊</span><span
style="font-family:Georgia,serif"> Ryan, I’ll have a look at it today
when I have a chance as
well and see if I can sort
it. </span></p>
<p class="MsoNormal"><span
style="font-family:Georgia,serif"> </span></p>
<div>
<p class="MsoNormal"><span
style="font-size:9pt;font-family:Consolas;color:black"> </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"
moz-do-not-send="true"><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></p>
</div>
<p class="MsoNormal"><span
style="font-family:Georgia,serif"> </span></p>
<p class="MsoNormal"><span
style="font-family:Georgia,serif"> </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"
moz-do-not-send="true"><sleevi@google.com></a><br>
<b>Date: </b>Friday,
July 17, 2020 at 11:50
AM<br>
<b>To: </b>Dimitris
Zacharopoulos <a
href="mailto:dzacharo@harica.gr"
target="_blank"
moz-do-not-send="true"><dzacharo@harica.gr></a><br>
<b>Cc: </b>"Jos Purvis
(jopurvis)" <a
href="mailto:jopurvis@cisco.com"
target="_blank"
moz-do-not-send="true"><jopurvis@cisco.com></a>,
<a
href="mailto:infrastructure@cabforum.org"
target="_blank"
moz-do-not-send="true">"infrastructure@cabforum.org"</a>
<a
href="mailto:infrastructure@cabforum.org"
target="_blank"
moz-do-not-send="true"><infrastructure@cabforum.org></a><br>
<b>Subject: </b>Re:
[Infrastructure]
Preparation of review
period for SC30 and SC31</span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal"><a
href="https://archive.cabforum.org/pipermail/infrastructure/2020-May/000223.html"
target="_blank"
moz-do-not-send="true">https://archive.cabforum.org/pipermail/infrastructure/2020-May/000223.html</a> for
the instructions</p>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On
Fri, Jul 17, 2020 at
11:48 AM Ryan Sleevi
<<a
href="mailto:sleevi@google.com"
target="_blank"
moz-do-not-send="true">sleevi@google.com</a>>
wrote:</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">
<div>
<p class="MsoNormal">Let
me dig out the
previous e-mail from
our discussions about
this.</p>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">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.</p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">On
Fri, Jul 17, 2020 at
11:43 AM Dimitris
Zacharopoulos <<a
href="mailto:dzacharo@harica.gr" target="_blank" moz-do-not-send="true">dzacharo@harica.gr</a>>
wrote:</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">
<div>
<p class="MsoNormal"
style="margin-bottom:12pt">That's fine.<br>
<br>
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>
Would this work?<br>
<br>
</p>
<div>
<p>DZ. </p>
</div>
<div>
<p>Jul 17, 2020
18:32:10 Jos
Purvis
(jopurvis) <<a
href="mailto:jopurvis@cisco.com" target="_blank" moz-do-not-send="true">jopurvis@cisco.com</a>>:</p>
<blockquote
style="margin-top:5pt;margin-bottom:5pt">
<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. </span></p>
<p
class="MsoNormal"><span
style="font-family:Georgia,serif"> </span></p>
<div>
<p
class="MsoNormal"><span
style="font-size:9pt;font-family:Consolas;color:black"> </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" moz-do-not-send="true"><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></p>
</div>
<p
class="MsoNormal"><span
style="font-family:Georgia,serif"> </span></p>
<p
class="MsoNormal"><span
style="font-family:Georgia,serif"> </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" moz-do-not-send="true">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" moz-do-not-send="true">jopurvis@cisco.com</a>><br>
<b>Cc: </b>"Dimitris
Zacharopoulos
(HARICA)" <<a
href="mailto:dzacharo@harica.gr" target="_blank" moz-do-not-send="true">dzacharo@harica.gr</a>>,
"<a
href="mailto:infrastructure@cabforum.org"
target="_blank" moz-do-not-send="true">infrastructure@cabforum.org</a>"
<<a
href="mailto:infrastructure@cabforum.org"
target="_blank" moz-do-not-send="true">infrastructure@cabforum.org</a>><br>
<b>Subject: </b>Re:
[Infrastructure] Preparation of review period for SC30 and SC31 </span></p>
</div>
<div>
<p
class="MsoNormal">
</p>
</div>
<div>
<div>
<p
class="MsoNormal">
</p>
</div>
<p
class="MsoNormal">
</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" moz-do-not-send="true">jopurvis@cisco.com</a>> wrote:</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:5pt
0in 5pt 4.8pt">
<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" moz-do-not-send="true">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?)</p>
</blockquote>
<div>
<p
class="MsoNormal">
</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. </p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Infrastructure mailing list
<a href="mailto:Infrastructure@cabforum.org" target="_blank" moz-do-not-send="true">Infrastructure@cabforum.org</a>
<a href="https://lists.cabforum.org/mailman/listinfo/infrastructure" target="_blank" moz-do-not-send="true">https://lists.cabforum.org/mailman/listinfo/infrastructure</a></pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Infrastructure mailing list<br>
<a href="mailto:Infrastructure@cabforum.org"
target="_blank" moz-do-not-send="true">Infrastructure@cabforum.org</a><br>
<a
href="https://lists.cabforum.org/mailman/listinfo/infrastructure"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://lists.cabforum.org/mailman/listinfo/infrastructure</a><br>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>