[RFC] SCAP Security Guide icon to be included into HTML guides generated by SSG?

[Jan Lieskovsky]

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

[Greg Elin]

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  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
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

[Shawn Wells]

+1

(Especially since users can change w/local style sheets if desired)

--
Shawn Wells
Director, Innovation Programs
[e-mail] | 443.534.0130
@shawndwells
> On Jun 3, 2014, at 7:11 AM, Greg Elin  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  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
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

Please vote [was: Re: [RFC] SCAP Security Guide icon to be included into HTML guides generated by SSG?]

[Jan Lieskovsky]

Hello folks,

since one image is better than thousand words, have put together couple
of examples how it could look like:
  [1] http://jlieskov.fedorapeople.org/logos/

The rhel6-guide.html is the vanilla one (how it looks now), then the proposals
are as follows (legend: filename = icon + text orientation + if the image is at the top or at bottom),
e.g.:
* rhel6-guide-horizontal-top.html - the "SCAP Security Guide" is on the side wrt to the logo, whole
                                    image is inserted at the top,
* rhel6-guide-vertical-bottom.html - the "SCAP Security Guide" text is below the logo, whole image
                                     got inserted at the bottom of the guide,
* rhel6-guide-icononly-top.html - there's just logo (no text), image got inserted at the top
* ... (see the other options)

All of the icons are clickable (after click should bring the user to SSG's Fedorahosted's home page).

If you have recommendations, where else on the page the logo could be inserted (and which one of
them would be the most preferred one), please share. The dimensions (w x h) of the included image
can be changed yet (decreased), if there would be impression this as generated now it would be too big.

Also, since this is just draft, I have (hard) included the PNG versions of the particular image. Once
(if) we are agreed, which version would be the most preferred one, I would start looking how
to modify the build process to include the images on-the-fly & optimize the process as much as
possible.

Last, but not least, I am aware the *-bottom.html versions of the examples contain
"SCAP Security Guide https://fedorahosted.org/scap-security-guide" at the top of the page
yet (didn't change this, since these are just drafts how the new guides could look like).

Please vote / share your opinions, which of the versions you like the most (even if it should
be the current / vanilla / not-changed one) with short argumentation why.

Thank you && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Technologies Team

----- Original Message -----
> From: "Shawn Wells" 
> To: "SCAP Security Guide" 
> Sent: Tuesday, June 3, 2014 1:40:32 PM
> Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML	guides	generated by SSG?
>
> +1
>
> (Especially since users can change w/local style sheets if desired)
>
> --
> Shawn Wells
> Director, Innovation Programs
> [e-mail] | 443.534.0130
> @shawndwells
>
> On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] > 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 < [e-mail] > 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
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

Please vote [was: Re: [RFC] SCAP Security Guide icon to be included into HTML guides generated by SSG?]

[Andrew Gilmore]

+1 for horizontal, although every implementation is using too much
whitespace for logo.

