[sugar] journal object transfer for 8.2
Hi Kim and Michael, have heard occasional requests to implement the sending and sharing of journal entries. Eben has specified how object transfer would work in the shell: http://wiki.laptop.org/go/Specifications/Object_Transfers And Benjamin Schwartz has implemented an activity that tries to solve this issue outside the shell: http://wiki.laptop.org/go/Share So the questions are: is this a feature we should deliver for the 8.2 release? Which amount of support we should add to the shell if any? Which transport means should we use? Should the shell work depend on file transfer capabilities to be added to telepathy? Thanks. Tomeu ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
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 ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
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 <[EMAIL PROTECTED]> 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 > [EMAIL PROTECTED] > http://lists.laptop.org/listinfo/devel > ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
On Mon, Jun 09, 2008 at 04:18:10PM -0400, 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. My feeling is that since Sugar has no control over the robustness of the network, the feature will function poorly, if at all. Consequently, I would rather see bug-fixes which will bring the system closer to its intended operation with high probability. However, this is just a personal preference. I'm (mostly) happy to release whatever you send my way, so long as it fixes more problems than it creates. > 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. Perhaps a few hours of triage are called for? Here are a few of my favorites: http://dev.laptop.org/ticket/7011 <--- Zoom buttons should cycle http://dev.laptop.org/ticket/7220 <--- Populate activity ring http://dev.laptop.org/ticket/4236 <--- Cancel activity startup http://dev.laptop.org/ticket/7020 <--- Force activity shutdown http://dev.laptop.org/ticket/6895 <--- Access point UI http://dev.laptop.org/ticket/6909 http://dev.laptop.org/ticket/5444 <--- Robustness to failure http://dev.laptop.org/ticket/6148 <--- Non-ASCII Activity Names http://dev.laptop.org/ticket/6471 <--- Activity startup times http://dev.laptop.org/ticket/6472 http://dev.laptop.org/ticket/6237 <--- Cloaked APs http://dev.laptop.org/ticket/6281 <--- 802.1x for NY,UY! http://dev.laptop.org/ticket/4877 <--- Session API Michael ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
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 <[EMAIL PROTECTED]> 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 >> [EMAIL PROTECTED] >> http://lists.laptop.org/listinfo/devel >> >> > ___ > Devel mailing list > [EMAIL PROTECTED] > 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/ ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
On Mon, Jun 9, 2008 at 10:12 PM, Michael Stone <[EMAIL PROTECTED]> wrote: >> So the questions are: is this a feature we should deliver for the 8.2 >> release? > > In my opinion, "no". > > Do you think differently? Personally I think we should put it at the very end of the prioritized list of new features: http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#New_features If someone find time to work in by the feature freeze (20 June), it will be a nice feature to have. But otherwise let's focus to complete the features which are already scheduled for inclusion and on bugfixes. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
On Mon, Jun 9, 2008 at 10:57 PM, Michael Stone <[EMAIL PROTECTED]> wrote: > On Mon, Jun 09, 2008 at 04:18:10PM -0400, 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. > > My feeling is that since Sugar has no control over the robustness of the > network, the feature will function poorly, if at all. Consequently, I > would rather see bug-fixes which will bring the system closer to its > intended operation with high probability. However, this is just a > personal preference. I'm (mostly) happy to release whatever you send my > way, so long as it fixes more problems than it creates. > >> 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. > > Perhaps a few hours of triage are called for? Here are a few of my > favorites: After the feature freeze we should definitely spend a good amount of time on bugs triage. The sugar components has not been seriously triaged in the last several months. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
On Mon, Jun 9, 2008 at 11:09 PM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: > On Mon, Jun 9, 2008 at 10:12 PM, Michael Stone <[EMAIL PROTECTED]> wrote: >>> So the questions are: is this a feature we should deliver for the 8.2 >>> release? >> >> In my opinion, "no". >> >> Do you think differently? > > Personally I think we should put it at the very end of the prioritized > list of new features: > > http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#New_features > > If someone find time to work in by the feature freeze (20 June), it > will be a nice feature to have. But otherwise let's focus to complete > the features which are already scheduled for inclusion and on > bugfixes. I really doubt there will be time for this, but would be nice to know if we should start talking about this after 8.2. Specially as changes across the stack may be needed. Regards, Tomeu ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
Le lundi 09 juin 2008 à 16:12 -0400, Michael Stone a écrit : > 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? The new (work in progress) Telepathy file transfer specification should be able to nicely implement object transfer. But I doubt we'll have an implementation ready for 8.2. Could be a cool feature for the next release cycle though. G. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] journal object transfer for 8.2
On Tue, Jun 10, 2008 at 9:48 AM, Guillaume Desmottes <[EMAIL PROTECTED]> wrote: > Le lundi 09 juin 2008 à 16:12 -0400, Michael Stone a écrit : >> 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? > > > The new (work in progress) Telepathy file transfer specification should > be able to nicely implement object transfer. But I doubt we'll have an > implementation ready for 8.2. > > Could be a cool feature for the next release cycle though. Yup, I think we should consider it for the next cycle. Marco ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
