diff --git a/WeeklyMeeting.md b/WeeklyMeeting.md
index 4a87c61..b8c6375 100644
--- a/WeeklyMeeting.md
+++ b/WeeklyMeeting.md
@@ -6,7 +6,7 @@ There is a weekly conference call using [Google Hangout](https://www.google.com/
 |---|---|
 | What |Dev Topics Meeting|
 |---||
-| When |Thursdays 16:30Z (8:30am Pacific)|
+| When |Thursdays 16:00Z (8:00am Pacific) (NOTE: time has changed (again). Previously, it was 16:30Z)|
 |---||
 | Where |Google Hangout, IRC fallback (see below)|
 |---||
@@ -17,23 +17,21 @@ There is a weekly conference call using [Google Hangout](https://www.google.com/
 
 ## Etiquette
 
-* Strive to follow the established agenda.
+* It's okay to talk about things not on the pre-arranged agenda. (But it helps to announce in advance if you know there's something you'll want to talk about! It encourages other interested people to prepare and to join in.)
 * Participants may have high latency; if you'd like to speak, say "turn" or raise your hand and wait for silence.
-* Be respectful.
 * Use IRC for textual chat *not* the hangout chat feature.
 
 ## Agenda
 
 URL: <https://plus.google.com/hangouts/_/04cdd3e81a07cd9adb8bd177a37e06b7a5b21e9d?authuser=0&hl=en>#
 
-Upcoming:
+Upcoming: 2012-11-15
 
 This will be a *NUTS AND BOLTS* meeting — engineering, debugging, making stable releases, etc. If you're more into *TESLA COILS AND CORPSES* then stay tuned for a future meeting about science, big new features, writing papers about our work, etc.
 
-* #1240; Is it done? (I think it still needs fixed tests.) Can we commit it to trunk and be done with it? Do we need to merge it with #1679?
-* #1679; Let's write a test for it! Has The Dod had continuous good service since he applied the patch? Has nejucomo tried reproducing his bug and applying the patch?
+Agenda:
 
-To prepare for this meeting: read the two tickets, write some unit tests for them, post your patches. ☺
+What can we do to move Tahoe-LAFS v1.10 along? Is David-Sarah too busy with [LeastAuthority](LeastAuthority).com to be Release Manager for Tahoe-LAFS v1.10? Should Tahoe-LAFS v1.10 contain only patches that are already on trunk?
 
 ## Proposed Future Topics
 
@@ -45,6 +43,11 @@ To prepare for this meeting: read the two tickets, write some unit tests for the
 
 ## Notes / Archives
 
+### 2012-11-08
+
+* #1240; Is it done? (I think it still needs fixed tests.) Can we commit it to trunk and be done with it? Do we need to merge it with #1679?
+* #1679; Let's write a test for it! Has The Dod had continuous good service since he applied the patch? Has nejucomo tried reproducing his bug and applying the patch?
+
 ### 2012-11-01
 
 **Garbage collection**: use cases and protocols;