Return-Path: Delivered-To: apmail-db-derby-commits-archive@www.apache.org Received: (qmail 15937 invoked from network); 3 Mar 2006 23:36:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Mar 2006 23:36:12 -0000 Received: (qmail 35181 invoked by uid 500); 3 Mar 2006 23:36:58 -0000 Delivered-To: apmail-db-derby-commits-archive@db.apache.org Received: (qmail 35119 invoked by uid 500); 3 Mar 2006 23:36:58 -0000 Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Derby Development" List-Id: Delivered-To: mailing list derby-commits@db.apache.org Received: (qmail 35108 invoked by uid 99); 3 Mar 2006 23:36:58 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2006 15:36:58 -0800 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 03 Mar 2006 15:36:57 -0800 Received: (qmail 15857 invoked by uid 65534); 3 Mar 2006 23:35:50 -0000 Message-ID: <20060303233549.15856.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r382967 - in /db/derby/site/trunk: build/site/derby_comm.html src/documentation/content/xdocs/derby_comm.xml Date: Fri, 03 Mar 2006 23:35:49 -0000 To: derby-commits@db.apache.org From: jta@apache.org X-Mailer: svnmailer-1.0.7 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: jta Date: Fri Mar 3 15:35:47 2006 New Revision: 382967 URL: http://svn.apache.org/viewcvs?rev=382967&view=rev Log: Modified the "Apache Derby: Get Involved!" page: (1) Updated references since graduation into the DB Project (2) Added "Communication Channels" subsection based on thread that started at http://mail-archives.apache.org/mod_mbox/db-derby-dev/200602.mbox/%3c43FF5559.5020305@bristowhill.com%3e (3) Added Derby Wiki links for new developers Modified: db/derby/site/trunk/build/site/derby_comm.html db/derby/site/trunk/src/documentation/content/xdocs/derby_comm.xml Modified: db/derby/site/trunk/build/site/derby_comm.html URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/build/site/derby_comm.html?rev=382967&r1=382966&r2=382967&view=diff ============================================================================== --- db/derby/site/trunk/build/site/derby_comm.html (original) +++ db/derby/site/trunk/build/site/derby_comm.html Fri Mar 3 15:35:47 2006 @@ -107,6 +107,9 @@ Provide Feedback
  • +Communication Channels +
  • +
  • Contribute Code or Documentation
  • @@ -134,7 +137,7 @@
  • - Participate in the Derby Wiki. + Add your wisdom to the Derby Wiki.
  • @@ -162,14 +165,49 @@ - -

    Contribute Code or Documentation

    + +

    Communication Channels

    -

    +

    +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 -

    + +

    Contribute Code or Documentation

    +

    If you would like to participate directly in Derby development, here are a few guidelines: @@ -183,35 +221,37 @@ -

  • The Derby community - voted to follow - the guidelines established by the +
  • Derby follows the guidelines established by the Apache DB Project.
  • - + + +

    +Additional information for contributors is on the +Derby Wiki. Below +is just a sampling of the topics covered: +

    +
      +
    • - Changes to how Derby follows the Apache DB Project guidelines may - be called for and voted on using the - derby-dev mail list. -
    • - +For New + Developers: Information to get started with Derby development. + +
    • - This page will maintain a list of how the Derby process differs from the - Apache DB Project process. -
    • + +Derby + Contributor Checklist: Tips for developers contributing code to Derby. + + +
    • +Derby + Commit Process: How a change to Derby actually gets committed.

    - -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.
  • - Participate in the Derby Wiki. + Add your wisdom to the Derby Wiki.
  • @@ -52,11 +52,51 @@
    +Communication Channels + +

    +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 -

    -Guidelines -

    If you would like to participate directly in Derby development, here are a few guidelines: @@ -69,32 +109,32 @@ Way.

  • -
  • The Derby community - voted to follow - the guidelines established by the +
  • Derby follows the guidelines established by the Apache DB Project.
  • -
  • - Changes to how Derby follows the Apache DB Project guidelines may - be called for and voted on using the - derby-dev mail list. -
  • -
  • - This page will maintain a list of how the Derby process differs from the - Apache DB Project process. -
  • -

    -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