Return-Path:
+
+The primary mechanism for Derby communication is
+the Derby mail lists.
+Anyone can participate, no matter what their time zone. The ASF
+maintains a reliable searchable archive of past discussions. Oversight
+is enabled. Many eyes ensures that the project evolves in a consistent
+direction.
+The main channel for development is the "derby-dev" mailing list, and the
+main channel for user support is the "derby-user" mailing list.
+As is usual with mailing lists, be prepared to wait for an answer.
+
+The Derby community also maintains an IRC channel on the freenode IRC
+network. You are welcome to stop by:
+ /server irc.freenode.org
+/join #derby
+
+However, keep in mind that all decisions occur on the Derby mail lists
+and not on IRC. Please summarize any off-list knowledge gained and post
+it for the benefit of all. For example, if a user asks a question and
+gets a response, post that exchange to derby-user. If developers work
+out a strategy for solving a problem, post a summary to derby-dev,
+including alternatives that were considered but ultimately dismissed and
+why. If developers figure out how something works, post a summary of the
+finding to derby-dev.
+
+In all cases, additional eyes can catch any errors, point out any
+subtleties, and fill in additional information. The more discussions are
+on-list, the more the rest of the community will benefit from the
+understanding that is developed.
+Contribute Code or Documentation
+
+Communication Channels
If you would like to participate directly in Derby development, here are a few guidelines: @@ -183,35 +221,37 @@ -
+Additional information for contributors is on the +Derby Wiki. Below +is just a sampling of the topics covered: +
+- -Use 'svn diff' for patches, not 'cvs diff' - -
--The Apache DB Project recommends using -cvs diff -output for creating patches, -but Derby uses svn, -so use 'svn diff' instead. +The remainder of this section includes some miscellaneous tips that don't +seem to have made it onto the Wiki (yet).
@@ -297,8 +337,7 @@
-Post the patch to the derby-dev mail list -or attach it to the Jira issue. +Attach the patch to the Jira issue.
@@ -390,7 +429,7 @@-Last updated: July 31, 2005 +Last updated: March 3, 2006
Modified: db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml?rev=382967&r1=382966&r2=382967&view=diff ============================================================================== --- db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml (original) +++ db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml Fri Mar 3 15:35:47 2006 @@ -26,7 +26,7 @@ Subscribe to the Derby mail lists.+The primary mechanism for Derby communication is +the Derby mail lists. +Anyone can participate, no matter what their time zone. The ASF +maintains a reliable searchable archive of past discussions. Oversight +is enabled. Many eyes ensures that the project evolves in a consistent +direction. +The main channel for development is the "derby-dev" mailing list, and the +main channel for user support is the "derby-user" mailing list. +As is usual with mailing lists, be prepared to wait for an answer. +
++The Derby community also maintains an IRC channel on the freenode IRC +network. You are welcome to stop by: +
+ +/server irc.freenode.org +/join #derby +
+ ++However, keep in mind that all decisions occur on the Derby mail lists +and not on IRC. Please summarize any off-list knowledge gained and post +it for the benefit of all. For example, if a user asks a question and +gets a response, post that exchange to derby-user. If developers work +out a strategy for solving a problem, post a summary to derby-dev, +including alternatives that were considered but ultimately dismissed and +why. If developers figure out how something works, post a summary of the +finding to derby-dev. +
+ ++In all cases, additional eyes can catch any errors, point out any +subtleties, and fill in additional information. The more discussions are +on-list, the more the rest of the community will benefit from the +understanding that is developed. +
+ +-Guidelines -
If you would like to participate directly in Derby development, here are a few guidelines: @@ -69,32 +109,32 @@ Way.
-Use 'svn diff' for patches, not 'cvs diff' -
++Additional information for contributors is on the +Derby Wiki. Below +is just a sampling of the topics covered: +
+ +
-The Apache DB Project recommends using
-cvs diff
-output for creating patches,
-but Derby uses svn
,
-so use 'svn diff
' instead.
+The remainder of this section includes some miscellaneous tips that don't
+seem to have made it onto the Wiki (yet).
@@ -161,8 +201,7 @@
-Post the patch to the derby-dev mail list -or attach it to the Jira issue. +Attach the patch to the Jira issue.
@@ -249,7 +288,7 @@
-Last updated: July 31, 2005 +Last updated: March 3, 2006