From: "David O'Brien" <daobrien@redhat.com>
To: fedora-selinux-list-request@redhat.com,
"NSA_SELinux List" <selinux@tycho.nsa.gov>,
"redhat-lspp@redhat.com" <redhat-lspp@redhat.com>
Cc: David Howells <dhowells@redhat.com>,
Forrest Taylor <ftaylor@redhat.com>,
Harald Hoyer <harald@redhat.com>,
James Morris <jmorris@redhat.com>,
Karsten Wade <kwade@redhat.com>,
Nalin Dahyabhai <nalin@redhat.com>,
Stephen John Smoogen <smooge@gmail.com>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Thomas Woerner <twoerner@redhat.com>,
Tomas Mraz <tmraz@redhat.com>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: RHEL5 Security Guide draft TOC for review/comment
Date: Mon, 31 Jul 2006 11:11:39 +1000 [thread overview]
Message-ID: <200607311111.40188.daobrien@redhat.com> (raw)
In-Reply-To: <200607281151.46191.daobrien@redhat.com>
top posting...
I've received a number of replies to this, offering suggestions and review
time, etc. Thanks to all.
I'll start collating comments and suggestions from everyone and put together a
revised TOC.
I have a number of volunteers for SELinux, which is great, so I'll have to ask
that people nominate a "focus-area", be it Policy, Troubleshooting, End-user
Control, Administrator Control, whatever. That way people can check out the
appropriate file and have their way with it, without fear of treading on
toes.
thanks everyone for the feedback and offers to help.
David
On Friday 28 July 2006 11:51, David O'Brien wrote:
> Firstly, apologies if you receive this twice. I'm casting a wide net...
>
> I've attached the draft TOC of the Red Hat Enterprise Linux 5 Security
> Guide for all to review and comment on. (Despite appearances it's not
> supposed to be a valid xml file; I wrote it that way for my own
> convenience.) As mentioned in the Scope Statement (attached), this is the
> integration of the RHEL4 Security Guide and the SELinux Guide. Our focus
> for this release is on accuracy and use cases, at the expense of low-level
> details.
>
> Please feel free to make any suggestions about structure, topics, etc., how
> we could use/enhance this info from other areas (Training?) or vice versa.
>
> I have a few names down for reviewers, authors/editors, etc., (see comments
> in file) but am looking for more. If there is an area where you feel you
> could contribute, please put your hand up. All contributors will be
> acknowledged and included in the colophon, and earn our undying gratitude.
> :-)
>
> cheers
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2006-07-31 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 1:51 RHEL5 Security Guide draft TOC for review/comment David O'Brien
2006-07-31 1:11 ` David O'Brien [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200607311111.40188.daobrien@redhat.com \
--to=daobrien@redhat.com \
--cc=dhowells@redhat.com \
--cc=drepper@redhat.com \
--cc=fedora-selinux-list-request@redhat.com \
--cc=ftaylor@redhat.com \
--cc=harald@redhat.com \
--cc=jmorris@redhat.com \
--cc=kwade@redhat.com \
--cc=nalin@redhat.com \
--cc=redhat-lspp@redhat.com \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
--cc=smooge@gmail.com \
--cc=tmraz@redhat.com \
--cc=twoerner@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.