On Tue, Jun 3, 2014 at 8:22 AM, Jan Lieskovsky  wrote:
> Hello folks,
>
> since one image is better than thousand words, have put together couple
> of examples how it could look like:
>   [1] http://jlieskov.fedorapeople.org/logos/
>
> The rhel6-guide.html is the vanilla one (how it looks now), then the
> proposals
> are as follows (legend: filename = icon + text orientation + if the image
> is at the top or at bottom),
> e.g.:
> rhel6-guide-horizontal-top.html - the "SCAP Security Guide" is on the
>
> side wrt to the logo, whole
>                                     image is inserted at the top,
> rhel6-guide-vertical-bottom.html - the "SCAP Security Guide" text is
>
> below the logo, whole image
>                                      got inserted at the bottom of the
> guide,
> rhel6-guide-icononly-top.html - there's just logo (no text), image got
>
> inserted at the top
> ... (see the other options)
>
> All of the icons are clickable (after click should bring the user to SSG's
> Fedorahosted's home page).
>
> If you have recommendations, where else on the page the logo could be
> inserted (and which one of
> them would be the most preferred one), please share. The dimensions (w x
> h) of the included image
> can be changed yet (decreased), if there would be impression this as
> generated now it would be too big.
>
> Also, since this is just draft, I have (hard) included the PNG versions of
> the particular image. Once
> (if) we are agreed, which version would be the most preferred one, I would
> start looking how
> to modify the build process to include the images on-the-fly & optimize
> the process as much as
> possible.
>
> Last, but not least, I am aware the *-bottom.html versions of the examples
> contain
> "SCAP Security Guide https://fedorahosted.org/scap-security-guide" at the
> top of the page
> yet (didn't change this, since these are just drafts how the new guides
> could look like).
>
> Please vote / share your opinions, which of the versions you like the most
> (even if it should
> be the current / vanilla / not-changed one) with short argumentation why.
> Thank you && Regards, Jan.
>
> Jan iankko Lieskovsky / Red Hat Security Technologies Team
>
> ----- Original Message -----
> > From: "Shawn Wells" 
> > To: "SCAP Security Guide" 
> > Sent: Tuesday, June 3, 2014 1:40:32 PM
> > Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML
>
> guides  generated by SSG?
> > +1
> >
> > (Especially since users can change w/local style sheets if desired)
> >
> > --
> > Shawn Wells
> > Director, Innovation Programs
> > [e-mail] | 443.534.0130
> > @shawndwells
> >
> > On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] >
>
> 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 < [e-mail] >
>
> 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
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

Please vote [was: Re: [RFC] SCAP Security Guide icon to be included into HTML guides generated by SSG?]

[Trevor Vaughan]

So, I'm late to the party.

I'm voting for vertical-top followed by horizontal-top.

Trevor

On Tue, Jun 3, 2014 at 10:30 AM, Andrew Gilmore  wrote:
> +1 for horizontal, although every implementation is using too much
> whitespace for logo.
>
> On Tue, Jun 3, 2014 at 8:22 AM, Jan Lieskovsky 
> wrote:
> > Hello folks,
> >
> > since one image is better than thousand words, have put together couple
> > of examples how it could look like:
> >   [1] http://jlieskov.fedorapeople.org/logos/
> >
> > The rhel6-guide.html is the vanilla one (how it looks now), then the
> > proposals
> > are as follows (legend: filename = icon + text orientation + if the image
> > is at the top or at bottom),
> > e.g.:
> > rhel6-guide-horizontal-top.html - the "SCAP Security Guide" is on the
> >
> > side wrt to the logo, whole
> >                                     image is inserted at the top,
> > rhel6-guide-vertical-bottom.html - the "SCAP Security Guide" text is
> >
> > below the logo, whole image
> >                                      got inserted at the bottom of the
> > guide,
> > rhel6-guide-icononly-top.html - there's just logo (no text), image got
> >
> > inserted at the top
> > ... (see the other options)
> >
> > All of the icons are clickable (after click should bring the user to
> > SSG's Fedorahosted's home page).
> >
> > If you have recommendations, where else on the page the logo could be
> > inserted (and which one of
> > them would be the most preferred one), please share. The dimensions (w x
> > h) of the included image
> > can be changed yet (decreased), if there would be impression this as
> > generated now it would be too big.
> >
> > Also, since this is just draft, I have (hard) included the PNG versions
> > of the particular image. Once
> > (if) we are agreed, which version would be the most preferred one, I
> > would start looking how
> > to modify the build process to include the images on-the-fly & optimize
> > the process as much as
> > possible.
> >
> > Last, but not least, I am aware the *-bottom.html versions of the
> > examples contain
> > "SCAP Security Guide https://fedorahosted.org/scap-security-guide" at
> > the top of the page
> > yet (didn't change this, since these are just drafts how the new guides
> > could look like).
> >
> > Please vote / share your opinions, which of the versions you like the
> > most (even if it should
> > be the current / vanilla / not-changed one) with short argumentation why.
> > Thank you && Regards, Jan.
> >
> > Jan iankko Lieskovsky / Red Hat Security Technologies Team
> >
> > ----- Original Message -----
> > > From: "Shawn Wells" 
> > > To: "SCAP Security Guide" 
> > > Sent: Tuesday, June 3, 2014 1:40:32 PM
> > > Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML
> >
> > guides  generated by SSG?
> > > +1
> > >
> > > (Especially since users can change w/local style sheets if desired)
> > >
> > > --
> > > Shawn Wells
> > > Director, Innovation Programs
> > > [e-mail] | 443.534.0130
> > > @shawndwells
> > >
> > > On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] >
> >
> > 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 < [e-mail] >
> >
> > 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
> > > [e-mail]
> > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> > >
> > > scap-security-guide mailing list
> > > [e-mail]
> > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> > >
> > > scap-security-guide mailing list
> > > [e-mail]
> > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

