All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: The SELinux Documentation Project [Request for topics]
Date: Mon, 28 Sep 2009 15:48:29 -0400	[thread overview]
Message-ID: <4AC1130D.8000601@manicmethod.com> (raw)

As we discussed at Linux Plumbers Conference during the 'Making SELinux 
Easier to Use" talk we have some document deficiencies in the SELinux 
project.

I volunteered to start an SELinux Documentation Project. The primary 
purpose of the project would be to get as much documentation as possible 
on the selinuxproject.org wiki, organized in a fashion that users can 
understand and consume easily.

As I admitted before, we, the developers, are not always the best people 
to judge what documentation users need and therefore am requesting 
users, hopefully from different backgrounds and environments, tell us 
what documentation they feel is lacking, what questions they've been 
asked or have asked themselves and couldn't find documentation for.

I think we need basic documentation that tells about SELinux (both 
beginner and advanced), howto's for specific things (using secmark, 
using netlabel, etc) and a set of short 'recipes' to accomplish simple 
tasks.

There are documents all over the place with various information, as well 
as blog entries and mailing list archives but the effort here is to 
consolidate all those resources onto selinuxproject.org.

I'd also like to see volunteers in the community to help out with the 
documentation effort, I know quite a few people already write things 
like this on blogs, etc and it would be great to see that information 
moved/copied onto selinuxproject.org.


Users:

Please, if you are a user and have run in to lack of documentation 
respond to this thread, or privately if you aren't comfortable talking 
on list so that we can collect what the biggest deficiencies are and get 
to writing documentation as soon as possible.


Thanks.

--
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.

             reply	other threads:[~2009-09-28 19:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-28 19:48 Joshua Brindle [this message]
2009-11-27 20:31 ` The SELinux Documentation Project Joshua Brindle
2009-11-28 12:17   ` 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=4AC1130D.8000601@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=Shonaiya@tresys.com \
    --cc=fedora-selinux-list@redhat.com \
    --cc=kmacmillan@tresys.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.