[tahoe-dev] barriers to using tahoe

Cyrille ndata ndatacyrille at gmail.com
Thu Feb 4 10:49:20 UTC 2010


''''&'&@''''                                                                                                                                  

-original message-
Subject: Re: [tahoe-dev] barriers to using tahoe
From: ludo at gnu.org (Ludovic Courtès)
Date: 04/02/2010 10:41

Hello,

Jody Harris <imhavoc at gmail.com> writes:

> On Wed, Feb 3, 2010 at 5:41 PM, Brian Warner <warner at lothar.com> wrote:
>
>> Jody Harris wrote:
>> > I asked a question about forking Twisted for the short term. There was
>> > no response to that. Either, "that's a good idea with obvious
>> > consequences.....," or "That's stupid because....."
>>
>> Eh, I think mostly it's just infeasible. It would take a lot of time and
>> work for a hypothetical fork to become as well tested, packaged, and
>> distributed as the mainline Twisted is, and then it would require a lot
>> of work to keep it from falling out-of-date. I believe it would be
>> faster to get the necessary patch accepted into mainline.
>>
>> The next step towards that is to write a unit test for the patch.
>> http://twistedmatrix.com/trac/ticket/3462 is the place to submit such a
>> patch.
>>
>> Well, that certainly wreaks....
>
> So, Tahoe-LAFS has broken usability pending a patch that another software
> team is reluctant to code a test for....

FWIW I also think that fixing the (S)FTP situation may significantly
improve user experience.

Thanks,
Ludo’.

_______________________________________________
tahoe-dev mailing list
tahoe-dev at allmydata.org
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev




More information about the tahoe-dev mailing list