<div dir="ltr">Shawn,<div><br></div><div>I like your explanation and naming of the components. OpenSCAP as the umbrella project name makes sense.</div><div><br></div><div>Greg</div><div><br></div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, May 1, 2014 at 2:31 PM, Shawn Wells <span dir="ltr">&lt;<a href="mailto:shawn@redhat.com" target="_blank">shawn@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><div><div class="h5">
    <br>
    <div>On 4/30/14, 10:39 AM, Martin Preisler
      wrote:<br>
    </div>
    <blockquote type="cite">
      <pre>----- Original Message -----
</pre>
      <blockquote type="cite" style="color:#000000">
        <pre><span>&gt; </span>From: &quot;Jan Lieskovsky&quot; <a href="mailto:jlieskov@redhat.com" target="_blank">&lt;jlieskov@redhat.com&gt;</a>
<span>&gt; </span>To: &quot;SCAP Security Guide&quot; <a href="mailto:scap-security-guide@lists.fedorahosted.org" target="_blank">&lt;scap-security-guide@lists.fedorahosted.org&gt;</a>
<span>&gt; </span>Cc: &quot;Peter Vrabec&quot; <a href="mailto:pvrabec@redhat.com" target="_blank">&lt;pvrabec@redhat.com&gt;</a>, &quot;Simon Lukasik&quot; <a href="mailto:slukasik@redhat.com" target="_blank">&lt;slukasik@redhat.com&gt;</a>, &quot;Martin Preisler&quot;
<span>&gt; </span><a href="mailto:mpreisle@redhat.com" target="_blank">&lt;mpreisle@redhat.com&gt;</a>
<span>&gt; </span>Sent: Wednesday, April 30, 2014 4:08:04 PM
<span>&gt; </span>Subject: [RFC] SCAP security guide to become member of larger community - OpenSCAP ecosystem by changing it&#39;s name to
<span>&gt; </span>OpenSCAP security guide?
<span>&gt; </span>
<span>&gt; </span>Hello folks,
<span>&gt; </span>
<span>&gt; </span>  in effort to increase discoverability of security compliance solutions,
<span>&gt; </span>Simon created github&#39;s entry for OpenSCAP ecosystem yesterday:
<span>&gt; </span>  [1] <a href="https://github.com/OpenSCAP" target="_blank">https://github.com/OpenSCAP</a>
<span>&gt; </span>
<span>&gt; </span>collecting all the relevant tools / products, necessary to perform
<span>&gt; </span>security compliance checks in automated way. The intention of this
<span>&gt; </span>ecosystem is to have all the parts available at one place, so people
<span>&gt; </span>interested in automated SCAP scans wouldn&#39;t need to search for:
<span>&gt; </span>* the scanner,
<span>&gt; </span>* tailoring / remediation tool,
<span>&gt; </span>* the content itself
<span>&gt; </span>at three different locations.
<span>&gt; </span>
<span>&gt; </span>For now those repositories are just mirrors of their parental ones
<span>&gt; </span>(copies which will get updated on regular basis - Simon can clarify
<span>&gt; </span>how often).
<span>&gt; </span>
<span>&gt; </span>Together with this change, we have received proposal of icon / logo
<span>&gt; </span>for the SCAP security guide project. Though yet before you download
<span>&gt; </span>&amp; inspect the attached tarballs, I need to mention, there are two
<span>&gt; </span>versions of the icons attached:
<span>&gt; </span>* one is for current &quot;SCAP Security Guide&quot; project name
<span>&gt; </span>(SCAP_logos_SCAP_security_guide.tar.gz),
<span>&gt; </span>* the second to see the proposal if the name of the project would change
<span>&gt; </span>  to &quot;OpenSCAP Security Guide&quot; (OpenSCAP_logos_SCAP_security_guide.tar.gz)
<span>&gt; </span>
<span>&gt; </span>Since there&#39;s effort to create OpenSCAP ecosystem, of which SCAP security
<span>&gt; </span>guide
<span>&gt; </span>project is its indisputable part, besides cloning the repository, the other
<span>&gt; </span>natural subsequent step, coming to mind is to have the project renamed
<span>&gt; </span>from SCAP security guide to OpenSCAP security guide.
<span>&gt; </span>
<span>&gt; </span>In our opinion, look at OpenSCAP ecosystem [1] might induce the potential
<span>&gt; </span>user&#39;s impression, the whole project being organized properly (all parts
<span>&gt; </span>being available at one place and all parts named by same prefix, differing
<span>&gt; </span>just by component&#39;s name).
<span>&gt; </span>
<span>&gt; </span>The pros / cons of the name change as I was able to collect are as follows:
<span>&gt; </span>
<span>&gt; </span>Pros:
<span>&gt; </span>* whole (security compliance) solution can be viewed / looked at like
<span>&gt; </span>  having organized &amp; unified form (distinguished just by component&#39;s name /
<span>&gt; </span>  colour of the icon),
<span>&gt; </span>
<span>&gt; </span>* all the necessary bits are reachable at one place (=&gt; lowering the
<span>&gt; </span>potential
<span>&gt; </span>  user&#39;s &quot;start barrier&quot; in effort to get familiar with the concept)
<span>&gt; </span>
<span>&gt; </span>Cons:
<span>&gt; </span>* user&#39;s accustomed to old name might get confused. It might need to take
<span>&gt; </span>  some time till they get accustomed to start using new name,
<span>&gt; </span>
<span>&gt; </span>* the content being named &quot;OpenSCAP Security Guide&quot; (IOW with OpenSCAP brand)
<span>&gt; </span>  might induce the impression, it&#39;s not usable in other tools / scanners
<span>&gt; </span>  than just by OpenSCAP one. This could be overcome by us providing tutorial
<span>&gt; </span>  articles / images pinpointing the use of SCAP Security Guide content with
<span>&gt; </span>  tools (scanners) other than OpenSCAP to disperse the potential confusion
<span>&gt; </span>  (clearly state it&#39;s possible to use it in other scanners too).
<span>&gt; </span>
<span>&gt; </span>To express my subjective opinion I like the idea of the project to be
<span>&gt; </span>renamed to &quot;OpenSCAP Security Guide&quot;. But wanted to know wider opinions
<span>&gt; </span>from the community on the potential translation.
</pre>
      </blockquote>
      <pre>I think it&#39;s not necessary to rename the projects themselves. However I am all for promoting the OpenSCAP &quot;umbrella&quot; and cross linking the projects. Renaming the projects would be very costly and confusing for existing users. The benefits aren&#39;t worth it IMO.

In my opinion scap-security-guide should stay as is because openscap-security-guide implies a tool lock-in which is not the case.</pre>
    </blockquote>
    <br></div></div>
    Jan, thank you for starting this conversation! I&#39;m <u><b>very</b></u>
    much in favor of a unified umbrella/naming.<br>
    <br>
    As sgrubb pointed out, OpenSCAP has classically been the
    interpreter. If we rename SSG to &quot;OpenSCAP Security Guide,&quot; the name
    creates an impression the content would only work with OpenSCAP. For
    this reason, are you proposing we change the OpenSCAP interpreter as
    well? e.g.:<br>
    <br>
    OpenSCAP: A portfolio of open source SCAP utilities and content,
    which includes:<br>
            * OpenSCAP Workbench:    Used for tailoring content
    (formerally scap-workbench)<br>
            * OpenSCAP Interpreter:    A cross platform, open source
    SCAP interpreter)<br>
            * OpenSCAP Content:        An open source project delivering
    a large body of SCAP content. Used as upstream for such profiles as
    the STIG and C2S<br>
            * OpenSCAP Anaconda Plugin:     A project to integrate SCAP
    scanning into Linux provisioning<br>
            * OpenSCAP Spacewalk Plugin:    A project to integrate
    centralized SCAP scanning into the Spacewalk/Satellite system
    management software<br>
    <br>
    <br>
  </div>

<br>_______________________________________________<br>
scap-security-guide mailing list<br>
<a href="mailto:scap-security-guide@lists.fedorahosted.org">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>
<br></blockquote></div><br></div>