Re: [Sugar-devel] anonymous ASLO messages

[Rafael Enrique Ortiz Guerrero]

On Tue, Nov 9, 2010 at 9:52 PM, Aleksey Lim  wrote:

> On Tue, Nov 09, 2010 at 09:36:37PM -0500, Rafael Enrique Ortiz Guerrero
> wrote:
> > Hi all
> >
> >
> >
> > On Tue, Nov 9, 2010 at 9:15 PM, Aleksey Lim 
> wrote:
> >
> > > On Wed, Nov 10, 2010 at 12:18:48PM +1100, James Cameron wrote:
> > > > On Wed, Nov 10, 2010 at 12:20:22AM +, Aleksey Lim wrote:
> > > > > On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:
> > > > > > On Tue, Nov 09, 2010 at 11:23:46PM +, Aleksey Lim wrote:
> > > > > > > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > > > > > > > These announcements from activities.sugarlabs.org of new
> > > releases are
> > > > > > > > sent without any included identity of the person who did the
> > > release.
> > > > > > > >
> > > > > > > > Could activities.sugarlabs.org please be changed to include
> the
> > > releaser
> > > > > > > > in these messages?
> > > > > > >
> > > > > > > The problem is that uploaders don't include release notes. The
> > > proper
> > > > > > > fix might be do not accept them (from uploading checks), so
> patches
> > > are
> > > > > > > welcome :).
> > > > > >
> > > > > > No, I think you misunderstand.  My observation has nothing to do
> with
> > > > > > whether release notes are present in the mail message.
> > > > > >
> > > > > > Where's the code?
> > > > >
> > > > > http://git.sugarlabs.org/projects/slo-activities
> > > > > http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing
> > > >
> > > > The file site/app/views/editors/email/aslo/release_en_plain.thtml
> > > > contains what looks like the release messages, but I cannot see where
> it
> > > > is used.  What is needed is the authenticated user's e-mail address.
> > > >
> > > > > But keep in mind that current code is php/cake based and
> > > > > new ASLO will be based on new AMO python/django code. So, would be
> > > > > useful if patch is not invasive and might be applied w/o starting
> new
> > > > > development/testing/production cycle.
> > > >
> > > > That says to me, "don't do anything, your effort will be wasted,
> nobody
> > > > else cares about this problem."  Thanks for the warning.  I see no
> way
> > > > forward.
> > >
> > > The thing is, we are using not supported AMO code base that have
> > > long standing bugs. Upstream has switched to django and we need to do
> > > the same. So, if you was thinking about easy hacking, then you was
> wrong ;)
> > >
> >
> >
> > from   AMO's Wiki [1] the migration is not yet complete:
> >
> > ''This project is currently underway, and will take some cycles to
> complete.
> > Bugs that take too much work to fix will likely be delayed until Zamboni
> is
> > completed, in order to prevent duplicate work when porting features.''
> >
> > Zamboni [2] is the code name for the Django project.
> >
> > [1] https://wiki.mozilla.org/AMO:Editors/InfoEditors
> > [2]http://blog.fligtar.com/2010/01/15/amo-zamboni-planning-underway/
>
> Mozilla uses Zamboni in production
> https://wiki.mozilla.org/AMO:Developers



I was outdated then :(.

>
> And Remora page says "Remora is no longer maintained"
> https://wiki.mozilla.org/Update:Remora
>
> I have long running plans about close (but not in launchpad way)
> integration of SL services, Bazaar + ASLO + ...
> The first step (during 0.92 release cycle), I'm planing to do, will be
> switching ASLO to Zamboni (with keeping existed functionality).
>

it sounds like a good plan, great!.


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

Re: [Sugar-devel] anonymous ASLO messages

[Aleksey Lim]

On Tue, Nov 09, 2010 at 09:36:37PM -0500, Rafael Enrique Ortiz Guerrero wrote:
> Hi all
> 
> 
> 
> On Tue, Nov 9, 2010 at 9:15 PM, Aleksey Lim  wrote:
> 
> > On Wed, Nov 10, 2010 at 12:18:48PM +1100, James Cameron wrote:
> > > On Wed, Nov 10, 2010 at 12:20:22AM +, Aleksey Lim wrote:
> > > > On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:
> > > > > On Tue, Nov 09, 2010 at 11:23:46PM +, Aleksey Lim wrote:
> > > > > > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > > > > > > These announcements from activities.sugarlabs.org of new
> > releases are
> > > > > > > sent without any included identity of the person who did the
> > release.
> > > > > > >
> > > > > > > Could activities.sugarlabs.org please be changed to include the
> > releaser
> > > > > > > in these messages?
> > > > > >
> > > > > > The problem is that uploaders don't include release notes. The
> > proper
> > > > > > fix might be do not accept them (from uploading checks), so patches
> > are
> > > > > > welcome :).
> > > > >
> > > > > No, I think you misunderstand.  My observation has nothing to do with
> > > > > whether release notes are present in the mail message.
> > > > >
> > > > > Where's the code?
> > > >
> > > > http://git.sugarlabs.org/projects/slo-activities
> > > > http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing
> > >
> > > The file site/app/views/editors/email/aslo/release_en_plain.thtml
> > > contains what looks like the release messages, but I cannot see where it
> > > is used.  What is needed is the authenticated user's e-mail address.
> > >
> > > > But keep in mind that current code is php/cake based and
> > > > new ASLO will be based on new AMO python/django code. So, would be
> > > > useful if patch is not invasive and might be applied w/o starting new
> > > > development/testing/production cycle.
> > >
> > > That says to me, "don't do anything, your effort will be wasted, nobody
> > > else cares about this problem."  Thanks for the warning.  I see no way
> > > forward.
> >
> > The thing is, we are using not supported AMO code base that have
> > long standing bugs. Upstream has switched to django and we need to do
> > the same. So, if you was thinking about easy hacking, then you was wrong ;)
> >
> 
> 
> from   AMO's Wiki [1] the migration is not yet complete:
> 
> ''This project is currently underway, and will take some cycles to complete.
> Bugs that take too much work to fix will likely be delayed until Zamboni is
> completed, in order to prevent duplicate work when porting features.''
> 
> Zamboni [2] is the code name for the Django project.
> 
> [1] https://wiki.mozilla.org/AMO:Editors/InfoEditors
> [2]http://blog.fligtar.com/2010/01/15/amo-zamboni-planning-underway/

Mozilla uses Zamboni in production
https://wiki.mozilla.org/AMO:Developers

And Remora page says "Remora is no longer maintained"
https://wiki.mozilla.org/Update:Remora

I have long running plans about close (but not in launchpad way)
integration of SL services, Bazaar + ASLO + ...
The first step (during 0.92 release cycle), I'm planing to do, will be
switching ASLO to Zamboni (with keeping existed functionality).

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

Re: [Sugar-devel] anonymous ASLO messages

[Rafael Enrique Ortiz Guerrero]

Hi all



On Tue, Nov 9, 2010 at 9:15 PM, Aleksey Lim  wrote:

> On Wed, Nov 10, 2010 at 12:18:48PM +1100, James Cameron wrote:
> > On Wed, Nov 10, 2010 at 12:20:22AM +, Aleksey Lim wrote:
> > > On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:
> > > > On Tue, Nov 09, 2010 at 11:23:46PM +, Aleksey Lim wrote:
> > > > > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > > > > > These announcements from activities.sugarlabs.org of new
> releases are
> > > > > > sent without any included identity of the person who did the
> release.
> > > > > >
> > > > > > Could activities.sugarlabs.org please be changed to include the
> releaser
> > > > > > in these messages?
> > > > >
> > > > > The problem is that uploaders don't include release notes. The
> proper
> > > > > fix might be do not accept them (from uploading checks), so patches
> are
> > > > > welcome :).
> > > >
> > > > No, I think you misunderstand.  My observation has nothing to do with
> > > > whether release notes are present in the mail message.
> > > >
> > > > Where's the code?
> > >
> > > http://git.sugarlabs.org/projects/slo-activities
> > > http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing
> >
> > The file site/app/views/editors/email/aslo/release_en_plain.thtml
> > contains what looks like the release messages, but I cannot see where it
> > is used.  What is needed is the authenticated user's e-mail address.
> >
> > > But keep in mind that current code is php/cake based and
> > > new ASLO will be based on new AMO python/django code. So, would be
> > > useful if patch is not invasive and might be applied w/o starting new
> > > development/testing/production cycle.
> >
> > That says to me, "don't do anything, your effort will be wasted, nobody
> > else cares about this problem."  Thanks for the warning.  I see no way
> > forward.
>
> The thing is, we are using not supported AMO code base that have
> long standing bugs. Upstream has switched to django and we need to do
> the same. So, if you was thinking about easy hacking, then you was wrong ;)
>


from   AMO's Wiki [1] the migration is not yet complete:

''This project is currently underway, and will take some cycles to complete.
Bugs that take too much work to fix will likely be delayed until Zamboni is
completed, in order to prevent duplicate work when porting features.''

Zamboni [2] is the code name for the Django project.

[1] https://wiki.mozilla.org/AMO:Editors/InfoEditors
[2]http://blog.fligtar.com/2010/01/15/amo-zamboni-planning-underway/









--
> Aleksey
> ___
> 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 UI Dictator

[Christian Marc Schmidt]

Whoever ends up as dictator: I'd still love to stay involved as an advisor.
I'd volunteer to throw my name into the hat for election if not for lack of
time. In any case, I agree that it would be great (and necessary) to have a
dedicated UX person who could keep the design up-to-date and consistent with
our experiential goals.

Christian

On Tue, Nov 9, 2010 at 12:27 PM, Michael Stone  wrote:

>
> On Tue, 9 Nov 2010 at 03:12:41 +, Martin Dengler wrote:
>
>> On Mon, Nov 08, 2010 at 07:49:19PM -0500, Bernie Innocenti wrote:
>>
>>> On Fri, 2010-10-29 at 10:02 +0100, Martin Dengler wrote:
>>>
 IMO a decent justification and a willingness to update the affected
 wiki pages - including the HIG - to a similar or better standard as
 what existed before should almost be enough for me.

 What I'm worried about is the HIG that exists - incomplete as it is -
 is being chipped away and we're left with UI that's justified by
 nothing but a patchwork of ad-hoc decisions made by very different
 people with very different users in mind.

>>>
>>> While I strongly believe in the power of loosely-managed
>>> volunteer-driven development, distributed authority doesn't seem to work
>>> equally well when it comes to human interface design.
>>>
>>> Good design implies one consistent vision, which is hard to obtain
>>> collaboratively. A case-by-case decision process results in either
>>> inconclusive discussions or UI inconsistency.
>>>
>>> It might work better if we agreed to delegate all design decisions to
>>> one clever dictator
>>>
>>
>> Great idea.
>>
>> Sebastian is calling for a HIG update as part of his SLOBs platform -
>> perhaps the new HIG Dictator should commit to doing that in some fixed
>> period of time?
>>
>> Failing one Dictator, erm, seizing power, perhaps we could just agree
>> on some group of people who will be the dictators, and not revisit
>> that for a while.
>>
>
> Agreeing on small group of people seems easy to arrange. Here's a strawman
> proposal for how that might look:
>  1. Per [1], the Oversight Board creates an ad-hoc 3-person UI Committee.
>
>  2. The initial voting members will be mtd, garycmartin, and  (a third
> person to be determined).
>
>  3. The initial term will be for six months.
>
> Next, there are details that we need to agree upon. For example, what does
> the
> committee do and at what rate does it do it? Another strawman:
>
>  4. The committee will meet as needed in order to address Queries received
> by
> any of its voting members.
>
>  5. The committee will meet within 2 weeks of receiving a Query.
>
>  6. Proposed Responses will be accepted by the committee by majority vote.
>
>  7. Minutes, received Queries, proposed Responses, and related discussion
> will
> be archived and organized by the Committee Secretary on the wiki.
>
> Finally, there some harder questions that I don't have easy answers for:
>  a) Who do we expect to do the work of formulating responses to Queries?
>
>  b) How will we make the committee successful and fun? In particular, how
> do
> we expect to organize the performance of the work that is necessary to
> prepare for and to follow through on the committee's decisions?
>
> (i.e., who's actually going to go out to collect experience reports,
> to perform user testing, or to develop prototypes when the Committee
> determines that these actions are necessary in order to properly
> respond
> to a Query?)
>
>  c) What kinds of disputes and/or grievances do we anticipate and how do we
> expect to resolve them?
>
> Thoughts?
>
> Regards,
>
> Michael
>
> [1]: http://wiki.sugarlabs.org/go/Sugar_Labs/Governance#Committees
>



-- 
anyth...@christianmarcschmidt.com
917/ 575 0013

http://www.christianmarcschmidt.com
http://www.linkedin.com/in/christianmarcschmidt
http://twitter.com/cms_
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] anonymous ASLO messages

[Aleksey Lim]

On Wed, Nov 10, 2010 at 12:18:48PM +1100, James Cameron wrote:
> On Wed, Nov 10, 2010 at 12:20:22AM +, Aleksey Lim wrote:
> > On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:
> > > On Tue, Nov 09, 2010 at 11:23:46PM +, Aleksey Lim wrote:
> > > > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > > > > These announcements from activities.sugarlabs.org of new releases are
> > > > > sent without any included identity of the person who did the release.
> > > > > 
> > > > > Could activities.sugarlabs.org please be changed to include the 
> > > > > releaser
> > > > > in these messages?
> > > > 
> > > > The problem is that uploaders don't include release notes. The proper
> > > > fix might be do not accept them (from uploading checks), so patches are
> > > > welcome :).
> > > 
> > > No, I think you misunderstand.  My observation has nothing to do with
> > > whether release notes are present in the mail message.
> > > 
> > > Where's the code?
> > 
> > http://git.sugarlabs.org/projects/slo-activities
> > http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing
> 
> The file site/app/views/editors/email/aslo/release_en_plain.thtml
> contains what looks like the release messages, but I cannot see where it
> is used.  What is needed is the authenticated user's e-mail address.
> 
> > But keep in mind that current code is php/cake based and
> > new ASLO will be based on new AMO python/django code. So, would be
> > useful if patch is not invasive and might be applied w/o starting new
> > development/testing/production cycle.
> 
> That says to me, "don't do anything, your effort will be wasted, nobody
> else cares about this problem."  Thanks for the warning.  I see no way
> forward.

The thing is, we are using not supported AMO code base that have
long standing bugs. Upstream has switched to django and we need to do
the same. So, if you was thinking about easy hacking, then you was wrong ;)

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

Re: [Sugar-devel] anonymous ASLO messages

[James Cameron]

On Wed, Nov 10, 2010 at 12:20:22AM +, Aleksey Lim wrote:
> On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:
> > On Tue, Nov 09, 2010 at 11:23:46PM +, Aleksey Lim wrote:
> > > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > > > These announcements from activities.sugarlabs.org of new releases are
> > > > sent without any included identity of the person who did the release.
> > > > 
> > > > Could activities.sugarlabs.org please be changed to include the releaser
> > > > in these messages?
> > > 
> > > The problem is that uploaders don't include release notes. The proper
> > > fix might be do not accept them (from uploading checks), so patches are
> > > welcome :).
> > 
> > No, I think you misunderstand.  My observation has nothing to do with
> > whether release notes are present in the mail message.
> > 
> > Where's the code?
> 
> http://git.sugarlabs.org/projects/slo-activities
> http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing

The file site/app/views/editors/email/aslo/release_en_plain.thtml
contains what looks like the release messages, but I cannot see where it
is used.  What is needed is the authenticated user's e-mail address.

> But keep in mind that current code is php/cake based and
> new ASLO will be based on new AMO python/django code. So, would be
> useful if patch is not invasive and might be applied w/o starting new
> development/testing/production cycle.

That says to me, "don't do anything, your effort will be wasted, nobody
else cares about this problem."  Thanks for the warning.  I see no way
forward.

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] anonymous ASLO messages

[Aleksey Lim]

On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:
> On Tue, Nov 09, 2010 at 11:23:46PM +, Aleksey Lim wrote:
> > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > > These announcements from activities.sugarlabs.org of new releases are
> > > sent without any included identity of the person who did the release.
> > > 
> > > Could activities.sugarlabs.org please be changed to include the releaser
> > > in these messages?
> > 
> > The problem is that uploaders don't include release notes. The proper
> > fix might be do not accept them (from uploading checks), so patches are
> > welcome :).
> 
> No, I think you misunderstand.  My observation has nothing to do with
> whether release notes are present in the mail message.
> 
> Where's the code?

http://git.sugarlabs.org/projects/slo-activities
http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing

But keep in mind that current code is php/cake based and
new ASLO will be based on new AMO python/django code. So, would be
useful if patch is not invasive and might be applied w/o starting new
development/testing/production cycle.

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

Re: [Sugar-devel] anonymous ASLO messages

[James Cameron]

On Tue, Nov 09, 2010 at 11:23:46PM +, Aleksey Lim wrote:
> On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > These announcements from activities.sugarlabs.org of new releases are
> > sent without any included identity of the person who did the release.
> > 
> > Could activities.sugarlabs.org please be changed to include the releaser
> > in these messages?
> 
> The problem is that uploaders don't include release notes. The proper
> fix might be do not accept them (from uploading checks), so patches are
> welcome :).

No, I think you misunderstand.  My observation has nothing to do with
whether release notes are present in the mail message.

Where's the code?

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] anonymous ASLO messages

[Aleksey Lim]

On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> These announcements from activities.sugarlabs.org of new releases are
> sent without any included identity of the person who did the release.
> 
> Could activities.sugarlabs.org please be changed to include the releaser
> in these messages?

The problem is that uploaders don't include release notes. The proper
fix might be do not accept them (from uploading checks), so patches are
welcome :).

> 
> -- 
> James Cameron
> http://quozl.linux.org.au/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
> 

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

[Sugar-devel] [ASLO] Release JAMesene-1

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.90

Download Now:
http://activities.sugarlabs.org/downloads/file/27096/jamesene-1.xo

Release notes:



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] [ASLO] Release CeibalTV-1

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.88

Download Now:
http://activities.sugarlabs.org/downloads/file/26924/ceibaltv-1.xo

Release notes:
Tv in sugar


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] [ASLO] Release Bubble Pop-1

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.90

Download Now:
http://activities.sugarlabs.org/downloads/file/27075/bubble_pop-1.xo

Release notes:



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] [ASLO] Release Sonata Media Player-11

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.88

Download Now:
http://activities.sugarlabs.org/downloads/file/26899/sonata-11.xo

Release notes:



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] [ASLO] Release Wordsearch-1

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.90

Download Now:
http://activities.sugarlabs.org/downloads/file/27077/wordsearch-1.xo

Release notes:



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] [ASLO] Release EduKT-3

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.90

Download Now:
http://activities.sugarlabs.org/downloads/file/27068/edukt-3.xo

Release notes:



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] [ASLO] Release MathGraph32-13

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.90

Download Now:
http://activities.sugarlabs.org/downloads/file/27093/mathgraph32-13.xo

Release notes:
Based on MathGraph32 version 3.2.4.6


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] [ASLO] Release Java-2

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.82

Download Now:
http://activities.sugarlabs.org/downloads/file/26832/java-2.xo

Release notes:
* The PATH variable shown when executing the activity was wrong
* The JRE path was changed from "jre1.6.0_18" to "jre". This aims to simpliy 
external references from other activities.
* LICENSE.txt file was added



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] anonymous ASLO messages

[James Cameron]

These announcements from activities.sugarlabs.org of new releases are
sent without any included identity of the person who did the release.

Could activities.sugarlabs.org please be changed to include the releaser
in these messages?

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [ASLO] Release FoodForce2-5

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.90

Download Now:
http://activities.sugarlabs.org/downloads/file/27102/foodforce2-5.xo

Release notes:
This is a new version of the FoodForce2 activity, Version 5

The new features are:
1. New storyline based on the events of the Haiti Earthquake.
2. New soundtracks and ambient sounds.
3. A localized version for Spanish.


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] [ASLO] Release Read SD Comics-2

[Sugar Labs Activities]

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

Sugar Platform:
0.82 - 0.90

Download Now:
http://activities.sugarlabs.org/downloads/file/27101/read_sd_comics-2.xo

Release notes:
Minor bug fix.  When creating a Journal entry I incorrectly gave it a MIME type 
of application/x-cbz, which would make it look like you could open the Journal 
entry with Read or View Slides, and in fact you can't.  The Journal entry 
points to a CBZ file, but does not contain one.


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] sugar at Latinoware

[Bruno Coudoin]

I am also there for GCompris.

Bruno Coudoin.



Le mardi 09 novembre 2010 à 11:48 -0300, Martin Abente a écrit :
> Hello amigos,
> 
> Today I am going to Brazil for a FOSS conference called
> "Latinoware" [1]. I have been invited by the Paraguayan organisation
> team to talk about Sugar and its development. One of my goals is to
> show that there have been many Latin Americans contributing to the
> project, I believe this can help to encourage the audience into
> considering Sugar for other IT based educational projects and also to
> contribute to Sugar.
> 
> So, i would like to hear about what other sugar development have been
> going on lately in Latin America? :)
> 
> I know about Paraguay (jasg, rgs and me), Uruguay (Daniel, Esteban^2
> and aa) and Argentina (gonzalo). I am pretty sure there are more
> people contributing, please cure my ignorance!
> 
> Saludos,
> Martin (tch) Abente
> 
> 1. www.latinoware.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] [PATCH] Adopt Updater to new activity version scheme

[Simon Schampijer]

On 11/08/2010 11:40 PM, James Cameron wrote:

Reviewed-by: James Cameron

Trivial, English grammar ... in the commit message, I suggest "Adapt"
not "Adopt".  Or if "Adopt" was really desired "Adopt new activity
version scheme in Updater" or "Updater adopts new activity version
scheme.".



Thanks for the review. Yes, "adapt" makes sense.

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

Re: [Sugar-devel] ObjectChooser() Issue?

[Aleksey Lim]

