= Weekly Meeting =

There is a twice-weekly videoconference using [https://www.google.com/+/learnmore/hangouts/ Google Hangout]. 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 8:00 AM Pacific time (which is currently 15:00Z) and also Mondays 22:00Z (which is currently 3:00 PM Pacific time)||
||= Where =||Google Hangout, IRC fallback (see below)||
||= Why =||Voice/video interaction complements IRC/mailing list||
||= How =||See Agenda below||
(*) Z (Zulu) time refers to UTC; [http://www.timeanddate.com/time/map/ check where you are] or see [http://www.timeanddate.com/countdown/generic?iso=20140306T1600&p0=1440&msg=Tahoe-LAFS+weekly+meeting+countdown the countdown].

== Upcoming ==

URL: https://plus.google.com/hangouts/_/76cpjl4elbqbt16b1u3f1u5cu0 and also get on irc.freenode.net #tahoe-lafs

Date: 2014-03-20

Agenda: ?


{{{#!comment
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"''.

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 ==

* #1382 #1382 #1382 and #1382; It is almost done. Is it done? Maybe we need ''one more round of code review''‽ Can we merge it?
* #2125 (amiller wants to work on it)
* do code-review on the tickets that already have patches written for them! [milestone:1.11.0 Milestone 1.11.0]
* POSSIBLE AGENDA ITEM: Tahoe-LAFS over I2P, Tor, and/or cjdns by Twisted Endpoints ([http://foolscap.lothar.com/trac/ticket/203 pycryptopp #203]) because https://pypi.python.org/pypi/txi2p exists now!
* POSSIBLE AGENDA ITEM: let's do ChaCha20⊕AES ([//trac/pycryptopp/ticket/84 pycryptopp #84] and [ticket:1164 Tahoe-LAFS #1164]).
* **Noether status report** by Daira ''("TESLA COILS AND CORPSES")''
* **Rainhill design review** which Daira will distribute; call for outside crypto expert reviewers ''("TESLA COILS AND CORPSES")''
* **Proof-of-Retrievability In The Presence Adaptive Adversaries** by Zooko ''("TESLA COILS AND CORPSES")''
* **Awesome Generalized Authenticated Data Structures, Part 2** by Andrew ''("TESLA COILS AND CORPSES")''
* **Awesome Generalized Cryptocurrencies, Part 2** by Brian ''("TESLA COILS AND CORPSES")''

== Notes / Archives ==

=== 2014-03-06 ===

* post-Tahoe-LAFS/new-!PetMail/"!FireFoxTahoeThing" ideas from Brian Warner, about how to do introduction, sharing, and garbage-collection.

[//pipermail/tahoe-dev/2014-March/008952.html notes]

=== 2014-12-13 ===

* ''("NUTS AND BOLTS")'': #1382

[//pipermail/tahoe-dev/2014-February/008908.html notes]

=== 2014-12-12 ===

* ''("NUTS AND BOLTS")'': #1382

[//pipermail/tahoe-dev/2014-February/008901.html notes]

=== 2014-02-06 ===

* ''("NUTS AND BOLTS")'': #1382

[//pipermail/tahoe-dev/2014-February/008895.html notes]

=== 2013-11-14 ===

* ''("NUTS AND BOLTS")'':

* plans for Tahoe-LAFS Summit next week in SF.
* #1382 #1382 #1382 and #1382 (because Mark_B and Zooko will both be in this dev chat and they want to work on comment:50:ticket:1382)

=== 2013-10-23 ===

* ''("NUTS AND BOLTS")'':

tests of packaging

#2049, #2050

publish buildbot config

travis-ci

tests of packaging:

* pip install allmydata-tahoe (currently fails due to Nevow bug #XXX )
* python setup.py install (currently doesn't install deps) (ticket #XXX )
* the tests from the old buildmaster and from the old misc/build_helpers/test*.py

=== 2013-10-02 ===

* ''("NUTS AND BOLTS")'': #1382 #1382 #1382 and #1382

[//pipermail/tahoe-dev/2013-October/008731.html notes]

=== 2013-09-11 ===

* ''("NUTS AND BOLTS")'': code-review on the tickets that already have patches written for them! [milestone:1.11.0 Milestone 1.11.0]

=== 2013-08-28 ===

* ''("NUTS AND BOLTS")'': Agenda: Planning for Tahoe-LAFS v1.11 release!

What will be new in Tahoe-LAFS v1.11? Here is the [query:status=closed&group=resolution&milestone=1.11.0 list of v1.11 tickets already closed]:  Here is the [query:status=assigned&status=new&status=reopened&keywords=~review-needed&milestone=1.11.0&group=status&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&order=priority list of v1.11 tickets awaiting code review].

[https://www.youtube.com/watch?v=0fAbv9EzHiw video recording!]

[//pipermail/tahoe-dev/2013-August/008679.html notes]

=== 2013-08-21 ===

* ''("NUTS AND BOLTS")'': Agenda: I2P, v1.11 release, Mark's tickets

[//pipermail/tahoe-dev/2013-August/008674.html notes]

=== 2013-08-07 ===

* ''("NUTS AND BOLTS")'': Agenda: GSoC, #1870, Buildbot

[//pipermail/tahoe-dev/2013-August/008631.html notes]

=== 2013-07-31 ===

* ''("NUTS AND BOLTS")'': Agenda: GSoC, #1057, #2027

[[//pipermail/tahoe-dev/2013-August/008633.html notes]

=== 2013-07-16 ===

* ''("NUTS AND BOLTS")'': Agenda: GSoC, #1382

[//pipermail/tahoe-dev/2013-July/008534.html notes]

=== 2013-07-09 ===

* ''("NUTS AND BOLTS")'': Agenda: Tahoe-LAFS v1.11 ticket triage

[//pipermail/tahoe-dev/2013-July/008534.html notes]

=== 2013-07-04 ===

* ''("NUTS AND BOLTS")'': Agenda: "Mark Berger's improvements to immutable peer selection"

[//pipermail/tahoe-dev/2013-July/008486.html notes]

=== 2013-06-20 ===

* ''("NUTS AND BOLTS")'': Agenda: "Mark Berger's improvements to immutable peer selection"

[//pipermail/tahoe-dev/2013-June/008425.html notes]

=== 2013-05-30 ===

* ''("NUTS AND BOLTS")'': Agenda: "Write some patches for Tahoe-LAFS v1.11!"

  * Leif's recent patches to the WUI (#1973)
  * improve the design and beauty of the WUI (https://github.com/tahoe-lafs/tahoe-lafs/pull/32 , #1492)
  * fix defects in the WUI (#1993, #1931, #1375, #1462, #1502, #1961, #622, #311, #525, #631, #1588, #1645, #1706)
  * write cool new WUI (#1942, #1369, #1551, #1499, #277)

(I can't remember whether we actually followed the agenda.)

=== 2013-05-02 ===

* ''("TESLA COILS AND CORPSES")'': Agenda: "Post-LAFS: What would you invent (or are you inventing) now that you already understand Tahoe-LAFS? Possibilities: LDMF (fancier authenticated data structures), Brian's secret file-sharing project within Mozilla, !BitTorrent Sync, saying 'Okay, storage is good enough, let's work on decentralized currencies/payment-systems instead.'"

Actual topic turned out to be "Post-Bitcoin" instead.

[//pipermail/tahoe-dev/2013-May/008262.html notes]

=== 2013-04-25 ===

* ''("NUTS AND BOLTS")'': Google Summer of Code project planning

[//pipermail/tahoe-dev/2013-May/008260.html notes]

=== 2013-04-18 ===

* ''("TESLA COILS AND CORPSES")'': Andrew Miller: "type-directed security definitions for generic authenticated data structures"

[//pipermail/tahoe-dev/2013-April/008192.html notes]

=== 2012-04-11 ===

* ''("NUTS AND BOLTS")'': IPv6 and tests thereof

[//pipermail/tahoe-dev/2013-April/008163.html notes]

=== 2012-03-14 ===

* ''("NUTS AND BOLTS")'': Tahoe-LAFS v1.10 patches; [milestone:1.10.0], contribute patches, tests, docs, or comments.

=== 2012-03-07 ===

* ''("NUTS AND BOLTS")'': Tahoe-LAFS v1.10 patches; [milestone:1.10.0], contribute patches, tests, docs, or comments.

[//pipermail/tahoe-dev/2013-March/008082.html notes]

=== 2013-02-28 ===

* ''("TESLA COILS AND CORPSES")'': (attempt number 3) Iraklis's research in applying Ristenpart's [http://eprint.iacr.org/2012/631 Message-Locked Encryption] to LAFS. This requires extending the model of Message-Locked Encryption, and it suggests interesting directions for future extensions of LAFS.

[//pipermail/tahoe-dev/2013-February/008063.html notes]

=== 2012-02-21 ===

* ''("TESLA COILS AND CORPSES")'': (attempt number 2) Iraklis's research in applying Ristenpart's [http://eprint.iacr.org/2012/631 Message-Locked Encryption] to LAFS. This requires extending the model of Message-Locked Encryption, and it suggests interesting directions for future extensions of LAFS.

=== 2012-02-14 ===

* ''("TESLA COILS AND CORPSES")'': Iraklis's research in applying Ristenpart's [http://eprint.iacr.org/2012/631 Message-Locked Encryption] to LAFS. This requires extending the model of Message-Locked Encryption, and it suggests interesting directions for future extensions of LAFS.

=== 2012-01-31 ===

* ''("NUTS AND BOLTS")'': Tahoe-LAFS v1.10, new WUI, "timeline" visualization, https://LeastAuthority.com commercialization of Tahoe-LAFS

[//pipermail/tahoe-dev/2013-February/007955.html notes]

=== ... ===

[some weekly hangouts were skipped due to travel]

=== 2012-01-10 ===

* ''("NUTS AND BOLTS")'': Tahoe-LAFS v1.10

=== 2012-12-13 ===

* ''("NUTS AND BOLTS")'': documentation and internationalization

* ''("NUTS AND BOLTS")'': Tahoe-LAFS v1.10

* ''("TESLA COILS AND CORPSES")'': new secure hash function

[//pipermail/tahoe-dev/2012-December/007892.html notes]

=== 2012-12-06 ===

* ''("TESLA COILS AND CORPSES")'': Proofs-of-Retrievability!

[//pipermail/tahoe-dev/2012-December/007887.html notes]

=== 2012-11-29 ===

* ''("NUTS AND BOLTS")'': documentation

* ''("TESLA COILS AND CORPSES")'': distributed introduction, defense against rollback attack

[//pipermail/tahoe-dev/2012-November/007867.html notes]

=== 2012-11-22 ===

* ''("NUTS AND BOLTS")'': work on Tahoe-LAFS v1.10 tickets!

[//pipermail/tahoe-dev/2012-November/007859.html notes]

=== 2012-11-15 ===

* ''("TESLA COILS AND CORPSES")'': async notifications

What a ''lot'' of people really want is an alternative to Dropbox — something that functions very like Dropbox but without exposing your plaintext to spying and corruption. David-Sarah implemented a part of this with the drop-upload feature. It seems to me that the blocker which prevents Tahoe-LAFS from doing the rest of it is that LAFS clients have no way to get an asynchronous notification that a file has changed (i.e., so that they don't have to poll to find out if the file has changed). So: could we add that? Why not just define a remote interface offered by LAFS clients to LAFS servers. The remote interface is "hey_you_this_file_has_changed(storageindex)".

=== 2012-11-08 ===

''("NUTS AND BOLTS")'': 

* #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 ===

''("TESLA COILS AND CORPSES")'': **Garbage collection**: use cases and protocols;

* #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].

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