From: "Sven Vermeulen" <sven.vermeulen@siphos.be>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-docs:master commit in: html/selinux/
Date: Tue, 24 May 2011 20:42:46 +0000 (UTC) [thread overview]
Message-ID: <6e189ac24974b13132afa3cf89a6226b5d0028bd.SwifT@gentoo> (raw)
commit: 6e189ac24974b13132afa3cf89a6226b5d0028bd
Author: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
AuthorDate: Tue May 24 20:38:20 2011 +0000
Commit: Sven Vermeulen <sven.vermeulen <AT> siphos <DOT> be>
CommitDate: Tue May 24 20:38:20 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/hardened-docs.git;a=commit;h=6e189ac2
Update previews
---
html/selinux/index.html | 62 ++++++----------------------------------------
1 files changed, 8 insertions(+), 54 deletions(-)
diff --git a/html/selinux/index.html b/html/selinux/index.html
index 1cd3b3f..ed9d56a 100644
--- a/html/selinux/index.html
+++ b/html/selinux/index.html
@@ -26,8 +26,7 @@
<option value="#doc_chap4">4. Contributors</option>
<option value="#doc_chap5">5. Subprojects</option>
<option value="#doc_chap6">6. Resources</option>
-<option value="#doc_chap7">7. Roadmap</option>
-<option value="#doc_chap8">8. I Want to Participate</option></select>
+<option value="#doc_chap7">7. I Want to Participate</option></select>
</form>
<p class="chaphead"><a name="doc_chap1"></a><span class="chapnum">1.
</span>Project Description</p>
@@ -182,59 +181,14 @@ Develop and maintain SELinux documentation specific to the Gentoo distribution
<li>
<a href="selinux-policy.html">Gentoo Hardened SELinux Development Policy</a>
</li>
+ <li>
+ <a href="roadmap.html">Gentoo Hardened Roadmap (incl. SELinux development)</a>
+ </li>
+ <li>
+ <a href="support-state.html">Gentoo Hardened Support Matrices (incl. SELinux)</a>
+ </li>
</ul>
<p class="chaphead"><a name="doc_chap7"></a><span class="chapnum">7.
- </span>Roadmap</p>
-<p>
-The following table depics the roadmap we have in mind for the Gentoo Hardened
-SELinux project:
-</p>
-<table class="ntable">
-<tr>
- <td class="infohead"><b>Milestone</b></td>
- <td class="infohead"><b>Progress</b></td>
-
- <td class="infohead"><b>Description</b></td>
- <td class="infohead"><b>ETA</b></td>
-</tr>
-<tr>
- <td class="tableinfo">Userland stabilization</td>
- <td class="tableinfo"><span class="code-keyword">on track</span></td>
- <td class="tableinfo">
- Stabilize the SELinux userland utilities currently available in ~arch.
- These utilities (and libraries) are needed to cover recent SELinux policies
- and improve user experience within Gentoo Hardened SELinux
- </td>
- <td class="tableinfo">
- 2011-05-24
- </td>
-</tr>
-<tr>
- <td class="tableinfo">Policy stabilization</td>
- <td class="tableinfo"><span class="code-keyword">on track</span></td>
- <td class="tableinfo">
- Stabilize the SELinux policies based on upstream 2.20101213. The current
- stable policies are not compatible with the current Gentoo stable state
- (such as openrc support, networking/wireless and more.)
- </td>
- <td class="tableinfo">
- 2011-06-07
- </td>
-</tr>
-<tr>
- <td class="tableinfo">Profile stabilization</td>
- <td class="tableinfo"><span class="code-keyword">on track</span></td>
- <td class="tableinfo">
- Stabilize the restructured Gentoo SELinux profiles. The existing profiles
- have proved to be a bit more daunting to manage whereas the new profiles are
- made to be flexible yet simple to maintain.
- </td>
- <td class="tableinfo">
- 2011-06-28
- </td>
-</tr>
-</table>
-<p class="chaphead"><a name="doc_chap8"></a><span class="chapnum">8.
</span>I Want to Participate</p>
<p>
To participate in the SELinux project first join the mailing list at
@@ -248,7 +202,7 @@ contributing work we will always need testers to use and audit the SELinux
policies. All development, testing, feedback, and productive comments will
be greatly appreciated.
</p>
-<p class="secthead"><a name="doc_chap8_sect2">Policy Submissions</a></p>
+<p class="secthead"><a name="doc_chap7_sect2">Policy Submissions</a></p>
<p>
The critical component of a SELinux system is having a strong policy. The
team does its best to support as many daemons as possible. However, we cannot
next reply other threads:[~2011-05-24 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 20:42 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-07 19:26 [gentoo-commits] proj/hardened-docs:master commit in: html/selinux/ Sven Vermeulen
2011-06-02 12:02 Sven Vermeulen
2011-05-31 20:28 Sven Vermeulen
2011-04-10 7:49 Sven Vermeulen
2011-02-19 17:01 Francisco Blas Izquierdo Riera
2011-02-19 3:21 Francisco Blas Izquierdo Riera
2011-02-19 3:12 Francisco Blas Izquierdo Riera
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=6e189ac24974b13132afa3cf89a6226b5d0028bd.SwifT@gentoo \
--to=sven.vermeulen@siphos.be \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox