= Weekly Meeting =

There is a weekly conference call using [https://www.google.com/+/learnmore/hangouts/ Google Hangout]. The agenda is set prior to each meeting and is focused on topics directly relevant to Tahoe-LAFS development. 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 =||Thursdays 15:30Z (8:30am Pacific); was: ~~Each Tuesday, 17:30-18:30Z~~||
||= Where =||Google Hangout, IRC fallback (see below)||
||= Why =||Voice/video interaction complements IRC/mailing list||
||= How =||See Agenda below||

== Etiquette ==

* Strive to follow the established agenda.
* 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/_/7be14e247a4503eb39a67cac571b7e4b01159b9e?authuser=0&hl=en#

Upcoming:

'''Note''': The meeting time and date have changed.  See the table above and double check the date here:

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.

* 2012-11-01: **Garbage collection**: use cases and protocols;

To prepare for this meeting: read tickets:

* #1832 (support indefinite leases with garbage collection)
* #1833 (storage server deletes garbage shares itself instead of waiting for crawler to notice them)
* #1834 (stop using share crawler for anything except constructing a leasedb)
* #1835 (stop grovelling the whole storage backend looking for externally-added shares to add a lease to)
* #1836 (use leasedb (not crawler) to figure out how many shares you have and how many bytes)
* #1837 (remove the "override lease duration" feature)

And [//pipermail/tahoe-dev/2012-October/007768.html the associated mailing list thread].

== Proposed Future Topics ==

* **Proof-of-Retrievability** review of a paper draft Zooko will distribute. (was scheduled: ~~2012-10-30~~)

* **Rainhill design review** which David-Sarah will distribute; call for outside crypto expert reviewers. (was scheduled: ~~2012-11-06~~)



== Notes / Archives ==

=== 2012-10-23 ===

Topics: Ticket #1240, Tahoe-LAFS birthday party, future agendas.

Attendees: Zooko, David-Sarah, amiller, ambimorph, nejucomo.

Concise summary:

* #1240 debug session - Incorrect caching logic suspected.
* Tahoe-LAFS birthday party - Saturday, 2012-10-27 at 23:00z - Each locale connects with a projector + google hangout.
* Future agendas - next week, Proof of Retrievability paper review; two weeks out, Rainhill review with outside crypto reviewers.

Finely detailed notes in [wiki:MeetingNotes_2012_10_23]

=== 2012-10-16 ===

Topics: Proof-of-Retrievability

Attendees: Zooko, David-Sarah, nejucomo

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."