tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

weekly update to the "WeeklyMeeting" page 

[Imported from Trac: page WeeklyMeeting, version 39]
zooko 2012-12-06 07:16:03 +00:00
parent 014932d72d
commit f27be711fb
1 changed files with 22 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

39
WeeklyMeeting.md

@ -14,7 +14,8 @@ There is a weekly conference call using [Google Hangout](https://www.google.com/
|---|| |---||
| How |See Agenda below| | How |See Agenda below|
|---|| |---||
(*) Z (Zulu) time refers to UTC; [check where you are](http://www.timeanddate.com/time/map/) or see [countdown](http://www.timeanddate.com/countdown/generic?iso=20121115T16&p0=1440&msg=Tahoe-Lafs+weekly+meeting). (*) Z (Zulu) time refers to UTC; [check where you are](http://www.timeanddate.com/time/map/) or see [the countdown](http://www.timeanddate.com/countdown/generic?iso=20121206T16&p0=1440&msg=Tahoe-Lafs+weekly+meeting%20countdown).
## Etiquette ## Etiquette
* It's okay to talk about things not on the pre-arranged agenda. (But it helps to announce in advance if you know there's something you'll want to talk about! It encourages other interested people to prepare and helps them avoid accidentally missing a meeting that they really would have wanted to attend.) * It's okay to talk about things not on the pre-arranged agenda. (But it helps to announce in advance if you know there's something you'll want to talk about! It encourages other interested people to prepare and helps them avoid accidentally missing a meeting that they really would have wanted to attend.)
@ -23,37 +24,31 @@ There is a weekly conference call using [Google Hangout](https://www.google.com/
## Agenda ## Agenda
URL: <https://plus.google.com/hangouts/_/935f3473d1cd505f0e1561b2879426ca1cd949b1?authuser=0&hl=en># URL: TBA
Upcoming: 2012-11-29 Upcoming: 2012-12-06
Agenda: Documentation! Agenda: Proofs-of-Retrievability!
* A brief update regarding the documentation and translation status by Patrick "marlowe".
* Let's just start editing and writing docs during the meeting and see what we get.
To prepare for this meeting: To prepare for this meeting:
* Read this thread: <https://tahoe-lafs.org/pipermail/tahoe-dev/2012-November/007860.html> . * Read this document: <https://zooko.com/uri/URI%3ADIR2-MDMF-RO%3Ancatoq5dkkdrsgrqzfhvfmhcui%3Az4ntrmimtgsgy4xsf7fvllvk3b232gs6kgvxp722odgpw4dt2pva/>
* Read associated tickets and patches.
* Write docs! Write brand new docs or write patches for existing docs. Bring your text to the meeting!
<!---
This will be a *"NUTS AND BOLTS"* meeting — it is about engineering, debugging, documentation, making stable releases, etc. 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"*. 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. 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"*. 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 ## Proposed Future Topics
* **Proof of Retrievability** which Zooko will distribute;*("TESLA COILS AND CORPSES")* * **documentation and internationalization** presented by Marlowe;*("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? *("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? *("NUTS AND BOLTS")*
@ -61,26 +56,36 @@ If you're more into engineering, debugging, documentation, making stable release
## Notes / Archives ## Notes / Archives
### 2012-11-29
* *("NUTS AND BOLTS")*: documentation
* *("TESLA COILS AND CORPSES")*: distributed introduction, defense against rollback attack
notes: <https://tahoe-lafs.org/pipermail/tahoe-dev/2012-November/007867.html>
### 2012-11-22 ### 2012-11-22
* NUTS AND BOLTS: work on Tahoe-LAFS v1.10 tickets! * *("NUTS AND BOLTS")*: work on Tahoe-LAFS v1.10 tickets!
notes: <https://tahoe-lafs.org/pipermail/tahoe-dev/2012-November/007859.html> notes: <https://tahoe-lafs.org/pipermail/tahoe-dev/2012-November/007859.html>
### 2012-11-15 ### 2012-11-15
* async notifications * *("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)". 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 ### 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? * #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? * #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 ### 2012-11-01
**Garbage collection**: use cases and protocols; *("TESLA COILS AND CORPSES")*: **Garbage collection**: use cases and protocols;
* #1832 (support indefinite leases with garbage collection) * #1832 (support indefinite leases with garbage collection)
* #1833 (storage server deletes garbage shares itself instead of waiting for crawler to notice them) * #1833 (storage server deletes garbage shares itself instead of waiting for crawler to notice them)