[Sugar-devel] Introduction - guidance needed
Hi All, I am an experienced python developer, I have also worked with zope, css, html, javascript, java, and web framework like turbogears. I have a physics background and is very much interested in educational activities. I came to know about the project through OLPC project page. I am interested in getting involved in sugar lab project in what ever way I can. I can contribute through code contribution, bug fixes, testing etc. I can also contribute in documenting the work also. Please guide me in getting started - please suggest me any projects which requires python expertise so that I can start exploring. I don't have a linux box, I have only a laptop with windows installed. Will that be a problem? Warm Regards, Roopesh ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Code Review process changes
On Fri, Apr 23, 2010 at 03:46, Bernie Innocenti ber...@codewiz.org wrote: On Tue, 2010-04-20 at 18:26 +0200, Sascha Silbe wrote: We'd like to try a different approach that's used by many successful projects - both small and large ones. Patches are sent to sugar-devel for review. Every Sugar developer (*) can review patches (and multiple reviews are quite welcome). Since the number of developers with commit access is limited, we have a sufficient level of QA even without limiting who can do reviews. Cannot find the rest of Sascha's email, was it sent to a list? The bits from Sascha that Bernie quoted refers to some context I cannot find, can someone repost? Or better, can we do what we agreed on #sugar and have a coherent proposal sent to the list? About Bernie's account on the kernel review practices, is it something that is being proposed for Sugar or is just food for thought? Thanks, Tomeu I noticed that we're already getting into this habit spontaneously, but it might be good to mention how the various tags are used in the Linux kernel. Here's the relevant excerpt from the Linux kernel documentation on submitting patches [1] [2]: -8--8--8--8--8--8- - Signed-off-by: this is a developer's certification that he or she has the right to submit the patch for inclusion into the kernel. It is an agreement to the Developer's Certificate of Origin, the full text of which can be found in Documentation/SubmittingPatches. Code without a proper signoff cannot be merged into the mainline. - Acked-by: indicates an agreement by another developer (often a maintainer of the relevant code) that the patch is appropriate for inclusion into the kernel. - Tested-by: states that the named person has tested the patch and found it to work. - Reviewed-by: the named developer has reviewed the patch for correctness; see the reviewer's statement in Documentation/SubmittingPatches for more detail. - Reported-by: names a user who reported a problem which is fixed by this patch; this tag is used to give credit to the (often underappreciated) people who test our code and let us know when things do not work correctly. - Cc: the named person received a copy of the patch and had the opportunity to comment on it. -8--8--8--8--8--8- Git handles some of these automatically. When you save a patch, you could simply do: # Export a patch with your Signed-off-by git format-patch -1 -s # Send patch to a maintainer, and cc the mailing list git send-email --to some...@sugarlabs.org --cc sugar-devel@lists.sugarlabs.org Committers should record in the patch who reviewed and ack'd a patch. This can be easily done by editing the comment in interactive mode: git am -i foo.patch (then use e to edit the patch) Alternatively, one could also edit the comment after the fact with git commit --amend. Attributing due credit to reviewers and testers is important because they're a scarce resource. A healthy development process depends on them as much as developers. Personal note: Instead of using a patch tracker, we could also ask patch submitters to file tickets at bugs.sugarlabs.org if there has been no review for, say, 3 days. This gives a streamlined process for most patches while still ensuring nothing gets lost. Another possibility is pinging on the list after a few days, perhaps adding on Cc people who are known to have worked in the area affected by the patch. for informational purposes, I continued to attach some patches to existing tickets. The difference is that it's no longer a required step for getting a patch in the mainline tree. [1] http://kernel.org/doc/Documentation/SubmittingPatches [2] http://kernel.org/doc/Documentation/development-process/5.Posting -- // 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 mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Code Review process changes
On Fri, Apr 23, 2010 at 12:43:33PM +0200, Tomeu Vizoso wrote: Cannot find the rest of Sascha's email, was it sent to a list? Yes, see [1]. Did gmail filter me out as SPAM again? Maybe you should deactivate the gmail SPAM filter for sugar-devel; we seem to have rather good filters on the list side already. The bits from Sascha that Bernie quoted refers to some context I cannot find, can someone repost? Does the archive link suffice or should I send you a copy privately? [1] http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023410.html CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Code Review process changes
On Fri, 2010-04-23 at 15:17 +1000, James Cameron wrote: Activities too? I've been tracking #1571 for months now, and if posting the patch here will work, I'm all for it. ;-) If you were just asking whether it's ok to post patches for activities here, sure: we have no separate mailing list for activities (*). If, instead, you were proposing to relax the rules for approving patches to activities, I think we should discuss this carefully. Many activities would probably be better off with their only maintainer reviewing and approving each patch personally. What about the fructose activities? What about orphaned activities? The question of how to handle the case of an unresponsive maintainer came up on #sugar last week: shall we define a formal procedure for taking over projects in ASLO and Gitorious? This is how Fedora handles it: http://fedoraproject.org/wiki/Package_maintainer_policy#What_to_do_if_a_Maintainer_is_absent If it seems reasonable, we could adopt the very same procedure for ASLO and Gitorious, of course with some obvious changes: s/bugzilla/trac/, s/FESco/SLOBs/, s/CVS/Gitorious or ASLO/. (*) this was a deliberate choice: this way, core developers would get a sense of what the infrastructure needs of activities really are, while activity writers would learn about Sugar internals and eventually become core developers. -- // 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] Remove the keep button from the default activity toolbar
On Thu, 2010-04-22 at 23:35 -0400, Frederick Grose wrote: Yes that would work, and wouldn't leave a hidden button taking up space on the tool bar. Ok, we'll work on a patch to do this. By the way, I don't see how one keeps a copy from the Journal to a new Journal item. One can copy to the clipboard and then keep a text file to the Journal from the primary Journal view (in the panel for the object icon - Sugar 0.88), and, in the extended Journal object view, one can copy files as text to attached devices--but how would one keep a copy of the running Activity? Ugh. We clearly need to put a lot more thought into Journal interaction: * lack of multiple selection makes certain tasks such as copying 10 photos to a pendrive amazingly repetitive and slow. * lack of a size column in the list view makes it hard to identify large items that could be deleted to free up some space. -- // 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] Introduction - guidance needed
Roopesh, If you're interested in developing Activities you might check out the FLOSS Manual Make Your Own Sugar Activities! at this URL: http://en.flossmanuals.net/ActivitiesGuideSugar/Introduction You might want to check out http://activities.sugarlabs.org to see what is already available. That might give you ideas about where you could contribute. You don't need a dedicated Linux box to do development for Sugar. You could run Linux in a VM on your laptop if it has enough memory to do that, or you could set up the laptop to boot either Linux or Windows. I do the dual-boot option myself. You just need to create a partition on your hard drive to hold Linux. Having Linux partitions on your laptop will not affect your experience running Windows, other than losing the disk space the partitions use. James Simmons Date: Fri, 23 Apr 2010 16:08:05 +0530 From: Roopesh P Raj roopesh.p...@gmail.com Subject: [Sugar-devel] Introduction - guidance needed To: sugar-devel@lists.sugarlabs.org Message-ID: m2qabbbe62e1004230338wadccd1cckaf39bcb7abb42...@mail.gmail.com Content-Type: text/plain; charset=iso-8859-1 Hi All, I am an experienced python developer, I have also worked with zope, css, html, javascript, java, and web framework like turbogears. I have a physics background and is very much interested in educational activities. I came to know about the project through OLPC project page. I am interested in getting involved in sugar lab project in what ever way I can. I can contribute through code contribution, bug fixes, testing etc. I can also contribute in documenting the work also. Please guide me in getting started - please suggest me any projects which requires python expertise so that I can start exploring. I don't have a linux box, I have only a laptop with windows installed. Will that be a problem? Warm Regards, Roopesh ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Remove the keep button from the default activity toolbar
On Fri, Apr 23, 2010 at 9:48 AM, Bernie Innocenti ber...@codewiz.orgwrote: On Thu, 2010-04-22 at 23:35 -0400, Frederick Grose wrote: Yes that would work, and wouldn't leave a hidden button taking up space on the tool bar. Ok, we'll work on a patch to do this. By the way, I don't see how one keeps a copy from the Journal to a new Journal item. One can copy to the clipboard and then keep a text file to the Journal from the primary Journal view (in the panel for the object icon - Sugar 0.88), and, in the extended Journal object view, one can copy files as text to attached devices--but how would one keep a copy of the running Activity? Ugh. We clearly need to put a lot more thought into Journal interaction: * lack of multiple selection makes certain tasks such as copying 10 photos to a pendrive amazingly repetitive and slow. * lack of a size column in the list view makes it hard to identify large items that could be deleted to free up some space. We should review this section of our design guidelines, http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Laptop_Experience/The_Journal#The_Notion_of_.22Keeping.22 . The 'Incremental backups paragraph' may be mis-worded. The 'keep (a copy)' button instantiates a new copy of the Activity. The incremental backups and keep-hints are said to 'keep a copy', but rather, they update and persist the working copy from the Learner's point of view. Perhaps we should just label the button or option 'Copy' because that is both the result and the action (at least in English where it is both a noun and a verb). I imagine that with the 'Keep a copy' action option on the proposed, 'Stop' button panel, Sugar Learners might see that phrase, and again, panic about 'saving' their Activity. An action option labelled 'Copy' may instead suggest that a new instance would be created, rather than suggest that they need to 'keep' their Activity or 'lose' it. The proposed 'Copy' icon might be improved by hinting that a new instance of the current Activity is to go (copied) into the Journal, perhaps by placing a new-object star (*) above the arrow pointing to the Journal. (See attached example.) --Fred attachment: Copy.png___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Remove the keep button from the default activity toolbar
On Fri, Apr 23, 2010 at 01:10:53PM -0400, Frederick Grose wrote: I imagine that with the 'Keep a copy' action option on the proposed, 'Stop' button panel, Sugar Learners might see that phrase, and again, panic about 'saving' their Activity. An action option labelled 'Copy' may instead suggest that a new instance would be created, rather than suggest that they need to 'keep' their Activity or 'lose' it. I like the proposal of renaming Keep to Copy and placing it in the palette of the Stop button. I was a bit worried about it getting confused with the clipboard action of the same name, but making it a secondary action of the Stop button should help with that. The proposed 'Copy' icon might be improved by hinting that a new instance of the current Activity is to go (copied) into the Journal, perhaps by placing a new-object star (*) above the arrow pointing to the Journal. (See attached example.) At least to me this icon isn't intuitive (I wouldn't even suspect what it does without reading the text; having read the text, the icon does not make the meaning any more clear). Maybe we should use some icon that indicates duplication? I can't think of one right now (two Journals wouldn't be right because we duplicate an entry, not the entire Journal), but maybe someone else has an idea? CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Remove the keep button from the default activity toolbar
On Fri, Apr 23, 2010 at 09:48:30AM -0400, Bernie Innocenti wrote: Ugh. We clearly need to put a lot more thought into Journal interaction: FWIW, we mostly need someone to actually implement many of the nice Journal designs [1] - somebody has already put some thought into the design, but so far nobody had time to implement it. * lack of multiple selection makes certain tasks such as copying 10 photos to a pendrive amazingly repetitive and slow. * lack of a size column in the list view makes it hard to identify large items that could be deleted to free up some space. FWIW (i.e. probably not much), my Janitor (*) activity prototype [2] already does both of these. I tried to keep close to the Journal design for multiple selection [3], but needed to postpone it because even after several hours of fighting with GTK I didn't even get the header colors to match. :-/ You can try out the activity without fear for your data, BTW: the Erase action currently only removes the entry from the list, but not the data store. For the real thing I'll probably use some kind of Commit button to execute all queued changes and provide Undo/Redo functions. (*) I'm aware the name is a noun, not a verb. Until I come up with a better one this is the working title; suggestions are quite welcome. [1] http://wiki.sugarlabs.org/go/Design_Team/Designs/Journal [2] git://git.sugarlabs.org/janitor/mainline.git [3] http://wiki.sugarlabs.org/go/Design_Team/Designs/Journal#06 CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Remove the keep button from the default activity toolbar
On 23 April 2010 15:02, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: I like the proposal of renaming Keep to Copy and placing it in the palette of the Stop button. I was a bit worried about it getting confused with the clipboard action of the same name, but making it a secondary action of the Stop button should help with that. This sounds odd. To make a copy of my work I have to go to the Stop menu? I've never seen Keep used in the field -- I've only seen misuse. Does anyone have any experience-backed counter opinions? I still think removing the button altogether will be a big improvement until the more advanced Journal solutions are actually implemented, even though technically you could say it would cause a functionality regression. If someone really does want to do a bit of hacking on this, put the Copy/Duplicate option in the Journal details view... Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH 3/4] fix AP association failure after removing encryption #1674
On 22 April 2010 23:01, James Cameron qu...@laptop.org wrote: The name has multiple purposes in Sugar and Network Manager interaction: 1. it identifies a connection (and Sugar was using it to identify an essid instead, before this patch), 2. it appears in Network Manager logs, 3. it is stored in connections.cfg as a section key. So it breaks compatibility with the old file format. Your saved secrets won't work after upgrading? If we're going to do this it would make sense to use the network ID, already used to separate APs into networks uniquely based on name, encryption, etc. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Remove the keep button from the default activity toolbar
On Fri, Apr 23, 2010 at 2:52 PM, Daniel Drake d...@laptop.org wrote: On 23 April 2010 15:02, Sascha Silbe sascha-ml-ui-sugar-de...@silbe.org wrote: I like the proposal of renaming Keep to Copy and placing it in the palette of the Stop button. I was a bit worried about it getting confused with the clipboard action of the same name, but making it a secondary action of the Stop button should help with that. This sounds odd. To make a copy of my work I have to go to the Stop menu? I've never seen Keep used in the field -- I've only seen misuse. Does anyone have any experience-backed counter opinions? Well, I added a keep button in Turtle Art to the default menu because kids would throw away their projects to start new ones and lose all of their work. (This was in part because the stop button was hard to find in pre-0.86 and it was easier to resume an old project than to start a new one, which only will change for 0.90). Ideally, we'd have versioning and could get rid of keep as a concept altogether... I still think removing the button altogether will be a big improvement until the more advanced Journal solutions are actually implemented, even though technically you could say it would cause a functionality regression. If someone really does want to do a bit of hacking on this, put the Copy/Duplicate option in the Journal details view... To me, this seems to be the proper place to put copy/dup. Daniel ___ 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] Introduction - guidance needed
On Fri, Apr 23, 2010 at 6:38 AM, Roopesh P Raj roopesh.p...@gmail.com wrote: Hi All, I am an experienced python developer, I have also worked with zope, css, html, javascript, java, and web framework like turbogears. I have a physics background and is very much interested in educational activities. I came to know about the project through OLPC project page. I am interested in getting involved in sugar lab project in what ever way I can. I can contribute through code contribution, bug fixes, testing etc. I can also contribute in documenting the work also. In addition to Jim's suggestion re writing an activity, we have a number open tickets of varying sorts in our bug tracker (bugs.sugarlabs.org) and a number of open feature requests described in our wiki (wiki.sugarlabs.org/go/Features) as places to get inspiration. Please guide me in getting started - please suggest me any projects which requires python expertise so that I can start exploring. I don't have a linux box, I have only a laptop with windows installed. Will that be a problem? Not a problem. You can install Sugar in a VM that runs in Windows. regards. -walter Warm Regards, Roopesh ___ 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] [ASLO] Release Poll-24
Activity Homepage: http://activities.sugarlabs.org/addon/4074 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26890/poll-24.xo Release notes: Added new button to control the activity options and also added a new feature to enable or disable the last vote mark. In this way the votes is kept secret to other voters. 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] Record v67
Hi Aleksey, I noticed Record v67's released. The changelog says: +* Fix 0sugar Cannot find cached 0sugar-launch implementation. isuue but I can't see any commit that could do that between v66 and v67; all I see are i18n commits: http://git.sugarlabs.org/projects/record Did I miss something, maybe? Hm, now I'm especially confused -- similar deal with the Speak repo: http://git.sugarlabs.org/projects/speak I see Bump v15 and Bump v16, but no commits that actually make the changes that the changelog says were made inbetween. Could you explain? Thanks, - Chris. -- Chris Ball c...@laptop.org One Laptop Per Child ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
