Re: [Sugar-devel] Setting public key - gitorious

2010-02-18 Thread Aleksey Lim 
On Thu, Feb 18, 2010 at 10:05:23PM -0500, Art Hunkins wrote:
> I thought I got it this time. I had something to commit, but the push fails 
> again with a publickey error. I thought we had that fixed.
> 
> [o...@xo-05-25-69 OurMusic.activity]$ git status
> # On branch master
> # Changed but not updated:
> #   (use "git add ..." to update what will be committed)
> #
> # modified:   csndsugui.py
> # modified:   ourmusic.py
> #
> no changes added to commit (use "git add" and/or "git commit -a")
> [o...@xo-05-25-69 OurMusic.activity]$ git commit -am "Fine-tune default font 
> displays through XO-1.5 and SoaS Blueberry"
> Created commit 5b8529c: Fine-tune default font displays through XO-1.5 and 
> SoaS Blueberry
>  2 files changed, 22 insertions(+), 4 deletions(-)
> [o...@xo-05-25-69 OurMusic.activity]$ git push 
> gitori...@sugarlabs.org:our-music/mainline.git
> The authenticity of host 'sugarlabs.org (18.85.2.155)' can't be established.
> RSA key fingerprint is ab:1a:b1:6f:56:f2:03:02:3b:1e:aa:cf:f2:69:15:5e.
> Are you sure you want to continue connecting (yes/no)? y
> Please type 'yes' or 'no': yes
> Warning: Permanently added 'sugarlabs.org,18.85.2.155' (RSA) to the list of 
> known hosts.
> Permission denied (publickey).
> fatal: The remote end hung up unexpectedly

could you post `ssh gitori...@git.sugarlabs.org -vvv` output

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] localización

2010-02-18 Thread Rafael Enrique Ortiz Guerrero 
Hola Kevin

Esta pregunta puede ser mejor contestada en la lista de olpc-sur o en
sugar-desarrollo



Rafael Ortiz



2010/2/18 Kevin Mauricio Benavides Castro :
> Hola alguien me puede ayudar necesito saber si hay alguna persona dentro de
> la comunidad que viva  cerca de brasil
> 
>
>
> --
> Kevin Mauricio Benavides Castro
> Fundación Zamora Terán
> www.fundacionzt.org
> Technical Support-Nicaragua OLPC
> www.wiki.laptop.org/go/user/kevin.benavides  - Soporte XO
> http://www.sistemascastros.netne.net/
> -
> www.fedoraproject.org
> Fedora Project Developer
> Linux User: #12356
>
>
> ___
> 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] Setting public key - gitorious

2010-02-18 Thread Art Hunkins 
I thought I got it this time. I had something to commit, but the push fails 
again with a publickey error. I thought we had that fixed.

[o...@xo-05-25-69 OurMusic.activity]$ git status
# On branch master
# Changed but not updated:
#   (use "git add ..." to update what will be committed)
#
# modified:   csndsugui.py
# modified:   ourmusic.py
#
no changes added to commit (use "git add" and/or "git commit -a")
[o...@xo-05-25-69 OurMusic.activity]$ git commit -am "Fine-tune default font 
displays through XO-1.5 and SoaS Blueberry"
Created commit 5b8529c: Fine-tune default font displays through XO-1.5 and 
SoaS Blueberry
 2 files changed, 22 insertions(+), 4 deletions(-)
[o...@xo-05-25-69 OurMusic.activity]$ git push 
gitori...@sugarlabs.org:our-music/mainline.git
The authenticity of host 'sugarlabs.org (18.85.2.155)' can't be established.
RSA key fingerprint is ab:1a:b1:6f:56:f2:03:02:3b:1e:aa:cf:f2:69:15:5e.
Are you sure you want to continue connecting (yes/no)? y
Please type 'yes' or 'no': yes
Warning: Permanently added 'sugarlabs.org,18.85.2.155' (RSA) to the list of 
known hosts.
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

Do I need to go through the ssh-keygen routine again??? (Aleksey, your 
copy/paste trick with "cat" seemed to work, but ???)

Art Hunkins

- Original Message - 
From: "Aleksey Lim" 
To: "Art Hunkins" 
Cc: 
Sent: Thursday, February 18, 2010 7:34 PM
Subject: Re: [Sugar-devel] Setting public key - gitorious


