Changes between Version 38 and Version 39 of WeeklyMeeting


Ignore:
Timestamp:
2012-12-06T07:16:03Z (12 years ago)
Author:
zooko
Comment:

weekly update to the "WeeklyMeeting" page

Legend:

Unmodified
Added
Removed
Modified

  • WeeklyMeeting

    v38 v39  
    99||= Why =||Voice/video interaction complements IRC/mailing list||
    1010||= How =||See Agenda below||
    11 (*) 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=20121115T16&p0=1440&msg=Tahoe-Lafs+weekly+meeting countdown].
     11(*) 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=20121206T16&p0=1440&msg=Tahoe-Lafs+weekly+meeting%20countdown the countdown].
     12
    1213== Etiquette ==
    1314
    … …  
    1819== Agenda ==
    1920
    20 URL: https://plus.google.com/hangouts/_/935f3473d1cd505f0e1561b2879426ca1cd949b1?authuser=0&hl=en#
     21URL: TBA
    2122
    22 Upcoming: 2012-11-29
     23Upcoming: 2012-12-06
    2324
    24 Agenda: Documentation!
     25Agenda: Proofs-of-Retrievability!
    2526
    26 * A brief update regarding the documentation and translation status by Patrick "marlowe".
    27 
    28 * Let's just start editing and writing docs during the meeting and see what we get.
    2927
    3028To prepare for this meeting:
    3129
    32 * Read this thread: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-November/007860.html .
     30* Read this document: https://zooko.com/uri/URI%3ADIR2-MDMF-RO%3Ancatoq5dkkdrsgrqzfhvfmhcui%3Az4ntrmimtgsgy4xsf7fvllvk3b232gs6kgvxp722odgpw4dt2pva/
    3331
    34 * Read associated tickets and patches.
    3532
    36 * Write docs! Write brand new docs or write patches for existing docs. Bring your text to the meeting!
    37 
     33{{{#!comment
    3834This will be a ''"NUTS AND BOLTS"'' meeting — it is about engineering, debugging, documentation, making stable releases, etc.
    3935
    4036If 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"''.
     37}}}
    4138
    42 {{{#!comment
    4339This will be a ''"TESLA COILS AND CORPSES"'' meeting — it is about science, big new features, writing papers about our work, etc.
    4440
    4541If you're more into engineering, debugging, documentation, making stable releases, etc. then stay tuned for a future meeting about ''"NUTS AND BOLTS"''.
    46 }}}
    4742
    4843== Proposed Future Topics ==
    4944
    50 * **Proof of Retrievability** which Zooko will distribute;''("TESLA COILS AND CORPSES")''
     45* **documentation and internationalization** presented by Marlowe;''("NUTS AND BOLTS")''
    5146
    5247* **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? ''("NUTS AND BOLTS")''
    … …  
    5651== Notes / Archives ==
    5752
     53=== 2012-11-29 ===
     54
     55* ''("NUTS AND BOLTS")'': documentation
     56
     57* ''("TESLA COILS AND CORPSES")'': distributed introduction, defense against rollback attack
     58
     59notes: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-November/007867.html
     60
    5861=== 2012-11-22 ===
    5962
    60 * NUTS AND BOLTS: work on Tahoe-LAFS v1.10 tickets!
     63* ''("NUTS AND BOLTS")'': work on Tahoe-LAFS v1.10 tickets!
    6164
    6265notes: https://tahoe-lafs.org/pipermail/tahoe-dev/2012-November/007859.html
    … …  
    6467=== 2012-11-15 ===
    6568
    66 * async notifications
     69* ''("TESLA COILS AND CORPSES")'': async notifications
    6770
    6871What 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)".
    6972
    7073=== 2012-11-08 ===
     74
     75''("NUTS AND BOLTS")'':
    7176
    7277* #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?
    … …  
    7580=== 2012-11-01 ===
    7681
    77 **Garbage collection**: use cases and protocols;
     82''("TESLA COILS AND CORPSES")'': **Garbage collection**: use cases and protocols;
    7883
    7984* #1832 (support indefinite leases with garbage collection)