On Tue, 2014-02-18 at 22:32 -0500, Shawn Wells wrote: > On 2/17/14, 6:19 PM, Spencer Shimko wrote: > > On Sun, Feb 16, 2014 at 10:37 PM, Steve Grubb <[email protected]> wrote: > >> On Sunday, February 16, 2014 04:03:24 PM Shawn Wells wrote:
> To test things out (as Greg Elin suggested), I merged the code into GitHub: > https://github.com/ssgproject > > It picked up historical changes made by those who have GitHub accounts, e.g: > https://github.com/ssgproject/content/commits/master/Makefile > > As mentioned, GutHub can also host HTML pages, giving us a version > controlled repo for the docs. We can CNAME ssgproject.org against this. > https://github.com/ssgproject/ssgproject.github.io > http://ssgproject.github.io/ > > A few days ago I also played around with the ticket system: > https://github.com/ssgproject/content/issues > > IMO, this seems like a much better community site. What's the right way > to go about this -- "just do it," or perhaps setup a poll? I want to say +1 "just do it", but I think poll might actually be the best way forward. Because if everyone isn't onboard, then this could possibly be the start of a slow downward spiral. I vote Aye. > _______________________________________________ > scap-security-guide mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scap-security-guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