> On Thu, Feb 18, 2010 at 06:59:31PM -0500, Art Hunkins wrote:
>> I did the "initial commit" with these results (similar to what I got
>> before):
>>
>> [o...@xo-05-25-69 ~]$ cd Activities/OurMusic.activity
>> [o...@xo-05-25-69 OurMusic.activity]$ git remote add origin
>> gitori...@git.sugarlabs.org:our-music/mainline.git
>> [o...@xo-05-25-69 OurMusic.activity]$ git push origin master
>> error: src refspec master does not match any.
>> fatal: The remote end hung up unexpectedly
>> error: failed to push some refs to
>> 'gitori...@git.sugarlabs.org:our-music/mainline.git'
>>
>> Is the problem perhaps that this is not an "initial commit"?
>
> yeah, I missed your "git init" command, most likely "src refspec master
> does not match any" says that you don't have any commits in your local
> repo.
>
> And since there is already commits in remore repo, you need to
>
>git pull gitori...@git.sugarlabs.org:/mainline.git
>
> to create new local repo, then copy&paste all files you changed since
> last remote commit and follow regular git worklows
> (`git (add|commit|push)`)
>
> btw, git will be much cleaner if you undestand how it works under the
> hood, http://www.eecs.harvard.edu/~cduan/technical/git
>
>
>> I think I've
>> studied all available sugarlabs materials about git; unfortunately, Linux
>> terminology is still largely a foreign language to me, and I often don't
>> understand what's being said. (Sorry to be so unenlightened.)
>>
>> Art Hunkins
>>
>> - Original Message - 
>> From: "Aleksey Lim" 
>> To: "Art Hunkins" 
>> Cc: 
>> Sent: Thursday, February 18, 2010 6:18 PM
>> Subject: Re: [Sugar-devel] Setting public key - gitorious
>>
>>
>> > On Thu, Feb 18, 2010 at 04:16:13PM -0500, Art Hunkins wrote:
>> >> Due to wonderful help from Aleksey, Bernie and Gary, I've been able to
>> >> both
>> >> login to my gitorious account and add a valid ssh key. Thanks so much,
>> >> guys.
>> >> Now all I need to do is to push updates of my projects there (here's
>> >> where
>> >> I'm now hung up).
>> >
>> > You can follow http://wiki.sugarlabs.org/go/Activity_Team/Git tutorials
>> > and 
>> > http://wiki.sugarlabs.org/go/Activity_Team/Git_Tutorial#Push_project
>> > in particular push your initial commit
>> >
>> > -- 
>> > Aleksey
>>
>
> -- 
> Aleksey 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] localización

2010-02-18 Thread Kevin Mauricio Benavides Castro 
Hola alguien me puede ayudar necesito saber si hay alguna persona dentro de
la comunidad que viva  cerca de brasil



-- 
Kevin Mauricio Benavides Castro
Fundación Zamora Terán
www.fundacionzt.org
Technical Support-Nicaragua OLPC
www.wiki.laptop.org/go/user/kevin.benavides  - Soporte XO
http://www.sistemascastros.netne.net/
-
www.fedoraproject.org
Fedora Project Developer
Linux User: #12356
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Setting public key - gitorious

2010-02-18 Thread Aleksey Lim 
On Thu, Feb 18, 2010 at 06:59:31PM -0500, Art Hunkins wrote:
> I did the "initial commit" with these results (similar to what I got 
> before):
> 
> [o...@xo-05-25-69 ~]$ cd Activities/OurMusic.activity
> [o...@xo-05-25-69 OurMusic.activity]$ git remote add origin 
> gitori...@git.sugarlabs.org:our-music/mainline.git
> [o...@xo-05-25-69 OurMusic.activity]$ git push origin master
> error: src refspec master does not match any.
> fatal: The remote end hung up unexpectedly
> error: failed to push some refs to 
> 'gitori...@git.sugarlabs.org:our-music/mainline.git'
> 
> Is the problem perhaps that this is not an "initial commit"?

yeah, I missed your "git init" command, most likely "src refspec master
does not match any" says that you don't have any commits in your local
repo.

And since there is already commits in remore repo, you need to

git pull gitori...@git.sugarlabs.org:/mainline.git

to create new local repo, then copy&paste all files you changed since
last remote commit and follow regular git worklows
(`git (add|commit|push)`)

btw, git will be much cleaner if you undestand how it works under the
hood, http://www.eecs.harvard.edu/~cduan/technical/git


> I think I've 
> studied all available sugarlabs materials about git; unfortunately, Linux 
> terminology is still largely a foreign language to me, and I often don't 
> understand what's being said. (Sorry to be so unenlightened.)
> 
> Art Hunkins
> 
> - Original Message - 
> From: "Aleksey Lim" 
> To: "Art Hunkins" 
> Cc: 
> Sent: Thursday, February 18, 2010 6:18 PM
> Subject: Re: [Sugar-devel] Setting public key - gitorious
> 
> 
> > On Thu, Feb 18, 2010 at 04:16:13PM -0500, Art Hunkins wrote:
> >> Due to wonderful help from Aleksey, Bernie and Gary, I've been able to 
> >> both
> >> login to my gitorious account and add a valid ssh key. Thanks so much, 
> >> guys.
> >> Now all I need to do is to push updates of my projects there (here's 
> >> where
> >> I'm now hung up).
> >
> > You can follow http://wiki.sugarlabs.org/go/Activity_Team/Git tutorials
> > and http://wiki.sugarlabs.org/go/Activity_Team/Git_Tutorial#Push_project
> > in particular push your initial commit
> >
> > -- 
> > Aleksey 
> 

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Master nameserver changed for sugarlabs.org et al.

2010-02-18 Thread Bernie Innocenti 
Hello,

as announced some time ago, I've moved the master nameserver of the
following domains:

 sugarlabs.org
 sugarlabs.net
 somosazucar.org
 somosazucar.net
 olenepal.org
 pustakalaya.org

The new master nameserver is ns1.sugarlabs.org, aka
lightwave.sugarlabs.org, a virtual machine hosted on treehouse.

The old master ns1.codewiz.org, aka trinity.develer.com, is now acting
as a secondary slave.

Access is regulated by the following (draft) documentation:

  http://wiki.sugarlabs.org/go/Sysadmin/Nameservers

This change was supposed to be straightforward, but as usual it took me
the entire day chasing bugs in slave configurations and notifies. Watch
out for name resolution problems over the next few days!

-- 
   // 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] Setting public key - gitorious

2010-02-18 Thread Art Hunkins 
I did the "initial commit" with these results (similar to what I got 
before):

[o...@xo-05-25-69 ~]$ cd Activities/OurMusic.activity
[o...@xo-05-25-69 OurMusic.activity]$ git remote add origin 
gitori...@git.sugarlabs.org:our-music/mainline.git
[o...@xo-05-25-69 OurMusic.activity]$ git push origin master
error: src refspec master does not match any.
fatal: The remote end hung up unexpectedly
error: failed to push some refs to 
'gitori...@git.sugarlabs.org:our-music/mainline.git'

Is the problem perhaps that this is not an "initial commit"? I think I've 
studied all available sugarlabs materials about git; unfortunately, Linux 
terminology is still largely a foreign language to me, and I often don't 
understand what's being said. (Sorry to be so unenlightened.)

Art Hunkins

- Original Message - 
From: "Aleksey Lim" 
To: "Art Hunkins" 
Cc: 
Sent: Thursday, February 18, 2010 6:18 PM
Subject: Re: [Sugar-devel] Setting public key - gitorious


> On Thu, Feb 18, 2010 at 04:16:13PM -0500, Art Hunkins wrote:
>> Due to wonderful help from Aleksey, Bernie and Gary, I've been able to 
>> both
>> login to my gitorious account and add a valid ssh key. Thanks so much, 
>> guys.
>> Now all I need to do is to push updates of my projects there (here's 
>> where
>> I'm now hung up).
>
> You can follow http://wiki.sugarlabs.org/go/Activity_Team/Git tutorials
> and http://wiki.sugarlabs.org/go/Activity_Team/Git_Tutorial#Push_project
> in particular push your initial commit
>
> -- 
> Aleksey 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Setting public key - gitorious

2010-02-18 Thread Aleksey Lim 
On Thu, Feb 18, 2010 at 04:16:13PM -0500, Art Hunkins wrote:
> Due to wonderful help from Aleksey, Bernie and Gary, I've been able to both 
> login to my gitorious account and add a valid ssh key. Thanks so much, guys. 
> Now all I need to do is to push updates of my projects there (here's where 
> I'm now hung up).

You can follow http://wiki.sugarlabs.org/go/Activity_Team/Git tutorials
and http://wiki.sugarlabs.org/go/Activity_Team/Git_Tutorial#Push_project
in particular push your initial commit

-- 
Aleksey
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Setting public key - gitorious

2010-02-18 Thread Art Hunkins 
Due to wonderful help from Aleksey, Bernie and Gary, I've been able to both 
login to my gitorious account and add a valid ssh key. Thanks so much, guys. 
Now all I need to do is to push updates of my projects there (here's where 
I'm now hung up).

Gary has pushed previous versions for me, so this is my first attempt. 
Starting from scratch I did the following from the top level of my activity 
(listed in gitorious as "our-music"):
git init
git add .
git status
git commit -a -m "message about this version"
git push gitori...@git.sugarlabs.org:our-music/mainline.git

>From "git status" on, I got the following output:

[o...@xo-05-25-69 OurMusic.activity]$ git status
# On branch master
#
# Initial commit
#
# Changes to be committed:
#   (use "git rm --cached ..." to unstage)
#
# new file: MANIFEST
# new file: MyMusicASCII.csd
# new file: MyMusicMIDI.csd
# new file: OurMusicASCII.csd
# new file: OurMusicMIDI.csd
# new file: activity/activity-ourmusic.svg
# new file: activity/activity.info
# new file: csndsugui.py
# new file: ourmusic.py
# new file: setup.py
#
[o...@xo-05-25-69 OurMusic.activity]$ git commit -a -m "Fine-tune default 
font displays through XO-1.5 and SoaS Blueberry"
Created initial commit ca2ec96: Fine-tune default font displays through 
XO-1.5 and SoaS Blueberry
 10 files changed, 1873 insertions(+), 0 deletions(-)
 create mode 100644 MANIFEST
 create mode 100644 MyMusicASCII.csd
 create mode 100644 MyMusicMIDI.csd
 create mode 100644 OurMusicASCII.csd
 create mode 100644 OurMusicMIDI.csd
 create mode 100644 activity/activity-ourmusic.svg
 create mode 100644 activity/activity.info
 create mode 100644 csndsugui.py
 create mode 100644 ourmusic.py
 create mode 100644 setup.py
[o...@xo-05-25-69 OurMusic.activity]$ git push 
gitori...@git.sugarlabs.org:our-music/mainline.git
To gitori...@git.sugarlabs.org:our-music/mainline.git
 ! [rejected]master -> master (non-fast forward)
error: failed to push some refs to 
'gitori...@git.sugarlabs.org:our-music/mainline.git'

What am I doing wrong or not doing? (I've the feeling that the above setup 
is for an "initial commit" and that I need something else.)

Art Hunkins

- Original Message - 
From: "Aleksey Lim" 
To: "Art Hunkins" 
Cc: 
Sent: Wednesday, February 17, 2010 5:27 PM
Subject: Re: [Sugar-devel] Setting public key - gitorious


> On Wed, Feb 17, 2010 at 05:06:25PM -0500, Art Hunkins wrote:
>> I'm trying to get the Nano text editor to create a text clip of my public
>> key to paste into my gitorious account.
>>
>> Basically, I can't manage to copy the single long stream of characters 
>> (it
>> overflows the window many times over) to a clip. I can get the entire 
>> line
>> of characters selected, but copying it doesn't create a clip.
>>
>> Any ideas?
>
> just type in Terminal
>
>cat 
>
> then double click on key text to select it and middle click in Browse in
> gitorious text field to paste
>
> -- 
> Aleksey 

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Sugar Digest 2010-02-18

2010-02-18 Thread Walter Bender 
===Sugar Digest===

1. The Sugar Labs Development Team continues to make great progress
towards our next release, Sucrose 0.88. Last weekend a "testing day"
was held in which most of the new features exercised. There will be
another meeting on Monday (February 22) at which we will be discussing
various outstanding details as we approach "string freeze" on March 1.
What has been significant in this release cycle has not only been the
steady progress we have been making on improving and stabilizing the
core Sugar platform, but also the introduction of a more systemic
mechanism for proposing, vetting, and implementing new features. While
the procedures we have put into place are still in need of
fine-tuning, we have seen progress on one key goal—greater involvement
from Sugar deployments. Sugar remains a volunteer-run project and thus
it is what its community makes of it. Our release process is intended
to provide a stable and predictable base from which the community can
build. Long-term maintenance and growth will come from our community.
A goal for Sucrose 0.90 is to have a well-defined set of features,
proposed from downstream, and developed downstream. Sugar, like
learning itself, is not something done for it. It is something you do
for yourself.

2. Tony Forster, Raúl Gutiérrez Segalés, Michael Stone, and Edward
Cherlin have given me detailed feedback on the new Turtle Art. Raúl
will be testing it this week in the field and I hope that with that
additional feedback to be able to make a final release as part of
Fructose 0.88. If you'd like to give it a test drive, please download
it from the wiki:

http://wiki.sugarlabs.org/go/TurtleArt-83.xo

New user-interface features include support for multiple turtles (this
enables the learner to engage in many of the types of problems opened
up by learning systems such as StarLogo). To facilitate debugging,
there is now runtime block highlighting and highlighting of the block
that raised an error. Boolean logic is now prefix instead of infix,
which makes it consistent with the arithmetic operators and less
ambiguous in its visual parsing. Many other UI improvements, a trash
palette (with restore), variable-length, editable string blocks,
labels on coordinate-grid overlays, etc. were driven by feedback from
the field.

We also completed a major refactoring of the code, resulting in a 90%
smaller download bundle-size and a faster first-time launch. Our goal
here is greatly simplified maintenance, more decentralized
localization and easier extension with new blocks and palettes.

3. Sugar on a Stick, Blueberry, is now in the Museum of Modern Art
(MoMA) permanent collection.

===In the community===

4. Sorry for the last minute notice, but Joy Ventura Riach from One
Laptop Per Child's regional center in Africa is organzing Learning
Team chats. The first meeting will be on Thursday, February 18, at 10
EST (15 UTC). Go to http://bit.ly/9TxkwD to join the discussion.

===Tech talk===

5. Thanks to the efforts of Luke Faraone, Sugar Labs has received some
 servers donated from the Wikipedia project. They will be deployed in
various locations, including RIT, Washington, and Cambridge. Stefan
Unterhauser (dogi) is helping in the effort to get the new machines up
and running and properly configured to meet our growing needs.

===Sugar Labs===

10. Gary Martin has generated a SOM from the past few weeks of
discussion on the IAEP mailing list (Please see
http://wiki.sugarlabs.org/go/File:2010-Jan-30-Feb-5-som.jpg and
http://wiki.sugarlabs.org/go/File:2010-Feb-6-12-som.jpg).

-- 
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] [FIELDBACK] Naming Alert

2010-02-18 Thread Gerald Ardito 
Simon,

This is really interesting.
I look forward to whether my kids make the same connections when I test with
them next week.

Gerald

On Thu, Feb 18, 2010 at 3:05 AM, Simon Schampijer wrote:

> Hi,
>
> I did a little survey in the Planetarium pilot last week [1]. The
> subject was "Start new" vs "Restart" in the home view. Christian did
> provide a test case and I made a Soas version of Sugar that let's you
> change the behavior with a button in the Home View [2].
>
> While of course there were interesting observations to make about
> starting activities one other user feedback caught my eye, too. There
> was a question in the survey: The naming alert.
>
> A little background: When I started the pilot, stopping the activity was
> a hard task for the learners. First you need to find the stop button,
> then you had to dismiss the naming alert. I use the wording "dismiss"
> because for new learners it does not make much sense, since they don't
> understand the concept of the Journal etc yet. What I did was, I removed
> the naming alert which improved temporarily somehow the situation. Since
> I wanted the kids to take notes I introduced an workflow introduced by
> the teacher. After each lesson (normally the kids work in one activity
> in a lesson), I let them take notes in the Journal entry. This works
> quite well and the kids like it a lot to do this. I tell them: "Describe
> in your words what you did today." You can write there as well if you
> did like it or not, or if it was hard task. And sometimes I give them a
> few words that should be contained. Like "coordinating system" when i
> did a lesson in Etoys on that.
>
> When doing the test the Naming Alert was present in the build. And the
> testers said: "Oh, that is nice, so I do not have to search for the
> Journal entry to take my notes." I asked them what does it look like and
> they said: "A bit like the Journal."
>
> What I concluded is: For the workflow it is important to have a way to
> directly take notes related to that activity you are doing at the
> moment. I still think, that it would be better to have that option in
> the activity toolbar, like discussed in the Design meetings. And I will
> strike for getting this into 0.90 :) But I think, if the kids use the
> Journal and take notes, the naming alert is not such a bad thing for 0.84.
>
> Thanks,
> Simon
>
> [1] http://wiki.sugarlabs.org/go/Deployments/Planetarium
> [2] 
> http://shell.sugarlabs.org/~erikos/soas-design-test-DE.iso
> ,
> http://shell.sugarlabs.org/~erikos/soas-design-test-EN.iso
>
>
> ___
> 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] Development team meeting --- 22. Feb 2010 (14:00 UTC)

2010-02-18 Thread Tomeu Vizoso 
Hi all,

next regular meeting will take place next monday. Current items in the
agenda are:

*  0.88 Release: bug database cleanup, fix bugs, etc
* Activity Team: Move to new toolbar

Feel free to add any items yourself to the wiki, and if this time
doesn't work well for you, please propose a new one.

http://wiki.sugarlabs.org/go/Development_Team/Meetings

Thanks,

Tomeu
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] ANN: introducing the Karma Lesson Template

2010-02-18 Thread Bryan Berry 
Please check out the Karma Lesson Template, a simple template for creating
lessons for the XO and elsewhere

http://karmaeducation.org/2010/02/18/introducing-the-karma-lesson-template/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [DESIGN] 0.88 Meeting --- 20. Feb 2010 (15:30 UTC)

2010-02-18 Thread Simon Schampijer 
Sorry, of course the meeting is the 20th of February.

Regards,
Simon

On 02/18/2010 09:11 AM, Simon Schampijer wrote:
> Hi,
>
> this Saturday we will have our bi-weekly design meeting. We will chat
> about the outcome of the testing of the "Start new" vs "Resume" behavior.
>
> As a second item I would like to discuss the questions raised regarding
> the 3G Feature by Daniel [1]. Daniel, if you have time on Saturday, it
> would be great if you could attend.
>
> Thanks,
> Simon
>
> Channel: #sugar-meeting (irc.frenode)
> Time: 15:30 UTC
>
> [1]
> http://lists.sugarlabs.org/archive/sugar-devel/2010-February/022541.html

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [DESIGN] 0.88 Meeting --- 18. Feb 2010 (15:30 UTC)

2010-02-18 Thread Simon Schampijer 
Hi,

this Saturday we will have our bi-weekly design meeting. We will chat 
about the outcome of the testing of the "Start new" vs "Resume" behavior.

As a second item I would like to discuss the questions raised regarding 
the 3G Feature by Daniel [1]. Daniel, if you have time on Saturday, it 
would be great if you could attend.

Thanks,
Simon

Channel: #sugar-meeting (irc.frenode)
Time: 15:30 UTC

[1] http://lists.sugarlabs.org/archive/sugar-devel/2010-February/022541.html
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [FIELDBACK] Naming Alert

2010-02-18 Thread Simon Schampijer 
Hi,

I did a little survey in the Planetarium pilot last week [1]. The
subject was "Start new" vs "Restart" in the home view. Christian did
provide a test case and I made a Soas version of Sugar that let's you
change the behavior with a button in the Home View [2].

While of course there were interesting observations to make about
starting activities one other user feedback caught my eye, too. There
was a question in the survey: The naming alert.

A little background: When I started the pilot, stopping the activity was 
a hard task for the learners. First you need to find the stop button, 
then you had to dismiss the naming alert. I use the wording "dismiss" 
because for new learners it does not make much sense, since they don't 
understand the concept of the Journal etc yet. What I did was, I removed 
the naming alert which improved temporarily somehow the situation. Since 
I wanted the kids to take notes I introduced an workflow introduced by 
the teacher. After each lesson (normally the kids work in one activity 
in a lesson), I let them take notes in the Journal entry. This works 
quite well and the kids like it a lot to do this. I tell them: "Describe 
in your words what you did today." You can write there as well if you 
did like it or not, or if it was hard task. And sometimes I give them a 
few words that should be contained. Like "coordinating system" when i 
did a lesson in Etoys on that.

When doing the test the Naming Alert was present in the build. And the 
testers said: "Oh, that is nice, so I do not have to search for the 
Journal entry to take my notes." I asked them what does it look like and 
they said: "A bit like the Journal."

What I concluded is: For the workflow it is important to have a way to 
directly take notes related to that activity you are doing at the 
moment. I still think, that it would be better to have that option in 
the activity toolbar, like discussed in the Design meetings. And I will 
strike for getting this into 0.90 :) But I think, if the kids use the 
Journal and take notes, the naming alert is not such a bad thing for 0.84.

Thanks,
 Simon

[1] http://wiki.sugarlabs.org/go/Deployments/Planetarium
[2] http://shell.sugarlabs.org/~erikos/soas-design-test-DE.iso,
http://shell.sugarlabs.org/~erikos/soas-design-test-EN.iso


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel