Re: [Sugar-devel] [IAEP] [ANNOUNCE] Bug tracker housekeeping
On 05/25/2009 12:25 PM, Martin Langhoff wrote: > On Fri, May 22, 2009 at 4:54 PM, Simon Schampijer wrote: >> Submitters: Please go through all the open bugs you have submitted. If > > BTW, if there's any guidance for the test team in Bxl on how to tag > the bugs found against latest SoaS, we'll be happy to follow... > > This search shows most (all?) the bugs we filed... > http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&milestone=soas_fossvt&distribution=SoaS > > cheers, > > > > m The bug tracker housekeeping was meant mostly for Sugar 0.84-0.86. We want to do the same for Soas when it is released. http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap In general - of course the work flow I described above would be good to do on a regular basis - chacking that the tickets I filed are valid, someone has followed up:) Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Help activity
Summary: There seems to already be Sugar 0.84 content translated into various languages on flossmanuals.net that someone could "remix" as HTML and link to from the Browse activity's home page. On Mon, May 25, 2009 at 5:41 AM, Caroline Meeks wrote: > We talked a bit about the Help Activity in Paris. I've taken our discussion > and written it up here: http://wiki.sugarlabs.org/go/Activities/Help I'm confused, is this related to the current OLPC Help (activity) in OLPC release 8.2 which is hosted at git.sugarlabs.org, or a new activity? That page says "I think it should be a blurb about being a community project, invitation to ask a question and a link to the manual in a reader." All that information belongs on the Browse home page! The Goals listed for the Help activity seem like the goals for a Sugar home page. Just have a "Getting help" section of the home page. "A manual in a reader"? Surely an HTML manual in a browser is the way to go.. > Please take a look and edit this spec and start to think about how it should > be implemented. I don't understand Help as an activity, Help is useful info organized in HTML pages. The current OLPC help activity starts a hulahop.webview that displays 'help/XO_Introduction.html' The benefit is it is a single-purpose activity with its own '(?)' icon in the Home view, and it lacks some browser chrome such as the location field and View menu. But those features become a confusing hindrance the moment you follow a link from Help to an external web site. Perhaps it would be better just to put a link to the local help files on the Browse home page as I suggest above, and/or provide a Journal entry for the local help content, especially when and if Browse gets multiple tabs. If the distinction between activities and library content goes away then there's even less reason for a standalone help activity. If you have a connection to the net, you should probably just go to the latest up-to-date online help for your software, e.g. http://www.laptop.org/manual or http://en.flossmanuals.net/bin/view/Sugar/8_4/TheJournal On Mon, May 25, 2009 at 5:17 PM, Bastien wrote: > If "translating" equates to "translating the flossmanuals" I think it's > worth anyway, whether these pages goes into the Help activity or not. The Flossmanuals.net site seems currently available in English, nl (Dutch), and fa (Persian), but it can host translations in other languages, see http://en.flossmanuals.net/FLOSSManuals/TranslatingAManual . I just realized that parts of the Sugar manual have been translated, e.g. http://translate.flossmanuals.net/bin/view/Sugar_es/WhatIsAnActivity !! > Idea: why not have a mediawiki_syntax2sugar_display converter? Then we > could create a Help activity based on content from the Sugar wiki. Or a > Tutorials activity based on all tutorials from the wiki. Or others > WikiBrowse activities based on other slices of the WikiPedia. Surely by "sugar display" you just mean HTML? In which case there are lots of tools to turn MediaWiki into HTML, several of which have been used for OLPC content and activities. Check out http://wiki.laptop.org/go/Wikislices http://wiki.laptop.org/go/WikiBrowse http://wiki.laptop.org/go/Wikibooks http://sugarlabs.org/go/Activities/InfoSlicer Note that the FlossManuals site uses TWiki, not MediaWiki. There are pros and cons to this. It seems incredibly simple to use http://en.flossmanuals.net/remix to export as HTML; I assume that's how someone created the current OLPC Help activity and online manual and PDF. But the division between the documentation and the wiki is unfortunate, and could be avoided if say wiki.sugarlabs.org had a Category:Sugar_help that people carefully maintain and occasionally turn into a Help manual using MediaWiki tools. MediaWiki's history and [Compare selected revisions] can help dedicated bilingual translators keep a translation in sync with updates to a "master" page. E.g. click on the "cambios" link in the translation header of http://wiki.laptop.org/go/Participate/lang-es . I don't know if FlossManuals/TWiki has advanced template support to do something similar. People are already working on Sugar/8_4 (sic) files on flossmanuals, there was discussion of a Sugar 0.84 manual in http://lists.laptop.org/pipermail/library/2009-March/thread.html http://wiki.sugarlabs.org/go/Sugar_help points users to http://en.flossmanuals.net/Sugar , but I believe this is for Sugar 0.82. (A while ago I complained that version info is not available in flossmanuals along with many other presentation and style problems.) Maybe someone can periodically create a Remix of the current state of these "8_4" chapters and turn it into library content, an activity (maybe create a Sugar_8_4 branch of the existing http://git.sugarlabs.org/projects/help ), and/or upload it to a directory on sugarlabs.org. Maybe someone already has; people seem to be working on stuff that isn't noted on the obvious wiki pages like http://wiki.s
Re: [Sugar-devel] Who wants to adopt the Clock activity?
Hi Pierre, On 26 May 2009, at 02:24, Pierre Métras wrote: > Hi Gary, > > I've read in a recent post in the Sugar IAEP list where you > explained how to > make an activity adopted by the Activity Team. Are you part of this > team or > how can I contact them without having to create a new account to be > able to > post once on the IAEP list? > > Last year, I've developed the Clock Activity: > http://wiki.laptop.org/go/Clock_activity > > It's a simple clock activity, with various displays: digital, > analog, simple > or complex. There is an option to enable the talking clock mode to > help the > child learn how to read the time, in French, English and Spanish. > This activity has been deployed in Peru in a previous version. > > I've no more the time to maintain it and to move it to SugarLabs. I > would like > to find another maintainer or maintainers to complete the move to > SugarLabs > and eventually update the code. Thanks for your email! Please consider Clock now adopted by the Activity team :-) I'll migrate it over to the Sugar Labs infrastructure in the next few days and make sure it gets into pootle. > I had planned a few changes: > > - Put the PO files into Pootle to support more languages. The > talking feature > is based on "time grammar" rules defined in the PO files. A small > inference > engine is able to use these rules to write the time in full letters. > This > allows to support new languages, written and spoken, without > touching the > code. But it put the burden of creating the "time grammar" rules to > the > translator. Since I didn't complete the Pootel integration, I don't > know if > this design choice was valid... > > - The talking feature spawn a espeak process to read the time aloud. > I've seen > that Sugar now integrates the espeak library and I think that > calling these > methods would be a lighter solution for the XO constrained system. Understood, seems like a nice feature, I can't initially offer more than basic migration and maintenance, but depending on time (no pun intended) I'll try to take a look at this and/or try and encourage other community members to help out (perhaps someone working in espeak looking to leverage/test their work). > - There are a few tickets opened for the activity: > http://bugs.laptop.org/ticket/9216 > http://bugs.laptop.org/ticket/9215 OK, will migrate these to dev.sugarlabs.org once the a Clock component is added. > - Last, the activity has to be tested against the 8.2.1 code base. > Future > plans were to see if the Clock could be integrated into the Sugar > border... Thanks, will also test in current Sugar builds and various environments before releasing a bundle on activities.sugarlabs.org. Think we have the frame based clock covered now, here are a some working screen shots from Martin Dengler's frame device: http://www.martindengler.com/tmp/screenshot_clock_device_frame-06_a6_a689bf1e-3f34-4da3-afed-aa910ab4f677.png http://www.martindengler.com/tmp/screenshot_clock_device_frame-07_84_841da15d-9bd7-4fe4-aada-8e8ab723f806.png http://www.martindengler.com/tmp/screenshot_clock_device_frame-08_4b_4ba1059e-4db9-4f22-8661-7916f6a167f8.png And some recent mockups from Eben: https://dl.getdropbox.com/u/1085311/clock_digital_basic.jpg https://dl.getdropbox.com/u/1085311/clock_digital_settings.jpg https://dl.getdropbox.com/u/1085311/clock_digital_calendar.jpg https://dl.getdropbox.com/u/1085311/clock_analog.jpg > I'm ready to assist and help the future maintainer, but no more time > to > develop by myself. Of course, he can decide what the future of this > activity > will be! Once the source is in Gitorious it's very easy to clone the repository, hack about on some ideas, and then if they works out request a merge. So if you have the occasional slice of free time in the future it would be easy (and you'd be most welcome) to dip back in again with minimal commitment. > Can you tell me who to contact to have this activity adopted? Congratulations, you got lucky with your first email ;-) Kind Regards, --Gary > Regards > Pierre Métras ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Help activity
Hi Caroline, Caroline Meeks writes: > We talked a bit about the Help Activity in Paris. I've taken our discussion > and written it up here: http://wiki.sugarlabs.org/go/Activities/Help > > Please take a look and edit this spec and start to think about how it should > be > implemented. Thanks. > It may not be worth translating it before it is rewritten. If "translating" equates to "translating the flossmanuals" I think it's worth anyway, whether these pages goes into the Help activity or not. Idea: why not have a mediawiki_syntax2sugar_display converter? Then we could create a Help activity based on content from the Sugar wiki. Or a Tutorials activity based on all tutorials from the wiki. Or others WikiBrowse activities based on other slices of the WikiPedia. Thanks, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Simplifying sugar-jhbuild
Tomeu Vizoso writes: > On Sun, May 24, 2009 at 13:31, Bastien wrote: >> +1 on the overall. >> >> Building Sugar from source should be as easy as: >> >> , >> | ~$ git://git.sugarlabs.org/sugar-core/mainline.git >> | ~$ ./configure >> | ~$ make >> | ~$ sudo make install >> ` > > Well, that works for the sugar shell provided you have all the > dependencies installed. The point of jhbuild is precisely to get you > an environment where all the dependencies of the software you are > interested in are installed without breaking your regular desktop. Sorry to be dull here... IIUC, what you describe is the main difference between jhbuild and, say, apt-get install sugar on Ubuntu: in the later case, dependancies are taken care of by the .deb package whereas in the jhbuild case they are all integrated in the jhbuild source? Does that make sense? > Please note that we don't need to use sudo as all dependencies are > installed in a user-writable directory. Ok. Thanks for the explanations. -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] introduction
Hi Martin, On 25 May 2009, at 20:24, Marten Vijn wrote: > Following http://wiki.sugarlabs.org/go/Activity_Team/Getting_Involved > > 1. User:Marten refers to me > 2. my public_key is in User:Marten > 3. I am on Activity Team/Contacts (I was not sure to me add meself) Welcome aboard! > 4. For the people that don't know me yet (I had the benefit of dragging myself over to SugarCamp :-) > Hi I am Marten, I live in Leiden, The Netherland. I have a girlfiend, > two kids (2,5 and 4,7 years). I was a physiotherapist and occupational > therapist before became a unix and net sysadmin. I run a XO-repaering > service and organize a camp. I may have noticed my English brake every > comple of lines. I have dyslexia, pls try to read want I mean. (In a > way > you lucky my Dutch is worse.) > > pls read more http://martenvijn.nl > > http://wiki.sugarlabs.org/go/Activity_Team/TODO > >> From here as a non-developer I seem to really get lost. > To not scare non-tech people I would: > - move Community Task more up +1 thanks, a very good idea (I'll go ahead and move it to the top, I need to update some of those items now anyway). > - create 5 simple tasks than can do done repetitive: > - download,burn,boot,give feedback > - hardware reports > - documentation for BIOS in cd-rom and usbdrive I think these items are perhaps more in line with the Bug Squad team, perhaps they would be better there? H, perhaps there are some other simple tasks we can come-up with for the Activity Team? > - reviewing Activities Yes I like this! It's a good way to get to know what's out there already. There are a couple of places I feel reviews should be going: 1) For reviews aiming at other users, at http:// activities.sugarlabs.org each Activity supports a 1-5 star rating, a comment field, and if you want, there is also a 'detailed review' submission form. This should be the place to go if you want to provide feedback for other Sugar users (kids/teachers/parents/the rest of us) to see. These input forms are not used that much yet, so if you do find any bugs or incorrect Mozilla text, please open a ticket on dev.sugarlabs.org and use the component "activities.sugarlabs.org" so we can get it fixed. 2) For general reviews of a more technical nature (more aimed at other developers than users), most currently supported Activities have an http://wiki.sugarlabs.org/go/Activities/ wiki page. A "Reviews" section could be added at the bottom of an Activities page; I think it would also be good to email such feedback directly to this list so that other developers can easily make use of it. 3) For specific Activity developer bugs/feature-requests/suggestions, the very best place is to open a trac ticket (dev.sugarlabs.org), or if that looks too scary, email to this list (sugar-devel@lists.sugarlabs.org ) and someone will file it for you. > - writing instruction-sets/PR-materials ? You might also want to look at http://en.flossmanuals.net/Sugar if the goal is more 'book like' releases of static information. Alternatively more general/dynamic instructions could probably go to the http://wiki.sugarlabs.org/go/Activities/ wiki page for each Activity (and could easily be picked up again at a later time if static 'book like' snapshots need to be pulled together for some formal release set of activities). > - Roadmaps for LocalSugarLabs (creating UserBase) Is this aimed at finding other interested local developers, you know for beer and high bandwidth hacking time? > Can I shuffle a bit on the TODO list to make more easy for new coming > people? Yes please do! Thanks for all the feedback. Regards, --Gary > cheers, > Marten > > -- > http://martenvijn.nl Marten Vijn > http://martenvijn.nl/trac/wiki/soas Sugar on a Stick > http://bsd.wifisoft.org/nek/ The Network Event Kit > http://har2009.org 13th-16th August > http://opencommunitycamp.org 26th Jul - 2nd August > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Help to Find the PO file of Some Activities to able me to Translate Them
Well the main thing here is about demoing... I've taken it upon myself to package about 50 activities... including fructose and glucose... now... we have things like flash which isnt an xo bundle, though many people believe it could/should be, and that would/should be considered a honey app, but it must be installed via rpm Really the only process required with the new jhconvert alexey has been working on is upload to git, then jhconvert creates the packages for the all the distros, including the .xo bundles... so really we want to make it as easy as authors not having to worry about packaging at all... just about uploading their latest source to git.sugarlabs.org, the only place the source really needs to be... we can automate the rest... but your process is currently the only sane thing I've seen written up and it'd be a shame to loose it in the anals of archived emails... so better wiki than nothing, no? kind Regards, David Van Assche On Mon, May 25, 2009 at 6:15 PM, Gary C Martin wrote: > On 25 May 2009, at 12:33, David Van Assche wrote: > > Super... that methodology should be written up some place as its a great >> guide to follow... >> > > I'd much rather try and find some agreement to cut un-necessary steps, > rather than to wikify/formalise it and push every unfortunate Activity > author through the same sausage factory! :-) > > /me puts on tinfoil hat and asbestos socks > > I've still not heard a good argument for why Activity authors currently > need to create two bundles with identical source content (one .xo zip and > one .bz2), upload them to two different locations, and document them in > several different places. It's really easy to get out of sync. I'm also > still not convinced about the sanity of distros needing to package up each > individual Activity (other than perhaps sucrose as one collection). If, for > a moment, you think of Sugar as a Firefox, and Activities as Addons, does > each distro really consider packaging up every Addon kicking about for > Firefox? Once a Sugar release and its platform dependancies are yum, > aptitude, or whatever installed; the Sugar UI should then be the one to > add/update additional Activities (via Browse as currently, or via a future > update control panel checking with activity.sugarlabs.org). > > Regards, > --Gary > > > David >> >> On Sun, May 24, 2009 at 5:32 PM, Gary C Martin >> wrote: >> Hi David, >> >> >> On 24 May 2009, at 11:47, David Van Assche wrote: >> >> Overall it would be nice if we had an activitiy matrix that showed the >> stages of projects. >> >> The Activity Team have been making contact with past authors, slowly, >> slowly we're moving along even if it means adopting extra activities >> ourselves: >> >> >> http://wiki.sugarlabs.org/go/Activity_Team/Activity_Status >> >> The best thing folks can do If they have a favourite activity that is not >> yet migrated to Sugar Labs infrastructure is make some noise about it. Email >> the IAEP and/or sugar-devel and advocate or ask about it, email the >> author/s, see if they are still working on it or have future plans. Many >> activity developers seem to think no one is interested/using their work and >> often seem pleasantly surprised when they get an email about their past >> efforts. >> >> >> This would be helpful to show what people could work on to. Something >> like, name of activity on one side, and on the other stage (planning, >> pre-source, alpha, beta, rc, release, packaged, xo bundled, translated) >> Something along those lines, but I'm sure someone can come up with a better >> matrix. If this was up at some place, we could know pretty quickly what >> people could be working on. It could even be split by distro too... The idea >> came to me because there are a ton of git projects with no code in them. >> >> If there are git projects with no code in them, what makes you think the >> developer will edit another page somewhere else with project status >> information! ;-b >> >> With my activity developer hat on, I do find it a pain how many seemingly >> random places there are to work on when releasing a new version, even more >> for a new project, or migrated one. My check-list/todo-list is something >> like: >> >> If it's a new project: >> >> - Create a Gitorious project repository for it http://git.sugarlabs.org/ and >> start hacking on your code >> >> - Request a trac component for you activity at http://dev.sugarlabs.org/ >> >> - Open a trac ticket to request addition to Pootle (if your >> strings/release is reasonably mature/ready) >> >> - Create a page at http://wiki.sugarlabs.org/go/Activities/ >> >> If it's a new release: >> >> - Update your activities wiki page at >> http://wiki.sugarlabs.org/go/Activities/ >> >> - Upload the .xo bundle, screenshots, notes to >> http://activities.sugarlabs.org/ >> >> - Upload .bz2 source to shell.sugarlabs.org /upload/sugar/sources/honey >> >> - Edit wiki table >> http://wiki.sugarlabs.org/go/Development_Team/Source_Code a
[Sugar-devel] introduction
Following http://wiki.sugarlabs.org/go/Activity_Team/Getting_Involved 1. User:Marten refers to me 2. my public_key is in User:Marten 3. I am on Activity Team/Contacts (I was not sure to me add meself) 4. For the people that don't know me yet Hi I am Marten, I live in Leiden, The Netherland. I have a girlfiend, two kids (2,5 and 4,7 years). I was a physiotherapist and occupational therapist before became a unix and net sysadmin. I run a XO-repaering service and organize a camp. I may have noticed my English brake every comple of lines. I have dyslexia, pls try to read want I mean. (In a way you lucky my Dutch is worse.) pls read more http://martenvijn.nl http://wiki.sugarlabs.org/go/Activity_Team/TODO >From here as a non-developer I seem to really get lost. To not scare non-tech people I would: - move Community Task more up - create 5 simple tasks than can do done repetitive: - download,burn,boot,give feedback - hardware reports - documentation for BIOS in cd-rom and usbdrive - reviewing Activities - writing instruction-sets/PR-materials ? - Roadmaps for LocalSugarLabs (creating UserBase) Can I shuffle a bit on the TODO list to make more easy for new coming people? cheers, Marten -- http://martenvijn.nl Marten Vijn http://martenvijn.nl/trac/wiki/soas Sugar on a Stick http://bsd.wifisoft.org/nek/ The Network Event Kit http://har2009.org 13th-16th August http://opencommunitycamp.org 26th Jul - 2nd August ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Help to Find the PO file of Some Activities to able me to Translate Them
On 25 May 2009, at 12:33, David Van Assche wrote: > Super... that methodology should be written up some place as its a > great guide to follow... I'd much rather try and find some agreement to cut un-necessary steps, rather than to wikify/formalise it and push every unfortunate Activity author through the same sausage factory! :-) /me puts on tinfoil hat and asbestos socks I've still not heard a good argument for why Activity authors currently need to create two bundles with identical source content (one .xo zip and one .bz2), upload them to two different locations, and document them in several different places. It's really easy to get out of sync. I'm also still not convinced about the sanity of distros needing to package up each individual Activity (other than perhaps sucrose as one collection). If, for a moment, you think of Sugar as a Firefox, and Activities as Addons, does each distro really consider packaging up every Addon kicking about for Firefox? Once a Sugar release and its platform dependancies are yum, aptitude, or whatever installed; the Sugar UI should then be the one to add/update additional Activities (via Browse as currently, or via a future update control panel checking with activity.sugarlabs.org). Regards, --Gary > David > > On Sun, May 24, 2009 at 5:32 PM, Gary C Martin > wrote: > Hi David, > > > On 24 May 2009, at 11:47, David Van Assche wrote: > > Overall it would be nice if we had an activitiy matrix that showed > the stages of projects. > > The Activity Team have been making contact with past authors, > slowly, slowly we're moving along even if it means adopting extra > activities ourselves: > > >http://wiki.sugarlabs.org/go/Activity_Team/Activity_Status > > The best thing folks can do If they have a favourite activity that > is not yet migrated to Sugar Labs infrastructure is make some noise > about it. Email the IAEP and/or sugar-devel and advocate or ask > about it, email the author/s, see if they are still working on it or > have future plans. Many activity developers seem to think no one is > interested/using their work and often seem pleasantly surprised when > they get an email about their past efforts. > > > This would be helpful to show what people could work on to. > Something like, name of activity on one side, and on the other stage > (planning, pre-source, alpha, beta, rc, release, packaged, xo > bundled, translated) Something along those lines, but I'm sure > someone can come up with a better matrix. If this was up at some > place, we could know pretty quickly what people could be working on. > It could even be split by distro too... The idea came to me because > there are a ton of git projects with no code in them. > > If there are git projects with no code in them, what makes you think > the developer will edit another page somewhere else with project > status information! ;-b > > With my activity developer hat on, I do find it a pain how many > seemingly random places there are to work on when releasing a new > version, even more for a new project, or migrated one. My check-list/ > todo-list is something like: > > If it's a new project: > > - Create a Gitorious project repository for it http://git.sugarlabs.org/ > and start hacking on your code > > - Request a trac component for you activity at http://dev.sugarlabs.org/ > > - Open a trac ticket to request addition to Pootle (if your strings/ > release is reasonably mature/ready) > > - Create a page at http://wiki.sugarlabs.org/go/Activities/ name> > > If it's a new release: > > - Update your activities wiki page at > http://wiki.sugarlabs.org/go/Activities/ > > > - Upload the .xo bundle, screenshots, notes to > http://activities.sugarlabs.org/ > > - Upload .bz2 source to shell.sugarlabs.org /upload/sugar/sources/ > honey > > - Edit wiki table http://wiki.sugarlabs.org/go/Development_Team/Source_Code > and make sure it's pointing to your latest .bz2 > > - Edit wiki table http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap > to get it on Soas > > - Write a [RELEASE] email and send it to > sugar-devel > > If the project is migrating from olpc infrastructure: > > - Migrate git repository from http://dev.laptop.org/ > > - Migrate open trac tickets from http://dev.laptop.org/ > > - Track down relevant wiki.laptop.org pages and indicate the migration > > - For deployed activities make sure relevant > http://wiki.laptop.org/go/Activities > page version templates point to the correct/latest working bundles. > > I'm sure I missed a step or two, but I think you get the picture! > > > On Sat, May 23, 2009 at 1:51 PM, Tomeu Vizoso > wrote: > Hi Mohammad, > > On Tue, May 19, 2009 at 06:36, Mohammad Hamed > wrote: > > Dear Software Translators, > > > > Could you please tell me how can I translate some Activities like: > > Physics, X2O, WFP, Implode, Conozco Uruguay to my language? > > FWIW: Having spoken with Alex Leve
Re: [Sugar-devel] Sugar Developer MINUTES
On 05/25/2009 11:51 AM, Walter Bender wrote: > Tomeu was quicker in his response than me... > > As Simon said, the current plan for *both* the XO-1 and the XO-1.5 in > regard to Sugar support is to build upon the work that OLPC and the > Fedora communities are doing towards getting a stock Fedora > distribution running on the hardware. Sugar would be packaged on top > of that. The current expectation is that this would happen in the F12 > time frame, coincident with the planned Sugar 0.86 release. As far as > porting Sugar 0.84 natively to the XO-1 hardware, this would require a > fair amount of work--beyond simply copying the Sugar files. I am > unaware of anyone working on that port. An interim solution is to run > Sugar on a Stick. Alternatively, DSD and the Paraguay team have done a > nice job of repackaging OLPC's 802 build to include some of the > improvements from Sugar 0.84. > > regards. > > -walter As Tomeu and Walter said - copying 0.84 over 0.82 won't work. There are some dependencies (xulrunner/hulahop, abiword, evince...) - and of course - the kernel - the hardware support for the XO. There are efforts from Chris Ball and the Fedora-Olpc working group (fedora-olpc-l...@redhat.com). Please refer to their work to know the current status. Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Developer MINUTES
[...] >>> That's why people are barking at the wrong tree when they say that >>> Sugar developers should port Sugar to whatever system. The skills >>> involved are very different from upstream work and if coders are not >>> coding we won't have anything new to ship. >>> >> If barking ever applies me to please let me know. My intention is to >> have usable contributions to our project. > > I was referring to some people that tried to put more pressure on > Sugar Labs by saying that we had "abandoned" the OLPC platform. It's > hard, but IMO a big part of our work is making people understand that > this is an open project and that everyone has the capacity to > contribute, so instead of complaining people should be able to get > their hards dirty and do their bit. > > Regards, > > Tomeu I want to highlight Tomeu's words. There is no "them" or "they"! In general - people should ask themselves what they can contribute to Sugar Labs - not the other way around. And many people are doing that already in various ways. Please keep on that path. Thanks, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Developer MINUTES
On Mon, May 25, 2009 at 16:25, Marten Vijn wrote: > On Mon, 2009-05-25 at 15:42 +0200, Tomeu Vizoso wrote: >> [adding sugar-devel again to CC] >> >> On Mon, May 25, 2009 at 14:36, Marten Vijn wrote: >> > On Mon, 2009-05-25 at 11:49 +0200, Tomeu Vizoso wrote: >> >> On Mon, May 25, 2009 at 11:34, NoiseEHC wrote: > >> >> >> >> Just copying files is unlikely to work. Regarding newer versions of >> >> Sugar working in the XO-1, I personally think it's very important and >> >> hope that others share this opinion >> > >> > I would love to see something an update kernel (OpenBSD) or mini-dist to >> > roll out never version. >> > >> >> and will contribute their time and >> >> skills to make it happen. >> > >> > Well I can help testing (or learn C, but that will take a while ;( ) >> >> Well, for this task (shipping an updated or new distro for the XO) >> there's little need for programming skills, it's mostly a matter of >> having someone who leads the effort and recruits people to help with >> the various tasks, give publicity to the effort, keep track of the >> open issues in the different bug trackers involved, help with >> packaging, do integration testing, etc. > > oke, from a side of a none developer, I would be good, a list of tasks > to: > - to do meself > - point people to Cool! I think that this is done better in a per team basis, so that people can have a closer contact with a subset of the community that better fits their experience and interests. You are already pretty much involved in the marketing team, but there are others in case you want to do something different. Each team has a getting involved page, a roadmap and a todo list in the wiki: http://wiki.sugarlabs.org/go/Activity_Team/Getting_Involved http://wiki.sugarlabs.org/go/Activity_Team/TODO http://wiki.sugarlabs.org/go/Activity_Team/Roadmap > For me is hard to so see what is needed and to move to the "right > direction". Knowing a bit from linux it is best to avoid dist-wars. Agreed, it helps having a personal goal related to Sugar, then it's a matter of seeing which other people are working closer to that goal and finding common tasks. > I 'll check the wiki and look/create for a task list. IHMO tasks shoud > be: > - do-able (beginning / end / clear steps) > - supported by a person > - avoiding flames/wars whatever negative energie > - complexicity index. > > Am I correct (by kind of consensus) that a tasklist would help? I think we have consensus on this, only that is quite a bit of work to maintain all those lists. But is something we'll get better slowly. >> That's why people are barking at the wrong tree when they say that >> Sugar developers should port Sugar to whatever system. The skills >> involved are very different from upstream work and if coders are not >> coding we won't have anything new to ship. >> > > If barking ever applies me to please let me know. My intention is to > have usable contributions to our project. I was referring to some people that tried to put more pressure on Sugar Labs by saying that we had "abandoned" the OLPC platform. It's hard, but IMO a big part of our work is making people understand that this is an open project and that everyone has the capacity to contribute, so instead of complaining people should be able to get their hards dirty and do their bit. Regards, Tomeu > Kind regards, > Marten > > > > > > >> Regards, >> >> Tomeu >> >> > Marten >> > >> >> Regards, >> >> >> >> Tomeu >> >> >> >> > ps: >> >> > If overwriting the old Sugar works on an XO-1 then an unzippable >> >> > "distribution" what could be applied to 802 would be just fine... >> >> > ___ >> >> > Sugar-devel mailing list >> >> > Sugar-devel@lists.sugarlabs.org >> >> > http://lists.sugarlabs.org/listinfo/sugar-devel >> >> > >> >> ___ >> >> Sugar-devel mailing list >> >> Sugar-devel@lists.sugarlabs.org >> >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > -- >> > Marten Vijn >> > linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6 >> > http://martenvijn.nl >> > http://opencommunitycamp.org >> > http://wifisoft.org >> > >> > >> > > -- > Marten Vijn > linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6 > http://martenvijn.nl > http://opencommunitycamp.org > http://wifisoft.org > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar with Metacity (again)
Am Montag, den 25.05.2009, 12:17 +0200 schrieb Bernie Innocenti: > [cc += cwickert] > > On 05/25/09 12:10, Bernie Innocenti wrote: > > On 05/25/09 11:19, Martin Langhoff wrote: > >> On Sat, May 23, 2009 at 7:30 PM, Bernie Innocenti > >> wrote: > >>> The only thing I didn't like very much is memory usage: 21MB VIRT, 10MB > >>> RSS. But I suppose we can't do much about it. > >> > >> Ugh. That's a ton for a wm :-( Are there alternatives that "fit" better? > > > > Openbox, the window manager used by LXDE and other desktops, is only > > slightly cheaper: 7.5MB RSS. > > Oops, I just realized I was measuring on x86_64, so that was an unfair > comparison after all. So Openbox's RSS on x86 is probably a good > saving, if someone is interested in experimenting with it. > > Christoph Wickert has been working on making LXDE from Fedora available > for the OLPC XO images. Perhaps he'd like to give it a shot? That was my plan. Sorry for not popping in earlier, I have just subscribed to this list after receiving Bernie's message. Basically it should not be to hard to get Openbox working: * Window decoration can be turned of. I guess this is what we want for most windows. * Supports window matching rules: default windows -> fullscreen + no decoration dialogs -> centered, on top, ... * I already have the OLPC specific keyboard shortcuts from the work I did with LXDE * It can be started with different config files I'm going to work on this, help and comments welcome. Regards, Christoph ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Activities] greater activities list by deleting activities list
I'd just like to be able to find ONE place to go to that would list the correct version of each activity FOR EACH RELEASE OF THE PLATFORM. Knowing that version 554 of stump-the-wumpus is the latest does me no good if I need a version no newer than 357 in order to run it under 8.2.1 on my XO. Since SugarLabs seems to be intent on running a few miles ahead of OLPC, having SL keep the list is counterproductive for XO-1 users. And wherever the list is kept, KEEP IT CORRECT, PLEASE! For some value of correct. "Activities/G1G1/8.2.1" should be the place for a G1G1 user to go to for the best version of activities that will run under 8.2.1. Not the list of G1G1 activities that now have been updated to run only with Sugar 0.84 or later. Otherwise somebody's going to get a lot of support requests as G1G1 users update their machines. IMO, Activities/All is hopeless -- the author rarely even says what build he has tested the activity under and there's no provision for the software update utility to determine if the activity is intended for the platform on which it is being installed. So anybody doing a "get latest" from that repository without having first read the description carefully is asking for trouble. - Original Message - From: Brian Jordan To: activit...@lists.laptop.org, Sugar Devel , Mel Chua Sent: Mon, 25 May 2009 07:48:04 + (UTC) Subject: [Activities] greater activities list by deleting activities list Is anyone against retiring the activit...@lists.laptop.org list in favor of migration to sugar-de...@lists.sugarlabs.org? Brian ___ Activities mailing list activit...@lists.laptop.org http://lists.laptop.org/listinfo/activities ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ANNOUNCE] Bug tracker housekeeping
On 05/25/2009 11:50 AM, Tomeu Vizoso wrote: > On Fri, May 22, 2009 at 16:54, Simon Schampijer wrote: >> Dear Sugar Community, >> >> After the dust of the 0.84 release has been settled we like to clean up >> the database. With each new Sucrose release comes some bug tracker >> housekeeping. This e-mail is designed to let you know about the things >> we ask you to do until May 27, 2009: >> >> Submitters: Please go through all the open bugs you have submitted. If >> some information has been requested - please provide this information. >> If the bug does not apply anymore - feel free to close it and leave a >> short note. >> >> Owners: Please go through the bugs you own and update them accordingly. >> If the bugs marked 0.84 still apply - please move them to the 0.86 >> milestone. >> >> __ >> >> Triage day: Wednesday - 27th of May 2009 - 16.00 (UTC) > > I guess we'll meet in #sugar-meeting in Freenode? > > Regards, > > Tomeu No, we will meet in a beer garden and count the bugs running over the food :) Regards, Simon I guess we have to use #sugar-meeting on Freenode for now... ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Developer MINUTES
On Mon, 2009-05-25 at 15:42 +0200, Tomeu Vizoso wrote: > [adding sugar-devel again to CC] > > On Mon, May 25, 2009 at 14:36, Marten Vijn wrote: > > On Mon, 2009-05-25 at 11:49 +0200, Tomeu Vizoso wrote: > >> On Mon, May 25, 2009 at 11:34, NoiseEHC wrote: > >> > >> Just copying files is unlikely to work. Regarding newer versions of > >> Sugar working in the XO-1, I personally think it's very important and > >> hope that others share this opinion > > > > I would love to see something an update kernel (OpenBSD) or mini-dist to > > roll out never version. > > > >> and will contribute their time and > >> skills to make it happen. > > > > Well I can help testing (or learn C, but that will take a while ;( ) > > Well, for this task (shipping an updated or new distro for the XO) > there's little need for programming skills, it's mostly a matter of > having someone who leads the effort and recruits people to help with > the various tasks, give publicity to the effort, keep track of the > open issues in the different bug trackers involved, help with > packaging, do integration testing, etc. oke, from a side of a none developer, I would be good, a list of tasks to: - to do meself - point people to For me is hard to so see what is needed and to move to the "right direction". Knowing a bit from linux it is best to avoid dist-wars. I 'll check the wiki and look/create for a task list. IHMO tasks shoud be: - do-able (beginning / end / clear steps) - supported by a person - avoiding flames/wars whatever negative energie - complexicity index. Am I correct (by kind of consensus) that a tasklist would help? > That's why people are barking at the wrong tree when they say that > Sugar developers should port Sugar to whatever system. The skills > involved are very different from upstream work and if coders are not > coding we won't have anything new to ship. > If barking ever applies me to please let me know. My intention is to have usable contributions to our project. Kind regards, Marten > Regards, > > Tomeu > > > Marten > > > >> Regards, > >> > >> Tomeu > >> > >> > ps: > >> > If overwriting the old Sugar works on an XO-1 then an unzippable > >> > "distribution" what could be applied to 802 would be just fine... > >> > ___ > >> > Sugar-devel mailing list > >> > Sugar-devel@lists.sugarlabs.org > >> > http://lists.sugarlabs.org/listinfo/sugar-devel > >> > > >> ___ > >> Sugar-devel mailing list > >> Sugar-devel@lists.sugarlabs.org > >> http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > > Marten Vijn > > linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6 > > http://martenvijn.nl > > http://opencommunitycamp.org > > http://wifisoft.org > > > > > > -- Marten Vijn linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6 http://martenvijn.nl http://opencommunitycamp.org http://wifisoft.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Help activity
Hi, We talked a bit about the Help Activity in Paris. I've taken our discussion and written it up here: http://wiki.sugarlabs.org/go/Activities/Help Please take a look and edit this spec and start to think about how it should be implemented. It may not be worth translating it before it is rewritten. Also, I'm not sure what is in the current help activity as it does not run on SoaS. Thanks, Caroline On Sun, May 24, 2009 at 1:13 PM, Bastien wrote: > Hi Diogo, > > > 2009/5/14 Diogo Serra @ IPLEIRIA : > >> Hy there, > >> > >> Where i can find the *.po of Help activity ? > > To my knowledge, there is no *.po for the Help activity (but the user > "Pootle" is a committer in git.sugarlabs.org so I'm not 100% sure...) > > The help activity is a collection of *.html page remixed from the > flossmanuals.com website: http://en.flossmanuals.net/ > > These pages are packaged in a .xo activity. > > Maybe Seth can tell us more on how to build a Help activity? How did > you export the flossmanuals pages to html? Raw scrapping? > > HTH, > > -- > Bastien > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar with Metacity (again)
On 05/25/09 12:18, Martin Langhoff wrote: > matchbox, according to ps_mem.py is 2.5MiB (private) + 430.5 > MiB(shared) with Browse.xo and Terminal.xo open on my development XO > after 3 days uptime. > > 'top' says 9644 RSS, 5436 Res, but the more I use the smap data > (parsed by ps_mem.py) the less I trust top's readings :-/ > > Perhaps it'd be better to get numbers with ps_mem.py ;-) Indeed. VMM is totally meaningless because it includes file mappings for all libraries and things like that. RSS varies with memory pressure and includes shared pages, so it's an equally unreliable estimate. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [SoaS] Announcing Snapshot 2009/05/24
I have tried the appliance image on VirtualBox. On the registration form it crashed with some python? error (will look the exact error if it is not a well known bug). It could be caused that I clicked more than once to the Next button. After that I only have an "Automatic login" user to choose from. It asked for my XO username correctly. Speak does not work, the sound output is garbage, changing languages kills the sound completely (but it does find the audio output). Browse has the same bug as in soas2-20090416.vmdk: 1. Go to Sugarlabs page (not the default page in Browse but sugarlabs.org) 2. Click on "Activities" 3. It will open the page in a popup window (what is different that using the default page in Browse) 4. Download an activity (I used Speak repeatedly) 5. There is no download notification and when you switch to Journal you can see that the download never finishes. Probably the notification at the end of download crashes. Sebastian Dziallas wrote: > Hi folks, > > after a short break, there's a new snapshot ready for you. It > incorporates the latest packages from the upcoming F11 release, as well > the Colors activity. Please report any bugs or issues you encounter and > list them appropriately for the soas_linuxtag milestone in trac, if needed. > > Our roadmap is located here: > http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap > > The current list of bugs for the RC can be found here: > http://www.tinyurl.com/soas-rc-tickets > > The image can be downloaded from here: > http://download.sugarlabs.org/soas/snapshots/2/Soas2-200905241902.iso > > The appliance image has been made available here: > http://download.sugarlabs.org/soas/appliances/soas2-20090524.zip > > Thanks and happy testing! :) > --Sebastian > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [ANNOUNCE] Bug tracker housekeeping
On Fri, May 22, 2009 at 4:54 PM, Simon Schampijer wrote: > Submitters: Please go through all the open bugs you have submitted. If BTW, if there's any guidance for the test team in Bxl on how to tag the bugs found against latest SoaS, we'll be happy to follow... This search shows most (all?) the bugs we filed... http://dev.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=owner&col=type&milestone=soas_fossvt&distribution=SoaS 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] Sugar with Metacity (again)
[cc += cwickert] On 05/25/09 12:10, Bernie Innocenti wrote: > On 05/25/09 11:19, Martin Langhoff wrote: >> On Sat, May 23, 2009 at 7:30 PM, Bernie Innocenti wrote: >>> The only thing I didn't like very much is memory usage: 21MB VIRT, 10MB >>> RSS. But I suppose we can't do much about it. >> >> Ugh. That's a ton for a wm :-( Are there alternatives that "fit" better? > > Openbox, the window manager used by LXDE and other desktops, is only > slightly cheaper: 7.5MB RSS. Oops, I just realized I was measuring on x86_64, so that was an unfair comparison after all. So Openbox's RSS on x86 is probably a good saving, if someone is interested in experimenting with it. Christoph Wickert has been working on making LXDE from Fedora available for the OLPC XO images. Perhaps he'd like to give it a shot? -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar with Metacity (again)
On Mon, May 25, 2009 at 12:10 PM, Bernie Innocenti wrote: > Openbox, the window manager used by LXDE and other desktops, is only > slightly cheaper: 7.5MB RSS. > > IMHO, not worth the pain of being out of the mainstream. matchbox, according to ps_mem.py is 2.5MiB (private) + 430.5 MiB(shared) with Browse.xo and Terminal.xo open on my development XO after 3 days uptime. 'top' says 9644 RSS, 5436 Res, but the more I use the smap data (parsed by ps_mem.py) the less I trust top's readings :-/ Perhaps it'd be better to get numbers with ps_mem.py ;-) 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] Sugar with Metacity (again)
On 05/25/09 11:19, Martin Langhoff wrote: > On Sat, May 23, 2009 at 7:30 PM, Bernie Innocenti wrote: >> The only thing I didn't like very much is memory usage: 21MB VIRT, 10MB >> RSS. But I suppose we can't do much about it. > > Ugh. That's a ton for a wm :-( Are there alternatives that "fit" better? Openbox, the window manager used by LXDE and other desktops, is only slightly cheaper: 7.5MB RSS. IMHO, not worth the pain of being out of the mainstream. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Developer MINUTES
Tomeu was quicker in his response than me... As Simon said, the current plan for *both* the XO-1 and the XO-1.5 in regard to Sugar support is to build upon the work that OLPC and the Fedora communities are doing towards getting a stock Fedora distribution running on the hardware. Sugar would be packaged on top of that. The current expectation is that this would happen in the F12 time frame, coincident with the planned Sugar 0.86 release. As far as porting Sugar 0.84 natively to the XO-1 hardware, this would require a fair amount of work--beyond simply copying the Sugar files. I am unaware of anyone working on that port. An interim solution is to run Sugar on a Stick. Alternatively, DSD and the Paraguay team have done a nice job of repackaging OLPC's 802 build to include some of the improvements from Sugar 0.84. regards. -walter On Mon, May 25, 2009 at 5:34 AM, NoiseEHC wrote: > >> >> I hope this anwers your question, >> Simon >> >> > > Unfortunately it does not. What I wanted to know whether I will be able > to use the latest Sugar on my XO-1 ever. It boots the kernel with 802 so > it is a working Linux distribution. If somehow I copy the latest Sugar > over the old Sugar (0.82 I think) will it work? If it does not work then > will anybody port it? What I see is that OLPC has very few developers so > probably this porting work will be out of question but will Sugar people > make any effort or would it be just wasting their time where the XO-1.5 > is almost finished? > > ps: > If overwriting the old Sugar works on an XO-1 then an unzippable > "distribution" what could be applied to 802 would be just fine... > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ANNOUNCE] Bug tracker housekeeping
On Fri, May 22, 2009 at 16:54, Simon Schampijer wrote: > Dear Sugar Community, > > After the dust of the 0.84 release has been settled we like to clean up > the database. With each new Sucrose release comes some bug tracker > housekeeping. This e-mail is designed to let you know about the things > we ask you to do until May 27, 2009: > > Submitters: Please go through all the open bugs you have submitted. If > some information has been requested - please provide this information. > If the bug does not apply anymore - feel free to close it and leave a > short note. > > Owners: Please go through the bugs you own and update them accordingly. > If the bugs marked 0.84 still apply - please move them to the 0.86 > milestone. > > __ > > Triage day: Wednesday - 27th of May 2009 - 16.00 (UTC) I guess we'll meet in #sugar-meeting in Freenode? Regards, Tomeu > - going through the list of 0.86 bugs and see if there are things that > needs to be added explicitly to the Roadmap. > - cleaning up left overs > > Thanks for reading, > Simon (for the BugSquad Team [1]) > > > [1] http://wiki.sugarlabs.org/go/BugSquad > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Developer MINUTES
On Mon, May 25, 2009 at 11:34, NoiseEHC wrote: > >> >> I hope this anwers your question, >> Simon >> >> > > Unfortunately it does not. What I wanted to know whether I will be able > to use the latest Sugar on my XO-1 ever. It boots the kernel with 802 so > it is a working Linux distribution. If somehow I copy the latest Sugar > over the old Sugar (0.82 I think) will it work? If it does not work then > will anybody port it? What I see is that OLPC has very few developers so > probably this porting work will be out of question but will Sugar people > make any effort or would it be just wasting their time where the XO-1.5 > is almost finished? Just copying files is unlikely to work. Regarding newer versions of Sugar working in the XO-1, I personally think it's very important and hope that others share this opinion and will contribute their time and skills to make it happen. Regards, Tomeu > ps: > If overwriting the old Sugar works on an XO-1 then an unzippable > "distribution" what could be applied to 802 would be just fine... > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Developer MINUTES
> > I hope this anwers your question, >Simon > > Unfortunately it does not. What I wanted to know whether I will be able to use the latest Sugar on my XO-1 ever. It boots the kernel with 802 so it is a working Linux distribution. If somehow I copy the latest Sugar over the old Sugar (0.82 I think) will it work? If it does not work then will anybody port it? What I see is that OLPC has very few developers so probably this porting work will be out of question but will Sugar people make any effort or would it be just wasting their time where the XO-1.5 is almost finished? ps: If overwriting the old Sugar works on an XO-1 then an unzippable "distribution" what could be applied to 802 would be just fine... ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar with Metacity (again)
On Sat, May 23, 2009 at 7:30 PM, Bernie Innocenti wrote: > The only thing I didn't like very much is memory usage: 21MB VIRT, 10MB > RSS. But I suppose we can't do much about it. Ugh. That's a ton for a wm :-( Are there alternatives that "fit" better? 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] greater activities list by deleting activities list
On 05/25/09 09:48, Brian Jordan wrote: > Is anyone against retiring the activit...@lists.laptop.org list in > favor of migration to sugar-de...@lists.sugarlabs.org? +1. I think platform developers should be aware of the challenges of activity writers, and vice-versa. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Simplifying sugar-jhbuild
On Sun, May 24, 2009 at 13:31, Bastien wrote: > +1 on the overall. > > Building Sugar from source should be as easy as: > > , > | ~$ git://git.sugarlabs.org/sugar-core/mainline.git > | ~$ ./configure > | ~$ make > | ~$ sudo make install > ` Well, that works for the sugar shell provided you have all the dependencies installed. The point of jhbuild is precisely to get you an environment where all the dependencies of the software you are interested in are installed without breaking your regular desktop. Please note that we don't need to use sudo as all dependencies are installed in a user-writable directory. Regards, Tomeu > (Sidenote: I guess it's a gitorious thingy, but mainline.git is a pretty > stupid name for a git repo. It forces the user to create folders by hand > when pulling several projects. Why not sugar-core.git?) > > I would also advocate having sugar-jhbuild reduced to sugar-core, where > the only activity is the Journal. Other activities should be installed > separately, either one by one or by bundle. > > Bernie Innocenti writes: > >> Today I've kick-started a newbie on building Sugar to fix a small bug >> and submit his first patch. >> >> It was just painful. jhbuild has plenty of rough corners and we could >> easily make things easier with a few changes: >> >> 1) Stop checking out random unstable versions of external projects. >> They break very often, and we cannot fix them. Let's instead upgrade >> manually every once in a while after some testing. >> >> 2) Do not build C modules that is already available (and recent enough) >> in popular distros. Specifically: abiword, matchbox, hippocanvas... >> >> 3) Let's move etoys away from the base set of components: the repository >> is often offline, building it breaks very often, and it takes a lot of >> time. You don't need it in order to test Sugar, the same way you don't >> need TamTam and TurtleArt. >> >> 4) We could check for prerequisites before starting the build. Some >> configure scripts are stupid enough to fail tests silently and proceed >> anyway using "no" as a command name in make :-) >> >> If there's consensus on implementing one or more of these points, I can >> provide patches (or just go on and commit them). > > -- > Bastien > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Dictionary everywhere ?
On Sun, May 24, 2009 at 01:42, S Page wrote: > There are a dozen dictionary extensions for Firefox, do any of those > work in Browse? > http://www.dailyblogtips.com/dictionary-extensions-for-firefox/ and > comments mention a few. Extensions that don't use anything firefox-specific can be used in Browse (google gears, for example). Regards, Tomeu >> 3) Language detection. > The HTML lang attribute? > > 95% of everything will be browser-based in the near future. > > Cheers, > -- > =S Page > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar with Metacity (again)
On Sat, May 23, 2009 at 21:30, Lucian Branescu wrote: > Perhaps Maximus from Ubuntu netbook remix may help with emulating > matchbox behaviour? https://launchpad.net/maximus We have a trade-off to take into account here between memory usage of maximus and the cost of implementation and maintenance of this job. Depending on that, would be better to duplicate this functionality inside the shell process. Regards, Tomeu > I don't really have a say in this, but I'd go for EWMH compliance. > Even Compiz could be used in XO 1.5, since it has some 3D support. > > 2009/5/23 Jonas Smedegaard : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: RIPEMD160 >> >> On Sat, May 23, 2009 at 07:30:15PM +0200, Bernie Innocenti wrote: >>>On 05/23/09 19:16, Bernie Innocenti wrote: I couldn't get this to boot, it hangs some time after the grub menu. But it might be because qemu is broken in Fedora 11. >>> >>>Oh, wait! It was just damn slow because I wasn't using kvm >>>(permissions issue). >>> >>>Now I could test it, and it looks good, modulo the bugs that Tomeu and >>>Gary reported. TurtleArt would work for me, but the window was >>>mispositioned. >>> >>>I'd say: let's switch early in the 0.86 release cycle, as soon as we've >>>shaked the major bugs, so activity maintainers have time to fix the >>>remaining issues in their code. >> >> Do you really mean to say that switching window manager should be done >> in a stable environment? Or did you mean to suggest swtiching early >> _after_ the 0.86 release? >> >> >> >>>The only thing I didn't like very much is memory usage: 21MB VIRT, 10MB >>>RSS. But I suppose we can't do much about it. >> >> Is the purpose to switch from one specific window manager to another >> specific one, or to move towards working properly with any >> EWMH-compliant window manager (and just picking one of them by default)? >> >> GNOME can work with different window managers too, even if it ships with >> this one as default. >> >> >> - Jonas >> >> - -- >> * Jonas Smedegaard - idealist og Internet-arkitekt >> * Tlf.: +45 40843136 Website: http://dr.jones.dk/ >> >> [x] quote me freely [ ] ask before reusing [ ] keep private >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.9 (GNU/Linux) >> >> iEYEAREDAAYFAkoYOssACgkQn7DbMsAkQLjXAQCeLGCK7GvW7PnLxRxg5GO++lg+ >> TQsAoJZ0RdYsWOleadgD+2Rbl0LyTkte >> =Dq8b >> -END PGP SIGNATURE- >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar with Metacity (again)
On Sat, May 23, 2009 at 20:04, Jonas Smedegaard wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: RIPEMD160 > > On Sat, May 23, 2009 at 07:30:15PM +0200, Bernie Innocenti wrote: >>On 05/23/09 19:16, Bernie Innocenti wrote: >>> I couldn't get this to boot, it hangs some time after the grub menu. >>> But it might be because qemu is broken in Fedora 11. >> >>Oh, wait! It was just damn slow because I wasn't using kvm >>(permissions issue). >> >>Now I could test it, and it looks good, modulo the bugs that Tomeu and >>Gary reported. TurtleArt would work for me, but the window was >>mispositioned. >> >>I'd say: let's switch early in the 0.86 release cycle, as soon as we've >>shaked the major bugs, so activity maintainers have time to fix the >>remaining issues in their code. > > Do you really mean to say that switching window manager should be done > in a stable environment? Or did you mean to suggest swtiching early > _after_ the 0.86 release? I guess Bernie meant to switch early in the 0.85 cycle (so now). >>The only thing I didn't like very much is memory usage: 21MB VIRT, 10MB >>RSS. But I suppose we can't do much about it. > > Is the purpose to switch from one specific window manager to another > specific one, or to move towards working properly with any > EWMH-compliant window manager (and just picking one of them by default)? I would say the later. > GNOME can work with different window managers too, even if it ships with > this one as default. Would be great if the choice of window manager could be left to integrators, I'm not sure it will be possible given our possible needs but I would say it's worth trying. Regards, Tomeu > > - Jonas > > - -- > * Jonas Smedegaard - idealist og Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEAREDAAYFAkoYOssACgkQn7DbMsAkQLjXAQCeLGCK7GvW7PnLxRxg5GO++lg+ > TQsAoJZ0RdYsWOleadgD+2Rbl0LyTkte > =Dq8b > -END PGP SIGNATURE- > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] greater activities list by deleting activities list
Is anyone against retiring the activit...@lists.laptop.org list in favor of migration to sugar-de...@lists.sugarlabs.org? Brian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Physics activity development
On Sun, May 24, 2009 at 8:59 PM, Gary C Martin wrote: > Hi Brian, > > On 24 May 2009, at 18:36, Brian Jordan wrote: > >> Hey all, >> >> Gary -- when you get a chance, can you add me as a committer on >> git.sl.o? I'd like to help clean things up! > > You're added! :-) > > Can I request we try and make small clean commits and try to let others know > what we are doing. If you want to hack, Gitorious supports quite a nice > 'Clone repository' and then 'Request merge' process (no commit rights needed > for the main project). The alternative, if you know what you are doing, is > just make your own local git branch to hack on, so you can take care of any > merge/conflict issues yourself when you fold it back into the current > master. > > I'm far from a git expert, but I can recommend some bed time reading at: > > http://www.eecs.harvard.edu/~cduan/technical/git/ > > and/or > > http://gitready.com/ > Thank you, will devote some to that! Need to learn to keep my crazy features in branches. > I'd like to get on with Labyrinth work, if you're willing to have an initial > clean up of the Physics source in the next few days... so what was > 'joysitck' feature all about? ;-) This would probably be best to describe on the wiki page, the idea was to make a UI for assigning keys on the XO-1 to impulses or changes on certain objects, so simple 2 player physics based games could be made from within Physics. Agreed, though, I will rid that from the code so we have a nice base line for crazy-feature branches. > Once the dev.sugarlabs.org component is added we should add the > features/bugs in there to keep them all together. FWIW, from a UI point of > view I had in mind: > > 1) remove/disable 'joysitick' feature as I have no idea what it was meant to > be ;-) > 2) build tool buttons correctly using RadioToolButton so they display state > correctly > 3) use set_accelerator to define visible keyboard shortcuts for the tools > >> Asaf -- do you have a http://git.sugarlabs.org account yet? >> >> This is some feedback from Asaf (these could fit as enhancements in >> http://dev.sugarlabs.org/ ): >> >>> While playing with the activity I found a "pause" button to stop time >>> could be very useful. It's complicated to build elaborate contraptions >>> if everything keeps falling. Maybe while everything is paused, >>> positions an velocities of objects could be modified. >>> >>> A minor modification I suggest is to create a separate button for >>> adding push pins. It is not intuitive to add them using the link tool. >>> If there are plans about creating tutorial levels this isn't that >>> necessary although I don't see any harm on adding it. >>> >>> An other thing I think could be grate is to be able to create >>> attractors an repulsors. With stuff like this it gets pretty >>> interesting, we could have objects orbiting around the attractors. > > Yes, all good stuff, there's also a list on > http://wiki.laptop.org/go/Physics_%28activity%29 as well, but I'd vote for > cleaning up what we have first, perhaps adding a play/pause, and keeping > Journal state so kids can actually keep their Physics creations (and send > them to friends when using sugar 0.84). +1 +1 +1 Brian > > Regards, > --Gary > >> Thanks >> >> Brian >> >> On Sun, May 24, 2009 at 4:17 PM, Gary C Martin >> wrote: >>> >>> Hey Brian, >>> >>> On 24 May 2009, at 13:57, Brian Jordan wrote: >>> Hey Gary, First, I'm attaching Asaf Paris Mandoki, who contacted me last week with an interest in developing on the Physics activity, and has great ideas of things to add. This is a great opportunity! :) I can handle getting Physics on gitorious, the bug tracker and a.sl.o. I will try to complete this by the end of today. >>> >>> Having chatted with Alex Levenson, I've already kicked off the migration >>> for >>> Physics (rep is now in Gitorious, trac request is in, and I've started to >>> poke at the code, running well at least in sugar-jhbuild and sugar 0.84). >>> X2o is next on my hit list once Physics is in a reasonable state. >>> The things I can use some help with are (1) integrating proper localization to the activity and >>> >>> Yep, I'm going to do a pass at the code and tidy up some partially >>> implemented / broken UI stuff, before requesting it's addition to pootle >>> (best to start with a reasonably stable set of strings). Would also like >>> to >>> get/text resolution independence (for non XO hardware) and get the scene >>> state saving to Journal... >>> >>> Want to get the basics out the way first before we break it again with >>> exciting new features ;-) >>> (2) figuring out a good way to include the pybox2d source in the git repository, while including an F9-compatible binary on a.sl.o (this was brought up w.r.t. Pippy a couple of times on the fedora devel lists, but I don't remember seeing a clear way of how to handle it). >>> >>> Yea I was worried this might be
Re: [Sugar-devel] wrong Activity versions for 8.2(.1) -- Etoys, Memorize, Terminal, Read, others
On 24.05.2009, at 03:56, S Page wrote: > Etoys at 94, but its web page's Activity_version says 98 > ==> Someone should update http://wiki.laptop.org/go/Activities/Etoys_(8.2) > !? > ==> http://activities.sugarlabs.org/en-US/sugar/addons/versions/4030 > is up to 100, but doesn't list a version for Sugar 0.82 Actually, the 8.2 version is correctly listed as 94: http://etoys.laptop.org/xo/8.2/ and for 8.2.1 it is 99 http://etoys.laptop.org/xo/8.2.1/ and the latest is 101 http://etoys.laptop.org/xo/ The versions listed at activities.sugarlabs.org are pretty much irrelevant because as part of Fructose, Etoys is installed by default anyways. Besides, most of its functionality is provided by the "etoys" glucose module which is not a downloadable activity. Activity version 94 is virtually identical to version 101. We updated the activity version whenever the glucose module version changed. This is not ideal, we should change the versioning scheme, but that's the way it is for now. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
