On Wednesday, July 8, 2015, Shawn Wells <[email protected]> wrote: > > > On 7/8/15 7:41 AM, Martin Preisler wrote: > > I wrote a small blog post about a new feature in SSG 0.1.24 - > building one HTML guide for each profile we ship and providing > a convenient switcher. > http://martin.preisler.me/2015/07/scap-security-guide-now-has-an-html-guide-for-each-profile/ > > It includes a screenshot and a live demo :-) Feedback appreciated. > > > From the posting: > > We plan to install these guides in downstream packages (e.g. Fedora > <https://fedoraproject.org/>). Instead of bundling them with the main > package we will create a subpackage -doc with the guides and other optional > documentation material. > > > That means we have: > - openscap-scanner > - scap-security-guide > - scap-security-guide-docs > > Having multiple naming schemes is a bit confusing, especially for new > users. Is it time to repackage SSG as openscap-content? > > e.g > openscap-scanner > openscap-workbench > openscap-content > openscap-content-docs > >> >> +1. I actually feel like this falls more in line with the openscap project and tightly integrates SSG into openscap.
> -- > SCAP Security Guide mailing list > [email protected] <javascript:;> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide > https://github.com/OpenSCAP/scap-security-guide/ >
-- SCAP Security Guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide https://github.com/OpenSCAP/scap-security-guide/
