Author: ihabunek
Date: Wed Dec 14 10:30:37 2011
New Revision: 1214144
URL: http://svn.apache.org/viewvc?rev=1214144&view=rev
Log:
Updated site pages on contributing and volunteerening.
Modified:
logging/log4php/trunk/src/site/apt/contributingpatches.apt
logging/log4php/trunk/src/site/apt/volunteering.apt
logging/log4php/trunk/src/site/site.vm
Modified: logging/log4php/trunk/src/site/apt/contributingpatches.apt
URL:
http://svn.apache.org/viewvc/logging/log4php/trunk/src/site/apt/contributingpatches.apt?rev=1214144&r1=1214143&r2=1214144&view=diff
==============================================================================
--- logging/log4php/trunk/src/site/apt/contributingpatches.apt (original)
+++ logging/log4php/trunk/src/site/apt/contributingpatches.apt Wed Dec 14
10:30:37 2011
@@ -18,13 +18,17 @@
------
------
-Contributing Patches to Apache log4php
+Contributing patches
Before you read this document, make sure you have read the general
information on the
{{{./volunteering.html}Volunteering}} page. Credits to the Apache Commons
project on which documents
this one is based on.
+
+ For guidelines on how to set up a development environment for Apache
log4php, there is a
+ {{{http://wiki.apache.org/logging-log4php/SettingUpALinuxEnvironment}
detailed guide}} on the
+ wiki pages.
-* Respect The Original Style
+* Respect the original style
Please respect the style of the orginal file. Make sure that your additions
fit in with that style.
The framework has coding conventions and every contribution is supposed to
adhere to them.
@@ -48,7 +52,7 @@ Contributing Patches to Apache log4php
* don't use _ in variablenames
-* Tabs Not Spaces
+* Tabs not spaces
PLEASE NO SPACES!
@@ -59,7 +63,7 @@ Contributing Patches to Apache log4php
will have to reformat it before it's applied or the patch will be rejected.
Again,
it's easier to get it right in the first place rather than have to reformat
and resubmit your patch.
-* Test Cases
+* Test cases
Classes needs to be tested with PHPUnit. If you are not familiar with the
principles
of regression testing, then the JUnit or even the PHPUnit site has some good
articles.
@@ -72,7 +76,7 @@ Contributing Patches to Apache log4php
of your contribution. Test cases ensure that bugs stay fixed and features
don't get broken.
Test cases will probably be needed anyway so submitting them saves time.
-* Creating A Patch
+* Creating a patch
The Apache log4php source code repository holds the current source.
Currently SVN is beeing used.
@@ -91,7 +95,7 @@ Contributing Patches to Apache log4php
Try to give your patch files meaningful names. This makes it easier for
developers who need to apply a number of different patches.
-* Submitting A Patch
+* S ubmitting a patch
There are two ways to go to submit a patch:
Modified: logging/log4php/trunk/src/site/apt/volunteering.apt
URL:
http://svn.apache.org/viewvc/logging/log4php/trunk/src/site/apt/volunteering.apt?rev=1214144&r1=1214143&r2=1214144&view=diff
==============================================================================
--- logging/log4php/trunk/src/site/apt/volunteering.apt (original)
+++ logging/log4php/trunk/src/site/apt/volunteering.apt Wed Dec 14 10:30:37 2011
@@ -20,28 +20,25 @@ Volunteering
On Volunteering
- If you want to volunteer and help with developing Apache log4php, you are
highly encouraged to read
- {{{http://www.apache.org/foundation/getinvolved.html}Apache getting
involved}}. If you have
+ If you want to volunteer and help with developing Apache log4php, you are
highly encouraged to
+ read {{{http://www.apache.org/foundation/getinvolved.html}Apache getting
involved}}. If you have
questions on that document, we might be able to answer them on the
developers mailinglist.
-
- Craig R. McClanahan posted an interesting mail to the Apache Commons
mailinglist. I modified
- the post to fit for log4php:
-
-
- The best way to contribute is to identify for yourself things that you
- think are broken, or could be improved, and then propose a patch. A
- couple of ways to identify possible candidates:
-
- * Have you used an API, and wished it would do something
- a little more? or a little different? In open source circles,
- people often get involved initially by "scratching your own itch"
- as the saying goes.
-
- * Have you called up the
{{{https://issues.apache.org/jira/browse/LOG4PHP}bug reports}}
- for the log4php project, and seen any bugs that you can create a
- patch for?
-
- * Have you checked your favorite package's {{{./roadmap.html}roadmap file}}
or
- {{{http://wiki.apache.org/logging/Log4PHP/TODO}todo files}}
- for things that have already been thought about, but just are
- not done yet?
+
+ The best way to contribute is to identify for yourself things that you think
are broken, or could
+ be improved, and then propose a patch. A couple of ways to identify
possible candidates:
+
+ * Have you used Apache log4php, and wished it would do something a little
more? or a little
+ different? In open source circles, people often get involved initially by
"scratching your
+ own itch" as the saying goes.
+
+ * Have a look at the {{{https://issues.apache.org/jira/browse/LOG4PHP}bug
reports}} for the
+ log4php project, and seen any bugs that you can create a patch for.
+
+ * Check out the project {{{http://wiki.apache.org/logging-log4php/TODO}todo
list}} for things that
+ have already been thought about, but just are not done yet.
+
+ * If you are apt at graphic design, Apache log4php is
+ {{{http://wiki.apache.org/logging-log4php/LogoProposals}looking for a
logo}}. Consider donating
+ one.
+
+ []
Modified: logging/log4php/trunk/src/site/site.vm
URL:
http://svn.apache.org/viewvc/logging/log4php/trunk/src/site/site.vm?rev=1214144&r1=1214143&r2=1214144&view=diff
==============================================================================
--- logging/log4php/trunk/src/site/site.vm (original)
+++ logging/log4php/trunk/src/site/site.vm Wed Dec 14 10:30:37 2011
@@ -10,7 +10,7 @@
#if ( $href.toLowerCase().startsWith("http:/") ||
$href.toLowerCase().startsWith("https:/") ||
$href.toLowerCase().startsWith("ftp:/") ||
$href.toLowerCase().startsWith("mailto:/";) ||
$href.toLowerCase().startsWith("file:/") ||
($href.toLowerCase().indexOf("://") != -1) )
- #set ( $linkClass = ' class="externalLink"' )
+ #set ( $linkClass = ' class="externalLink" target="_blank"' )
#if ( $linkTarget )
#else
