From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from jazzswing.ncsc.mil (jazzswing.ncsc.mil [144.51.68.65]) by tycho.ncsc.mil (8.9.3/8.9.3) with ESMTP id MAA24930 for ; Thu, 25 Oct 2001 12:30:48 -0400 (EDT) Received: from jazzswing.ncsc.mil (localhost [127.0.0.1]) by jazzswing.ncsc.mil with ESMTP id QAA08522 for ; Thu, 25 Oct 2001 16:28:49 GMT Received: from atlantic.mail.pas.earthlink.net (atlantic.mail.pas.earthlink.net [207.217.120.179]) by jazzswing.ncsc.mil with ESMTP id QAA08518 for ; Thu, 25 Oct 2001 16:28:48 GMT Received: from rh1025061onemain (1Cust251.tnt1.beaverton.or.da.uu.net [63.21.201.251]) by atlantic.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with SMTP id JAA25641 for ; Thu, 25 Oct 2001 09:30:43 -0700 (PDT) Message-ID: <008b01c15d71$8b70d600$edaafea9@com> From: "randaL" To: Subject: an offer to help with documentation Date: Thu, 25 Oct 2001 09:24:34 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0088_01C15D36.DC6358C0" Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov This is a multi-part message in MIME format. ------=_NextPart_000_0088_01C15D36.DC6358C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable While I have yet to install SELinux, I have spent considerable time = pouring over all the material available online since first hearing of it = on Slashdot. I expect to have this accomplished by next week, or at = least attempted several times . What I have learned so far has = excited me quite a bit, and I wish that my programming skills were up to = par so that I could contribute... but that is likely to be several years = down the road (if ever). I feel that this is an important direction for = Linux to grow, and commend the people who made the decision to bring = this to the OpenSource Community (and of course the people who have = worked to bring it to its current state). It occurs to me that I may be able to offer assistance in developing the = documentation. This would necessitate my full understanding of the = product as it continues to mature, and provide me with a firm basis on = which to contribute to the code (should I ever develop my skills to that = level). It would provide focus. Additionally, it could allow resources = to be utilized more effectively. Based on the description of content, I = am not sure how I could be of immediate use to the project--I expect = that I would need more time playing with the software--but I wanted to = express my willingness to help as I am able. >>From the ToDo-page, I read the following: -------------------------------------------------------------------------= ------- Documentation Tasks In general the SEL team only works on these tasks to the extent they = are necessary to describe the system to other researchers and developers = or as time is available. a.. Create an Administrator Guidance Document=20 Discuss the use of Flask controls in various environment (ISP, = Desktop, Firewall, etc.) b.. Create a User Guidance Document=20 What to expect as differences in SEL. Simple explanation of contexts = and when they or their effects might be user visible. c.. Create an Application Developer Guidance Document=20 Discussion of how to create a policy snippet for an application. How = and when to use the additional system calls. How to use for assured = pipelines, etc. -------------------------------------------------------------------------= ------- Who is in charge of documentation, and what is the current status of = these documents. What format(s) are being used (plaintext, html, = latex)? What are the priorities -- their expected completion dates? Is = additional help still needed in this area? regards, Randal Hicks ------=_NextPart_000_0088_01C15D36.DC6358C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
While I have yet to install = SELinux, I=20 have spent considerable time pouring over all the material available = online=20 since first hearing of it on Slashdot. =20 I expect to have this accomplished by next week, or at least attempted = several=20 times <grin>.  What I have learned so far has excited me = quite a bit,=20 and I wish that my programming skills were up to par so that I could=20 contribute... but that is likely to be several years down the road (if=20 ever).  I feel that this is an important direction for Linux to = grow, and=20 commend the people who made the decision to bring this to the OpenSource = Community (and of course the people who have worked to bring it to its = current=20 state).
 
It occurs to me that I may = be able=20 to offer assistance in developing the documentation.  = This would=20 necessitate my full understanding of the product as it continues = to mature,=20 and provide me with a firm basis on which to contribute to the code = (should=20 I ever develop my skills to that level).  It would provide=20 focus.  Additionally, it could allow resources to be utilized more=20 effectively.  Based on the description of content, I am not sure = how I=20 could be of immediate use to the project--I expect that I would need = more time=20 playing with the software--but I wanted to express my willingness to = help as I=20 am able.
 
From the ToDo-page, I read = the=20 following:
 

Documentation Tasks

In general the SEL team only works on these = tasks to=20 the extent they are necessary to describe the system to other = researchers and=20 developers or as time is available.

  • Create an Administrator Guidance Document =

    Discuss the use of Flask controls in = various=20 environment (ISP, Desktop, Firewall, etc.)

  • Create a User Guidance Document

    What to expect as differences in SEL. = Simple=20 explanation of contexts and when they or their effects might be user = visible.

  • Create an Application Developer Guidance = Document=20

    Discussion of how to create a policy = snippet for an=20 application. How and when to use the additional system calls. How to = use for=20 assured pipelines, etc.


 
Who is in charge of = documentation,=20 and what is the current status of these documents.  What format(s) = are=20 being used (plaintext, html, latex)? What are the priorities -- their = expected=20 completion dates?  Is additional help still needed in this=20 area?
 
regards,
Randal = Hicks
------=_NextPart_000_0088_01C15D36.DC6358C0-- -- You have received this message because you are subscribed to the selinux 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.