You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2005/09/10 07:18:33 UTC

svn commit: r279951 - in /forrest/trunk/site-author/content/xdocs: events.xml forrest-tuesday.xml

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 @@
       <title>Upcoming events</title>
 
       <section id="forrest-tuesday">
-        <title>ForrestTuesday monthly get-together (6 September 2005)</title>
+        <title>ForrestTuesday monthly get-together (4 October 2005)</title>
         <p>
           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.
       </p>
       <p>
-        The next event will take place on <strong>6 September 2005</strong>. See 
-        <a href="http://www.timeanddate.com/worldclock/fixedtime.html?year=2005&amp;month=9&amp;day=6&amp;hour=6&amp;min=0&amp;sec=0">start time</a>
+        The next event will take place on <strong>4 October 2005</strong>. See 
+        <a href="http://www.timeanddate.com/worldclock/fixedtime.html?year=2005&amp;month=10&amp;day=4&amp;hour=6&amp;min=0&amp;sec=0">start time</a>
         and
-        <a href="http://www.timeanddate.com/worldclock/meetingtime.html?day=6&amp;month=9&amp;year=2005&amp;p1=136&amp;p2=48&amp;p3=176&amp;p4=240&amp;p5=224&amp;p6=213">zone overlap</a>
+        <a href="http://www.timeanddate.com/worldclock/meetingtime.html?day=4&amp;month=10&amp;year=2005&amp;p1=136&amp;p2=48&amp;p3=176&amp;p4=240&amp;p5=224&amp;p6=213">zone overlap</a>
         and notes about the
         <a href="site:plan/overview">topic of the day</a>.
       </p>
@@ -82,7 +82,7 @@
         </li>
         <li>
           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.
         </li>
         <li>
           At the start time, connect to irc.freenode.net and join the channel.
@@ -116,17 +116,31 @@
           this setup ...
         </li>
         <li>
-          Set the channel mode: <code>/mode #channelname +n</code>
+          Set the channel mode: <code>/mode +n</code>
         </li>
         <li>
-          Declare today's topic: <code>/topic #channelname ForrestTuesday: XHTML2 core and Jira cleanup</code>
+          Declare today's topic: <code>/topic ForrestTuesday: XHTML2 core and Jira cleanup</code>
+        </li>
+        <li>Ask cheche to start the logger bot and tell the URL for the live logfile.
+        </li>
+        <li>
+          Make sure that your client is creating a logfile.
+        </li>
+        <li>
+          Announce to the dev mailing list that the channel is open and tell the channel name
+          and the URL for the live log.
+        </li>
+        <li>
+          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.
         </li>
-        <li>Ask cheche to start the eggbot.</li>
         <li>
-          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.
         </li>
         <li>
-          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.
         </li>
       </ul>
     </section>