Re: [Sugar-devel] [Marketing] [IAEP] Soliciting SoaS v.4 Codename Colour Suggestions
I believe the themeing for SoaS is Icecream and not berries. I vote for vanilla or Cookies Cream :-P Peter On Fri, Jun 4, 2010 at 10:00 AM, Bert Freudenberg b...@freudenbergs.de wrote: Gooseberry. Green. http://en.wikipedia.org/wiki/Gooseberry Tasty, funny name, what more do we want? ;) - Bert - On 03.06.2010, at 20:31, Sebastian Dziallas wrote: We'd like to kick off the process for the upcoming Sugar on a Stick v.4 already, while gearing up for the SoaS PR at LinuxTag, too. And so we're looking forward to your ideas and suggestions on the codename and colour selections for the next release iteration. These will be discussed at the next meeting, which is scheduled to take place on Monday, June 7 on 1900 UTC in #sugar-meeting. Thanks, --Sebastian ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Marketing] [IAEP] Soliciting SoaS v.4 Codename Colour Suggestions
Ah. Had forgotten about that theme. And Mirabelle isn't an ice cream I recognize either ;) - Bert - On 04.06.2010, at 11:12, Peter Robinson wrote: I believe the themeing for SoaS is Icecream and not berries. I vote for vanilla or Cookies Cream :-P Peter On Fri, Jun 4, 2010 at 10:00 AM, Bert Freudenberg b...@freudenbergs.de wrote: Gooseberry. Green. http://en.wikipedia.org/wiki/Gooseberry Tasty, funny name, what more do we want? ;) - Bert - On 03.06.2010, at 20:31, Sebastian Dziallas wrote: We'd like to kick off the process for the upcoming Sugar on a Stick v.4 already, while gearing up for the SoaS PR at LinuxTag, too. And so we're looking forward to your ideas and suggestions on the codename and colour selections for the next release iteration. These will be discussed at the next meeting, which is scheduled to take place on Monday, June 7 on 1900 UTC in #sugar-meeting. Thanks, --Sebastian ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] fix trivial typo in extension loading exception
El Thu, 03-06-2010 a las 11:57 +1000, James Cameron escribió: Unfortunately, the old process is still in place. A new process will enter into effect when the wiki is changed. I think you should test a proposed new process and not wait for it to enter into effect. If you don't have time to test the process, then it means the new process cannot be adopted, because it is untested. It's also my fault: I promised that I'd write down a final draft of the review process that we had agreed upon a couple of weeks ago. Hopefully I'll have some time to work on it next week, but feel free to beat me on time. This email summarizes the current status: - Mensaje reenviado De: Tomeu Vizoso to...@tomeuvizoso.net Para: Bernie Innocenti ber...@codewiz.org Cc: Sugar Devel sugar-devel@lists.sugarlabs.org, Fedora OLPC List fedora-olpc-l...@redhat.com, Peter Robinson pbrobin...@gmail.com, SoaS s...@lists.sugarlabs.org, Sebastian Dziallas s...@sugarlabs.org Asunto: changes to the review process (was Re: [Sugar-devel] Sugar 0.88 packages) Fecha: Mon, 17 May 2010 12:18:10 +0200 On Sat, May 15, 2010 at 00:02, Bernie Innocenti ber...@codewiz.org wrote: El Fri, 14-05-2010 a las 08:59 +0200, Tomeu Vizoso escribió: I'm just asking for someone to propose a set of concrete and coherent changes to the current process, is it really asking too much? I'm sorry but I cannot go through the old threads, ask individuals for clarifications, then draft that new process myself. Do you want the proposal posted to the wiki? We could basically take Sasha's original plan and copy it to the wiki. I think it was quite well thought: http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023410.html I propose the following amendments: 1) Scrap the paragraph saying that any sugar developer can approve changes, because it turned out to be a controversial point. The who and the where of reviews are orthogonal topics that can be discussed independently. 2) Also scrap the part where Sascha proposes ways to track patches in the list, since we can now use Patchwork for this. 3) Add all the clarifications in my follow-up to Sascha's proposal: http://lists.sugarlabs.org/archive/sugar-devel/2010-April/023468.html 4) The existing conventions still apply for referencing tickets in the commit logs 5) When a corresponding ticket exists, the committer should add a link to the patch discussion in Patchwork before committing the patch. Does this sound good enough for an initial iteration? If so, I could take care of transcribing it into the wiki. Then, we can further refine the process as we go. Hi Bernie, I think this is an excellent step forward, I really appreciate you having taken the time to do this. I still need to explore patchwork further and I'm a bit concerned about requiring that reviewers amend the commit message but I'm willing to give it a test drive and see how it works in real. I'm looking forward for the new text proposal. 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] tuchpad revelde
On Fri, Jun 4, 2010 at 10:20 AM, Kevin Mauricio Benavides Castro kmbc141...@gmail.com wrote: hola walter XO 1 CL1 You may want to try the new Touch Pad control-panel widget (in the py140 build from Paraguay) that lets you switch between the capacitive touch pad and the resistive (stylus) in situations where the capacitive is not working. (http://wiki.sugarlabs.org/go/Features/Touchpad_control_panel_section) regards. -walter 2010/6/3 fors...@ozonline.com.au Kevin I hope I understand you correctly. There is a patch which has been applied to later builds. http://wiki.laptop.org/go/Touchpad_driver_changes I know it is in the os140py build and later. The touchpad is monitored and if it gives bad data it is automatically recalibrated. The result is that there are more frequent periods of bad behaviour but they only last for a few seconds Tony Hola como estan a todos los de la lista tengo un problema en un colegio de una comunidad se entregaron XO y la mayoria de los casos de problemas tecnicos son de touchpad que es muy revelde para solucionar este problema temporalmente uso la combinacion de teclas para calibrarlo pero algunos de usted ha podido solucionar esto -- Abrazoss.. Kevin Mauricio Benavides Castro XO and XS Technical Support Member of the Volunteer Group for OLPC and sugarlabs www.wiki.laptop.org/go/user/kevin.benavides http://www.sistemascastros.netne.net/ - Linux User: #12356 div dir=ltrHola como estan a todos los de la lista tengo un problema en un colegio de una comunidad se entregaron XO y la mayoria de los casos de problemas tecnicos son de touchpad que es muy revelde para solucionar este problema temporalmente uso la combinacion de teclas para calibrarlobr brpero algunos de usted ha podido solucionar estobr clear=allbr-- brAbrazoss..brbrKevin Mauricio Benavides Castro brXO and XS Technical SupportbrMember of the Volunteer Group for OLPC and sugarlabsbra href=http://www.wiki.laptop.org/go/user/kevin.benavides;www.wiki.laptop.org/go/user/kevin.benavides/a br bra href=http://www.sistemascastros.netne.net/;http://www.sistemascastros.netne.net//abr-brLinux User: #12356brbr /div ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Abrazoss.. Kevin Mauricio Benavides Castro XO and XS Technical Support Member of the Volunteer Group for OLPC and sugarlabs www.wiki.laptop.org/go/user/kevin.benavides http://www.sistemascastros.netne.net/ - Linux User: #12356 -- 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] [IAEP] Soliciting SoaS v.4 Codename Colour Suggestions
Alphonso | saffron - red http://en.wikipedia.org/wiki/Alphonso_(mango) Alphonso is arguably the best available variety of Mango, which is one of the most awaited summertime fruits in India. Besides there are so many mango varieties (http://en.wikipedia.org/wiki/Mango), it is only fair that one of them gets to be selected as a SoaS codename :-) Sweet Cheers, Anish On Fri, Jun 4, 2010 at 2:30 PM, Bert Freudenberg b...@freudenbergs.de wrote: Gooseberry. Green. http://en.wikipedia.org/wiki/Gooseberry Tasty, funny name, what more do we want? ;) - Bert - On 03.06.2010, at 20:31, Sebastian Dziallas wrote: We'd like to kick off the process for the upcoming Sugar on a Stick v.4 already, while gearing up for the SoaS PR at LinuxTag, too. And so we're looking forward to your ideas and suggestions on the codename and colour selections for the next release iteration. These will be discussed at the next meeting, which is scheduled to take place on Monday, June 7 on 1900 UTC in #sugar-meeting. Thanks, --Sebastian ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ 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] [Marketing] Soliciting SoaS v.4 Codename Colour Suggestions
Sebastian, I guess you want to drop the name we had chosen together previously, Cloudberry? If you remember we had wanted to underline collaboration and connectivity, and decided to postpone that name when we realized that it was too ambitious for this release. This is a marketing discussion and should really be in the marketing meeting. Sugar on a Stick is a pillar of our marketing strategy and the name needs to fit with our strategy. That said, I wouldn't want to spoil anyone's fun choosing ice cream flavors. It could be nice to pick a non-berry flavor too as Peter and others have said in the past. Sean On Thu, Jun 3, 2010 at 8:31 PM, Sebastian Dziallas sebast...@when.com wrote: We'd like to kick off the process for the upcoming Sugar on a Stick v.4 already, while gearing up for the SoaS PR at LinuxTag, too. And so we're looking forward to your ideas and suggestions on the codename and colour selections for the next release iteration. These will be discussed at the next meeting, which is scheduled to take place on Monday, June 7 on 1900 UTC in #sugar-meeting. Thanks, --Sebastian ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Abacus-8
Activity Homepage: http://activities.sugarlabs.org/addon/4293 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26932/abacus-8.xo Release notes: * Added hexadecimal abacus * Cleaned up code to make it easier to modify/add customizations Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] initial commit to git?
On Fri, Jun 4, 2010 at 14:43, Art Hunkins abhun...@uncg.edu wrote: What did I do wrong or leave out? Try: git remote add origin ssh://gitori...@git.sugarlabs.org/sun-moon-music/mainline.git git push origin master -- Luke Faraone http://luke.faraone.cc ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Abacus-9
Activity Homepage: http://activities.sugarlabs.org/addon/4293 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26933/abacus-9.xo Release notes: * A customization toolbar: design your own abacus Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] initial commit to git?
I am still having trouble (after following your suggestions as best I know how), and have copied my complete console output below. Obviously my local repository and git are not communicating properly. I note that to my knowledge, ssh keys are installed properly, as illustrated by the fact that I've had no trouble updating [with new versions] my older two activities. The output: [liveu...@localhost SMMClone.activity]$ git add . [liveu...@localhost SMMClone.activity]$ git status # On branch master # # Initial commit # # Changes to be committed: # (use git rm --cached file... to unstage) # # new file: MANIFEST # new file: MoonMusic.csd # new file: SunMusic.csd # new file: activity/activity-sunmoonmusic.svg # new file: activity/activity.info # new file: csndsugui.py # new file: setup.py # new file: sunmoonmusic.py # [liveu...@localhost SMMClone.activity]$ git commit -a -mInitial commit [master (root-commit) 22b48a2] Initial commit 8 files changed, 1185 insertions(+), 0 deletions(-) create mode 100755 MANIFEST create mode 100755 MoonMusic.csd create mode 100755 SunMusic.csd create mode 100755 activity/activity-sunmoonmusic.svg create mode 100755 activity/activity.info create mode 100755 csndsugui.py create mode 100755 setup.py create mode 100755 sunmoonmusic.py [liveu...@localhost SMMClone.activity]$ git remote add origin usage: git remote add [options] name url -f, --fetch fetch the remote branches -t, --track branch branch(es) to track -m, --master branch master branch --mirror no separate remotes [liveu...@localhost SMMClone.activity]$ ssh://gitori...@git.sugarlabs.org/sun-moon-music/mainline.git bash: ssh://gitori...@git.sugarlabs.org/sun-moon-music/mainline.git: No such file or directory [liveu...@localhost SMMClone.activity]$ git push origin master fatal: 'origin' does not appear to be a git repository fatal: The remote end hung up unexpectedly [liveu...@localhost SMMClone.activity]$ Thanks for any further help/suggestions. Art Hunkins - Original Message - From: Luke Faraone l...@faraone.cc To: Art Hunkins abhun...@uncg.edu Cc: sugar-devel@lists.sugarlabs.org Sent: Friday, June 04, 2010 4:15 PM Subject: Re: [Sugar-devel] initial commit to git? On Fri, Jun 4, 2010 at 14:43, Art Hunkins abhun...@uncg.edu wrote: What did I do wrong or leave out? Try: git remote add origin ssh://gitori...@git.sugarlabs.org/sun-moon-music/mainline.git git push origin master -- Luke Faraone http://luke.faraone.cc ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] initial commit to git?
On Fri, Jun 4, 2010 at 22:31, Art Hunkins abhun...@uncg.edu wrote: [liveu...@localhost SMMClone.activity]$ git remote add origin usage: git remote add [options] name url -f, --fetch fetch the remote branches -t, --track branch branch(es) to track -m, --master branch master branch --mirror no separate remotes [liveu...@localhost SMMClone.activity]$ ssh://gitori...@git.sugarlabs.org/sun-moon-music/mainline.git bash: ssh://gitori...@git.sugarlabs.org/sun-moon-music/mainline.git : No such file or directory Sorry, the git add remote origin and ssh lines were supposed to be on the same line, separated by a space. My mail client munged it and split it across lines. Apologies for the inconvenience. -- Luke Faraone http://luke.faraone.cc ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
