You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@struts.apache.org by lu...@apache.org on 2017/09/19 06:32:39 UTC
[1/3] struts-site git commit: Fixes links in TOC of "How To Help FAQ"
page
Repository: struts-site
Updated Branches:
refs/heads/master 6f3601646 -> beef7d4f2
Fixes links in TOC of "How To Help FAQ" page
Project: http://git-wip-us.apache.org/repos/asf/struts-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/struts-site/commit/b508ae1c
Tree: http://git-wip-us.apache.org/repos/asf/struts-site/tree/b508ae1c
Diff: http://git-wip-us.apache.org/repos/asf/struts-site/diff/b508ae1c
Branch: refs/heads/master
Commit: b508ae1c1ef673e356f6a50abe40db2a63ea6375
Parents: 792955c
Author: Yasser Zamani <ya...@live.com>
Authored: Fri Sep 15 23:35:07 2017 +0430
Committer: Yasser Zamani <ya...@live.com>
Committed: Fri Sep 15 23:35:07 2017 +0430
----------------------------------------------------------------------
source/helping.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/struts-site/blob/b508ae1c/source/helping.md
----------------------------------------------------------------------
diff --git a/source/helping.md b/source/helping.md
index 806a2eb..db8aaae 100644
--- a/source/helping.md
+++ b/source/helping.md
@@ -35,7 +35,7 @@ title: Helping
We don't sell Struts for money, but anyone who wants to be our customer can pay us back by donating
the time and energy that money represents.
- - ### <a class="anchor" name="patches"></a>How do I create a patch?
+ - ### How do I create a patch?<a class="anchor" name="patches"></a>
A patch is a machine-readable script that can automatically recreate a change to a text file,
including source code and documentation. The patch format is also human-readable. Developers often pass
@@ -65,7 +65,7 @@ title: Helping
The [NetBeans community](http://www.netbeans.org/community/contribute/patches.html) also has a helpful section on the
subject of creating patches.
- - ### <a class="anchor" name="issues"></a>How can I report defects or suggest features?
+ - ### How can I report defects or suggest features?<a class="anchor" name="issues"></a>
Tracking of defect reports and enhancement suggestions for Apache Struts products is handled through the
[Apache Struts JIRA instance](https://issues.apache.org/jira/browse/WW).
@@ -88,7 +88,7 @@ title: Helping
Feature suggestions are also maintained in the [JIRA issue tracker](https://issues.apache.org/jira/browse/WW).
- - ### <a class="anchor" name="contribute"></a>How can I contribute to the Struts source code?
+ - ### How can I contribute to the Struts source code?<a class="anchor" name="contribute"></a>
A very good place to start is by **reviewing the list of open issues** and pending feature suggestions in the
[issue tracker](#issues).
@@ -111,7 +111,7 @@ title: Helping
You can try to fake what a JSP container does, but a much more reliable testing regime would actually execute
the tag in a real container.
- - ### <a class="anchor" name="documentation"></a>How can I contribute to the documentation?
+ - ### How can I contribute to the documentation?<a class="anchor" name="documentation"></a>
The Struts 2 documentation is maintained using the Atlassian Confluence wiki software and automatically
exported to HTML for viewing on the website. To help with the Struts 2 documentation, you must create
@@ -126,7 +126,7 @@ title: Helping
in relation to the rest of the documentation.
Again, someone has to figure that out before it can be added, and that someone might as well be you.
- - ### <a class="anchor" name="release"></a>So when is the next release coming out?
+ - ### So when is the next release coming out?<a class="anchor" name="release"></a>
Here is the truth regarding releases:
@@ -158,7 +158,7 @@ title: Helping
and keep an eye on what is coming down the pipeline.
This way you are at least forewarned and forearmed.
- - ### <a class="anchor" name="release_help"></a>What can I do to help the next release along?
+ - ### What can I do to help the next release along?<a class="anchor" name="release_help"></a>
- Most importantly, download the latest [nightly build](builds.html#NightlyBuilds) or development release
and test it against your own applications. Report any and all issues or suspected issues to
@@ -192,7 +192,7 @@ title: Helping
If Developers are supporting each other on the lists, the Committers have more time to spend on the next
release.
- - ### <a class="anchor" name="decides_help"></a>How can I help make the decisions?
+ - ### How can I help make the decisions?<a class="anchor" name="decides_help"></a>
A guiding principle of the Apache Software Foundation is "them that do the work, make the decisions".
This phrase is actually a double-entendre. A project will make some decisions by voting (very few),
[3/3] struts-site git commit: Fixes links in TOC of "How To Help FAQ"
page
Posted by lu...@apache.org.
Fixes links in TOC of "How To Help FAQ" page
Project: http://git-wip-us.apache.org/repos/asf/struts-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/struts-site/commit/beef7d4f
Tree: http://git-wip-us.apache.org/repos/asf/struts-site/tree/beef7d4f
Diff: http://git-wip-us.apache.org/repos/asf/struts-site/diff/beef7d4f
Branch: refs/heads/master
Commit: beef7d4f232858dcaa59dfb3fd2e66751f2ccb70
Parents: 6f36016 a5d35dc
Author: Lukasz Lenart <lu...@apache.org>
Authored: Tue Sep 19 08:32:15 2017 +0200
Committer: Lukasz Lenart <lu...@apache.org>
Committed: Tue Sep 19 08:32:15 2017 +0200
----------------------------------------------------------------------
source/helping.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------
[2/3] struts-site git commit: Removes waste anchors in "How To Help
FAQ" page
Posted by lu...@apache.org.
Removes waste anchors in "How To Help FAQ" page
Project: http://git-wip-us.apache.org/repos/asf/struts-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/struts-site/commit/a5d35dc2
Tree: http://git-wip-us.apache.org/repos/asf/struts-site/tree/a5d35dc2
Diff: http://git-wip-us.apache.org/repos/asf/struts-site/diff/a5d35dc2
Branch: refs/heads/master
Commit: a5d35dc2dc1e069a83f0acb4540dbcb7f51c91f3
Parents: b508ae1
Author: Yasser Zamani <ya...@live.com>
Authored: Sat Sep 16 14:14:43 2017 +0430
Committer: Yasser Zamani <ya...@live.com>
Committed: Sat Sep 16 14:14:43 2017 +0430
----------------------------------------------------------------------
source/helping.md | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/struts-site/blob/a5d35dc2/source/helping.md
----------------------------------------------------------------------
diff --git a/source/helping.md b/source/helping.md
index db8aaae..4f25cf0 100644
--- a/source/helping.md
+++ b/source/helping.md
@@ -35,7 +35,7 @@ title: Helping
We don't sell Struts for money, but anyone who wants to be our customer can pay us back by donating
the time and energy that money represents.
- - ### How do I create a patch?<a class="anchor" name="patches"></a>
+ - ### How do I create a patch?
A patch is a machine-readable script that can automatically recreate a change to a text file,
including source code and documentation. The patch format is also human-readable. Developers often pass
@@ -65,7 +65,7 @@ title: Helping
The [NetBeans community](http://www.netbeans.org/community/contribute/patches.html) also has a helpful section on the
subject of creating patches.
- - ### How can I report defects or suggest features?<a class="anchor" name="issues"></a>
+ - ### How can I report defects or suggest features?
Tracking of defect reports and enhancement suggestions for Apache Struts products is handled through the
[Apache Struts JIRA instance](https://issues.apache.org/jira/browse/WW).
@@ -88,7 +88,7 @@ title: Helping
Feature suggestions are also maintained in the [JIRA issue tracker](https://issues.apache.org/jira/browse/WW).
- - ### How can I contribute to the Struts source code?<a class="anchor" name="contribute"></a>
+ - ### How can I contribute to the Struts source code?
A very good place to start is by **reviewing the list of open issues** and pending feature suggestions in the
[issue tracker](#issues).
@@ -111,7 +111,7 @@ title: Helping
You can try to fake what a JSP container does, but a much more reliable testing regime would actually execute
the tag in a real container.
- - ### How can I contribute to the documentation?<a class="anchor" name="documentation"></a>
+ - ### How can I contribute to the documentation?
The Struts 2 documentation is maintained using the Atlassian Confluence wiki software and automatically
exported to HTML for viewing on the website. To help with the Struts 2 documentation, you must create
@@ -126,7 +126,7 @@ title: Helping
in relation to the rest of the documentation.
Again, someone has to figure that out before it can be added, and that someone might as well be you.
- - ### So when is the next release coming out?<a class="anchor" name="release"></a>
+ - ### So when is the next release coming out?
Here is the truth regarding releases:
@@ -158,7 +158,7 @@ title: Helping
and keep an eye on what is coming down the pipeline.
This way you are at least forewarned and forearmed.
- - ### What can I do to help the next release along?<a class="anchor" name="release_help"></a>
+ - ### What can I do to help the next release along?
- Most importantly, download the latest [nightly build](builds.html#NightlyBuilds) or development release
and test it against your own applications. Report any and all issues or suspected issues to
@@ -192,7 +192,7 @@ title: Helping
If Developers are supporting each other on the lists, the Committers have more time to spend on the next
release.
- - ### How can I help make the decisions?<a class="anchor" name="decides_help"></a>
+ - ### How can I help make the decisions?
A guiding principle of the Apache Software Foundation is "them that do the work, make the decisions".
This phrase is actually a double-entendre. A project will make some decisions by voting (very few),