[RFC] Rename stig-rhel6-server to stig-rhel6-server-upstream?

[Shawn Wells]

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 iase.disa.mil), I'd like to 
rename to stig-rhel6-server-upstream.

Many community members realize the upstream->downstream relationship, 
however I'd like to re-enforce this through the profile name itself.

Thoughts? Objections?

EXTERNAL: [RFC] Rename stig-rhel6-server to stig-rhel6-server-upstream?

[Kachigian, Christopher R]

I agree with the rename.



Chris Kachigian

Lockheed Martin IS&GS
700 N Frederick Ave
Gaithersburg MD 20879

O: 301-240-7709
C: 215-359-6331 (Primary)

-----Original Message-----
From: Shawn Wells [[e-mail]<mailto:[e-mail]>]
Sent: Friday, December 20, 2013 07:48 AM Mountain Standard Time
To: scap-security-guide(a)lists.fedorahosted.org
Subject: EXTERNAL: [RFC] Rename stig-rhel6-server to stig-rhel6-server-upstream?


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 iase.disa.mil), I'd like to
rename to stig-rhel6-server-upstream.

Many community members realize the upstream->downstream relationship,
however I'd like to re-enforce this through the profile name itself.

Thoughts? Objections?
_______________________________________________
scap-security-guide mailing list
scap-security-guide(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

[David Smith]

Agreed with the proposed name change.  The need has become increasingly
obvious with more people participating in the community and using the
project's content.


On Fri, Dec 20, 2013 at 9:48 AM, Shawn Wells <shawn(a)redhat.com&gt; wrote:

>  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 iase.disa.mil), I'd like to
>  rename to stig-rhel6-server-upstream.
>
>  Many community members realize the upstream->downstream relationship,
>  however I'd like to re-enforce this through the profile name itself.
>
>  Thoughts? Objections?
>  _______________________________________________
>  scap-security-guide mailing list
>  scap-security-guide(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>

[Nunez, Luis K]

+1

-ln

From: scap-security-guide-bounces(a)lists.fedorahosted.org
[mailto:[e-mail]] On Behalf Of Dave Smith
Sent: Friday, December 20, 2013 10:02 AM
To: scap-security-guide(a)lists.fedorahosted.org
Subject: Re: [RFC] Rename stig-rhel6-server to stig-rhel6-server-upstream?

Agreed with the proposed name change.  The need has become increasingly obvious with more
people participating in the community and using the project's content.

On Fri, Dec 20, 2013 at 9:48 AM, Shawn Wells
<[e-mail]<mailto:[e-mail]>> wrote:
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 iase.disa.mil<http://iase.disa.mil>), I'd like to rename to
stig-rhel6-server-upstream.

Many community members realize the upstream->downstream relationship, however I'd
like to re-enforce this through the profile name itself.

Thoughts? Objections?
_______________________________________________
scap-security-guide mailing list
[e-mail]<mailto:[e-mail]>
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

[Steinke, Leland J Sr CTR DISA DD (US)]

I like the idea.  The devil, as always, is in the details.  DISA FSO has some unique
requirements that need to be addressed somehow.  If they can be isolated for STIG
synchronization and maintenance without causing undue stress on the rest of the SSG
content, it could be all to the good.


Thanks,
Leland
--
Leland Steinke, Security+
DISA FSO Technical Support Contractor
tapestry technologies, Inc
717-267-5797 (DSN 570)
leland.j.steinke.ctr(a)mail.mil (gov't)
lsteinke(a)tapestrytech.com (com'l)


>  -----Original Message-----
>  From: scap-security-guide-bounces(a)lists.fedorahosted.org [mailto:scap-
>  security-guide-bounces(a)lists.fedorahosted.org] On Behalf Of Shawn Wells
>  Sent: Friday, December 20, 2013 9:48 AM
>  To: scap-security-guide(a)lists.fedorahosted.org
>  Subject: [RFC] Rename stig-rhel6-server to stig-rhel6-server-upstream?
>  
>  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 iase.disa.mil), I'd like to
>  rename to stig-rhel6-server-upstream.
>  
>  Many community members realize the upstream->downstream relationship,
>  however I'd like to re-enforce this through the profile name itself.
>  
>  Thoughts? Objections?
>  _______________________________________________
>  scap-security-guide mailing list
>  scap-security-guide(a)lists.fedorahosted.org
>  https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide