Re: [Sugar-devel] GSoC proposal status

Hi Tony, > On February 22, 2016 at 1:32 AM Tony Anderson > wrote: > > > Hi, Jerry > > When I am talking about Sugar, I am referring to 0.106. You will find > ds-backup.py and ds-backup.sh in /usr/bin. The shell script determines > whether the > schoolserver is

Re: [Sugar-devel] GSoC proposal status

Hi, Jerry When I am talking about Sugar, I am referring to 0.106. You will find ds-backup.py and ds-backup.sh in /usr/bin. The shell script determines whether the schoolserver is registered and connected and whether a backup is needed (> 24hours). This script is apparently executed via

Re: [Sugar-devel] GSoC proposal status

Hi Samuel, > On February 21, 2016 at 5:56 PM Samuel Greenfeld > wrote: > > > Just for the record: > > The XO laptop backup mechanism for Sugar creates separate > "datastore--MM-DD_HH:MM" directories for each backup. > That is not integrated into sugar(the last time

Re: [Sugar-devel] GSoC proposal status

I haven't used the ds_backup.py as released, but AFIK rsync uses the -d flag which deletes objects from the backup if they have been deleted in the Journal. While it does make multiple snapshots, AFIK, the restore mechanism does not support using them for versioning. I don't believe there are

Re: [Sugar-devel] GSoC proposal status

Just for the record: The XO laptop backup mechanism for Sugar creates separate "datastore--MM-DD_HH:MM" directories for each backup. If I recall correctly, the schoolserver also periodically looks through these backups, hardlinks identical items to save space, and prunes backups beyond a set

Re: [Sugar-devel] GSoC proposal status

Hi, Sam Thanks for your comments. These issues need review and comment within the community. "Just my 2c, but this complicates the experience a lot. Do we show this temp journal entry to the user? If so, wouldn't that be confusing? But it we hide it, it becomes more complex. Eg, a user

Re: [Sugar-devel] GSoC proposal status

Hi all, Just added a bunch of Sugarizer projects on the page: http://wiki.sugarlabs.org/go/Summer_of_Code/2016#Sugarizer If some of you are interested to be co-mentor on these projects, do not hesitate to add your name. Best regards from France. Lionel.

Re: [Sugar-devel] GSoC proposal status

On Sat, Feb 20, 2016 at 6:00 PM Tony Anderson wrote: > Hi, Walter > > I have some concerns about the proposed GSOC tasks as well as some ideas > for new tasks. > > I agree that the Journal needs rethinking. Below are my thoughts > (re-thoughts?). > > Specifically, > > The

Re: [Sugar-devel] GSoC proposal status

I added a section "Sugar on the Ground". I left out the "not Sugar" projects: flashing XOs, anti-theft. I added a few of the more controversial UI proposals, but they merit discussion. IMHO, we made a mistake when we removed the obligatory "commit message" when exiting activities. -walter On

Re: [Sugar-devel] GSoC proposal status

Thanks Tony. I'll give this a careful read in the AM. I'm at the end of my productive energy level at the moment. -walter On Sat, Feb 20, 2016 at 2:00 AM, Tony Anderson wrote: > Hi, Walter > > I have some concerns about the proposed GSOC tasks as well as some ideas > for

Re: [Sugar-devel] GSoC proposal status

Hi, Walter I have some concerns about the proposed GSOC tasks as well as some ideas for new tasks. I agree that the Journal needs rethinking. Below are my thoughts (re-thoughts?). Specifically, The Journal is the file system for Sugar. It does not use directories but instead was intended

[Sugar-devel] GSoC proposal status

FYI, as per the discussion at this month's SLOB meeting, I submitted an application to Google Summer of Code on behalf of Sugar Lbs. Lionel has agreed to be the co-admin this summer. We should hear by the end of the month as to whether or not we are accepted and how many slots we get. It is