From b960838e77003c56696f8f7e3bb738d32d487a19 Mon Sep 17 00:00:00 2001 From: warner <> Date: Sun, 24 Jul 2016 20:50:41 +0000 Subject: [PATCH] reformat, freshen up meeting info [Imported from Trac: page WeeklyMeeting, version 213] --- WeeklyMeeting.md | 62 +++++++++++++++++++++--------------------------- 1 file changed, 27 insertions(+), 35 deletions(-) diff --git a/WeeklyMeeting.md b/WeeklyMeeting.md index 4413511..4fb5e3c 100644 --- a/WeeklyMeeting.md +++ b/WeeklyMeeting.md @@ -1,61 +1,53 @@ # Weekly Meeting -There is a twice-weekly videoconference using [Google Hangout](https://www.google.com/+/learnmore/hangouts/). The connection URL is posted on this page and IRC a few minutes before the meeting. +There is a weekly videoconference, currently using [Google Hangout](https://www.google.com/+/learnmore/hangouts/). The connection URL is posted on this page and IRC a few minutes before the meeting. | Who |Core developers or interested community members| |---|---| | What |Dev Topics Meeting| |---|| -| When |Fridays 16:00Z (*Tesla Coils and Corpses*) and Tuesdays 16:00Z (*Nuts and Bolts*)| +| When |Tuesdays 16:00Z-18:00Z (in summer. one hour off in winter)| |---|| -| Where |Google Hangout, IRC fallback (see below)| +| Where |Google Hangout, IRC fallback| |---|| | Why |Voice/video interaction complements IRC/mailing list| |---|| | How |See Agenda below| |---|| -(*) Z (Zulu) time refers to UTC; [check where you are](http://www.timeanddate.com/time/map/) +| IRC |join channel "#tahoe-lafs" on irc.freenode.net (port 7000 for TLS)| +|---|| -## HELP PICK A MEETING TIME +(Z "Zulu" time refers to UTC; [check where you are](http://www.timeanddate.com/time/map/), but the meeting is tied to civil time, not UTC, so when the various countries all switch to/from DST, the meeting's UTC time changes) -Go to register what times of day you could attend meetings every week +The first half of the meeting is "Nuts and Bolts" (engineering!): bug triage, discussion of current development efforts, branch and patch review, etc. After a short break, we switch to "Tesla Coils and Corpses" (science!): brainstorming of new features, analysis of other projects, and other forward-looking explorations. -## Upcoming +## Agenda for next meeting (26-Jul-2016) -### the next *Tesla Coils and Corpses* meeting +* topic 1 +* topic 2 -URL: +## Other Stuff -Agenda: Programming language design -- conditions and restarts in Common Lisp +We switch chat tools every few months, in an attempt to overcome performance problems. Tools we've used: -This will be a *"TESLA COILS AND CORPSES"* meeting — it is about science, big new features, writing papers about our work, etc. +* Google Hangouts +* +* +* +* +* -If you're more into engineering, debugging, documentation, making stable releases, etc. then stay tuned for a future meeting about *"NUTS AND BOLTS"*. +Most require a browser extension to enable screensharing. -### the next *Nuts and Bolts* meeting +We frequently keep notes on an etherpad, the URL for which is posted at the start of the meeting. Patrick [McDonald](McDonald) turns these notes into the Tahoe Weekly News. -URL: TBA +Other resources that usually get referenced during the course of the meeting: -get on channel "#tahoe-lafs" on irc.oftc.net (port 6697 for TLS) - -agenda: TBA - -This will be a *"NUTS AND BOLTS"* meeting — it is about engineering, debugging, documentation, 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"*. - -## WebRTC (not in use) - -WebRTC seems to require Google !Chrome/Chromium or a FireFox ≥ v28 or so. - -* recommended WebRTC chat rooms: - - — This one claims to be fully Open Source. - - — This one claims to be only partially Open Source, but it supports screen-sharing (although only with Google !Chrome/Chromium) and opentokrtc.com doesn't seem to. - -* other WebRTC chat rooms: - - - - - - +* +* +* +* +* ## Proposed Future Topics @@ -351,4 +343,4 @@ From IRC, Zooko summarizes (edited for spelling): 1. "The reason we can do better than the previous state of the art is that we've expanded the setting to multiple servers and multiple clients, which opens up new defenses for the good guys against Ponda Baba." 2. "It is useful way to think, to start with the completely safe camouflaged download protocol: just run your normal verifier, but tell it to save what it gets, and then to talk about how to make it faster without breaking camouflage." -3. "There are two dimensions of how you might be able to make it faster: the dimension of multiple downloader/verifiers and the dimension of multiple servers." \ No newline at end of file +3. "There are two dimensions of how you might be able to make it faster: the dimension of multiple downloader/verifiers and the dimension of multiple servers."