On Fri, 07 Sep 2007 12:43:38 +0200, G"oran Krampe <goran at krampe.se> wrote:

> Hi!
>
>> Hi Igor,
>>
>> got the point :)
>>
>> And now, every p2p developer events participant rushes out for buying a
>> really reliable backup service/equipment, just in case the contributions
>> she/he made three years ago where never replicated to somebody else (or
>> where "lost" by everybody else as well).
>>
>> How's history addressed in such scenarios (except DIY/DeverythingY), any
>> experience/good practice? TIA.
>>
>> /Klaus
>
> Note that the "developer events" model/system I am describing has nothing
> to do with maintaining source code or anything. It is purely meant as a
> "aha, he is doing that too!"-kinda tool. Purely transient information
> being passed around.

Ok thanks, sounds interesting :)

> For persistent logging of changes etc - I and Matthew Fulmer are working
> on  DeltaStreams which probably could serve as a good basis for such
> experiments.

ditto.

/Klaus

> And it could also very well be used for payloads for a
> "developer events" system.
>
> regards, G"oran
>
>
>