headers
Simon Schampijer | 9 Feb 10:59
Picon

[ANNOUNCE] Sugar 0.88 --- Testing Day --- Saturday 13th of February

Dear Sugar community,

the preparation for the 0.88 is getting close and the fearless Feature 
owners are working together with the 'keeping-everything-together" 
maintainers to produce another release. However, this will only get a 
rock solid software with testing and bug fixing!

And, guess what, YOU can help to make this happen!

We invite you to join in this Saturday for our first Sugar 0.88 testing 
day.

*** When: Saturday 13th of February
           Kickoff-Meeting 1: 14:00 UTC
           Kickoff-Meeting 2: 19:00 UTC

*** Where: Channel: #sugar (irc-freenode)

*** Todo: Put your name on the wiki page [1]

*** How to test: We will use a Sugar on a Stick [2] image with the 
latest 0.87.x release. This will contain the 0.88 Features landed. The 
image will be present at the end of the week and linked on the wiki [3] 
page and announced on the mailing list.

This will be an asynchronous effort, hence "Testing day" :). However we 
will do two kickstart meetings. One at 14:00 UTC and one at 19:00 UTC. 
In these meetings we will give a short introduction to what to test and 
answer questions about how to get the image on a usb-key and of course 
how to gather the results. Instructions will of course be present on the 
wiki page, too.

*** Help needed:
I am kicking off this testing day, since I think this is vital to the 
success of the 0.88 release. We had problems in the last releases that 
testing did not happen at all or too late, hence bugs were found late 
etc. We want to advance in this regard.

To make this meeting a success help is needed in the following areas:

- Of course, testing. Join the testing day, do testing and follow the 
instructions to gather that feedback (bug report etc).

- Testing instructions: As described in the "Feature Status" mail, the 
feature owners have to fill out the "How to test" section in the Feature 
page before the testing day. This should be as detailed as possible, 
imagine what could possibly go wrong and how a tester could test that 
Feature without having the technical background and has not been working 
on that Feature for days, weeks or months.

- Follow up on bug reports: The Feature owners and bug submitter has to 
follow up on the bug reports. The final goal is of course to fix the 
bug. This is a little process that often takes several iterations to be 
done. Ideally, Feature Owners are present at the Testing day, too. To 
help gathering the feedback and answer possible questions. Please fill 
in the field 'Feature owner' [3] when you can attend the meeting and are 
a Feature owner.

- Running the testing day: We need people to help coordinating that day. 
Keeping the wiki page up to date. Being present at the kickstart 
meetings. Helping people to flash their usb keys, enter bug reports etc. 
Please fill in the field 'Coordinator' when you can help in this area [3].

Suggestions, additions, questions are highly welcome of course.

Thanks,
    Simon

[1] http://wiki.sugarlabs.org/go/0.88/Testing#Attendees

[2] http://wiki.sugarlabs.org/go/Sugar_on_a_Stick

[3] http://wiki.sugarlabs.org/go/0.88/Testing#Testing_image
Permalink | Reply | 0 comments |
headers
Simon Schampijer | 9 Feb 09:40
Picon

[ANNOUNCE] Feature Status - Tasks for the next days

Hi,

in yesterday's developer meeting (thanks Tomeu for bringing that back to 
the surface!) we went through the status of the Features reflected here 
[1].

First a few words on what will happen this week:

Reviewing and Landing the Features already in review
- Who: Feature owner, module maintainers
- Due: Wednesday morning

New Tarballs
- Who: module maintainers
- Due: should be available latest by Wednesday evening

Packaging the tarballs for Fedora
- Who: the amazing Fedora packaging team
- Due: Ideally Thursday evening

Producing a Soas-Image for testing
I did a F12 image containing the latest 0.87.x rpms and it worked fine, 
I will do another one with the latest rpms.
- Who: Simon
- Due: Friday evening

Making a testplan for each Feature
Fill out the "How to test" section in the Feature page. This should be 
as detailed as possible, imagine what could possibly go wrong
- Who: Feature owner
- Due: Friday evening

Testing day on Saturday 13th of February 2010
Everyone is welcome to test the Soas image containing the bleeding edge 
0.87.x Sugar. I will send out another note about the testing day details.

The long term roadmap leading to 0.88 can be seen here [1b].

*** Enhanced Color Selector
The enhanced color selector did go over several design iterations. 
Finally, in last Saturday's design meeting we went back to an initial 
design. The design is clear and we hope it gives a good way to users to 
find their desired color. Walter provided a new patch based on a review 
from Aleksey and asked for another review. Christian has done another 
mockup. Both can be found in [2].

If the review is going well, we will land it in the next days. This will 
only change the color selector in the Control Panel, not the initial 
screen. As we are late in the development cycle, already this change 
would be too invasive.

*** 3G Support
Basic functionality has already been landed. We have 3 other patches 
that enhance the Feature pending review. Tomeu will take care of the 
review and we hope we can round the Feature up in the next days. We 
still need the icon for the frame device and Control Panel section.

If you have a 3G Modem it would be great you could test it and give it a 
go (currently in sugar-jhbuild). Testing image ready soon.

*** Enhanced Gettext
This one is very close to land. Sayamindu updated the patch based on 
reviewer feedback. [3] I will take care of another review.

*** Write to journal anytime
This one is a bit tricky. We discussed it in the design meetings several 
times and as well on the mailing list. Walter summarized the current 
situation in yesterday's meeting as follows:
(1) we want kids to write notes to the journal
(2) we put the naming alert in to enable/encourage that
(3) It failed on three counts: 1. only worked on exit; 2. confusing; 3. 
not well integrated.
(4) we could make the naming alert available at any time to address #1
(5) we could have the naming alert take you directly into a journal view 
to address #2,3
(6) or, more simply, replace the naming alert with a little text entry 
widget

We mainly agreed that (6) would be a good way forward. Though the code 
is not finished yet and it changes API. On the other hand there was a 
big interest to enhance the current situation, mainly: we want kids to 
write notes to the journal. It was proposed to try different approaches 
in testing, and if we feel strongly about it, the Feature could be 
backported. As 0.84 (which contains the naming alter) becomes available 
in a broad range soon, this might be important. Full logs about the 
discussion can be found in [4].

*** Font configuration
The Feature Status was marked 100%, as the gconf setting to set the Font 
size did land already. The UI to change the font size does not make it 
for 0.88 and has been postponed to 0.90. The settings manager Sayamindu 
has been proposing is needed to update the font when changing the size 
in the control panel without restarting Sugar [5]. We decided
to keep this separate till it gets a reasonable amount of packaging
done.

*** Dotted_Activity_Versions
This has been going to a first round of review [6]. There is a little 
bug that has to been investigated. This hopefully happens in the next 
days. Quite close, too.

Thanks everyone for all the hard work on the Features and following the 
Feature process.

Regards,
    Simon

[1] 
http://wiki.sugarlabs.org/go/0.88/Feature_List#Sugar_0.88_Accepted_Features

[1b] http://wiki.sugarlabs.org/go/0.88/Roadmap#Schedule

[2] http://bugs.sugarlabs.org/ticket/1592

[3] http://bugs.sugarlabs.org/ticket/1684

[4] http://me.etin.gs/sugar-meeting/sugar-meeting.log.20100208_0908.html

[5] http://lists.sugarlabs.org/archive/sugar-devel/2010-February/022411.html

[6] http://bugs.sugarlabs.org/ticket/1701
Permalink | Reply | 0 comments |
headers
Sayamindu Dasgupta | 9 Feb 07:02
Picon
Gravatar

[RELEASE] Sugar Settings Manager 0.87.1

Hello,
I just release Sugar Settings Manager version 0.87.1
Currently the settings manager, if started while Sugar 0.87.x is
running, monitors the font related GConf keys and applies the changes
real-time (as the GConf values change).
Note that this is not yet a part of core Sugar (glucose). We decided
to keep this separate till it gets a reasonable amount of packaging
done. For proper integration, check out the patches at
http://bugs.sugarlabs.org/ticket/1692

Link: http://download.sugarlabs.org/sources/external/sugar-settings-manager/sugar-settings-manager-0.87.1.tar.gz

Thanks,
Sayamindu

--

