The time has come where we need a domain name. In part for branding/marketing of the project, but also to provide us with blogs, large document storage, potential shell access for committers, etc. We can get hosting for free from openshift.com, but what should we call the domain name?
Some ideas have been: ssgproject scapsecurityguides scapsecurityguide scapguides scap-security-guide scapcontent
Or should we make up a name ala Aqueduct and Accumulo style?
On 04/29/2013 11:17 AM, Shawn Wells wrote:
The time has come where we need a domain name. In part for branding/marketing of the project, but also to provide us with blogs, large document storage, potential shell access for committers, etc. We can get hosting for free from openshift.com, but what should we call the domain name?
Some ideas have been: ssgproject scapsecurityguides scapsecurityguide scapguides scap-security-guide scapcontent
Or should we make up a name ala Aqueduct and Accumulo style?
Probably the latter.
Once one removes the domain the current name is not very informative.
Additional questions pertinent to name choice: will SSG always apply to just Red Hat? Or Fedora? Just the OS or more? Does a guide include remediation?
On 4/29/13 11:26 AM, Gary Gapinski wrote:
On 04/29/2013 11:17 AM, Shawn Wells wrote:
The time has come where we need a domain name. In part for branding/marketing of the project, but also to provide us with blogs, large document storage, potential shell access for committers, etc. We can get hosting for free from openshift.com, but what should we call the domain name?
Some ideas have been: ssgproject scapsecurityguides scapsecurityguide scapguides scap-security-guide scapcontent
Or should we make up a name ala Aqueduct and Accumulo style?
Probably the latter.
Once one removes the domain the current name is not very informative.
Additional questions pertinent to name choice: will SSG always apply to just Red Hat? Or Fedora?
I really hope not.
Most ambitiously I'd like to see a "scapsecurityguides.org" become a true community of upstream SCAP content, for any platform. The various .mil/.gov sites always house "official" content, but developers need an upstream location.
Just the OS or more? Does a guide include remediation?
Currently SSG has RHEL and JBoss content, with the doors open for remediation patches.
I'm a fan of scap-security-guides.org. I'm not as much a fan of run-on domains.
If you want to have fun, you could be scap.securityguides.org or some such.
Trevor
On Mon, Apr 29, 2013 at 11:32 AM, Shawn Wells shawn@redhat.com wrote:
On 4/29/13 11:26 AM, Gary Gapinski wrote:
On 04/29/2013 11:17 AM, Shawn Wells wrote:
The time has come where we need a domain name. In part for branding/marketing of the project, but also to provide us with blogs, large document storage, potential shell access for committers, etc. We can get hosting for free from openshift.com, but what should we call the domain name?
Some ideas have been: ssgproject scapsecurityguides scapsecurityguide scapguides scap-security-guide scapcontent
Or should we make up a name ala Aqueduct and Accumulo style?
Probably the latter.
Once one removes the domain the current name is not very informative.
Additional questions pertinent to name choice: will SSG always apply to just Red Hat? Or Fedora?
I really hope not.
Most ambitiously I'd like to see a "scapsecurityguides.org" become a true community of upstream SCAP content, for any platform. The various .mil/.gov sites always house "official" content, but developers need an upstream location.
Just the OS or more? Does a guide include
remediation?
Currently SSG has RHEL and JBoss content, with the doors open for remediation patches.
______________________________**_________________ scap-security-guide mailing list scap-security-guide@lists.**fedorahosted.orgscap-security-guide@lists.fedorahosted.org https://lists.fedorahosted.**org/mailman/listinfo/scap-**security-guidehttps://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
scap-security-guide@lists.fedorahosted.org
-
Gary Gapinski -
Shawn Wells -
Trevor Vaughan