<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>Let me play devil’s advocate to Shaun’s advocate. :)</div>
<div><br>
</div>
<div>While the contribution of a diagram becomes easier by allowing any contributor to use their own tool so as long as the contributor follows explicit guidelines, the act of reviewing/modifying a diagram to ensure it meets our standards becomes more difficult
when we do not dictate or suggest a toolset. As Matt points out, we need to consider our review options.</div>
<div><br>
</div>
<div>If we want a reviewer to be able to modify a diagram with ease, we must consider what toolsets are compatible with one another. </div>
<div><br>
</div>
<div>Alternatively, if we chose not to consider toolsets, we should be explicit about what type of assets(shapes, stencils, or project symbols) a contributor can use. That way, a reviewer can reproduce the assets of a contributor’s diagram in the reviewer's
own editor. However, it may take the reviewer more time and effort to modify the diagram.</div>
<div><br>
</div>
<div>-Nate</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Matt Kassawara <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Friday, May 13, 2016 at 1:08 PM<br>
<span style="font-weight:bold">To: </span>Shaun O'Meara <<a href="mailto:someara@mirantis.com">someara@mirantis.com</a>><br>
<span style="font-weight:bold">Cc: </span>Rackspace Hosting <<a href="mailto:Nate.Archer@rackspace.com">Nate.Archer@rackspace.com</a>>, Christian Berendt <<a href="mailto:christian@berendt.io">christian@berendt.io</a>>, Olga Gusarenko <<a href="mailto:ogusarenko@mirantis.com">ogusarenko@mirantis.com</a>>,
Shaun OMeara <<a href="mailto:shaun@omeara.co.za">shaun@omeara.co.za</a>>, "<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>" <<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a>>,
Darren Chan <<a href="mailto:darren.chan@RACKSPACE.COM">darren.chan@RACKSPACE.COM</a>><br>
<span style="font-weight:bold">Subject: </span>Re: Diagram recommendations for Openstack Contributor Guides<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">YES! As long as your tool of choice creates diagrams that meet the guidelines, which shouldn't lean toward any particular tool, use it. Diagrams often assist knowledge transfer in ways not possible with just words, so let's make contributions
easier rather than harder. Also, we should consider review options for diagrams similar to my suggestions for general content. If someone contributes a technically accurate diagram, almost anyone can modify it to meet guidelines.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, May 13, 2016 at 11:40 AM, Shaun O'Meara <span dir="ltr">
<<a href="mailto:someara@mirantis.com" target="_blank">someara@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
First off let me say that I am not an advocate of any one tool over another, none of the tools is perfect, and many are pretty horrible.
<div><br>
</div>
<div>Ideally I would like to be in a situation that as a contributor I have a set of explicit guidelines and recommended tools that I can choose from to contribute in the most effective and efficient way for me. </div>
<div><br>
</div>
<div>To play devils advocate here, I don't believe that we can or should dictate tooling, but we can provide explicit style guidelines.</div>
<div><br>
</div>
<div>Thanks</div>
<div>Shaun</div>
<div class="HOEnZb">
<div class="h5">
<div><br>
On Friday, May 13, 2016, Matt Kassawara <<a href="mailto:mkassawara@gmail.com" target="_blank">mkassawara@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">I think <a href="http://draw.io" target="_blank">draw.io</a> is one of the stronger plays, but has some of the same limitations as other online tools.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, May 13, 2016 at 8:28 AM, Nate Archer <span dir="ltr">
<<a>Nate.Archer@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>What is everyone’s thoughts on <a href="https://www.draw.io/" target="_blank">
Draw.io</a>? I’ve used in the past and while the toolset is somewhat limited, it has the ability to save and open editable SVG’s, as well as the ability to export the diagram as a PNG file.</div>
<div><br>
</div>
<div>Downside is when you open an SVG file in Draw.io that has been created in another tool, certain elements of the illustration might not show up. This problem is mitigated if you use Draw.io exclusively, as with any software.</div>
<div><br>
</div>
<div>As Darren and Matt have pointed out, Inkscape is cumbersome to use, and has many of the same problems as Draw.io, without any of the strengths.</div>
<div><br>
</div>
<div>-Nate</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Matt Kassawara <<a>mkassawara@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Friday, May 13, 2016 at 7:36 AM<br>
<span style="font-weight:bold">To: </span>Christian Berendt <<a>christian@berendt.io</a>><br>
<span style="font-weight:bold">Cc: </span>Olga Gusarenko <<a>ogusarenko@mirantis.com</a>>, Shaun OMeara <<a>shaun@omeara.co.za</a>>, "<a>someara@mirantis.com</a>" <<a>someara@mirantis.com</a>>, "<a>openstack-docs@lists.openstack.org</a>" <<a>openstack-docs@lists.openstack.org</a>>,
Rackspace Hosting <<a>Nate.Archer@rackspace.com</a>>, Darren Chan <<a>darren.chan@RACKSPACE.COM</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [OpenStack-docs] Diagram recommendations for Openstack Contributor Guides<br>
</div>
<div>
<div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">If you contribute diagrams, you'll quickly figure out that Inkscape is difficult to use and produces rough content at best. If we want OpenStack to appear more professional and less like a science experiment to our increasingly less technical
(read: decision makers) audience, we have to use a tool that creates professional looking content. Some of the online tools are surprisingly decent, so I wouldn't rule them out. Unfortunately, regardless of what we use, we're never going to have standardized
SVGs that any online or installed tools can consistently parse.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, May 13, 2016 at 3:46 AM, Christian Berendt <span dir="ltr">
<<a>christian@berendt.io</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 13 May 2016 at 10:34:48, Shaun OMeara (<a>shaun@omeara.co.za</a>) wrote:<br>
> > Opensource<br>
<br>
With this requirement we are only able to use Inkscape, it is the only listed open source software.<br>
<br>
Omnigraffle, DrawSVG, and Lucidchart are not open sourced.<br>
<br>
I would prefer to not rely on hosted services like Lucidchart and DrawSVG. This way we are depending on the availability of a 3rd party service provider.<br>
<span><font color="#888888"><br>
Christian.<br>
<br>
--<br>
Christian Berendt<br>
</font></span>
<div>
<div><br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a>OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</span></div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
<br>
</div>
</div>
<span class="HOEnZb"><font color="#888888">-- <br>
<div dir="ltr">
<div>
<div dir="ltr"><b>Shaun O'Meara</b>
<div><b>Sr. Systems Architect</b></div>
<div><b>Mirantis, Inc</b></div>
<div><b><a href="tel:%2B27%20%280%2983%20634%208904" value="+27836348904" target="_blank">+27 (0)83 634 8904</a> (South Africa)</b></div>
<div><b><a href="tel:%2B1%20%28628%29%20444%209094" value="+16284449094" target="_blank">+1 (628) 444 9094</a> (USA)</b></div>
<div><b><a href="http://www.mirantis.com" target="_blank">www.mirantis.com</a></b></div>
</div>
</div>
</div>
<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</div>
</span>
</body>
</html>