-- 
Sayamindu Dasgupta
[http://sayamindu.randomink.org/ramblings]
Permalink | Reply | 0 comments |
headers
Sugar Labs Activities | 8 Feb 23:22
Favicon

[ASLO] Release Domino-8

Activity Homepage:
http://activities.sugarlabs.org/addon/4212

Sugar Platform:
0.82 - 0.86

Download Now:
http://activities.sugarlabs.org/downloads/file/26579/domino-8.xo

Release notes:

Sugar Labs Activities
http://activities.sugarlabs.org
Permalink | Reply | 0 comments |
headers
Nicholas Doiron | 8 Feb 18:03
Picon
Gravatar

[sugar-devel][olpc-haiti] Offline Maps Beta 2

Everyone's still snowbound here in Pittsburgh, so I made some significant
updates to the OfflineMap activity.  Right now it's being designed for
Haiti, but if there's interest the same codebase could be used by another
deployment.

* Satellite Maps: Gonaives,Grand Goave,Miragoave,Anse a Galets,Etroits
* Roadmaps: PortAuPrince,Lagonav,Jacmel,Leogane,Jeremie,Sant Marc,PortDePaix
* Add to maps with markers, lines, and shapes: roadmap-level precision
* Load Google Earth KML files with >100 points, rivers, polygon areas
* Activity can be shared, markers editable by all users
* When connected to the internet, you can paste from OSM or Google Maps

Information and Screenshots:
http://wiki.laptop.org/go/User:Ndoiron/OfflineMap
Download:
http://haiti.latest.disaster-tool.appspot.com/OfflineMaps-2.xo
Tutorial, links to sample KML files:
http://wiki.laptop.org/go/User:Ndoiron/OfflineMapTutorial

Regards,
Nick Doiron
Permalink | Reply | 0 comments |
headers
Tomeu Vizoso | 8 Feb 16:23

development team meeting minutes

Hi,

we have just hold the scheduled meeting of the development team, see
here for logs:

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

Next one is scheduled for two weeks for now. Feedback on the date,
time and agenda are most welcome in:

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

Regards,

Tomeu
Permalink | Reply | 0 comments |
headers
Gonzalo Odiard | 7 Feb 19:59
Picon

The Journal and the no document centric activities

One of my activities is a game that does not produce any document in the journal. Only the scores  are recorded in activity_root/data.
The problem in the XO is that it gives an error because the method Activity save() method checks whether a file was generated with the name provided. Implode activities like record two files to not display the error. The solution was to implement file recording scores at the data directory in the method can_close() rather than write_file() in my activity.
The problem is that it continues to generate an entry in the journal to the output of the activity and I think that you should not do. The same applies to the Log and Terminal activities that are most likely not used by students, but also pollute the journal.
Is there any way around it now?
Accept some modification on this?

--
Gonzalo Odiard
SugarLabs Argentina
_______________________________________________
Sugar-devel mailing list
Sugar-devel <at> lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Permalink | Reply | 6 comments |
headers
Aleksey Lim | 8 Feb 10:27
Picon

Re: The Journal and the no document centric activities

*



On Sun, Feb 07, 2010 at 03:59:10PM -0300, Gonzalo Odiard wrote:
> One of my activities is a game that does not produce any document in the
> journal. Only the scores  are recorded in activity_root/data.
> The problem in the XO is that it gives an error because the method Activity
> save() method checks whether a file was generated with the name
> provided. Implode
> activities like record two files to not display the error. The solution was
> to implement file recording scores at the data directory in the method
> can_close() rather than write_file() in my activity.
> The problem is that it continues to generate an entry in the journal to the
> output of the activity and I think that you should not do. The same applies
> to the Log and Terminal activities that are most likely not used by
> students, but also pollute the journal.
> Is there any way around it now?
> Accept some modification on this?


pass to Activity.__init__ create_jobject=False e.g.

    class MyActivity(activity.Activity):
        def __init__(self, handle):
            activity.Activity.__init__(self, handle, create_jobject=False)

but keep in mind http://bugs.sugarlabs.org/ticket/1714 :)

--

-- 
Aleksey
Permalink | Reply | 4 comments |
headers
Gonzalo Odiard | 9 Feb 01:52
Picon

Re: The Journal and the no document centric activities

Thanks!

Gonzalo

On Mon, Feb 8, 2010 at 6:27 AM, Aleksey Lim <alsroot <at> member.fsf.org> wrote:
On Sun, Feb 07, 2010 at 03:59:10PM -0300, Gonzalo Odiard wrote:
*
> One of my activities is a game that does not produce any document in the
> journal. Only the scores  are recorded in activity_root/data.
> The problem in the XO is that it gives an error because the method Activity
> save() method checks whether a file was generated with the name
> provided. Implode
> activities like record two files to not display the error. The solution was
> to implement file recording scores at the data directory in the method
> can_close() rather than write_file() in my activity.
> The problem is that it continues to generate an entry in the journal to the
> output of the activity and I think that you should not do. The same applies
> to the Log and Terminal activities that are most likely not used by
> students, but also pollute the journal.
> Is there any way around it now?
> Accept some modification on this?

pass to Activity.__init__ create_jobject=False e.g.

   class MyActivity(activity.Activity):
       def __init__(self, handle):
           activity.Activity.__init__(self, handle, create_jobject=False)

but keep in mind http://bugs.sugarlabs.org/ticket/1714 :)

--
Aleksey



--
Gonzalo Odiard
Responsable de Desarrollo
Sistemas Australes
_______________________________________________
Sugar-devel mailing list
Sugar-devel <at> lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Permalink | Reply | 2 comments |
headers
Walter Bender | 9 Feb 04:00
Picon

Re: The Journal and the no document centric activities

FYI, I just added this tip to the Activites FAQ in the wiki:
http://wiki.sugarlabs.org/go/Activity_Team/FAQ

-walter

--

-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org
Permalink | Reply | 0 comments |
headers
Urso Wieske | 7 Feb 13:38

Where can I Find the list of sugar Core project.

Hi folks

I am trying to get an overall picture whats in the sugar distribution  
of a/next release.
Can someone point me to à specific page?

Thanks
Urso

Sent from my iPhone
_______________________________________________
Sugar-devel mailing list
Sugar-devel <at> lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Permalink | Reply | 2 comments |

Gmane