[Sugar-devel] bugs installing .xol library content from USB flash drive; status of .xol?
I ran into http://bugs.sugarlabs.org/ticket/1748 , Can't open library bundles (.xol) from USB flash drive. In the bug I suggest the one-line Python fix, it seems worth considering for a 10.1.3 update. But when you do this it seems you can never remove the content from ~/Library and the OLPC home page's expandable Library content, since it doesn't show in the Journal. I filed http://bugs.sugarlabs.org/ticket/2283 , you can't remove Library content installed from a .xol on USB flash drive So maybe the feature should be removed in favor of the workarounds in bug 1748: * drag the .xol into the Journal, then open from there * navigate to the .xol in Browse using file:///media, and "download" from there Other .xol issues: bug #470 , no icon for .xol files bug #1354 , no metadata in the Journal for .xol files bug #1258 , you can view HTML content in ZIP files without unpacking or installing them (more an enhancement, but so damn cool!) There was Sugar talk about unifying content and activities so these bugs would go away, what's the status? Is http://wiki.sugarlabs.org/go/User:Alsroot/trash/Unified_Objects really in the trash? 8-/ Regards, -- =S Page ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New IRC bot
Hi all, FIY, To keep IRC logs, I've setup IRC bot - supybot[1]. It supports many useful plugins[2] including meetings (so, we can replace meetbot with more powerful one). Full irc logs and meeting logs will be stored on [4] (each channel has link to meetings page). [1] http://sourceforge.net/projects/supybot/ [2] http://ubottu.com/stdin/supydocs/plugins.html [3] http://meetbot.debian.net/Manual.html [4] http://jita.sugarlabs.org/ -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New IRC channel for newby questiones regarding sugar development
Hi all, I think it should be useful to have #sugar-newbies IRC channel on freenode. The reasons to have one more channel in addition to #sugar: * one of useful things during teaching sugar development tricks is keeping IRC logs (not all #sugar members agree with having such logs on #sugar). Decent search (xapian based) will be added later (any contributions are welcome). * channel is intended primarily for development related questions (though it's hard to say where sugar using stops and sugar development starts) * its topic says "Ask your nub question about sugar development here." so, it will help with making incoming borders lower. Logs will be stored here http://jita.sugarlabs.org/freenode/%23sugar-newbies/index.html -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] Stability stuff
El Fri, 03-09-2010 a las 11:23 -0400, Martin Abente escribió: > Well, thats true in theory, assuming all the activities are properly > designed for sugar. In the field you already know thats not the case. > Also... even when the activities are being implemented in python > through the Activity Class, the read and write methods needs to be > implemented by the programmer. That means it > depends on the activity specifics again. Yes, but if an activity fails to save when Sugar asks it to quit, then it's already buggy today: we also have a "Stop" item in the menu of the activity frame icon. > > This is also a very good suggestion. We could start by doing this, which > > is a lot easier and almost equally effective. > > I see it this way: Why waiting to get sick to do something about it. > Preventive medicine > is always better. Why waiting for the machine to freeze (waiting 3 or more > minutes until its back > to a usable state again) to do something about it, also with potential > data loss. > > Having a message telling kids that the machine is too overloaded should be > enough, with > recommendations about saving any current work and closing earlier > activities. > > This kind of mechanisms should help to the overall stability, and it makes > even more sense when you > think about XO's 1 scenarios. > > :) Yes, I already agreed with you on this. The hard part of this patch would be setting a threshold to disallow opening another activity. Memory footprint of activities varies wildly. Shall we take the worst case, pissing off users who knew what they were doing, or shall we be optimistic, risking the current behavior in some cases? If we also had both the "graceful stop on oom" that I was thinking of, we could afford to be be optimistic in the "oom prevention" code. Anyway, for now I'd vote for doing what you suggest in the easiest possible way even if it saves the system only 50% of the times. It would still be a huge improvement upon the current behavior. -- // 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
[Sugar-devel] Patchwork upgraded
I refreshed our git snapshot of Patchwork. (Patchwork now requires Django 1.2, which isn't yet packaged for Ubuntu, so I installed it locally in the lib/packages/ directory). -- // 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] known issues with collaboration in XS 0.5.2
On 3 September 2010 11:48, Martin Langhoff wrote: > On Fri, Sep 3, 2010 at 12:43 PM, Tomeu Vizoso wrote: >> I have a local XS 0.6 that is working fine but I'm finding that the XS >> 0.5.2 at jabber.sugarlabs.org is not returning some results for some >> of the queries that I make. > > There are very important bugfixes in the "final" ejabberd that is in > olpcxs-testing repo for xs-0.6 > > I should release a 0.6.1 with the contents of olpcxs-testing, but > things haven't been kind to me lately. Can we at least move them into the olpcxs repo so that they get installed with an out-of-the-box "yum update" ? Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Corrected instructions re Spellchecker in Write-63
Hi there, sorry for the delay in getting back to you but I finally had time to follow the steps you mentioned and it works great! The only thing I haven't figured out is what the "dlgSpell" mapping does since I can't really see a difference in the UI... Last but not least I was wondering whether there was a way to use languages other than English for the spellchecker? When I switch Sugar's language to Spanish on build 852 the spellchecker seems to be deactivated from what I can tell. Cheers, Christoph On Sun, Aug 29, 2010 at 12:13 AM, wrote: > Christoph, > I fixed a copy and paste error in my previous email. > > To reveal the spelling checker popup menu open a terminal session and > use vi to edit /home/olpc/Activities/Write.activity/keybindings.xml > > change the line > > > to > > > > and if you want to reveal the Spelling dialog access on the menu > change > > > > to > > > > > rihowa...@gmail.com > > linux - the best things in life are free > > > > > > On Aug 28, 2010, at 8:38 PM, Christoph Derndorfer wrote: > > Since this topic came again up while talking to someone who is working on a > smaller deployment in Central America I was wondering whether anybody here > knows whether the lack of being able to use the spellchecker is indeed a bug > or intended to be like this? > > Cheers, > Christoph > > On Mon, Aug 16, 2010 at 9:05 PM, Christoph Derndorfer < > christoph.derndor...@gmail.com> wrote: > >> Hi, >> >> while writing an article on the XO-1.5 (build 851, Write-63) I realized >> that wrongly spelled words were being underlined with red yet there was no >> way to access the traditional suggestions menu with a right-click or >> something. I also didn't find any functionality on the tabs that make use of >> the spellchecker. >> >> Am I missing something here or does Write include a spellchecker that's >> really not quite as powerful and useful as it could be? >> >> Thanks, >> Christoph >> >> -- >> Christoph Derndorfer >> co-editor, olpcnews >> url: www.olpcnews.com >> e-mail: christ...@olpcnews.com >> > > > > -- > Christoph Derndorfer > co-editor, olpcnews > url: www.olpcnews.com > e-mail: christ...@olpcnews.com > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] known issues with collaboration in XS 0.5.2
On Fri, Sep 3, 2010 at 12:43 PM, Tomeu Vizoso wrote: > I have a local XS 0.6 that is working fine but I'm finding that the XS > 0.5.2 at jabber.sugarlabs.org is not returning some results for some > of the queries that I make. There are very important bugfixes in the "final" ejabberd that is in olpcxs-testing repo for xs-0.6 I should release a 0.6.1 with the contents of olpcxs-testing, but things haven't been kind to me lately. You aren't telling us exactly what problems you saw on the old ejabberd. All I can say is: that old ejabberd (+patches) had plenty of gremlins and unexplainable behaviours. The ejabberd in olpcxs-testing has been 100% reliable in behaviour, and I reworked the patches until I didn't see any buggy behaviour. Highly recommended. Should work with just a rebuild if you're not on F9. I cannot confirm that the right patches are in the latest ejabberd on F13. cheers, m -- 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] known issues with collaboration in XS 0.5.2
I noticed very strange and inconsistent behavior with j.sl.o yesterday while running two instances of sugar-jhbuild (build from git as of about 1 week ago). In neither case did I see an other XOs except the local ones on my access point. In one case, the icons appeared black and white. In the other case, in XO colors. -walter On Fri, Sep 3, 2010 at 12:43 PM, Tomeu Vizoso wrote: > Hi, > > I have a local XS 0.6 that is working fine but I'm finding that the XS > 0.5.2 at jabber.sugarlabs.org is not returning some results for some > of the queries that I make. > > Are there any similar fixed issues in 0.6 besides what is in > http://wiki.laptop.org/go/XS_Release_Notes#XS_0.6 ? > > Thanks, > > Tomeu > ___ > 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
[Sugar-devel] known issues with collaboration in XS 0.5.2
Hi, I have a local XS 0.6 that is working fine but I'm finding that the XS 0.5.2 at jabber.sugarlabs.org is not returning some results for some of the queries that I make. Are there any similar fixed issues in 0.6 besides what is in http://wiki.laptop.org/go/XS_Release_Notes#XS_0.6 ? Thanks, Tomeu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] Stability stuff
On Fri, Sep 3, 2010 at 11:23 AM, Martin Abente wrote: > for sugar. In the field you already know thats not the case. Also... even > when > the activities are being implemented in python through the Activity Class, > the > read and write methods needs to be implemented by the programmer. That > means it > depends on the activity specifics again. Well, if the activity doesn't save on close,it won't save on close and will be messing up user data left-and-right. We cannot design the system for brokenness... 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] Collaboration testing
On 03.09.2010, at 18:08, Tomeu Vizoso wrote: > On Fri, Sep 3, 2010 at 18:05, Bert Freudenberg wrote: >> On 03.09.2010, at 12:53, Bernie Innocenti wrote: >> >>> I've put my very simple recipe for testing collaboration here: >>> >>> http://wiki.sugarlabs.org/go/Collaboration#Testing >> >> >> With a little fiddling I got two users to run sugar on the same machine. >> >> However, no icon for the other user pops up in neighborhood view. >> >> I'm attaching the log. It shows how the "test1" user is first added (when I >> ran the second instance) and removed (when I closed it) but it is never seen >> in the UI. >> >> This is in the latest jhbuild on Fedora 13. > > You may want to try after disabling the firewall: # /etc/init.d/iptables stop > > Otherwise I can give it a look tomorrow. > > Regards, > > Tomeu Makes no difference AFAICT. - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Collaboration testing
On Fri, Sep 3, 2010 at 18:05, Bert Freudenberg wrote: > On 03.09.2010, at 12:53, Bernie Innocenti wrote: > >> I've put my very simple recipe for testing collaboration here: >> >> http://wiki.sugarlabs.org/go/Collaboration#Testing > > > With a little fiddling I got two users to run sugar on the same machine. > > However, no icon for the other user pops up in neighborhood view. > > I'm attaching the log. It shows how the "test1" user is first added (when I > ran the second instance) and removed (when I closed it) but it is never seen > in the UI. > > This is in the latest jhbuild on Fedora 13. You may want to try after disabling the firewall: # /etc/init.d/iptables stop Otherwise I can give it a look tomorrow. Regards, Tomeu > - Bert - > > > ___ > 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] Collaboration testing
On 03.09.2010, at 12:53, Bernie Innocenti wrote: > I've put my very simple recipe for testing collaboration here: > > http://wiki.sugarlabs.org/go/Collaboration#Testing With a little fiddling I got two users to run sugar on the same machine. However, no icon for the other user pops up in neighborhood view. I'm attaching the log. It shows how the "test1" user is first added (when I ran the second instance) and removed (when I closed it) but it is never seen in the UI. This is in the latest jhbuild on Fedora 13. - Bert - telepathy-salut.log Description: Binary data ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] Stability stuff
On Fri, 03 Sep 2010 01:46:02 +0200, Bernie Innocenti wrote: > El Thu, 02-09-2010 a las 09:26 -0400, Martin Abente escribió: >> Weird, I really tried to trigger it on our last Dextrose build and never >> happened. > > Perhaps it's gone, but I have not done anything to fix it. The bug seems > to be in Pytrhon, dbus or their dependencies. > > >> The whole idea of killing activities is a little bit controversial I >> think, you have to assume to many things about activities, so far just a >> few activities in sugar uses all the proper mechanisms, I am afraid that >> in >> most of the cases kids would just loose their current work. > > I thought almost all activities understood the protocol for quitting > cleanly (probably a dbus message). You can test it by clicking Stop from > the menu on the icons top of the frame. That wouldn't work without > sending an IPC message of some kind (probably we use dbus because we > can't stand to use established X11 standards to manage applications). > Well, thats true in theory, assuming all the activities are properly designed for sugar. In the field you already know thats not the case. Also... even when the activities are being implemented in python through the Activity Class, the read and write methods needs to be implemented by the programmer. That means it depends on the activity specifics again. > >> What about... If the system load is already close to a "critical" point, >> SUGAR could just stop new activities from being executed with a proper >> warning, and suggestions. > > This is also a very good suggestion. We could start by doing this, which > is a lot easier and almost equally effective. I see it this way: Why waiting to get sick to do something about it. Preventive medicine is always better. Why waiting for the machine to freeze (waiting 3 or more minutes until its back to a usable state again) to do something about it, also with potential data loss. Having a message telling kids that the machine is too overloaded should be enough, with recommendations about saving any current work and closing earlier activities. This kind of mechanisms should help to the overall stability, and it makes even more sense when you think about XO's 1 scenarios. :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] examples of .xol activity bundles?
On 31 August 2010 09:41, Erik Blankinship wrote: > Are there examples of .xol activity bundles being used in activities other > than browse? I would be interested in seeing how they can be used to bundle > content other than resources meant for display by web browsers. > Related, how can you specify which activity is meant to open a .xol file > (maybe a mime type?) Sugar is somewhat lacking in content support at the moment. I wrote some notes about the current problems and possible solutions here: http://wiki.sugarlabs.org/go/Features/Content_support Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Sliderule-15
Activity Homepage: http://activities.sugarlabs.org/addon/4222 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/27028/sliderule-15.xo Release notes: * added log log scale Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Release command (sugar-tools) use commit messages now
Hi, I did change [1] the release script (sugar-tools) to use commit messages and not looking for closed tickets only. Basically we do now: git log v0.89.7..v0.89.8 --no-merges --pretty=format:"%s (%an)" which does gives us the commit message and the name of the author. What you will get in the editable output then is more verbose but you can then pick from the messages what looks relevant to you (as a maintainer). We did look in the tickets back in the days since we did attach as well test cases and appended them to the release mail. Since this is not practice anymore... If anyone encounters any issues (dear all maintainers:) please ping me. Regards, Simon [1] http://git.sugarlabs.org/projects/sugar-tools/repos/mainline/commits/266a77e157002d7863e3043da6a9ccbc0a171a16 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SUGAR_PROFILE feature, slimming down sugar-jhbuild
El Fri, 03-09-2010 a las 14:28 +0200, Bert Freudenberg escribió: > [te...@fedora13 ~]$ unset XAUTHORITY > [te...@fedora13 ~]$ xauth add fedora13.localdomain/unix:0 MIT-MAGIC-COOKIE-1 > 74cc20607c72001dd921d6c2fe58cf09 > xauth: creating new authority file /home/test1/.Xauthority > > Maybe add that to your simple instructions? Yes, please. Perhaps sudo was clearing $XAUTHORITY in my case. > This is a vanilla Fedora 13 install. I have no idea why "sudo -i" > preserves XAUTHORITY, according to its man page it should not. > /var/run/gdm is inaccessible so this seems to make little sense. > But then, what do I know? ;) They added it explicitly to /etc/sudoers. It should be done only when sudoing to root, not to other unprivileged users who obviously would be unable to access the auth cookie. Probably sudo does not allow this distinction and they fixed the root case, the most common one. -- // 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_PROFILE feature, slimming down sugar-jhbuild
On 03.09.2010, at 12:53, Bernie Innocenti wrote: > El Fri, 03-09-2010 a las 10:23 +0200, Tomeu Vizoso escribió: >> On Thu, Sep 2, 2010 at 23:06, Sascha Silbe >> wrote: >>> The only reason I still haven't removed GConf-dbus is that I lack >>> patches for the _documentation_, not the code. >>> We explain how to use SUGAR_PROFILE to run multiple instances of Sugar >>> in parallel, but not how to do the same using multiple OS-level user >>> accounts. > > I've put my very simple recipe for testing collaboration here: > > http://wiki.sugarlabs.org/go/Collaboration#Testing xauth times out for me: [b...@fedora13 ~]$ xauth list fedora13.localdomain/unix:0 MIT-MAGIC-COOKIE-1 74cc20607c72001dd921d6c2fe58cf09 [b...@fedora13 ~]$ sudo useradd -m test1 [sudo] password for bert: [b...@fedora13 ~]$ sudo -i -u test1 [te...@fedora13 ~]$ export DISPLAY=:0 [te...@fedora13 ~]$ xauth add fedora13.localdomain/unix:0 MIT-MAGIC-COOKIE-1 74cc20607c72001dd921d6c2fe58cf09 xauth: timeout in locking authority file /var/run/gdm/auth-for-bert-an3WwY/database Any idea? Ah, reading the xauth manpage gives a clue: [te...@fedora13 ~]$ unset XAUTHORITY [te...@fedora13 ~]$ xauth add fedora13.localdomain/unix:0 MIT-MAGIC-COOKIE-1 74cc20607c72001dd921d6c2fe58cf09 xauth: creating new authority file /home/test1/.Xauthority Maybe add that to your simple instructions? This is a vanilla Fedora 13 install. I have no idea why "sudo -i" preserves XAUTHORITY, according to its man page it should not. /var/run/gdm is inaccessible so this seems to make little sense. But then, what do I know? ;) - Bert - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] sugar-0.89.8
On 09/03/2010 11:11 AM, Tomeu Vizoso wrote: > == Source == > > http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.89.8.tar.bz2 > > == News == > > * sugar-emulator crashes on startup (rpms) #2269 > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > Thanks for the new rpm, I adjusted the http://wiki.sugarlabs.org/go/0.90/0.89.5_Notes accordingly. Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] examples of .xol activity bundles?
Ok, I will investigate. It would be nice if , for example, a sugar video game engine could load .xol bundles with more levels. On Fri, Sep 3, 2010 at 4:17 AM, Tomeu Vizoso wrote: > On Tue, Aug 31, 2010 at 17:41, Erik Blankinship > wrote: > > Are there examples of .xol activity bundles being used in activities > other > > than browse? I would be interested in seeing how they can be used to > bundle > > content other than resources meant for display by web browsers. > > Related, how can you specify which activity is meant to open a .xol file > > (maybe a mime type?) > > AFAIK, only browse will be used to open a .xol file, but I would > better check the source. > > Regards, > > Tomeu > > > ___ > > 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] Bug tracking Vs Patch review
El Fri, 03-09-2010 a las 04:46 +0100, Marco Pesenti Gritti escribió: > Sounds good to me. I would put the notes somewhere on the wiki as > experimental/unofficial so that we can integrate improvements. Done: http://wiki.sugarlabs.org/go/Talk:Development_Team/Code_Review > > It's a useful aid on the side, but I don't think it needs to get in the > > middle of the patch workflow. People are generally good at keeping track > > of threads in mailing list within their MUA. > Some people are, some are less, included our most active maintainer :) > I think we agree about patchwork being an additional tool anyway. Sure, let me know if the current service works well enough, or if you'd like me to configure it differently. Anyone who would like admin privileges for the web administration interface and access to the codebase on sunjammer, just ping one of us sysadmins on #sugar. > This is a bit simplistic. The submitter might just think we don't care > and stop submitting patches. Let's forget about that for now though, > we need to make this work well for the existing contributors before we > even start thinking about involving more. Fair enough. These social dynamics are complex even when all contributors share the same culture. Let's promote an attitude of violen^W friendliness towards new contributors, especially those unfamiliar with the engagement rules of FLOSS projects. -- // 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_PROFILE feature, slimming down sugar-jhbuild
Sascha, please keep me on cc if you want me to notice your replies. I sort all messages from mailing-lists into separate folders that I quickly check for interesting threads only when I have some free time. OTOH, I won't cc you because you told me that you find it annoying. El Fri, 03-09-2010 a las 10:23 +0200, Tomeu Vizoso escribió: > On Thu, Sep 2, 2010 at 23:06, Sascha Silbe > wrote: > > The only reason I still haven't removed GConf-dbus is that I lack > > patches for the _documentation_, not the code. > > We explain how to use SUGAR_PROFILE to run multiple instances of Sugar > > in parallel, but not how to do the same using multiple OS-level user > > accounts. I've put my very simple recipe for testing collaboration here: http://wiki.sugarlabs.org/go/Collaboration#Testing Is there a better place? I'm glad to write any amount of documentation needed if it's a step in the direction of killing support for multiple user profiles in Sugar and the complexity that goes with it :-) PS: I spoke to tomeu & marcopg on IRC. Another reason for keeping GConf-dbus around is letting users test sugar without system-wide installation of new schemas. There doesn't seem to be an easy way to allow local schemas. Because GConf-dbus is such a huge PITA, perhaps we could live with this annoyance of requiring users to do "sudo gconftool..." every time they need to update schemas? -- // 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] screenreader for sugar
On Thu, Sep 2, 2010 at 18:25, Esteban Arias wrote: > xo-1.0 | F11 | Dextrose version | Gnome desktop | orca 2.26.3 > > If I set: "run at startup" > orca run correctly. Hi Esteban, to clarify, you configure orca in some way so it runs when sugar starts up and it reads what is on the screen? Thanks, Tomeu > If I excecute "orca" from Terminal, shows error: > /usr/lib/python2.6/site-packages/orca/mouse_review.py:189: Warning: invalid > uninstantiatable type `(null)' in cast to `GdkDisplayX11' > self._mouseDwellTimeout(event.detail1, event.detail2) > > Displays Preferences dialog, but dont reads screen. > > Regards, > Esteban Arias. > > 2010/9/2 Tomeu Vizoso >> >> On Wed, Sep 1, 2010 at 14:51, Esteban Arias >> wrote: >> > I install orca on xo 1.0 with gnome for f11. >> > If I config to start session with orca, runs ok. But if I execute orca >> > from >> > terminal, dont run correctly: >> >> Hi Esteban, >> >> could be that your email arrived to us incomplete? >> >> Regards, >> >> Tomeu >> >> > >> > >> > 2010/9/1 pbrobin...@gmail.com >> >> >> >> On Wed, Sep 1, 2010 at 10:24 AM, Tomeu Vizoso >> >> wrote: >> >> > On Fri, Aug 20, 2010 at 14:10, Tomeu Vizoso >> >> > wrote: >> >> >> On Fri, Aug 20, 2010 at 14:08, Esteban Arias >> >> >> wrote: >> >> >>> hi, >> >> >>> we can colaborate with this proyect. >> >> >> >> >> >> Excelent, have you tried already orca with Sugar? And with GNOME? >> >> > >> >> > I would say that the next step is for someone who knows how orca is >> >> > used to give it a try and file tickets for the biggest issues. Not >> >> > sure we can make much more until then. >> >> >> >> The gnome guys mentioned this the other day and there's going to be >> >> some more work done within gnome hopefully for F-14. So hopefully we >> >> should be looking better for that release. >> >> >> >> Peter >> > >> > >> > >> > -- >> > Esteban Arias >> > Investigación y Desarrollo - Plan Ceibal >> > Avda. Italia 6201 >> > Montevideo - Uruguay. >> > Tel.: 2601.57.73 Interno 2228 >> > E-mail : ear...@plan.ceibal.edu.uy >> > >> > > > > > -- > Esteban Arias > Investigación y Desarrollo - Plan Ceibal > Avda. Italia 6201 > Montevideo - Uruguay. > Tel.: 2601.57.73 Interno 2228 > E-mail : ear...@plan.ceibal.edu.uy > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Patch for documentation of graphics/animator.py
Hi Kandarp, some comments follow inline. On Mon, Aug 30, 2010 at 20:46, Kandarp Kaushik wrote: > Tomeu, > Thank you for the pointers. > As recommended, we developed the devtutor activity, and uploaded its source > code at http://git.sugarlabs.org/projects/devtutor. This is an activity to > help understand the Sugar APIs for the developers. > We did get a strong insight on key areas of activity development while > working on this activity. > We also revised the patch based on your feedback and recommendations. Thank > you for your time. We are using PEP 257 as the documentation standard. > Please have a look at the revised patch, and let us know your feedback > - http://seeta.in/dextrose/API%20patch/. +"""Stop animation, remove animation instance.""" Maybe "remove all animation instances" instead? +"""Reset timeout_sid.""" timeout_sid is an implementation detail. I'm not sure we can do much better than saying "Stops animation", maybe mentioning it will emit the 'completed' signal if the animation was running. +Description: Update frame after small time gaps, end after t=duration I would find more useful to say: "Update animation to the next frame" +Description: pass This method is intended to be overridden by subclasses. We should say so or leave it undocumented for now. > Hope it meets the requisite standards. If not, we'll be happy to revise it. > As discussed with you on IRC, our next step is to add documentation of > modules like sugar.graphics. I really think it will be a much better place to start with rather than animator.py. Regards, Tomeu > Regards, > Kandarp > On Sun, Aug 15, 2010 at 7:51 PM, Tomeu Vizoso wrote: >> >> On Sat, Aug 14, 2010 at 18:02, wrote: >> > Hello all, >> > >> > I've made some changes to the docstrings in graphics/animator.py for its >> > documentation and have uploaded the HTML generated using sphinx at: >> > http://seeta.in/sugar/api/documentation/desttemp/html2/animator.html >> > >> > You can compare it with the initial one at: >> > http://api.sugarlabs.org/sphinx/animator.html >> > >> > Attaching the original and new animator.py files along with the patch >> > generated using 'git format-patch master' >> > >> > I've also made a spreadsheet for the documentation and am maintaining it >> > at >> > >> > https://spreadsheets.google.com/a/seeta.in/ccc?key=0AjslliQkdNyvdFZjWnNwcEZzSC1fMkt6ZDlOOUFFMUE&hl=en#gid=0 >> > Attaching it. >> > >> > Please see if you would like to help or let me know in case of any >> > suggestions/feedback. >> >> Hi Kandarp, some suggestions follow: >> >> > Subject: [PATCH] description of animator.py >> >> The docstring for the module animator.py isn't really included in this >> patch. >> >> > animator1.py | 69 >> > ++--- >> >> This is very weird as there's no animator1.py file in sugar-toolkit. >> Please go through a git tutorial first, we'll all save time. >> >> > + :Inherits: gobject.GObject >> >> Sphinx cannot get this information from the code? Is it common >> practice in sphinx-generated docs? >> >> > + Returns >> > + - None >> >> Can we leave this implicit? >> >> > + Description: Adds animation type >> >> Why type? Seems to be adding an Animation instance. >> >> > + Parameters >> > + - None >> >> Can we leave this implicit? >> >> > + Description: Stops animation, removes animation type >> >> See above. >> >> > + Description: Records starting time, sets timeout_sid >> >> Docstrings should describe functionality, not explain the implementation. >> >> > +class Animation(object): >> >> Watch out adding trailing spaces >> >> > + Description: Updates frame, ends after t=duration >> >> PEP 257 says to use the first line for the one-line summary. >> >> Are you using any documented guidelines for the format of the docstrings? >> >> I would _strongly_ advise to start by adding docstrings to packages >> and modules. And only once that's done then get to classes and other >> top-level elements, then finally to methods. >> >> If you try to document the details before understanding the big >> picture, you are likely to fail. >> >> Regards, >> >> Tomeu >> >> > Regards, >> > Kandarp. >> > >> > >> > ___ >> > 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] [RELEASE] sugar-0.89.8
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.89.8.tar.bz2 == News == * sugar-emulator crashes on startup (rpms) #2269 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] depending on introspection
On Sat, Aug 21, 2010 at 14:00, Sascha Silbe wrote: > Excerpts from Tomeu Vizoso's message of Wed Aug 18 11:05:15 +0200 2010: > >> Sascha, what would take to have a modern GNOME stack on the Debian >> systems you use? > > As long as newer GNOME libraries won't break existing applications, > somebody setting up a repository with updated GNOME packages would > suffice. Jonas has been doing something like this for Debian Lenny. > > If instead GNOME is doing backwards-incompatible flag-day changes (as > some of the posts in this thread suggest), we would need to wait > for Debian (as a whole) to do the switch-over. > Shared libraries have mechanisms to deal with ABI changes (so newer, > backported packages could be installed in parallel to the old ones), > but it may fail for other reasons (e.g. shared data files). Gtk 3.0 and library versions depending on it can be installed in parallel, just like gtk 1.2 and gtk 2.0 used to be. There may be other issues with non-library changes such as the availability of GConf. > So the really interesting question is: What "modern" GNOME packages do > we want to use in Sugar 0.92, what are their (potentially indirect) > dependencies and what's the compatibility story for the whole set? We'll basically need 3.0 versions of all our GNOME dependencies from http://wiki.sugarlabs.org/go/0.88/Platform_Components plus their dependencies. > I've seen some introspection related stuff fly by in Debian; maybe it's > already enough for Sugar 0.92? I'm pretty sure we'll need stuff that has not even been released yet :/ Regards, Tomeu > Sascha > > -- > http://sascha.silbe.org/ > http://www.infra-silbe.de/ > > ___ > 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] [PATCH] Build Squeak VM 4.0.3 from tarfile
On Fri, Sep 3, 2010 at 00:10, Bert Freudenberg wrote:
> This is almost the same as my patch from April, which never made it in.
> Instead of building from the outdated "olpc" subversion branch, the Squeak VM
> is build from a release tarball.
> It adds a cmake dependency, and gives an error if make is run without running
> autogen.sh first.
> Also adds a "clean" make target to please jhbuild.
Not sure how relevant it is, but someone at Collabora was adding cmake
support to upstream jhbuild recently.
http://git.gnome.org/browse/jhbuild/commit/?id=aa564775b5c26527c5ff1d5ad8db8a3565d4dff2
Regards,
Tomeu
> Signed-off-by: Bert Freudenberg
> ---
> config/modulesets/glucose-external.modules | 15 +++-
> config/modulesets/patches/squeak-autogen.patch | 28
> +++
> config/modulesets/patches/squeak-makefile.patch | 11 +
> config/sysdeps/debian-family.xml | 1 +
> config/sysdeps/fedora-family.xml | 1 +
> config/sysdeps/mandrivalinux-2009.1.xml | 1 +
> 6 files changed, 51 insertions(+), 6 deletions(-)
> create mode 100644 config/modulesets/patches/squeak-autogen.patch
> create mode 100644 config/modulesets/patches/squeak-makefile.patch
>
> diff --git a/config/modulesets/glucose-external.modules
> b/config/modulesets/glucose-external.modules
> index d76b1f0..0577963 100644
> --- a/config/modulesets/glucose-external.modules
> +++ b/config/modulesets/glucose-external.modules
> @@ -5,8 +5,8 @@
> href="git://dev.laptop.org/projects/" />
> href="git://git.gnome.org"/>
> - - href="http://squeakvm.org/svn/squeak/branches/";
> trunk-template="olpc"/>
> + + href="http://squeakvm.org/unix/release/"/>
> href="git://git.imendio.com/projects/"/>
> @@ -61,10 +61,13 @@
>
>
>
> -
> -
> -
> -
> +
> + + repo="squeakvm.org"
> +
> hash="sha256:87cd3f708cb3d330f6d74931fd7488784f45b0f467f14e2dc6fbdc9d3df97189"
> size="3623094">
> +
> +
> +
>
>
>
> diff --git a/config/modulesets/patches/squeak-autogen.patch
> b/config/modulesets/patches/squeak-autogen.patch
> new file mode 100644
> index 000..ff9274d
> --- /dev/null
> +++ b/config/modulesets/patches/squeak-autogen.patch
> @@ -0,0 +1,28 @@
> +--- /dev/null 2010-09-02 18:58:30.359785873 +0200
> autogen.sh 2010-09-02 22:07:35.577316348 +0200
> +@@ -0,0 +1,25 @@
> ++#!/bin/sh
> ++EXCLUDE="gl FileCopyPlugin SqueakFFIPrims B3DAcceleratorPlugin
> PseudoTTYPlugin UnixOSProcessPlugin XDisplayControlPlugin"
> ++
> ++test -d bld || mkdir bld
> ++
> ++OPTIONS=""
> ++for p in $EXCLUDE ; do
> ++ OPTIONS="$OPTIONS --without-${p}"
> ++done
> ++
> ++(cd bld && ../unix/cmake/configure $OPTIONS "$@")
> ++
> ++cat > Makefile <<__EOF__
> ++default:
> ++ make -C bld
> ++
> ++install:
> ++ make -C bld install
> ++
> ++check:
> ++ �...@echo SKIPPED: No tests defined for Squeak VM
> ++
> ++clean:
> ++ rm -rf bld Makefile
> ++__EOF__
> diff --git a/config/modulesets/patches/squeak-makefile.patch
> b/config/modulesets/patches/squeak-makefile.patch
> new file mode 100644
> index 000..043dc7d
> --- /dev/null
> +++ b/config/modulesets/patches/squeak-makefile.patch
> @@ -0,0 +1,11 @@
> +--- Makefile.orig 2010-09-02 22:11:03.702191222 +0200
> Makefile 2010-09-02 22:21:14.580177789 +0200
> +@@ -1,7 +1,5 @@
> + all : .force
> +- test -d bld || mkdir bld
> +- (cd bld; ../unix/cmake/configure)
> +- (cd bld; make)
> ++ �...@test -d bld || (echo ERROR: run autogen.sh first; exit 1)
> +
> + install : all
> + (cd bld; make install)
> diff --git a/config/sysdeps/debian-family.xml
> b/config/sysdeps/debian-family.xml
> index ce11329..9870451 100644
> --- a/config/sysdeps/debian-family.xml
> +++ b/config/sysdeps/debian-family.xml
> @@ -3,6 +3,7 @@
>
>
>
> +
>
>
>
> diff --git a/config/sysdeps/fedora-family.xml
> b/config/sysdeps/fedora-family.xml
> index 83ec629..f97efb4 100644
> --- a/config/sysdeps/fedora-family.xml
> +++ b/config/sysdeps/fedora-family.xml
> @@ -7,6 +7,7 @@
>
>
>
> +
>
>
>
> diff --git a/config/sysdeps/mandrivalinux-2009.1.xml
> b/config/sysdeps/mandrivalinux-2009.1.xml
> index 0acac46..7fa1131 100644
> --- a/config/sysdeps/mandrivalinux-2009.1.xml
> +++ b/config/sysdeps/mandrivalinux-2009.1.xml
> @@ -9,6 +9,7 @@
>
>
>
> +
>
>
>
> --
> 1.7.2.2
>
>
> ___
> 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 broken in F14?
On Thu, Sep 2, 2010 at 22:06, Bernie Innocenti wrote: > El Thu, 02-09-2010 a las 10:44 +0200, Tomeu Vizoso escribió: > >> I'm testing daily the Sugar 0.90 packages that Peter (big thanks!) is >> doing on F14 and the tarballs that you see I'm making are intended to >> fix issues I find there. I'm still updating, but as of yesterday Sugar >> was starting correctly and I couldn't find any major issues. > > Still broken here. I have F14 fully updated, plus the Sugar packages > from updates-testing. If I remove ~/.sugar, I get to see the color > selection screen before Sugar dies. > > Do you have any other non-standard rpms installed? Any other environment > tweaks? None that I know of. >> I alone won't find all the issues so if you (and others) can file the >> bugs you find, I will be able to fix them faster. > > I've already filed 2... one happened to be yet another GConf-dbus issue, > the other one still stands: > > http://bugs.sugarlabs.org/ticket/2269 Ok, making a release now that should include a fix for that one. Didn't noticed that one at first because I was running Sugar as the main session (not sugar-emulator). There's this standing issue with sugar-emulator: http://bugs.sugarlabs.org/ticket/2278 Regards, Tomeu > -- > // 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_PROFILE feature, slimming down sugar-jhbuild (was: [PATCH] Make building GConf-dbus optional)
On Thu, Sep 2, 2010 at 23:06, Sascha Silbe wrote: > Excerpts from Bernie Innocenti's message of Thu Sep 02 19:27:59 +0200 2010: > >> Compiling this module frequently breaks, resulting in difficulties for >> novice developers and waste of time for everyone else. > > The only reason I still haven't removed GConf-dbus is that I lack > patches for the _documentation_, not the code. > We explain how to use SUGAR_PROFILE to run multiple instances of Sugar > in parallel, but not how to do the same using multiple OS-level user > accounts. > > As soon as somebody updates the wiki with a good HowTo, I will kick > GConf-dbus out of sugar-jhbuild with *delight*. :) I agree the biggest challenge here is the documentation. > In general any help with removing packages from sugar-jhbuild is > welcome. A good starting point would be to create backports of the very > latest Telepathy packages for the supported distros. That would be great, the telepathy guys are quite proactive regarding packaging and will be able to help, just pass by #telepathy on Freenode and say hi. Regards, Tomeu > Sascha > > -- > http://sascha.silbe.org/ > http://www.infra-silbe.de/ > > ___ > 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 broken in F14? (was Re: Bug tracking Vs Patch review)
On Thu, Sep 2, 2010 at 22:51, Sascha Silbe wrote: > Excerpts from Tomeu Vizoso's message of Thu Sep 02 10:44:35 +0200 2010: > >> I alone won't find all the issues so if you (and others) can file the >> bugs you find, I will be able to fix them faster. > I sure will look for, find and report more bugs after you fixed the > blocker one [1] that prevents me from testing. :-P Sorry, have commented in the ticket. Thanks, Tomeu > BTW: Thanks for working on this! > > Sascha > > [1] https://bugs.sugarlabs.org/ticket/2217 > -- > http://sascha.silbe.org/ > http://www.infra-silbe.de/ > > ___ > 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] [Dextrose] Stability stuff
Excerpts from Bernie Innocenti's message of Fri Sep 03 01:46:02 +0200 2010: > I thought almost all activities understood the protocol for quitting > cleanly (probably a dbus message). You can test it by clicking Stop from > the menu on the icons top of the frame. That wouldn't work without > sending an IPC message of some kind (probably we use dbus because we > can't stand to use established X11 standards to manage applications). We simply use X11 to close the window: In jarabe/view/palettes.py: class CurrentActivityPalette(BasePalette): def __stop_activate_cb(self, menu_item): self._home_activity.get_window().close(1) Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] examples of .xol activity bundles?
On Tue, Aug 31, 2010 at 17:41, Erik Blankinship wrote: > Are there examples of .xol activity bundles being used in activities other > than browse? I would be interested in seeing how they can be used to bundle > content other than resources meant for display by web browsers. > Related, how can you specify which activity is meant to open a .xol file > (maybe a mime type?) AFAIK, only browse will be used to open a .xol file, but I would better check the source. Regards, Tomeu > ___ > 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] Bug tracking Vs Patch review
On Thu, Sep 2, 2010 at 22:02, Bernie Innocenti wrote: > El Wed, 01-09-2010 a las 23:43 +0100, Marco Pesenti Gritti escribió: > >> We agree that we should try out reviews on the mailing list, let's >> just do it. > > If Tomeu is ok with it, I'll repost some of my old patches to the list > to get them reviewed and, hopefully, approved. > > To recap, the submission rules I propose are really simple: > > 1) On the submitter end: > > git commit -s > git format-patch -1 > git send-email --to maintainer --cc list foo.patch > > 2) Anyone who sees the patch can reply with inline comments > Multiple reviews are welcome. > > 3) The reviewer can conclude the message with one of these tags: > > Acked-by: Joe Hacker > Reviewed-by: Joe Hacker > Tested-by: Joe Hacker > > Only module maintainers and peers can ack a patch. > The meaning of these tags should be already self-explanatory. > In case someone has doubts, here's the full explanation: > http://lxr.linux.no/linux/Documentation/SubmittingPatches > > 4) if submitter has write access to the repository, he/she amends > the patch, appending any collected tags to it: > > git commit --amend > git push > > (submitters with multiple patches in their queue may need to > rebase or switch to a clean branch) > > 5) in case the patch closes a bug in Trac, submitter closes the > bug mentioning the commit ID as usual > > Let's get started this way. If needed, we could refine the rules later > on. To avoid confusion, I'd wait updating the documentation in the wiki > until we've tested this new workflow for a while. > > If a maintainer cannot stand to approve patches submitted to the > mailing-list, I'd ask them to state it clearly, so we don't needlessly > disappoint submitters. If a submitter still prefers the old workflow, > they can keep filing patches in the bug tracker as before. > > Agreed? Fine with me, though if people could wait a couple of weeks before sending stuff only for 0.92 it would save quite a bit of time by not having to branch and cherry pick stuff into sucrose-0.90 so early. >> I'm pretty confident we can setup and improve patchwork to help us >> tracking patch status reliably. I don't have a lot of time but I will >> commit to help out with both infrastructure and the reviews >> themselves. > > We've already had Patchwork on this list for a while: > > http://patchwork.sugarlabs.org/project/sugar/list/ > > It's a useful aid on the side, but I don't think it needs to get in the > middle of the patch workflow. People are generally good at keeping track > of threads in mailing list within their MUA. > > In case a patch gets overlooked by the maintainer, the submitter can > resend it after a while. If even the submitter forgets, someone else > could ping. If nobody cares to ping, it means that patch wasn't very > interesting after all. I personally agree with this, but some people in this project seem to have problem with pinging. Maybe the change of process will be a good chance for people to lose their timidness, we'll see. Regards, Tomeu > -- > // 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] [PATCH] Make building GConf-dbus optional
On Thu, Sep 2, 2010 at 19:27, Bernie Innocenti wrote: > Compiling this module frequently breaks, resulting in difficulties for > novice developers and waste of time for everyone else. > > This patch simply makes GConf-dbus an optional compilation unit. If > there's some consensus, I could follow up with a more aggressive patch > removing it althogether. > > GConf-dbus is unmaintained and is no longer part of any Linux > distribution. It was used to support multiple Sugar profiles within > the same UNIX user, a feature of dubious usefulness that could be used > to test collaboration without creating multiple accounts. But what happens with the schemas installed by Sugar? Don't we need to do something so these schemas are taken into account by the session GConf? Unless I'm missing something, Sugar will fail to start in a clean system when built from jhbuild. Regards, Tomeu > Signed-off-by: Bernie Innocenti > --- > config/modulesets/glucose-0.84.modules | 1 - > config/modulesets/glucose-versionsupport.modules | 1 - > config/modulesets/glucose.modules | 1 - > 3 files changed, 0 insertions(+), 3 deletions(-) > > diff --git a/config/modulesets/glucose-0.84.modules > b/config/modulesets/glucose-0.84.modules > index 9d7e1cd..005988e 100644 > --- a/config/modulesets/glucose-0.84.modules > +++ b/config/modulesets/glucose-0.84.modules > @@ -21,7 +21,6 @@ > > checkoutdir="sugar"/> > > - > > > > diff --git a/config/modulesets/glucose-versionsupport.modules > b/config/modulesets/glucose-versionsupport.modules > index a26c8a6..372ddc0 100644 > --- a/config/modulesets/glucose-versionsupport.modules > +++ b/config/modulesets/glucose-versionsupport.modules > @@ -21,7 +21,6 @@ > > checkoutdir="sugar"/> > > - > > > > diff --git a/config/modulesets/glucose.modules > b/config/modulesets/glucose.modules > index 2a9a8ce..12c8171 100644 > --- a/config/modulesets/glucose.modules > +++ b/config/modulesets/glucose.modules > @@ -21,7 +21,6 @@ > > > > - > > > > -- > 1.7.2.2 > > ___ > 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