On Tue, Nov 09, 2010 at 03:10:56PM -0300, Gonzalo Odiard wrote:
> On Tue, Nov 9, 2010 at 3:04 PM, Aleksey Lim  wrote:
> 
> > On Mon, Nov 08, 2010 at 01:01:02PM -0500, Art Hunkins wrote:
> > > At Sasha's suggestion, I've arrived at the following code to send the
> > > filepath of a soundfile to Csound via its reference in the Journal. The
> > > filename (self.filename[0]) is being correctly passed:
> > >
> > >  def choose1(self, widget):
> > >   chooser =  ObjectChooser(parent=self,
> > what_filter=mime.GENERIC_TYPE_AUDIO)
> > >   result = chooser.run()
> > >   if result == gtk.RESPONSE_ACCEPT:
> > > jobject = chooser.get_selected_object()
> >
> > After destroying "jobject" object, you will lose
> > /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
> > file, so either keep this object or move/hard-link file somethere
> > for later usage (but remove it after using).
> >
> >
> Why is destroyed jobject ?
> Only curiosity, I have read the mail and don't understand what is the
> problem with the code.

The thing is that after creating sugar.datastore.datastore.DSObject
(here "jobject" variable) and calling "file_path", temporary file will be
created (in fact, hard link to the file stored in ds), after deleting
"jobject" this file will be removed.

Code tries to use "file_path" after deleting "jobject", thus file is
already deleted.


> 
> Gonzalo
> 
> 
> 
> > > if jobject and jobject.file_path:
> > >   self.filename[0] = str(jobject.file_path)
> > > #  open(jobject.file_path).read()
> > > #  open(self.filename[0]).read()
> > >   else:
> > > self.filename[0] = "0"
> > >
> > > The problem is that the file cannot be opened by Csound - either via the
> > > above function as it stands, or by the addition of either line that is
> > > commented out.
> > >
> > > I receive this error message (from Csound):
> > > diskinfo can't open
> > > /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
> > > The filepath and name are correct, and the file can be played fine with
> > > either Browse or Jukebox.
> > >
> > > What must I do to make the referenced soundfile readable?
> > >
> > > Art Hunkins
> > >
> > > ___
> > > Sugar-devel mailing list
> > > Sugar-devel@lists.sugarlabs.org
> > > http://lists.sugarlabs.org/listinfo/sugar-devel
> > >
> >
> > --
> > Aleksey
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >

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

Re: [Sugar-devel] ObjectChooser() Issue?

[James Simmons]

I sent this answer to Art yesterday, but I didn't send it to the
group.  I think this may be the answer to his problem.

James Simmons


On Mon, Nov 8, 2010 at 4:56 PM, James Simmons  wrote:
> Art,
>
> One thing I noted when I tried to read paths from Journal entries is
> that they don't stay valid forever.  I think they are symbolic links
> to the actual file.  If you read through a list of Journal objects
> only the current one will have a valid path, and the others get
> disconnected.  Hard coding a value that worked before isn't going to
> work.
>
> I would guess that the object chooser will give you a valid jobject.
>
> Maybe try this:
>
> jobject.get_file_path()
>
> instead of jobject.file_path.  It may be that using get_file_path()
> makes the datastore create the symbolic link, whereas just using
> .file_path just give the current value in the field, which might be
> stale.  I use .get_file_path() in Sugar Commander and it seems to work
> OK.
>
> James Simmons
>
>
> On Mon, Nov 8, 2010 at 4:36 PM, Art Hunkins  wrote:
>> James,
>>
>> I tried the following variations of my "open" line:
>> open(jobject.file_path, "r").read()
>>
>> open(jobject.file_path, "r")
>>
>> self.read_file = open(jobject.file_path, "r")
>> self.read_file = open(jobject.file_path, "r").read()
>>
>> open(self.filename[0], "r").read()
>>
>> open(self.filename[0], "r")
>>
>> self.read_file = open(self.filename[0], "r")
>> self.read_file = open(self.filename[0], "r").read()
>>
>> Same result: Csound can't open the file.
>>
>> Strangely, as well, I hardcoded the filepath of the file I was selecting
>> from the Journal into Csound - to see if one of the above would at least
>> enable the (same) file to be read. No luck; still can't open the file.
>>
>> Passing the name works fine; Csound just can't open the file. And the only
>> files I seem to be able to *open* are the ones I place in the activity's
>> folder and hardcode in Csound.
>>
>> Thanks so much for your help. Do you have any idea whether using *your*
>> Journal (and USB) methods (from your Using the Journal chapter) I'd have any
>> better luck opening soundfiles to play in Csound?
>>
>> Art Hunkins
>>
>>
>> - Original Message - From: "James Simmons" 
>> To: "Art Hunkins" 
>> Sent: Monday, November 08, 2010 1:45 PM
>> Subject: Re: [Sugar-devel] ObjectChooser() Issue?
>>
>>
>> Art,
>>
>> You probably want to put the "r" argument in your open statement like this:
>>
>>       self.read_file = open(fileName,"r")
>>
>> What may be happening is that you are by default opening the file
>> read/write, which Sugar will not allow.
>>
>> James Simmons
>>
>>
>> On Mon, Nov 8, 2010 at 12:01 PM, Art Hunkins  wrote:
>>>
>>> At Sasha's suggestion, I've arrived at the following code to send the
>>> filepath of a soundfile to Csound via its reference in the Journal. The
>>> filename (self.filename[0]) is being correctly passed:
>>>
>>> def choose1(self, widget):
>>> chooser = ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO)
>>> result = chooser.run()
>>> if result == gtk.RESPONSE_ACCEPT:
>>> jobject = chooser.get_selected_object()
>>> if jobject and jobject.file_path:
>>> self.filename[0] = str(jobject.file_path)
>>> # open(jobject.file_path).read()
>>> # open(self.filename[0]).read()
>>> else:
>>> self.filename[0] = "0"
>>>
>>> The problem is that the file cannot be opened by Csound - either via the
>>> above function as it stands, or by the addition of either line that is
>>> commented out.
>>>
>>> I receive this error message (from Csound):
>>> diskinfo can't open
>>> /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
>>> The filepath and name are correct, and the file can be played fine with
>>> either Browse or Jukebox.
>>>
>>> What must I do to make the referenced soundfile readable?
>>>
>>> Art Hunkins
>>>
>>> ___
>>> 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] ObjectChooser() Issue?

[Gonzalo Odiard]

On Tue, Nov 9, 2010 at 3:04 PM, Aleksey Lim  wrote:

> On Mon, Nov 08, 2010 at 01:01:02PM -0500, Art Hunkins wrote:
> > At Sasha's suggestion, I've arrived at the following code to send the
> > filepath of a soundfile to Csound via its reference in the Journal. The
> > filename (self.filename[0]) is being correctly passed:
> >
> >  def choose1(self, widget):
> >   chooser =  ObjectChooser(parent=self,
> what_filter=mime.GENERIC_TYPE_AUDIO)
> >   result = chooser.run()
> >   if result == gtk.RESPONSE_ACCEPT:
> > jobject = chooser.get_selected_object()
>
> After destroying "jobject" object, you will lose
> /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
> file, so either keep this object or move/hard-link file somethere
> for later usage (but remove it after using).
>
>
Why is destroyed jobject ?
Only curiosity, I have read the mail and don't understand what is the
problem with the code.

Gonzalo



> > if jobject and jobject.file_path:
> >   self.filename[0] = str(jobject.file_path)
> > #  open(jobject.file_path).read()
> > #  open(self.filename[0]).read()
> >   else:
> > self.filename[0] = "0"
> >
> > The problem is that the file cannot be opened by Csound - either via the
> > above function as it stands, or by the addition of either line that is
> > commented out.
> >
> > I receive this error message (from Csound):
> > diskinfo can't open
> > /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
> > The filepath and name are correct, and the file can be played fine with
> > either Browse or Jukebox.
> >
> > What must I do to make the referenced soundfile readable?
> >
> > Art Hunkins
> >
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >
>
> --
> Aleksey
> ___
> 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] ObjectChooser() Issue?

[Aleksey Lim]

On Mon, Nov 08, 2010 at 01:01:02PM -0500, Art Hunkins wrote:
> At Sasha's suggestion, I've arrived at the following code to send the 
> filepath of a soundfile to Csound via its reference in the Journal. The 
> filename (self.filename[0]) is being correctly passed:
> 
>  def choose1(self, widget):
>   chooser =  ObjectChooser(parent=self, what_filter=mime.GENERIC_TYPE_AUDIO)
>   result = chooser.run()
>   if result == gtk.RESPONSE_ACCEPT:
> jobject = chooser.get_selected_object()

After destroying "jobject" object, you will lose 
/home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
file, so either keep this object or move/hard-link file somethere
for later usage (but remove it after using).

> if jobject and jobject.file_path:
>   self.filename[0] = str(jobject.file_path)
> #  open(jobject.file_path).read()
> #  open(self.filename[0]).read()
>   else:
> self.filename[0] = "0"
> 
> The problem is that the file cannot be opened by Csound - either via the 
> above function as it stands, or by the addition of either line that is 
> commented out.
> 
> I receive this error message (from Csound):
> diskinfo can't open 
> /home/olpc/.sugar/default/data/f70f03b1-fe40-44e6-9d75-5ef274cf0ad2.wav
> The filepath and name are correct, and the file can be played fine with 
> either Browse or Jukebox.
> 
> What must I do to make the referenced soundfile readable?
> 
> Art Hunkins
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
> 

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

[Sugar-devel] Test

[Simon Schampijer]

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

Re: [Sugar-devel] Sugar UI Dictator

[Michael Stone]

On Tue, 9 Nov 2010 at 03:12:41 +, Martin Dengler wrote:

On Mon, Nov 08, 2010 at 07:49:19PM -0500, Bernie Innocenti wrote:

On Fri, 2010-10-29 at 10:02 +0100, Martin Dengler wrote:

IMO a decent justification and a willingness to update the affected
wiki pages - including the HIG - to a similar or better standard as
what existed before should almost be enough for me.

What I'm worried about is the HIG that exists - incomplete as it is -
is being chipped away and we're left with UI that's justified by
nothing but a patchwork of ad-hoc decisions made by very different
people with very different users in mind.


While I strongly believe in the power of loosely-managed
volunteer-driven development, distributed authority doesn't seem to work
equally well when it comes to human interface design.

Good design implies one consistent vision, which is hard to obtain
collaboratively. A case-by-case decision process results in either
inconclusive discussions or UI inconsistency.

It might work better if we agreed to delegate all design decisions to
one clever dictator


Great idea.

Sebastian is calling for a HIG update as part of his SLOBs platform -
perhaps the new HIG Dictator should commit to doing that in some fixed
period of time?

Failing one Dictator, erm, seizing power, perhaps we could just agree
on some group of people who will be the dictators, and not revisit
that for a while.


Agreeing on small group of people seems easy to arrange. Here's a strawman
proposal for how that might look: 


  1. Per [1], the Oversight Board creates an ad-hoc 3-person UI Committee.

  2. The initial voting members will be mtd, garycmartin, and  (a third
 person to be determined).

  3. The initial term will be for six months.

Next, there are details that we need to agree upon. For example, what does the
committee do and at what rate does it do it? Another strawman:

  4. The committee will meet as needed in order to address Queries received by
 any of its voting members.

  5. The committee will meet within 2 weeks of receiving a Query.

  6. Proposed Responses will be accepted by the committee by majority vote.

  7. Minutes, received Queries, proposed Responses, and related discussion will
 be archived and organized by the Committee Secretary on the wiki.

Finally, there some harder questions that I don't have easy answers for: 


  a) Who do we expect to do the work of formulating responses to Queries?

  b) How will we make the committee successful and fun? In particular, how do
 we expect to organize the performance of the work that is necessary to
 prepare for and to follow through on the committee's decisions?

 (i.e., who's actually going to go out to collect experience reports,
 to perform user testing, or to develop prototypes when the Committee
 determines that these actions are necessary in order to properly respond
 to a Query?)

  c) What kinds of disputes and/or grievances do we anticipate and how do we
 expect to resolve them?

Thoughts?

Regards,

Michael

[1]: http://wiki.sugarlabs.org/go/Sugar_Labs/Governance#Committees
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [PATCH] Adopt Updater to new activity version scheme

[Simon Schampijer]

On 11/08/2010 11:40 PM, James Cameron wrote:

Reviewed-by: James Cameron

Trivial, English grammar ... in the commit message, I suggest "Adapt"
not "Adopt".  Or if "Adopt" was really desired "Adopt new activity
version scheme in Updater" or "Updater adopts new activity version
scheme.".



Pushed as: 
http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/468fe070e0a60e9690e89a0649919509c310974e


Thanks again for taking the time to review,
   Simon
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [PATCH] Adopt to new numbering scheme #2425

[Simon Schampijer]

On 11/02/2010 12:05 PM, Gonzalo Odiard wrote:

Reviewed-by:  "Gonzalo Odiard"



Gonzalo and James, thanks for the review.

Pushed as: 
http://git.sugarlabs.org/sugar/mainline/commit/49232e552248e48063970ca67455462d11220468


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

Re: [Sugar-devel] [ANNOUNCE] git.sugarlabs.org migration and downtime

[Aleksey Lim]

On Tue, Nov 09, 2010 at 12:16:45PM +, Aleksey Lim wrote:
> On Tue, Nov 09, 2010 at 05:42:26AM +, Aleksey Lim wrote:
> > On Sun, Nov 07, 2010 at 10:33:03PM +, Aleksey Lim wrote:
> > > Hi all,
> > > 
> > > Thanks for testing new gitorious instance (if you didn't try yet,
> > > go to [1]). Since usual git.sugarlabs.org workflows looks good and since
> > > several people have ssh login issues (we are limitied in investigation
> > > these issues on current git.sugarlabs.org instance) and keeping im mind
> > > that [1] works for them, we are migrating git.sugarlabs.org to the new
> > > Gitorios code base and moving it to another host to make users support
> > > more responsive.
> > > 
> > > git.sugarlabs.org will be inaccessible starting from
> > > 2010-11-09 01:00 UTC, for 2 hours.
> > > 
> > > [1] http://jita.sugarlabs.org/
> > > 
> > > P.S.
> > > Previous request to test common SL login system was just a try to
> > > investigate this feature, git.sugarlabs.org will still use regular
> > > accounts after migration.
> > 
> > New Gitorios is ready for using from regular http://git.sugarlabs.org.
> > There are found isses that will be fixed soon:
> > 
> > * HTTP cloning doesn't work
> > * cgit.sugarlabs.org is useless
> > * http://cia.vc plugin is inactive
> 
> Since git.sugarlabs.or IP was changed, while trying to interact via ssh,
> you will be warned about that. You need to tweak ~/.ssh/known_hosts file,
> delete line with substring "git.sugarlabs.org".

For people who need to change known_hosts record manually, info about
RSA host key for new git.sugarlabs.org:

git.sugarlabs.org ssh-rsa
B3NzaC1yc2EDAQABAAABAQCmJXgCnPx+ngxdhXkIXbAy2aGHj9w5udPQDq8e5OX1X8Qvi6+C356OhL8veZDKXbn9B9Aq6HwzoK0ZzDqk9nUeY6qvBNhTNTvDLbY+0+rAskRbscNH7mcuGvp5ygTSfcTkagXK6QCj84jkhDVlPAWfKOw2vzu+7AXkoNknqXnMyHv0No3INJnDDUGM75/4KCVZqiXuojgMA4vsq9yrc1vWRMuJaMg9fvirJTJDjvc8ZOXVsbsx2GjdCyHeMxuOIKlwfkDvuptFGNeWtOS6q/w/xPRxHiwUCfBo+8NvYx8JpIr1IaP2US00oLFE823b4DSVulFXgq6jw2gFrcru7O/3

2048 4f:5e:5c:7f:ca:94:49:9d:2e:77:85:86:7c:de:56:f1

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

Re: [Sugar-devel] Request to review solution for SL #2464

[Gonzalo Odiard]

Thanks James.
The problem with the permissions in the activity.info file must be because
the last time i created the xo file by hand with zip and now i am using
setup.py
I will put this information information in the ticket.
I am trying to add fill/linux64_27 but fedora 14 is crazy in my machine...

Gonzalo


On Tue, Nov 9, 2010 at 4:13 AM, James Cameron  wrote:

> On Tue, Nov 09, 2010 at 02:33:02AM -0300, Gonzalo Odiard wrote:
> > I have uploaded a new xo to 
> > http://dev.laptop.org/~gonzalo/Paint-29.xo
> > I don't have a 0.82 system, can anybody confirm if is working ok?
>
> Tested on freshly installed XO-1 OLPC OS 8.2.1 build gg-802-1, Sugar
> 0.82.1, and it starts okay.  This addresses the problem in SL #2464.
>
> I was able to draw, quit, and then restore the drawing.
>
> There were no unusual messages in the log.  Attached.
>
> Also checked that it is essentially the same as git master for Paint,
> except for the activity.info file version line.
>
> Reviewed the changes from activities.sugarlabs.org Paint-28 and your
> Paint-29 ... apart from the code changes, the other interesting things
> were:
>
> - MANIFEST is present in -29, not in -28, (is it needed?),
> - a patch file is present in -28, not in -29, (this is good),
> - .gitignore present in -28, not in -29, (this is good),
> - fill/linux32_27 was added in -29, (this is good).
>
> Well done.
>
> --
> James Cameron
> http://quozl.linux.org.au/
>



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

Re: [Sugar-devel] Request to review solution for SL #2464

[Gonzalo Odiard]

I have added the binaries for python 2.7 in 64 bit arch

Gonzalo

On Tue, Nov 9, 2010 at 7:14 AM, Gonzalo Odiard  wrote:

> Thanks James.
> The problem with the permissions in the activity.info file must be because
> the last time i created the xo file by hand with zip and now i am using
> setup.py
> I will put this information information in the ticket.
> I am trying to add fill/linux64_27 but fedora 14 is crazy in my machine...
>
> Gonzalo
>
>
> On Tue, Nov 9, 2010 at 4:13 AM, James Cameron  wrote:
>
>> On Tue, Nov 09, 2010 at 02:33:02AM -0300, Gonzalo Odiard wrote:
>> > I have uploaded a new xo to 
>> > http://dev.laptop.org/~gonzalo/Paint-29.xo
>> > I don't have a 0.82 system, can anybody confirm if is working ok?
>>
>> Tested on freshly installed XO-1 OLPC OS 8.2.1 build gg-802-1, Sugar
>> 0.82.1, and it starts okay.  This addresses the problem in SL #2464.
>>
>> I was able to draw, quit, and then restore the drawing.
>>
>> There were no unusual messages in the log.  Attached.
>>
>> Also checked that it is essentially the same as git master for Paint,
>> except for the activity.info file version line.
>>
>> Reviewed the changes from activities.sugarlabs.org Paint-28 and your
>> Paint-29 ... apart from the code changes, the other interesting things
>> were:
>>
>> - MANIFEST is present in -29, not in -28, (is it needed?),
>> - a patch file is present in -28, not in -29, (this is good),
>> - .gitignore present in -28, not in -29, (this is good),
>> - fill/linux32_27 was added in -29, (this is good).
>>
>> Well done.
>>
>> --
>> James Cameron
>> http://quozl.linux.org.au/
>>
>
>
>
> --
> Gonzalo Odiard
>
>
>


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

Re: [Sugar-devel] [PATCH] Add new numbering scheme #2425

[Simon Schampijer]

On 11/02/2010 12:04 PM, Gonzalo Odiard wrote:

Reviewed-by:  "Gonzalo Odiard"


Gonzalo and James, thanks for the review.

Pushed as: 
http://git.sugarlabs.org/projects/sugar-toolkit/repos/mainline/commits/c7a80a1e56e4f52e280b0b1d87643899726f6c36


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

[Sugar-devel] sugar at Latinoware

[Martin Abente]

Hello amigos,

Today I am going to Brazil for a FOSS conference called "Latinoware" [1]. I
have been invited by the Paraguayan organisation team to talk about Sugar
and its development. One of my goals is to show that there have been many
Latin Americans contributing to the project, I believe this can help to
encourage the audience into considering Sugar for other IT based educational
projects and also to contribute to Sugar.

So, i would like to hear about what other sugar development have been going
on lately in Latin America? :)

I know about Paraguay (jasg, rgs and me), Uruguay (Daniel, Esteban^2 and aa)
and Argentina (gonzalo). I am pretty sure there are more people
contributing, please cure my ignorance!

Saludos,
Martin (tch) Abente

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

Re: [Sugar-devel] [ANNOUCE] git.sugarlabs.org migration and downtime

[Aleksey Lim]

On Tue, Nov 09, 2010 at 05:42:26AM +, Aleksey Lim wrote:
> On Sun, Nov 07, 2010 at 10:33:03PM +, Aleksey Lim wrote:
> > Hi all,
> > 
> > Thanks for testing new gitorious instance (if you didn't try yet,
> > go to [1]). Since usual git.sugarlabs.org workflows looks good and since
> > several people have ssh login issues (we are limitied in investigation
> > these issues on current git.sugarlabs.org instance) and keeping im mind
> > that [1] works for them, we are migrating git.sugarlabs.org to the new
> > Gitorios code base and moving it to another host to make users support
> > more responsive.
> > 
> > git.sugarlabs.org will be inaccessible starting from
> > 2010-11-09 01:00 UTC, for 2 hours.
> > 
> > [1] http://jita.sugarlabs.org/
> > 
> > P.S.
> > Previous request to test common SL login system was just a try to
> > investigate this feature, git.sugarlabs.org will still use regular
> > accounts after migration.
> 
> New Gitorios is ready for using from regular http://git.sugarlabs.org.
> There are found isses that will be fixed soon:
> 
> * HTTP cloning doesn't work
> * cgit.sugarlabs.org is useless
> * http://cia.vc plugin is inactive

Since git.sugarlabs.or IP was changed, while trying to interact via ssh,
you will be warned about that. You need to tweak ~/.ssh/known_hosts file,
delete line with substring "git.sugarlabs.org".

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