From: Joshua Brindle <method@manicmethod.com>
To: fedora-selinux-list@redhat.com, SE Linux <selinux@tycho.nsa.gov>
Cc: Karl MacMillan <kmacmillan@tresys.com>,
Kathy Shonaiya <Shonaiya@tresys.com>,
Murray McAllister <mmcallis@redhat.com>,
"'Christopher J. PeBenito'" <cpebenito@tresys.com>
Subject: Re: The SELinux Documentation Project
Date: Fri, 27 Nov 2009 15:31:14 -0500 [thread overview]
Message-ID: <4B103712.2050709@manicmethod.com> (raw)
In-Reply-To: <4AC1130D.8000601@manicmethod.com>
Joshua Brindle wrote:
> As we discussed at Linux Plumbers Conference during the 'Making SELinux
> Easier to Use" talk we have some document deficiencies in the SELinux
> project.
>
<snip>
We have gotten some good contributions to the documentation project over
the last couple months but there is always more to do. I've updated the
Documentation TODO at:
<http://selinuxproject.org/page/Documentation_TODO>
with some docs we'd like written and some guidance on what the format
should be. Use cases would be particularly appreciated.
If you haven't gone to the documentation wiki lately take a look at
<http://selinuxproject.org/page/Main_Page>
and see what's been added.
Thanks for the help of the contributors and hopefully this effort will
go a long way toward gaining users and keeping SELinux enabled.
--
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.
next prev parent reply other threads:[~2009-11-27 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 19:48 The SELinux Documentation Project [Request for topics] Joshua Brindle
2009-11-27 20:31 ` Joshua Brindle [this message]
2009-11-28 12:17 ` The SELinux Documentation Project Dominick Grift
2009-11-28 19:10 ` Joshua Brindle
2009-12-14 17:49 ` Serge E. Hallyn
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=4B103712.2050709@manicmethod.com \
--to=method@manicmethod.com \
--cc=Shonaiya@tresys.com \
--cc=cpebenito@tresys.com \
--cc=fedora-selinux-list@redhat.com \
--cc=kmacmillan@tresys.com \
--cc=mmcallis@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.