Return-Path: Delivered-To: apmail-forrest-svn-archive@www.apache.org Received: (qmail 65268 invoked from network); 10 Sep 2005 05:18:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Sep 2005 05:18:37 -0000 Received: (qmail 46869 invoked by uid 500); 10 Sep 2005 05:18:37 -0000 Delivered-To: apmail-forrest-svn-archive@forrest.apache.org Received: (qmail 46823 invoked by uid 500); 10 Sep 2005 05:18:36 -0000 Mailing-List: contact svn-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Forrest Developers List" List-Id: Delivered-To: mailing list svn@forrest.apache.org Received: (qmail 46810 invoked by uid 99); 10 Sep 2005 05:18:36 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Sep 2005 22:18:36 -0700 X-ASF-Spam-Status: No, hits=-9.8 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, 09 Sep 2005 22:18:47 -0700 Received: (qmail 65212 invoked by uid 65534); 10 Sep 2005 05:18:34 -0000 Message-ID: <20050910051834.65211.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r279951 - in /forrest/trunk/site-author/content/xdocs: events.xml forrest-tuesday.xml Date: Sat, 10 Sep 2005 05:18:33 -0000 To: svn@forrest.apache.org From: crossley@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: crossley Date: Fri Sep 9 22:18:30 2005 New Revision: 279951 URL: http://svn.apache.org/viewcvs?rev=279951&view=rev Log: Update with some lessons learned. Prepare for the next. Modified: forrest/trunk/site-author/content/xdocs/events.xml forrest/trunk/site-author/content/xdocs/forrest-tuesday.xml Modified: forrest/trunk/site-author/content/xdocs/events.xml URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/events.xml?rev=279951&r1=279950&r2=279951&view=diff ============================================================================== --- forrest/trunk/site-author/content/xdocs/events.xml (original) +++ forrest/trunk/site-author/content/xdocs/events.xml Fri Sep 9 22:18:30 2005 @@ -25,7 +25,7 @@ Upcoming events
- ForrestTuesday monthly get-together (6 September 2005) + ForrestTuesday monthly get-together (4 October 2005)

On the first Tuesday of each month we have a 24-hour get-together using IRC and other collaborative tools, to work on Forrest development and Modified: forrest/trunk/site-author/content/xdocs/forrest-tuesday.xml URL: http://svn.apache.org/viewcvs/forrest/trunk/site-author/content/xdocs/forrest-tuesday.xml?rev=279951&r1=279950&r2=279951&view=diff ============================================================================== --- forrest/trunk/site-author/content/xdocs/forrest-tuesday.xml (original) +++ forrest/trunk/site-author/content/xdocs/forrest-tuesday.xml Fri Sep 9 22:18:30 2005 @@ -34,10 +34,10 @@ and lasts for 24 hours.

- The next event will take place on 6 September 2005. See - start time + The next event will take place on 4 October 2005. See + start time and - zone overlap + zone overlap and notes about the topic of the day.

@@ -82,7 +82,7 @@
  • Listen to the dev mailing list. That is where any decisions will be - made and the name of the IRC channel. + made and the name of the IRC channel will be announced.
  • At the start time, connect to irc.freenode.net and join the channel. @@ -116,17 +116,31 @@ this setup ...
  • - Set the channel mode: /mode #channelname +n + Set the channel mode: /mode +n
  • - Declare today's topic: /topic #channelname ForrestTuesday: XHTML2 core and Jira cleanup + Declare today's topic: /topic ForrestTuesday: XHTML2 core and Jira cleanup +
  • +
  • Ask cheche to start the logger bot and tell the URL for the live logfile. +
  • +
  • + Make sure that your client is creating a logfile. +
  • +
  • + Announce to the dev mailing list that the channel is open and tell the channel name + and the URL for the live log. +
  • +
  • + During the session, occasionally refer to the live logfile URL. People can read + what they missed, and also refer to previous discussion by stating the time that + it occurred.
  • -
  • Ask cheche to start the eggbot.
  • - Make sure that your client is creating a logfile or set up a logger bot. + At the end, everyone leaves the channel and it will automatically close. + Ask cheche to stop the logger bot.
  • - Announce to the dev mailing list that the channel is open and tell the name. + Add the logfile to the Forrest Events repository. Hopefully someone will also add a summary.