Please vote [was: Re: [RFC] SCAP Security Guide icon to be included into HTML guides generated by SSG?]

[Jan Lieskovsky]

Hello Trevor,

----- Original Message -----
> From: "Trevor Vaughan" 
> To: "SCAP Security Guide" 
> Sent: Friday, June 20, 2014 11:39:31 PM
> Subject: Re: Please vote [was: Re: [RFC] SCAP Security Guide icon to be	included into HTML guides generated by SSG?]
>
> So, I'm late to the party.

Not that late as it might seem (due to OpenSCAP issue not recognizing <img>
element in <description> / <front-matter> elements I didn't actually get into
the state I would be able to submit a patch implementing the proposal yet).
> I'm voting for vertical-top followed by horizontal-top.

Not sure I understand the vote - to have vertical in the header of the guide,
while horizontal in the footer of it? Can you clarify yet?

Thank you && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Technologies Team
> Trevor
>
> On Tue, Jun 3, 2014 at 10:30 AM, Andrew Gilmore < [e-mail] >
> wrote:
>
> +1 for horizontal, although every implementation is using too much whitespace
> for logo.
>
> On Tue, Jun 3, 2014 at 8:22 AM, Jan Lieskovsky < [e-mail] > wrote:
>
> Hello folks,
>
> since one image is better than thousand words, have put together couple
> of examples how it could look like:
> [1] http://jlieskov.fedorapeople.org/logos/
>
> The rhel6-guide.html is the vanilla one (how it looks now), then the
> proposals
> are as follows (legend: filename = icon + text orientation + if the image is
> at the top or at bottom),
> e.g.:
> rhel6-guide-horizontal-top.html - the "SCAP Security Guide" is on the side
>
> wrt to the logo, whole
> image is inserted at the top,
> rhel6-guide-vertical-bottom.html - the "SCAP Security Guide" text is below
>
> the logo, whole image
> got inserted at the bottom of the guide,
> rhel6-guide-icononly-top.html - there's just logo (no text), image got
>
> inserted at the top
> ... (see the other options)
>
> All of the icons are clickable (after click should bring the user to SSG's
> Fedorahosted's home page).
>
> If you have recommendations, where else on the page the logo could be
> inserted (and which one of
> them would be the most preferred one), please share. The dimensions (w x h)
> of the included image
> can be changed yet (decreased), if there would be impression this as
> generated now it would be too big.
>
> Also, since this is just draft, I have (hard) included the PNG versions of
> the particular image. Once
> (if) we are agreed, which version would be the most preferred one, I would
> start looking how
> to modify the build process to include the images on-the-fly & optimize the
> process as much as
> possible.
>
> Last, but not least, I am aware the *-bottom.html versions of the examples
> contain
> "SCAP Security Guide https://fedorahosted.org/scap-security-guide " at the
> top of the page
> yet (didn't change this, since these are just drafts how the new guides could
> look like).
>
> Please vote / share your opinions, which of the versions you like the most
> (even if it should
> be the current / vanilla / not-changed one) with short argumentation why.
> Thank you && Regards, Jan.
>
> Jan iankko Lieskovsky / Red Hat Security Technologies Team
>
> ----- Original Message -----
> > From: "Shawn Wells" < [e-mail] >
> > To: "SCAP Security Guide" < [e-mail] >
> > Sent: Tuesday, June 3, 2014 1:40:32 PM
> > Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML guides
> > generated by SSG?
> >
> > +1
> >
> > (Especially since users can change w/local style sheets if desired)
> >
> > --
> > Shawn Wells
> > Director, Innovation Programs
> > [e-mail] | 443.534.0130
> > @shawndwells
> >
> > On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] > 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 < [e-mail] >
> > 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
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> [phone]
> [e-mail]
>
> -- This account not approved for unencrypted proprietary information --
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

Please vote [was: Re: [RFC] SCAP Security Guide icon to be included into HTML guides generated by SSG?]

[Trevor Vaughan]

Oh, sorry, I was attempting to rank.

My vote is as follows.

1) vertical-top
2) horizontal-top
3) everything else

Though, having a header and footer might be nice. The footer doesn't really
take up that much space and adds a bit of finality to the whole document.

Thanks,

Trevor

On Mon, Jun 23, 2014 at 5:12 AM, Jan Lieskovsky  wrote:
> Hello Trevor,
>
> ----- Original Message -----
> > From: "Trevor Vaughan" 
> > To: "SCAP Security Guide" 
> > Sent: Friday, June 20, 2014 11:39:31 PM
> > Subject: Re: Please vote [was: Re: [RFC] SCAP Security Guide icon to be
>   included into HTML guides generated by SSG?]
> > So, I'm late to the party.
>
> Not that late as it might seem (due to OpenSCAP issue not recognizing <img>
> element in <description> / <front-matter> elements I didn't actually get
> into
> the state I would be able to submit a patch implementing the proposal yet).
> > I'm voting for vertical-top followed by horizontal-top.
>
> Not sure I understand the vote - to have vertical in the header of the
> guide,
> while horizontal in the footer of it? Can you clarify yet?
> Thank you && Regards, Jan.
>
> Jan iankko Lieskovsky / Red Hat Security Technologies Team
> > Trevor
> >
> > On Tue, Jun 3, 2014 at 10:30 AM, Andrew Gilmore < [e-mail] >
> > wrote:
> >
> > +1 for horizontal, although every implementation is using too much
>
> whitespace
> > for logo.
> >
> > On Tue, Jun 3, 2014 at 8:22 AM, Jan Lieskovsky < [e-mail] >
>
> wrote:
> > Hello folks,
> >
> > since one image is better than thousand words, have put together couple
> > of examples how it could look like:
> > [1] http://jlieskov.fedorapeople.org/logos/
> >
> > The rhel6-guide.html is the vanilla one (how it looks now), then the
> > proposals
> > are as follows (legend: filename = icon + text orientation + if the
>
> image is
> > at the top or at bottom),
> > e.g.:
> > rhel6-guide-horizontal-top.html - the "SCAP Security Guide" is on the
>
> side
> > wrt to the logo, whole
> > image is inserted at the top,
> > rhel6-guide-vertical-bottom.html - the "SCAP Security Guide" text is
>
> below
> > the logo, whole image
> > got inserted at the bottom of the guide,
> > rhel6-guide-icononly-top.html - there's just logo (no text), image got
> >
> > inserted at the top
> > ... (see the other options)
> >
> > All of the icons are clickable (after click should bring the user to
>
> SSG's
> > Fedorahosted's home page).
> >
> > If you have recommendations, where else on the page the logo could be
> > inserted (and which one of
> > them would be the most preferred one), please share. The dimensions (w x
>
> h)
> > of the included image
> > can be changed yet (decreased), if there would be impression this as
> > generated now it would be too big.
> >
> > Also, since this is just draft, I have (hard) included the PNG versions
>
> of
> > the particular image. Once
> > (if) we are agreed, which version would be the most preferred one, I
>
> would
> > start looking how
> > to modify the build process to include the images on-the-fly & optimize
>
> the
> > process as much as
> > possible.
> >
> > Last, but not least, I am aware the *-bottom.html versions of the
>
> examples
> > contain
> > "SCAP Security Guide https://fedorahosted.org/scap-security-guide " at
>
> the
> > top of the page
> > yet (didn't change this, since these are just drafts how the new guides
>
> could
> > look like).
> >
> > Please vote / share your opinions, which of the versions you like the
>
> most
> > (even if it should
> > be the current / vanilla / not-changed one) with short argumentation why.
> > Thank you && Regards, Jan.
> >
> > Jan iankko Lieskovsky / Red Hat Security Technologies Team
> >
> > ----- Original Message -----
> > > From: "Shawn Wells" < [e-mail] >
> > > To: "SCAP Security Guide" < [e-mail]
> > > Sent: Tuesday, June 3, 2014 1:40:32 PM
> > > Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML
>
> guides
> > > generated by SSG?
> > >
> > > +1
> > >
> > > (Especially since users can change w/local style sheets if desired)
> > >
> > > --
> > > Shawn Wells
> > > Director, Innovation Programs
> > > [e-mail] | 443.534.0130
> > > @shawndwells
> > >
> > > On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] >
>
> 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 < [e-mail] >
> > > 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
> > > [e-mail]
> > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> > >
> > > scap-security-guide mailing list
> > > [e-mail]
> > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> > >
> > > scap-security-guide mailing list
> > > [e-mail]
> > > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
> >
> > --
> > Trevor Vaughan
> > Vice President, Onyx Point, Inc
> > [phone]
> > [e-mail]
> >
> > -- This account not approved for unencrypted proprietary information --
> >
> > scap-security-guide mailing list
> > [e-mail]
> > https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

