+1 (Especially since users can change w/local style sheets if desired)
-- Shawn Wells Director, Innovation Programs [email protected] | 443.534.0130 @shawndwells > On Jun 3, 2014, at 7:11 AM, Greg Elin <[email protected]> wrote: > > I recommend going with the powered by approach on all output so SSG logo > always present. > > Default company logo could be a "logo here" light gray placeholder image. > > Greg > > >> On Tue, Jun 3, 2014 at 5:52 AM, Jan Lieskovsky <[email protected]> wrote: >> Hello folks, >> >> since (for now [if we ever will]) we didn't change the name of the project, >> and will keep the SCAP Security Guide one, and since we have received icons >> for both of the alternatives (renaming to OpenSCAP SG, or staying with >> current >> name) of the project name, would like to check with you the following: >> >> Would the community want the SCAP Security Guide icon to be included in the >> HTML version of the guide (for particular products), the SSG product creates >> within the build process? Also, would we want this icon to be included on >> the project wiki pages? >> >> Or would we rather want to stay with current position, having wiki page & >> corresponding HTML guides vendor neutral, so they can be modified (according >> to the subsequent needs) afterwards? >> >> Opinions for SVG icon inclusion / against it appreciated. >> >> Thank you && Regards, Jan. >> -- >> Jan iankko Lieskovsky / Red Hat Security Technologies Team >> >> _______________________________________________ >> scap-security-guide mailing list >> [email protected] >> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide > > _______________________________________________ > scap-security-guide mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
_______________________________________________ scap-security-guide mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
