Changes

Jump to navigation Jump to search
Add "Sugar Local Lab" idea
Line 22: Line 22:     
"A major effort is underway to port Sugar activities from Python to Javascript in anticipation of offering them in an Android environment. There are certainly many new activities in either Python or Javascript (or both) which could be done. In the area of Sugar activities, there is another effort to port Python Sugar activities from GTK to GTK+3. One specific area of interest is collaboration. Our current technique is being deprecated and so some work is needed to re-implement activities using a collab-wrap which provides a simpler api for activities which support collaboration. As volunteers, in the end,  you should tackle what interests you. Personally, I would like to see more effort on new development; however, it is hard to deny the need for porting." http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052036.html [[User:Davelab6|Davelab6]] ([[User talk:Davelab6|talk]])
 
"A major effort is underway to port Sugar activities from Python to Javascript in anticipation of offering them in an Android environment. There are certainly many new activities in either Python or Javascript (or both) which could be done. In the area of Sugar activities, there is another effort to port Python Sugar activities from GTK to GTK+3. One specific area of interest is collaboration. Our current technique is being deprecated and so some work is needed to re-implement activities using a collab-wrap which provides a simpler api for activities which support collaboration. As volunteers, in the end,  you should tackle what interests you. Personally, I would like to see more effort on new development; however, it is hard to deny the need for porting." http://lists.sugarlabs.org/archive/sugar-devel/2016-April/052036.html [[User:Davelab6|Davelab6]] ([[User talk:Davelab6|talk]])
 +
 +
From sugar-devel bug thread today: I actually like the idea of a "Sugar Lab On A Stick" which is to say, if everything was in [a] distribute version control system repo[s], then the repo[s] could be distributed to mostly-offline communities (using outernet.is or similar) who could be productive for say 6 weeks or 6 months, and then their commits could find their way back to the central Sugar Labs mothership repos - eg, via sneaker-net from village to town and then uploaded. For that I think Github won't work, because the PR and issue discussions are not kept in the repo. The best self-contained DVCS solution I've seen to this is, as I said, www.fossil-scm.org, although there are some git-based systems. I don't think of this as a 2016 or 17 goal, but I am noting it here as a long term goal. [[User:Davelab6|Davelab6]] ([[User talk:Davelab6|talk]])
    
== GNU General Public License only? ==
 
== GNU General Public License only? ==

Navigation menu