<div dir="ltr">Agreed with the proposed name change.  The need has become increasingly obvious with more people participating in the community and using the project&#39;s content.<br><div><div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Fri, Dec 20, 2013 at 9:48 AM, 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">
SSG enjoys a fantastic working relationship with DISA FSO, however in aspirations to clearly delineate between the upstream STIG profile (e.g. that of SSG) and the formal STIG (listed on <a href="http://iase.disa.mil" target="_blank">iase.disa.mil</a>), I&#39;d like to rename to stig-rhel6-server-upstream.<br>

<br>
Many community members realize the upstream-&gt;downstream relationship, however I&#39;d like to re-enforce this through the profile name itself.<br>
<br>
Thoughts? Objections?<br>
______________________________<u></u>_________________<br>
scap-security-guide mailing list<br>
<a href="mailto:scap-security-guide@lists.fedorahosted.org" target="_blank">scap-security-guide@lists.<u></u>fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide" target="_blank">https://lists.fedorahosted.<u></u>org/mailman/listinfo/scap-<u></u>security-guide</a><br>
</blockquote></div><br></div></div></div></div>