Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
A policy document using RTC should not contain commented out content. This change is not semantically significant.
Index: site-author/incubation/Incubation_Policy.xml
===================================================================
— site-author/incubation/Incubation_Policy.xml (revision 423542)
+++ site-author/incubation/Incubation_Policy.xml (working copy)
@@ -13,26 +13,6 @@
<link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"/>
</properties>
<body>
- <!-- TODO: decision making process
- <section id="How+we+make+decisions+on+our+incubation+policies">
- <title>How we make decision on our incubation policies
-</title> - <p>Apache projects usually make releases, and have deliverables. The
-code they put in is managed through lazy consensus and voting only
-when it's deemed to be required or requested.
-</p> - <p>Incubator releases are basically Incubated Projects' release to the
-Sponsor PMC. So how incubation is done is our "code".
-</p> - <p>Hence there is no need to "ratify" such rules if there seems to be
-consensus, as it's much easier to manage.
-</p> - <p>Because of this, we do not have the "draft" status on our policy docs
-and simply use them as our guide, that will change in need without
-having to go through tedious votes when there is good consensus.
-</p> - </section>
- -->
<section id="TOC">
<title>Incubation Policy: Table of Contents</title>