[Jan Lieskovsky]

----- Original Message -----
> From: "Shawn Wells" 
> To: "SCAP Security Guide" 
> Sent: Tuesday, June 3, 2014 1:40:32 PM
> Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML	guides	generated by SSG?
>
> +1
>
> (Especially since users can change w/local style sheets if desired)
>
> --
> Shawn Wells
> Director, Innovation Programs
> [e-mail] | 443.534.0130
> @shawndwells
>
> On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] > 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.

So place there just something like gray-ed out bounding box with the stub
text "Place your company logo here" instead of including exact SSG logo
as proposed in the subsequent reply to this thread?

And should this 'grayed out default bounding box / stub' approach be consistent
for both 1) upstream git repo content 2) upcoming RHEL-6 package? Or is the
approach: 1) upstream git repo content having gray-ed out image stub 2)
RHEL-6 rpm having exact icon (one of those proposed) as proposed in the follow-up
on this thread acceptable too? [*]

Thank you && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Technologies Team

P.S.: [*] Asking mainly due the reasons I am not aware of subsequent ways, how
          the benchmark could be utilized by downstream vendors. If they would want /
          prefer just stub instead of direct image, that option should be considered.
> Greg
>
> On Tue, Jun 3, 2014 at 5:52 AM, Jan Lieskovsky < [e-mail] > 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
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

[Shawn Wells]

On 6/3/14, 8:12 AM, Jan Lieskovsky wrote:
> ----- Original Message -----
> > > From: "Shawn Wells"
> > > To: "SCAP Security Guide"
> > > Sent: Tuesday, June 3, 2014 1:40:32 PM
> > > Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML	guides	generated by SSG?
> > >
> > > +1
> > >
> > > (Especially since users can change w/local style sheets if desired)
> > >
> > > --
> > > Shawn Wells
> > > Director, Innovation Programs
> > > [e-mail]  | 443.534.0130
> > > @shawndwells
> > >
> > > On Jun 3, 2014, at 7:11 AM, Greg Elin <[e-mail]  > 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.
>
> So place there just something like gray-ed out bounding box with the stub
> text "Place your company logo here" instead of including exact SSG logo
> as proposed in the subsequent reply to this thread?
>
> And should this 'grayed out default bounding box / stub' approach be consistent
> for both 1) upstream git repo content 2) upcoming RHEL-6 package? Or is the
> approach: 1) upstream git repo content having gray-ed out image stub 2)
> RHEL-6 rpm having exact icon (one of those proposed) as proposed in the follow-up
> on this thread acceptable too? [*]

Building upon Greg's comments, there are two easy methods for "branding":

- One aspect is the default logo, (e.g. displaying 
SCAP-SecurityGuide-Horizontal.png as reflected in your mock ups)
     - The other is including a "powered by" footer (similar to 
"Generated by OpenSCAP 1.0.8")

Government and commercial users are turning to the OpenSCAP family and 
replacing legacy and proprietary tooling. OpenSCAP+SSG is becoming a 
brand-name scanning engine :) Having the SSG logo included by default in 
upstream and RHEL6 releases is very ideal, both from a community 
brand/marketing/awareness perspective, but also for a "validation of 
content." ISSE/ISSO staff want to see the logo in the result printouts.

Some users, particularly System Integrators and 3PAO's, have expressed 
desires to brand the scanning output. I believe documenting how to 
overwrite the primary logo (e.g. with a style sheet) will meet their needs.

OpenSCAP's current footer reads "/Generated by OpenSCAP ($version) on 
$date/" -- perhaps we could update OpenSCAP to also include the content 
source? Something like "/Generated by OpenSCAP ($version) on $date, 
using $contentSource $version/"
> Thank you && Regards, Jan.
>
> Jan iankko Lieskovsky / Red Hat Security Technologies Team
>
> P.S.: [*] Asking mainly due the reasons I am not aware of subsequent ways, how
>            the benchmark could be utilized by downstream vendors. If they would want /
>            prefer just stub instead of direct image, that option should be considered.

[Greg Elin]

Shawn,

Thanks for that clarity.

Expressing the Oscap logo text to indicate report generated by is important and will build trust.

As an end user, I want to know a tool I trust ran the report.

As an end user, the next question I have is essentially, "Are these the right tests?"

At a simple level, that means I care about the name of the profile and WHO provided the profile and S-CAP. If the provider is SSG that is a second branding opportunity for SSG.  (Eg: Chrome rendered my Facebook page.). With security and compliance I care more about certifying each link in the chain.

Understanding who is providing the scanner, and who is providing the content, and who is providing the profiles and what is inside of the profile is very hard right now. But that is another discussion.

Mostly my point is there are at least two important branding opportunities. Also I think all branding must be at least in the first page of any report it content display, clearly in the summary.

Greg
> 301-652-9585at 12:58 AM, Shawn Wells  wrote:
> > On 6/3/14, 8:12 AM, Jan Lieskovsky wrote:
> > ----- Original Message -----
> > > > From: "Shawn Wells" 
> > > > To: "SCAP Security Guide" 
> > > > Sent: Tuesday, June 3, 2014 1:40:32 PM
> > > > Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML	guides	generated by SSG?
> > > >
> > > > +1
> > > >
> > > > (Especially since users can change w/local style sheets if desired)
> > > >
> > > > --
> > > > Shawn Wells
> > > > Director, Innovation Programs
> > > > [e-mail] | 443.534.0130
> > > > @shawndwells
> > > >
> > > > On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] > 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.
> >
> > So place there just something like gray-ed out bounding box with the stub
> > text "Place your company logo here" instead of including exact SSG logo
> > as proposed in the subsequent reply to this thread?
> >
> > And should this 'grayed out default bounding box / stub' approach be consistent
> > for both 1) upstream git repo content 2) upcoming RHEL-6 package? Or is the
> > approach: 1) upstream git repo content having gray-ed out image stub 2)
> > RHEL-6 rpm having exact icon (one of those proposed) as proposed in the follow-up
> > on this thread acceptable too? [*]
>
> Building upon Greg's comments, there are two easy methods for "branding":
> - One aspect is the default logo, (e.g. displaying SCAP-SecurityGuide-Horizontal.png as reflected in your mock ups)
> - The other is including a "powered by" footer (similar to "Generated by OpenSCAP 1.0.8")
>
> Government and commercial users are turning to the OpenSCAP family and replacing legacy and proprietary tooling. OpenSCAP+SSG is becoming a brand-name scanning engine :) Having the SSG logo included by default in upstream and RHEL6 releases is very ideal, both from a community brand/marketing/awareness perspective, but also for a "validation of content." ISSE/ISSO staff want to see the logo in the result printouts.
>
> Some users, particularly System Integrators and 3PAO's, have expressed desires to brand the scanning output. I believe documenting how to overwrite the primary logo (e.g. with a style sheet) will meet their needs.
>
> OpenSCAP's current footer reads "Generated by OpenSCAP ($version) on $date" -- perhaps we could update OpenSCAP to also include the content source? Something like "Generated by OpenSCAP ($version) on $date, using $contentSource $version"
> > Thank you && Regards, Jan.
> >
> > Jan iankko Lieskovsky / Red Hat Security Technologies Team
> >
> > P.S.: [*] Asking mainly due the reasons I am not aware of subsequent ways, how
> >           the benchmark could be utilized by downstream vendors. If they would want /
> >           prefer just stub instead of direct image, that option should be considered.
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide

