journal object transfer for 8.2

[Polychronis Ypodimatopoulos]

An OLPC intern would have actually taken up this task, but changed 
direction for the summer. I 'm not sure though how network robustness 
will improve if some networking (such as file transfer) is done in the 
Journal. A slightly more radical change may be necessary ;-)

p.

Walter Bender wrote:
> I would argue otherwise. Since Sugar has no control over the
> robustness of the network, having some way of sharing at a basic level
> from the Journal is seemingly a high priority. Half of the
> high-priority bugs in the link you provide are in fact not really
> Sugar bugs, but subsystem bugs. The others don't seem to be
> particularly pressing.
>
> -walter
>
> On Mon, Jun 9, 2008 at 4:12 PM, Michael Stone <michael at laptop.org> wrote:
>   
>> Tomeu,
>>
>>     
>>> have heard occasional requests to implement the sending and sharing of
>>> journal entries.
>>>       
>> It's a desirable feature but, from my perspective, it's much lower in
>> immediate priority than work which brings the sugar UI revision into a
>> releasable condition and which "polish" the existing work by closing
>> several of the 379 tickets assigned to component 'sugar':
>>
>>  http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component=sugar&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component
>>
>>     
>>> So the questions are: is this a feature we should deliver for the 8.2
>>> release?
>>>       
>> In my opinion, "no".
>>
>> Do you think differently?
>>
>> Michael
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>>
>>     
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>   

-- 
Polychronis Ypodimatopoulos
Graduate student
Viral Communications
MIT Media Lab
Tel: +1 (617) 459-6058
http://www.mit.edu/~ypod/