[Sugar-devel] Journal-like activities (was: Re: [ASLO] Release Read ETexts-19)
On Wed, Mar 17, 2010 at 05:08:08PM -0500, James Simmons wrote: I was looking at the code for Leer Pen Drive and thinking how I could improve on it, and in the process I ended up looking at git.sugarlabs.org at the code for Journal. Apparently that is not the most recent code, I guess you were looking at the journal project (don't have internet access right now, so cannot check the exact name). That's indeed rather old code; the Journal has been integrated into the sugar package. That wouldn't be too surprising except that the Journal Activity can write to a USB or thumb drive. I couldn't figure out how or even where it was doing it, [...] The journal project is part of 0.82. Back then the data store handled removable media. In 0.84+, the data store was rewritten from scratch [1] and only handles the on-disk, native Sugar objects. Handling of traditional (POSIX) file storage (USB sticks, hard disks, etc.) has been moved into the Journal. The code you're looking for is sugar/src/jarabe/journal/model.py. In there, the classes DatastoreResultSet and InplaceResultSet form an abstraction layer over the data store and mounted (POSIX) file systems. but it does seem that you could write an Activity that does everything the Journal does, from writing to mounted media to unmounting it. Almost everything the Journal does can be done in an activity as well. It all boils down to permissions; usually the permissions are based on security considerations. The following actions are implemented (source references are for 0.88): - show item in Journal (D-Bus API) - sugar/src/jarabe/journal/journalactivity.py - D-Bus doesn't allow a second process with the same service name, so not overridable - show object picker (D-Bus API) - sugar/src/jarabe/journal/journalactivity.py - again, D-Bus prevents activities from providing this - mounting/unmounting file systems (e.g. USB sticks) - show new mount points: sugar/src/jarabe/journal/volumestoolbar.py - unmounting: sugar/src/jarabe/view/palettes.py:VolumePalette - mounting (Frame, not Journal): sugar/extensions/deviceicon/volume.py - without Rainbow: - activities are able to mount and umount file systems using gio (resp. gvfs for older systems) - with Rainbow: - gio/gvfs probably refuses to unmount file systems mounted by the Frame from within activities (because the user ids are different) - browsing data store / file systems, reading all entries / files - sugar/src/jarabe/journal/model.py - without Rainbow: - unrestricted - with Rainbow: - currently: - data store access unrestricted - file system access prevented by gio/gvfs permission settings - future: - see P_DOCUMENT / P_DOCUMENT_RO Bitfrost [2] protections - reading a single data store entry / file via Object Picker - sugar-toolkit/src/sugar/graphics/objectchooser.py - unrestricted - writing a single data store entry / file (acquired via Object Picker) - without Rainbow: - unrestricted - with Rainbow: - currently: - data store access unrestricted - file system access prevented by gio/gvfs permission settings - future - unrestricted - writing random data store entries / files - without Rainbow: - unrestricted - with Rainbow: - currently: - data store access unrestricted - file system access prevented by gio/gvfs permission settings - future - subject to P_DOCUMENT Bitfrost [2] protection Bitfrost protections can be disabled, see the Bitfrost specs [2] for details. Sorry for the long mail; it's not just an answer to your questions but also a Rainbow TODO list. :) [1] http://wiki.sugarlabs.org/go/Development_Team/Datastore_Rewrite [2] http://dev.laptop.org/git/security/tree/bitfrost.txt CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Hangman on sugar - Collaboration functionality required
Hey folks, i have used the SugarCollaboration manual to initialize communication between two XO's. What i need is to use this application to handle the game collaboration (multiplayer). Think of each user sending a letter to guess the word. I don't have any idea of how to achieve such functionality, concerning the graphical appearance on each XO. I am the only developer on the project so i need your help folks :) If anyone has the time to hack on my repo is greatfully welcome. The repo: http://bitbucket.org/gakos/hangman.activity/overview/ Just send me your username in bitbucket to add you in the writers list Kind regards, John -- Gakos Ioannis Undergraduate student Computer Engineering Informatics University Of Patras,Greece ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ASLO - Activities with 0.82 compatibility
On Wed, Mar 17, 2010 at 5:36 PM, Walter Bender walter.ben...@gmail.com wrote: I've updated ASLO for Paint, Measure and Log to reflect Martin's tests. Thanks! cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fwd: Porting a game to Sugar
Gary, When I was working on my book I tried using the SUGAR_PROFILE environment variable for the first time. (Previously I had used two computers to test). It worked like a charm on F10 (Sugar .82) but on F11 both instances of sugar-emulator came up as THE SAME USER. Also, when I tried using sugar-jhbuild on F11 I found that it came up as user James Simmons both times, never prompting me to enter a name. I asked this very list about this and was told that from .84 (I think) onwards SUGAR_PROFILE does not work and that I should run either sugar-jhbuild or sugar-emulator as separate Linux users. Someone suggested using ssh -XY for the second user. This did seem to resolve the problem of getting multiple users with the same name. With sugar-jhbuild the second user came up as Annie Simmons (the name on the second Linux user id) without prompting for a name. I wrote up what I was told here: http://en.flossmanuals.net/ActivitiesGuideSugar/SugarCollaboration If this is NOT correct I want to know about it. I would have to say based on my own experience that this at least *seems* to be correct. I don't want to lead John and others like him astray. James Simmons On Wed, Mar 17, 2010 at 8:07 PM, Gary C Martin g...@garycmartin.com wrote: Hi Guys, On 17 Mar 2010, at 14:45, James Simmons wrote: Tomeu and everyone, John is trying to follow my instructions on setting up a collaboration test environment for his Sugar Activity. It isn't working for him on F12 and I couldn't get my own test environment working on F11. All the testing I did for the book was on F10 using Salut with the F10 firewall program disabled. I think my instructions are good as far as they go, but there may be security issues preventing them from working. The only thing I can think of that MIGHT help is to use jabber.sugarlabs.org as a server. It seems to me that has worked for me on F11 in the past. The problem I had with it when it didn't work recently was that I could see others on the network but my instances could not see each other. I believe this was caused by configuration on the server that limited the number of active users. If anyone can help him he'd be grateful. The only things I can suggest are: 1). Use jabber.sugarlabs.org instead of Salut. 2). As a *last* resort, downgrade to F10 and disable the firewall. FWIW: under 0.86.x (pretty sure, certainly 0.84.x) I could test local (gabble) in F11 using sugar-jhbuild by launching two instances of sugar using the SUGAR_PROFILE=. environment variable. I've just tried to retest this now that my F11 environment is running the latest Sugar 0.87.x and it will only launch one (the first) instance. Additional invocations for other SUGAR_PROFILE= values just hang with no console output unless you first kill the previous process (so not much use for testing collaboration anymore). SUGAR_PROFILE=1 ./sugar-jhbuild run sugar-emulator pops up file SUGAR_PROFILE=2 ./sugar-jhbuild run sugar-emulator have to kill above process before it appears Any one else seeing this? I can open a ticket if someone tells me which logs would be of use for debugging this. Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal-like activities (was: Re: [ASLO] Release Read ETexts-19)
Hi James, I am very glad people are exploring alternatives around the Journal. Not sure what your goals are -- would be interesting to hear. Comments - I don't know how pluggable the Journal is, but I'd encourage working on patches to the Journal itself. I don't think a proper activity can take the role of the Journal, as it is pretty special. - There's been interesting discussions around teaching the Journal about it's backup, which is on the XS (if there is one). An exciting idea bandied about was to do something inspired by Apple's Time Machine. I am happy to improve things on the XS side if needed. Aleksey is the current maintainer, he'll probably have suggestions ;-) cheers, m On Thu, Mar 18, 2010 at 10:44 AM, James Simmons nices...@gmail.com wrote: Sascha, No need to apologize for a long email; this is interesting. I'm thinking I'll start working on an improved version of Gabriel's Leer Pen Drive and see where that takes me. I like the idea of the Journal very much, but the implementation of the Journal Activity (if it's correct to call it that) is not what I would like it to be. James Simmons On Thu, Mar 18, 2010 at 8:09 AM, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: On Wed, Mar 17, 2010 at 05:08:08PM -0500, James Simmons wrote: I was looking at the code for Leer Pen Drive and thinking how I could improve on it, and in the process I ended up looking at git.sugarlabs.org at the code for Journal. Apparently that is not the most recent code, I guess you were looking at the journal project (don't have internet access right now, so cannot check the exact name). That's indeed rather old code; the Journal has been integrated into the sugar package. That wouldn't be too surprising except that the Journal Activity can write to a USB or thumb drive. I couldn't figure out how or even where it was doing it, [...] The journal project is part of 0.82. Back then the data store handled removable media. In 0.84+, the data store was rewritten from scratch [1] and only handles the on-disk, native Sugar objects. Handling of traditional (POSIX) file storage (USB sticks, hard disks, etc.) has been moved into the Journal. The code you're looking for is sugar/src/jarabe/journal/model.py. In there, the classes DatastoreResultSet and InplaceResultSet form an abstraction layer over the data store and mounted (POSIX) file systems. but it does seem that you could write an Activity that does everything the Journal does, from writing to mounted media to unmounting it. Almost everything the Journal does can be done in an activity as well. It all boils down to permissions; usually the permissions are based on security considerations. The following actions are implemented (source references are for 0.88): - show item in Journal (D-Bus API) - sugar/src/jarabe/journal/journalactivity.py - D-Bus doesn't allow a second process with the same service name, so not overridable - show object picker (D-Bus API) - sugar/src/jarabe/journal/journalactivity.py - again, D-Bus prevents activities from providing this - mounting/unmounting file systems (e.g. USB sticks) - show new mount points: sugar/src/jarabe/journal/volumestoolbar.py - unmounting: sugar/src/jarabe/view/palettes.py:VolumePalette - mounting (Frame, not Journal): sugar/extensions/deviceicon/volume.py - without Rainbow: - activities are able to mount and umount file systems using gio (resp. gvfs for older systems) - with Rainbow: - gio/gvfs probably refuses to unmount file systems mounted by the Frame from within activities (because the user ids are different) - browsing data store / file systems, reading all entries / files - sugar/src/jarabe/journal/model.py - without Rainbow: - unrestricted - with Rainbow: - currently: - data store access unrestricted - file system access prevented by gio/gvfs permission settings - future: - see P_DOCUMENT / P_DOCUMENT_RO Bitfrost [2] protections - reading a single data store entry / file via Object Picker - sugar-toolkit/src/sugar/graphics/objectchooser.py - unrestricted - writing a single data store entry / file (acquired via Object Picker) - without Rainbow: - unrestricted - with Rainbow: - currently: - data store access unrestricted - file system access prevented by gio/gvfs permission settings - future - unrestricted - writing random data store entries / files - without Rainbow: - unrestricted - with Rainbow: - currently: - data store access unrestricted - file system access prevented by gio/gvfs permission settings - future - subject to P_DOCUMENT Bitfrost [2] protection Bitfrost protections can be disabled, see the Bitfrost specs [2] for details. Sorry for the long mail; it's not just an answer to your questions but also a Rainbow TODO list. :) [1]
Re: [Sugar-devel] Journal-like activities (was: Re: [ASLO] Release Read ETexts-19)
Martin, My peeves with the Journal are: 1). It represents mounted media (USB and SD cards) just like Journal entries. I think Journal entries should be represented like Journal entries and anything in the regular file system should look like a hierarchical file system with folders. Making a USB drive look like the Journal creates false expectations for the user. 2). I'd like to sort Journal entries by something other than time last used, descending. Other than those two things, not much. Gabriel's utility is a gtk.FileChooserWidget that lets you copy files to the clipboard. Mine would use a gtk.Notebook to display two tabs: one for the Journal and one for the file system. It would let you copy files from the file system directly into the Journal. The Journal would be shown as a table with column headings. You could sort by clicking on the column heading. Maybe you could resume Activities from the Journal view. You would not be able to do that from the file system tab. This should be pretty trivial to put together. James Simmons On Thu, Mar 18, 2010 at 10:07 AM, Martin Langhoff martin.langh...@gmail.com wrote: Hi James, I am very glad people are exploring alternatives around the Journal. Not sure what your goals are -- would be interesting to hear. Comments - I don't know how pluggable the Journal is, but I'd encourage working on patches to the Journal itself. I don't think a proper activity can take the role of the Journal, as it is pretty special. - There's been interesting discussions around teaching the Journal about it's backup, which is on the XS (if there is one). An exciting idea bandied about was to do something inspired by Apple's Time Machine. I am happy to improve things on the XS side if needed. Aleksey is the current maintainer, he'll probably have suggestions ;-) cheers, m ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hi; GSoC?
Isaac Dupree wrote: I wonder if this Zero/Sugar project could use some GSOC support, or if there are more useful/important things to work on? I think 0install+Sugar integration would be a very valuable project. The Sugar Labs Oversight Board recently approved a statement that Sugar needs a mechanism for supporting access to non-Sugar dependencies. I think 0install fits the bill well. There are many Sugar developers who are skeptical of 0install's utility for Sugar. I think a GSoC project to add deep 0install support to the Sugar core would be a great way to resolve this issue. If the GSoC project produces a compelling result, then perhaps more developers will be convinced, and the project's code can be committed to Sugar mainline. There are many aspects to 0install, so you might want to focus your efforts on some subset of the 0install system. Some examples: Enable 0share for local sharing of Activities. Use 0install's cryptographic identifiers as indices in a commenting system (This activity is super-fun and never crashed for me.) Add 0mirror support to the school server (XS), possibly integrated with ASLO mirroring. Use 0test to improve Activity reliability across different Sugar versions, distros and hardware. Add 0compile to Sugar for running on unusual architectures (e.g. MIPS) Add 0publish support to the Develop activity, so that users can easily create and publish Activities. Add 0install support to the Journal. and many more --Ben signature.asc Description: OpenPGP digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hangman on sugar - Collaboration functionality required
John, If by SugarColaboration manual you mean the Shared Activities chapter of Make Your Own Sugar Activities! you should follow the instructions to get Batalla Naval from Git and try it out. This uses DBus calls over Telepathy to send the moves back and forth. Since you are just sending letters you might also be able to use the Text Channel like MiniChat does, but the DBus calls method would be considered more correct. James Simmons Date: Thu, 18 Mar 2010 16:21:21 +0200 From: John I. Gakos gakos.ioan...@gmail.com Subject: [Sugar-devel] Hangman on sugar - Collaboration functionality required To: sugar-devel@lists.sugarlabs.org Message-ID: 78f33bdd1003180721o7770ea5cuc88377ad140d0...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hey folks, i have used the SugarCollaboration manual to initialize communication between two XO's. What i need is to use this application to handle the game collaboration (multiplayer). Think of each user sending a letter to guess the word. I don't have any idea of how to achieve such functionality, concerning the graphical appearance on each XO. I am the only developer on the project so i need your help folks :) If anyone has the time to hack on my repo is greatfully welcome. The repo: http://bitbucket.org/gakos/hangman.activity/overview/ Just send me your username in bitbucket to add you in the writers list Kind regards, John ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Journal-like activities (was: Re: [ASLO] Release Read ETexts-19)
On Thu, Mar 18, 2010 at 11:07:04AM -0400, Martin Langhoff wrote: Hi James, I am very glad people are exploring alternatives around the Journal. Not sure what your goals are -- would be interesting to hear. Comments - I don't know how pluggable the Journal is, but I'd encourage working on patches to the Journal itself. I don't think a proper activity can take the role of the Journal, as it is pretty special. - There's been interesting discussions around teaching the Journal about it's backup, which is on the XS (if there is one). An exciting idea bandied about was to do something inspired by Apple's Time Machine. I am happy to improve things on the XS side if needed. Aleksey is the current maintainer, he'll probably have suggestions ;-) Well, I'm thinking more about having something like Journal toolkit to make your-own-journal-for-minutes rather then plugins to journal. So, current Journal could be split into not UI Shell (dbus)service, that will handle all privileged operations like mounts, non-ds sources, object chooser, etc and Journal activity(among others) that uses Shell. (i.e. back to the future:) In fact for Library-2 I'm planing something similar: * Journal, construction kit, will incapsulate journal specific stuff which is sugar core agnostic, will depend only on Shell dbus API and ds dbus/fs api * Shell service, I hope such dbus service will work in non root environment * Activity itself cheers, m On Thu, Mar 18, 2010 at 10:44 AM, James Simmons nices...@gmail.com wrote: Sascha, No need to apologize for a long email; this is interesting. I'm thinking I'll start working on an improved version of Gabriel's Leer Pen Drive and see where that takes me. I like the idea of the Journal very much, but the implementation of the Journal Activity (if it's correct to call it that) is not what I would like it to be. James Simmons On Thu, Mar 18, 2010 at 8:09 AM, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: On Wed, Mar 17, 2010 at 05:08:08PM -0500, James Simmons wrote: I was looking at the code for Leer Pen Drive and thinking how I could improve on it, and in the process I ended up looking at git.sugarlabs.org at the code for Journal. Apparently that is not the most recent code, I guess you were looking at the journal project (don't have internet access right now, so cannot check the exact name). That's indeed rather old code; the Journal has been integrated into the sugar package. That wouldn't be too surprising except that the Journal Activity can write to a USB or thumb drive. I couldn't figure out how or even where it was doing it, [...] The journal project is part of 0.82. Back then the data store handled removable media. In 0.84+, the data store was rewritten from scratch [1] and only handles the on-disk, native Sugar objects. Handling of traditional (POSIX) file storage (USB sticks, hard disks, etc.) has been moved into the Journal. The code you're looking for is sugar/src/jarabe/journal/model.py. In there, the classes DatastoreResultSet and InplaceResultSet form an abstraction layer over the data store and mounted (POSIX) file systems. but it does seem that you could write an Activity that does everything the Journal does, from writing to mounted media to unmounting it. Almost everything the Journal does can be done in an activity as well. It all boils down to permissions; usually the permissions are based on security considerations. The following actions are implemented (source references are for 0.88): - show item in Journal (D-Bus API) - sugar/src/jarabe/journal/journalactivity.py - D-Bus doesn't allow a second process with the same service name, so not overridable - show object picker (D-Bus API) - sugar/src/jarabe/journal/journalactivity.py - again, D-Bus prevents activities from providing this - mounting/unmounting file systems (e.g. USB sticks) - show new mount points: sugar/src/jarabe/journal/volumestoolbar.py - unmounting: sugar/src/jarabe/view/palettes.py:VolumePalette - mounting (Frame, not Journal): sugar/extensions/deviceicon/volume.py - without Rainbow: - activities are able to mount and umount file systems using gio (resp. gvfs for older systems) - with Rainbow: - gio/gvfs probably refuses to unmount file systems mounted by the Frame from within activities (because the user ids are different) - browsing data store / file systems, reading all entries / files - sugar/src/jarabe/journal/model.py - without Rainbow: - unrestricted - with Rainbow: - currently: - data store access unrestricted - file system access prevented by gio/gvfs permission settings - future: - see P_DOCUMENT / P_DOCUMENT_RO Bitfrost [2] protections - reading a single data store entry / file via Object Picker -
Re: [Sugar-devel] Hi; GSoC?
On Thu, Mar 18, 2010 at 11:43:22AM -0400, Benjamin M. Schwartz wrote: Isaac Dupree wrote: I wonder if this Zero/Sugar project could use some GSOC support, or if there are more useful/important things to work on? I think 0install+Sugar integration would be a very valuable project. The Sugar Labs Oversight Board recently approved a statement that Sugar needs a mechanism for supporting access to non-Sugar dependencies. I think 0install fits the bill well. There are many Sugar developers who are skeptical of 0install's utility for Sugar. I think a GSoC project to add deep 0install support to the Sugar core would be a great way to resolve this issue. If the GSoC project produces a compelling result, then perhaps more developers will be convinced, and the project's code can be committed to Sugar mainline. There are many aspects to 0install, so you might want to focus your efforts on some subset of the 0install system. Some examples: Enable 0share for local sharing of Activities. Use 0install's cryptographic identifiers as indices in a commenting system (This activity is super-fun and never crashed for me.) Add 0mirror support to the school server (XS), possibly integrated with ASLO mirroring. Use 0test to improve Activity reliability across different Sugar versions, distros and hardware. Add 0compile to Sugar for running on unusual architectures (e.g. MIPS) Add 0publish support to the Develop activity, so that users can easily create and publish Activities. Add 0install support to the Journal. Just a sumary what was already done in 0sugar: * 0sugar tool [1], something like high level packaging wraper aroud pure 0install (e.g. creating rpm from spec files) - convenient tool to wrap projects exsited/packaged/new to 0install feeds - build binary based projects in maintener environment and in users environment as well - hosting 0sugar projects, by one commnd 0sugar project will be uploaded to the right place and be ready for using * 0sugar-inject and 0sugar-launch tools [2], let activity developers use 0sugar project as external dependencies and if there is such need, budnle all deps to xo, it already works well for a half of ASLO activities Some points to do: * Bulild farm for binary based 0sugar projects - since building 0sugar projects should be not common practice (in most cases there is not need in 0sugar itest, in other cases dependency could be python based or rely on distro packages) we can setup such build farm in our environment and integrate it w/ 0sugar tool (by one command project will be send to build farm) - reuse existed build farms e.g. opensuse's, could be not useful e.g. in cases when we need build recent pygame for XO-1 env (all exsted distros don't contain fc9 versions and recent pygame at the same time) * Turn activity bundles into 0install feeds [3] e.g. it gives us a chance to preserve fully bundled .xo i.e. 0activities could obviousle distinguished from .xo ..and like was laready mentioned.. * closer integration of 0sugar and shell, not sure if start hacking current Journal is the right way [4] - full cycle of using 0sugar activities - 0sugar integration - ... * ... [1] http://wiki.sugarlabs.org/go/Documentation_Team/Services/Activity_Developers_Guide [2] http://wiki.sugarlabs.org/go/Documentation_Team/Services/Service_Developers_Guide [3] http://wiki.sugarlabs.org/go/Features/Zero_Sugar_Activities [4] http://lists.sugarlabs.org/archive/sugar-devel/2010-March/023047.html -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] GSoC Ideas
I want to participate at GSoC for Sugar. What idea could I recommend? http://socghop.appspot.com/gsoc/program/accepted_orgs/google/gsoc2010 -- Carlos Mauro Cárdenas Fernández Ingeniero de Sistemas 4582877 980525716 Creemos en el amor de los Seres Humanos http://forpapers.blogspot.com/ http://unimauro.blogspot.com/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar Labs Accepted as GSoC 2010 Organisation
Chris - You must have known something! Sugar Labs is part of the fold. [1] Thanks all for helping me along. Now the real fun starts :) Tim @timClicks [1] http://socghop.appspot.com/gsoc/program/accepted_orgs/google/gsoc2010 On 13 March 2010 12:11, Chris Ball c...@laptop.org wrote: Hi Tim, Sugar Labs application for Google Summer of Code 2010 has been accepted. Wow, that was quick. Many congrats and thanks! I'm not sure exactly on the politics of the situation, but my personal feeling is that we should be quite encouraging of supporting OLPC projects. That sounds great; I'd be happy to chat more about this. - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Ticket #245 - More information needed
James Cameron (qu...@laptop.org) wrote: G'day Kenny, Thanks for taking ownership of the ticket. You mentioned you didn't know if the same behaviour is being reproduced on the XO, so I did some testing for you and added my findings to the ticket. Hope that helps. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Hi James, The comparison table you've created is excellent! Thank you very much for your time. -- Kenny Meyer Software Geek | http://kenny.alwaysdata.net Shoot for the moon, even if you miss, you'll land amongst the stars.. - Les Brown signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hi; GSoC?
On 03/18/10 11:43, Benjamin M. Schwartz wrote: Isaac Dupree wrote: I wonder if this Zero/Sugar project could use some GSOC support, or if there are more useful/important things to work on? I think 0install+Sugar integration would be a very valuable project. The Sugar Labs Oversight Board recently approved a statement that Sugar needs a mechanism for supporting access to non-Sugar dependencies. I think 0install fits the bill well. There are many Sugar developers who are skeptical of 0install's utility for Sugar. I think a GSoC project to add deep 0install support to the Sugar core would be a great way to resolve this issue. If the GSoC project produces a compelling result, then perhaps more developers will be convinced, and the project's code can be committed to Sugar mainline. Was there a discussion I could read, about, conversely, how well the (non-Zero) .xo packaging is doing and how easily it could be extended to meet some of our (Sugar's) needs? -Isaac ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Hi; GSoC?
Isaac, Welcome, and thanks for setting such a good example for other potential GSoC participants. I wonder if this Zero/Sugar project could use some GSOC support, I agree with Ben that 0install-related Sugar work likely encompasses at least one good and worthy GSoC project. First, it's a good springboard toward networking, cryptography, and UI design, if you have interests in any of these areas. Second, you'll get to meet and to work with maintainers from both 0install and Sugar, so it will be a great open-source educational experience. Thrid, it's got an exceptionally direct educational benefit; namely, tremendously improved access to software for connected Sugar learners like those in Uruguay, Paraguay, and elsewhere. or if there are more useful/important things to work on? First, *definitely* take Walter up on his offer of advice. (In fact, if you're both willing, please take notes and publish them; I'd like learn from your conversation!) Second, take a look at ideas that people have expressed interest in mentoring in the past. Many of them are still relevant. Third, talk to people visiting OLPC or Sugar deployments. Bernie Innocenti, Daniel Drake, Bryan Berry, Caroline Meeks, and Simon Schampijer are all great people to track down. (And there are many more, especially if you're interested in making friends in the southern hemisphere.) Finally, here's a short list of various people's essays and emails on exciting technical problems and potential solutions from which you (or others) might fashion an interesting and useful project: networking: http://wiki.laptop.org/go/Network2/Paper http://wiki.laptop.org/go/Network_principles platform: http://dev.laptop.org/~mstone/draft-sugar-core-priorities-01.txt http://lists.sugarlabs.org/archive/sugar-devel/2008-July/007441.html http://lists.laptop.org/pipermail/devel/2008-June/015838.html journal+datastore: http://wiki.laptop.org/go/Journal2 http://wiki.sugarlabs.org/go/Design_Team/Designs/Journal http://wiki.laptop.org/go/Olpcfs security: http://dev.laptop.org/git/security/plain/bitfrost.txt http://wiki.laptop.org/go/Rainbow/Next_Steps More questions? Regards, Michael ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