[Greg Elin]

In addition to being an end user, I am also a potential repackager.

As a repackager/vendor user, I care about sharing the upstream brand with my end users in direct proportion to its halo effect.

Examples:
Intel inside
Genuine Kodak film and chemicals

As a repackager I also want to emphasize my brand.

I think figuring out the powered by OpenSCAP with content from SSG logos and text is first deliverable.

That said, the best deliverable probably starts with just some mock ups of the summary page with all logos and text before any implementations.

Greg

Greg Elin
P: 917-304-3488
E:  [e-mail]

Sent from my iPhone
> On Jun 4, 2014, at 12:58 AM, Shawn Wells  wrote:
> > On 6/3/14, 8:12 AM, Jan Lieskovsky wrote:
> > ----- Original Message -----
> > > > From: "Shawn Wells" 
> > > > To: "SCAP Security Guide" 
> > > > Sent: Tuesday, June 3, 2014 1:40:32 PM
> > > > Subject: Re: [RFC] SCAP Security Guide icon to be included into HTML	guides	generated by SSG?
> > > >
> > > > +1
> > > >
> > > > (Especially since users can change w/local style sheets if desired)
> > > >
> > > > --
> > > > Shawn Wells
> > > > Director, Innovation Programs
> > > > [e-mail] | 443.534.0130
> > > > @shawndwells
> > > >
> > > > On Jun 3, 2014, at 7:11 AM, Greg Elin < [e-mail] > 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.
> >
> > So place there just something like gray-ed out bounding box with the stub
> > text "Place your company logo here" instead of including exact SSG logo
> > as proposed in the subsequent reply to this thread?
> >
> > And should this 'grayed out default bounding box / stub' approach be consistent
> > for both 1) upstream git repo content 2) upcoming RHEL-6 package? Or is the
> > approach: 1) upstream git repo content having gray-ed out image stub 2)
> > RHEL-6 rpm having exact icon (one of those proposed) as proposed in the follow-up
> > on this thread acceptable too? [*]
>
> Building upon Greg's comments, there are two easy methods for "branding":
> - One aspect is the default logo, (e.g. displaying SCAP-SecurityGuide-Horizontal.png as reflected in your mock ups)
> - The other is including a "powered by" footer (similar to "Generated by OpenSCAP 1.0.8")
>
> Government and commercial users are turning to the OpenSCAP family and replacing legacy and proprietary tooling. OpenSCAP+SSG is becoming a brand-name scanning engine :) Having the SSG logo included by default in upstream and RHEL6 releases is very ideal, both from a community brand/marketing/awareness perspective, but also for a "validation of content." ISSE/ISSO staff want to see the logo in the result printouts.
>
> Some users, particularly System Integrators and 3PAO's, have expressed desires to brand the scanning output. I believe documenting how to overwrite the primary logo (e.g. with a style sheet) will meet their needs.
>
> OpenSCAP's current footer reads "Generated by OpenSCAP ($version) on $date" -- perhaps we could update OpenSCAP to also include the content source? Something like "Generated by OpenSCAP ($version) on $date, using $contentSource $version"
> > Thank you && Regards, Jan.
> >
> > Jan iankko Lieskovsky / Red Hat Security Technologies Team
> >
> > P.S.: [*] Asking mainly due the reasons I am not aware of subsequent ways, how
> >           the benchmark could be utilized by downstream vendors. If they would want /
> >           prefer just stub instead of direct image, that option should be considered.
>
> scap-security-guide mailing list
> [e-mail]
> https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide