Author: lukaszlenart
Date: Wed Jan 22 10:45:07 2014
New Revision: 1560308
URL: http://svn.apache.org/r1560308
Log:
Add page titles
Modified:
struts/site/trunk/content/markdown/builds.md
struts/site/trunk/content/markdown/bylaws.md
struts/site/trunk/content/markdown/dev-mail.md
struts/site/trunk/content/markdown/git-for-struts.md
struts/site/trunk/content/markdown/releases.md
struts/site/trunk/content/markdown/volunteers.md
Modified: struts/site/trunk/content/markdown/builds.md
URL:
http://svn.apache.org/viewvc/struts/site/trunk/content/markdown/builds.md?rev=1560308&r1=1560307&r2=1560308&view=diff
==============================================================================
--- struts/site/trunk/content/markdown/builds.md (original)
+++ struts/site/trunk/content/markdown/builds.md Wed Jan 22 10:45:07 2014
@@ -1,6 +1,6 @@
-# Source Code
+<head><title>Source Code</title></head>
-## Source Code
+# Source Code
As a convenience to developers who are helping to create and maintain the
Apache Struts framework,
public access to the live source code repository is available. This is our
one-and-only development repository.
@@ -27,7 +27,7 @@ With the [Git client](http://git-scm.com
For more about using version control systems at Apache, see the ASF's
[Source Code Repositories](http://www.apache.org/dev/#version-control) page.
-## Building Apache Struts
+# Building Apache Struts
If you are building Apache Struts from source, we recommend that you install
and use
[Apache Maven 3.](http://maven.apache.org) During the build process, Maven
will automatically acquire
@@ -50,7 +50,7 @@ For more about using Maven to build Stru
For more about using Maven to build Struts 1, see our [Maven wiki
page.](http://wiki.apache.org/struts/StrutsMaintenanceMaven)
-## NightlyBuilds
+# NightlyBuilds
As part of our continuous integration practice, we also make available each
morning the
[latest stable development
build.](https://builds.apache.org/view/S-Z/view/Struts/job/Struts2-JDK6/lastStableBuild/org.apache.struts$struts2-assembly/)
@@ -63,7 +63,7 @@ If you do **not** plan to contribute to
NOTE: The Struts 2 nightly build is not fully operational. We suggest that
contributors checkout
the [source code](#SourceCode) instead.
-## Test Builds
+# Test Builds
As we prepare for a new release, the project group may create interim *test
builds*. When test builds are available,
we post them [here](http://people.apache.org/builds/struts/) in binary, source
and library distributions.
@@ -75,7 +75,7 @@ made the "Best Available" release. If th
as "Beta" release. When a test build is upgraded to "Beta" or "GA" by a vote
of the project members,
we make the distribution available as a formal [release.](downloads.html)
-## Maven Snapshots
+# Maven Snapshots
When a distribution is first made available, it is rated as a development
build or "snapshot". Later, the quality
of the distribution may be upgraded to "Beta" or "General Availability", based
on feedback from the community,
@@ -91,7 +91,7 @@ specify the ASF Snapshot repository in t
</repositories>
-## Licensing of Apache Struts Builds
+# Licensing of Apache Struts Builds
Apache Struts 2 source code and documentation is licensed to the Apache
Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file included in any
distribution for additional information
Modified: struts/site/trunk/content/markdown/bylaws.md
URL:
http://svn.apache.org/viewvc/struts/site/trunk/content/markdown/bylaws.md?rev=1560308&r1=1560307&r2=1560308&view=diff
==============================================================================
--- struts/site/trunk/content/markdown/bylaws.md (original)
+++ struts/site/trunk/content/markdown/bylaws.md Wed Jan 22 10:45:07 2014
@@ -1,6 +1,6 @@
-# Project Management Committee Charter
+<head><title>Project Management Committee Charter</title></head>
-## Apache Struts PMC Charter
+# Apache Struts PMC Charter
Struts is a Project of the [Apache Software
Foundation](http://apache.org/foundation) (ASF), formed by a resolution
of the [ASF Board of Directors](http://apache.org/foundation/board/). As an
ASF Project, Struts is subject to the
@@ -10,54 +10,54 @@ The Project Charter incorporates by refe
of [How the ASF works](http://apache.org/foundation/how-it-works.html, with
the additional guidelines
and clarifications found herein.
-## Roles and Responsibilities
+# Roles and Responsibilities
The roles and responsibilities that people can assume in the project are based
on merit.
Everybody can help no matter what their role. Those who have been long term or
valuable contributors to
the project can earn the right to commit directly to the source repository and
to cast binding votes during
the decision-making process.
-### Users.
+# Users.
Users are the people who use the products of the Project. People in this role
aren't contributing code,
but they are using the products, reporting bugs, making feature requests, and
such. This is by far
the most important category of people as, without users, there is no reason
for the Project.
When a user starts to contribute code or documentation patches, they become a
Contributor.
-### Contributors.
+# Contributors.
Contributors are the people who write code or documentation patches or
contribute positively to the project
in other ways. When a volunteer's patch is applied, the contribution is
recognized in the version control log.
-### Committers.
+# Committers.
Contributors who give frequent and valuable contributions to a subproject of
the Project can have their status
promoted to that of a "*Committer*" for that subproject. A Committer has write
access to the source code repository.
Committer status is granted by the Project Management Committee by majority
vote.
-### Project Management Committee (PMC).
+# Project Management Committee (PMC).
Committers and other volunteers who frequently participate with valuable
contributions may have their status promoted
to that of a "*Project Management Committee Member*". The PMC is responsible
for the day-to-day management
of the Project.
-## Management
+# Management
The Vice President is appointed by the ASF Board. The Vice President is
assisted by the Project Management Committee
(PMC) and also serves as the PMC chair. The PMC may nominate new members.
Nominees may then be approved
with a 3/4 majority vote of the PMC. Membership can be revoked by a unanimous
vote of all the active PMC members
other than the member in question. The list of active PMC members can be found
on our [Volunteers page](volunteers.html).
-## PMC Duties
+# PMC Duties
The PMC is responsible for the day-to-day management of the Struts Project.
The PMC oversees all changes
made to the codebase. The PMC must ensure that all code under a Apache Struts
repository is the lawful property
of the Foundation and may be distributed under the [Apache Software
License](http://apache.org/licenses/).
All releases of a Struts subproject must be sanctioned by the Project
Management Committee.
-## Subprojects
+# Subprojects
Subprojects are the Project's unit of release. Each subproject should
represent an implementation of a Struts framework
or a related component. Each subproject should focus on creating, maintaining,
and releasing a single software
@@ -72,13 +72,13 @@ identify the initial source from which t
repositories, if any, which are to be created. Creation of a new subproject
requires approval by a 3/4 majority
vote of the PMC.
-## Decision Making
+# Decision Making
All [Volunteers](http://apache.org/foundation/how-it-works.html#roles) (Users,
Developers, Committers, PMC Members)
are encouraged to participate in the decision-making process, but binding
decisions are made only
by the Project Management Committee.
-## Voting
+# Voting
Any subscriber to the list may
[vote](http://apache.org/foundation/voting.html) on any issue or action item.
Votes from Developers and Committers are especially welcome. However, the only
binding votes are those cast by a PMC
@@ -136,7 +136,7 @@ Voting represent consensus and votes are
to a +1 after discussion, and likewise a +1 may be converted to a -1. By
convention, Committers should allow a vote
to circulate for 72 hours before taking action.
-## Action Items
+# Action Items
All decisions revolve around "*Action Items*". Action Items consist of the
following:
- Long Term Plans
@@ -146,28 +146,28 @@ All decisions revolve around "*Action It
- Release Plan
- Release Grade
-### Long Term Plans
+## Long Term Plans
Long term plans are simply announcements that group members are working on
particular issues related to the Project.
These items are not voted on, but Committers and PMC Members who do not agree
with a particular plan, or think that
an alternative plan would be better, are obligated to inform the group of
their feelings.
-### Short Term Plan
+## Short Term Plan
Short term plans are announcements that a volunteer is working on a particular
set of documentation or code files
with the implication that other volunteers should avoid them or try to
coordinate their changes.
-### Product Changes
+## Product Changes
All product changes to the repository are subject to lazy consensus.
-### Showstoppers
+## Showstoppers
Showstoppers are issues that require a fix be in place before the next public
release. They are designated as "blockers"
in the issue tracker in order to focus special attention on these problems. An
issue becomes a showstopper when it is
designated as such in the issue tracker by a PMC member and remains so by lazy
consensus.
-### Release Plan
+## Release Plan
A release plan must be used to keep all volunteers aware of when a release is
desired, whether it will be a major,
minor, or milestone release, who will be the release manager, when the
repository will be tagged to create
@@ -176,7 +176,7 @@ plan must be incorporated into the produ
Lazy majority decides each issue in a release plan.
-### Release Grade
+## Release Grade
After a proposed release is built, it must be tested and classified before
being released to the general public.
The proposed release may be assigned "Alpha", "Beta" or "General Availability"
classifications by majority vote.
@@ -184,7 +184,7 @@ Once a release is classified by the PMC
Distributions may be reclassified or withdrawn by majority vote, but the
release number may not be reused by another distribution.
-## Sandbox
+# Sandbox
Pursuant to the ["Rules for
Revolutionaries"](http://incubator.apache.org/learn/rules-for-revolutionaries.html),
any committer may submit experimental material to the Sandbox area of the
repository at his or her own discretion.
Modified: struts/site/trunk/content/markdown/dev-mail.md
URL:
http://svn.apache.org/viewvc/struts/site/trunk/content/markdown/dev-mail.md?rev=1560308&r1=1560307&r2=1560308&view=diff
==============================================================================
--- struts/site/trunk/content/markdown/dev-mail.md (original)
+++ struts/site/trunk/content/markdown/dev-mail.md Wed Jan 22 10:45:07 2014
@@ -1,6 +1,6 @@
-# Dev Mailing List
+<head><title>Dev Mailing List</title></head>
-## Development Lists
+# Development Lists
The following mailing lists are meant for people who want to contribute to
Struts itself. Patches, Documentation
improvements and discussion on future Struts are welcome. **For questions on
using Struts, please subscribe to the
@@ -36,7 +36,7 @@ Please make sure you have read the guide
</table>
-## Archives
+# Archives
You can read the [ASF
Mail](http://mail-archives.apache.org/mod_mbox/struts-dev/) or the
[Mark Mail](http://markmail.org/list/org.apache.struts.dev/) archives if you
are looking for older discussions.
Modified: struts/site/trunk/content/markdown/git-for-struts.md
URL:
http://svn.apache.org/viewvc/struts/site/trunk/content/markdown/git-for-struts.md?rev=1560308&r1=1560307&r2=1560308&view=diff
==============================================================================
--- struts/site/trunk/content/markdown/git-for-struts.md (original)
+++ struts/site/trunk/content/markdown/git-for-struts.md Wed Jan 22 10:45:07
2014
@@ -1,3 +1,5 @@
+<head><title>Git for Struts</title></head>
+
# Using Git with Struts
So far, Struts 2 is using SVN. There are plans to move on to GIT but
Modified: struts/site/trunk/content/markdown/releases.md
URL:
http://svn.apache.org/viewvc/struts/site/trunk/content/markdown/releases.md?rev=1560308&r1=1560307&r2=1560308&view=diff
==============================================================================
--- struts/site/trunk/content/markdown/releases.md (original)
+++ struts/site/trunk/content/markdown/releases.md Wed Jan 22 10:45:07 2014
@@ -1,12 +1,12 @@
-# Release Guidelines
+<head><title>Release Guidelines</title></head>
-## Release Guidelines
+# Release Guidelines
This document describes the Apache Struts release process and our [coding
conventions](#Coding),
which are applicable to all subprojects. Both stable and development releases
are
[available for download.](downloads.html)
-## Release Process
+# Release Process
A [point release](http://commons.apache.org/releases/versioning.html) should
be made before and after
any product change that is not a "fully-compatible change" (see link). This
includes moving a dependency from
@@ -60,13 +60,13 @@ Additional remarks:
- If a serious flaw if found in a test build or release, it may be withdrawn
by a majority vote of the PMC and
removed from ASF distribution channels.
-## Coding Conventions and Guidelines
+# Coding Conventions and Guidelines
Source code and documentation contributed to the Struts repositories should
observe the:
- The ["Code Conventions for the Java Programming
Language"](http://www.oracle.com/technetwork/java/codeconvtoc-136057.html),
as published by Oracle.
-### Clarifications
+# Clarifications
- First, "Observe the style of the original". Resist the temptation to make
stylistic changes for their own
sake. But, if you must reformat code, commit style changes separately from
code changes. Either change
the style, commit, and then change the code, or vice-versa.
Modified: struts/site/trunk/content/markdown/volunteers.md
URL:
http://svn.apache.org/viewvc/struts/site/trunk/content/markdown/volunteers.md?rev=1560308&r1=1560307&r2=1560308&view=diff
==============================================================================
--- struts/site/trunk/content/markdown/volunteers.md (original)
+++ struts/site/trunk/content/markdown/volunteers.md Wed Jan 22 10:45:07 2014
@@ -1,6 +1,4 @@
-<head>
-<title>Volunteers</title>
-</head>
+<head><title>Volunteers</title></head>
# Volunteers
