On Wednesday, July 8, 2015, Shawn Wells &lt;<a href="mailto:shawn@redhat.com">shawn@redhat.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    <br>
    <br>
    <div>On 7/8/15 7:41 AM, Martin Preisler
      wrote:<br>
    </div>
    <blockquote type="cite">
      <pre>I wrote a small blog post about a new feature in SSG 0.1.24 -
building one HTML guide for each profile we ship and providing
a convenient switcher.

<a href="http://martin.preisler.me/2015/07/scap-security-guide-now-has-an-html-guide-for-each-profile/" target="_blank">http://martin.preisler.me/2015/07/scap-security-guide-now-has-an-html-guide-for-each-profile/</a>

It includes a screenshot and a live demo <span title=":-)"><span>:-)</span></span> Feedback appreciated.
</pre>
    </blockquote>
    <br>
    From the posting:<br>
    <br>
    <blockquote type="cite">
      
      <p style="border:0px;font-family:Lato,sans-serif;font-size:16px;font-style:normal;font-weight:normal;margin:0px 0px 24px;outline:0px;padding:0px;vertical-align:baseline;color:rgb(43,43,43);font-variant:normal;letter-spacing:normal;line-height:24px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">We
        plan to install these guides in downstream packages (e.g.<span> </span><a href="https://fedoraproject.org/" style="border:0px;font-family:inherit;font-size:16px;font-style:inherit;font-weight:inherit;margin:0px;outline:0px;padding:0px;vertical-align:baseline;color:rgb(36,137,13);text-decoration:underline" target="_blank">Fedora</a>). Instead of bundling
        them with the main package we will create a subpackage -doc with
        the guides and other optional documentation material.</p>
    </blockquote>
    <br>
    That means we have:<br>
    - openscap-scanner<br>
    - scap-security-guide<br>
    - scap-security-guide-docs<br>
    <br>
    Having multiple naming schemes is a bit confusing, especially for
    new users. Is it time to repackage SSG as openscap-content?<br>
    <br>
    e.g<br>
    openscap-scanner<br>
    openscap-workbench<br>
    openscap-content<br>
    openscap-content-docs<br>
  </div>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br></blockquote></blockquote><div><br></div><div>+1. I actually feel like this falls more in line with the openscap project and tightly integrates SSG into openscap.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">--<br>
SCAP Security Guide mailing list<br>
<a href="javascript:;" onclick="_e(event, &#39;cvml&#39;, &#39;scap-security-guide@lists.fedorahosted.org&#39;)">scap-security-guide@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide</a><br>
<a href="https://github.com/OpenSCAP/scap-security-guide/" target="_blank">https://github.com/OpenSCAP/scap-security-guide/</a><br></blockquote>