Why the binindex.html page is not accesible from the general menu (on the left of each page ?)
Michael
Ceki G�lc� wrote:
Hi All,
I am reproducing this message as the original CVS commit message failed to get through.
Modified Files: docs/site/bylaws.html src/xdocs/site/bylaws.xml
----------------------------------------------------------------------
Corrected the hideous error on the bylaws page where most of the page would
be shown as if it were a URL link.
This is due to a bug whereby velocity shortens elements with an empty body.
For example, the anchor <a name="x"></a> was tranformed into <a name="x"/>.
This confuses most browsers and even kills IE.
----------------------------------------------------------------------
Index: site/bylaws.xml =================================================================== RCS file: /home/cvs/logging-site/src/xdocs/site/bylaws.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- site/bylaws.xml 22 Dec 2003 17:41:24 -0000 1.4 +++ site/bylaws.xml 17 Apr 2004 11:31:59 -0000 1.5 @@ -35,12 +35,10 @@
<ul>
<li><a href="#Roles and Responsibilities">Roles and Responsibilities</a></li>
- <li><a href="#Decision Making">How decisions are made</a></li>
+ <li><a href="#Decision Making">How decisions are made</a></li>
</ul>
- <h2><a name="Roles and Responsibilities"></a>
- Roles and Responsibilities
- </h2>
+ <h2>Roles and Responsibilities<a name="Roles and Responsibilities"> </a></h2>
<p>Apache projects define a set of roles with associated rights and responsibilities. These roles govern what tasks an @@ -57,10 +55,7 @@ </li> </ul>
- <h3 class="subsection"> - <a name="Users"></a> - Users - </h3> + <h3 class="subsection">Users<a name="Users"> </a></h3>
<p>The most important participants in the project are people who use our software. The majority of our developers start out as @@ -75,10 +70,9 @@ support forums. </p>
- <h3 class="subsection">
- <a name="Developers"></a>
- Developers
- </h3>
+
+ <h3 class="subsection">Developers<a name="Developers"> </a></h3>
+
<p>All of the volunteers who are contributing time, code,
documentation, or resources to the Logging Services Project. A developer that
@@ -87,7 +81,7 @@
invitations depends on many factors.
</p>
- <h3 class="subsection"><a name="Committers"></a>Committers</h3>
+ <h3 class="subsection">Committers<a name="Committers"> </a></h3>
<p>The project's Committers are responsible for the project's technical management. All committers have write access to the @@ -122,9 +116,9 @@ etc. </p>
- <h3 class="subsection"><a name="Project Management Committee"></a>Project Management Committee
- </h3>
-
+ <h3 class="subsection">Project Management Committee
+ <a name="Project Management Committee"> </a></h3>
+
<p>The Project Management Committee (PMC) for Apache Logging Services was
created by a <a href="mission.html">resolution</a> of the board
of the Apache Software Foundation on 18<sup>th</sup> November
@@ -172,17 +166,19 @@
responsibility who it chooses to appoint as the PMC chair.
</p>
- <h3 class="section"><a name="Decision Making"></a>Decision Making</h3>
+ <h3 class="section">Decision Making
+ <a name="Decision Making"> </a>
+ </h3>
- <p>Within the Logging Services project, different types of decisions require
- different forms of approval. For example, the <a href="#Roles and
- Responsibilities">previous section</a> describes several
- decisions which require "lazy consensus" approval. This section
- defines how voting is performed, the types of approvals, and
- which types of decision require which type of approval.
+ <p>Within the Logging Services project, different types of
+ decisions require different forms of approval. For example, the
+ previous section describes several decisions which require
+ "lazy consensus" approval. This section defines how voting is
+ performed, the types of approvals, and which types of decision
+ require which type of approval.
</p>
- <h3 class="subsection"><a name="Voting"></a>Voting</h3> + <h3 class="subsection">Voting<a name="Voting"> </a></h3>
<p>Decisions regarding the project are made by votes on the primary project mailing list ([EMAIL PROTECTED]). Where @@ -239,7 +235,7 @@ codebase. These typically take the form of a veto (-1) in reply to the commit message sent when the commit is made.</p>
- <h3><a name="Approvals"></a>Approvals </h3> + <h3>Approvals<a name="Approvals"> </a></h3>
<p>These are the types of approvals that can be sought. Different actions require different types of approvals</p> @@ -284,8 +280,8 @@ </tr> </table>
- <h3><a name="Vetoes"></a>Vetoes</h3> - + <h3>Vetoes<a name="Vetoes"> </a></h3> + <p>A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a valid reason explaining the reasons for the veto. The validity of a veto, if challenged, can be confirmed @@ -298,7 +294,7 @@ withdrawn, the action that has been vetoed must be reversed in a timely manner.</p>
- <h3><a name="Actions"></a>Actions</h3> + <h3>Actions<a name="Actions"> </a></h3>
<p>This section describes the various actions which are undertaken within the project, the corresponding approval required for that @@ -408,7 +404,7 @@ </table>
- <h3><a name="Voting Timeframes"></a>Voting Timeframes</h3> + <h3>Voting Timeframes<a name="Voting Timeframes"> </a></h3>
<p>Votes are open for a period of 72 hours to allow all active voters time to consider the vote. Votes relating to code changes are
