diff --git a/WeeklyMeeting.md b/WeeklyMeeting.md index b8ff50f..a50c655 100644 --- a/WeeklyMeeting.md +++ b/WeeklyMeeting.md @@ -25,27 +25,28 @@ There is a weekly conference call using [Google Hangout](https://www.google.com/ URL: -Upcoming: 2012-11-22 +Upcoming: 2012-11-29 -Agenda: close out [/query?status=assigned&status=new&status=reopened&group=status&milestone=1.10.0 tickets for Tahoe-LAFS v1.10]! - -This will be a *NUTS AND BOLTS* meeting — it is about engineering, debugging, making stable releases, etc. - -If you're more into science, big new features, writing papers about our work, etc. then stay tuned for a future meeting about *TESLA COILS AND CORPSES*. +Agenda: **Proof-of-Retrievability** which Zooko will distribute +This will be a *TESLA COILS AND CORPSES* meeting — it is about science, big new features, writing papers about our work, etc. +If you're more into engineering, debugging, documentation, making stable releases, etc. then stay tuned for a future meeting about *NUTS AND BOLTS*. ## Proposed Future Topics -* **Proof-of-Retrievability** which Zooko will distribute - -* **Tahoe-LAFS v1.10** What can we do to move Tahoe-LAFS v1.10 along? Is David-Sarah too busy with LeastAuthority.com to be Release Manager for Tahoe-LAFS v1.10? Should Tahoe-LAFS v1.10 contain only patches that are already on trunk? - -* **Rainhill design review** which David-Sarah will distribute; call for outside crypto expert reviewers +* *NUTS AND BOLTS* **Tahoe-LAFS v1.10** What can we do to move Tahoe-LAFS v1.10 along? Is David-Sarah too busy with LeastAuthority.com to be Release Manager for Tahoe-LAFS v1.10? Should Tahoe-LAFS v1.10 contain only patches that are already on trunk? +* *TESLA COILS AND CORPSES* **Rainhill design review** which David-Sarah will distribute; call for outside crypto expert reviewers ## Notes / Archives +### 2012-11-22 + +* NUTS AND BOLTS: work on Tahoe-LAFS v1.10 tickets! + +notes: + ### 2012-11-15 * async notifications