Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread David Farning
ect: Re: [Sugar-devel] [ASLO] Tech Report > > On Wed, Mar 9, 2011 at 8:25 AM, Walter Bender > wrote: > > > On Wed, Mar 9, 2011 at 8:18 AM, Chris Leonard > wrote: > > I don't think it is necessarily essential to report current status on every &g

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Chris Leonard
On Wed, Mar 9, 2011 at 8:25 AM, Walter Bender wrote: > On Wed, Mar 9, 2011 at 8:18 AM, Chris Leonard > wrote: > > I don't think it is necessarily essential to report current status on > every > > language, that is tracked by the hosting L10n envirnment. I was > suggesting > > something much simp

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Walter Bender
On Wed, Mar 9, 2011 at 8:18 AM, Chris Leonard wrote: > I don't think it is necessarily essential to report current status on every > language, that is tracked by the hosting L10n envirnment.  I was suggesting > something much simpler. > > Yes/No on POT generated and hosted somewhere (or other L10n

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Chris Leonard
I don't think it is necessarily essential to report current status on every language, that is tracked by the hosting L10n envirnment. I was suggesting something much simpler. Yes/No on POT generated and hosted somewhere (or other L10n equivalent). A link to where L10n on the Activity is performe

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Aleksey Lim
On Wed, Mar 09, 2011 at 07:40:44AM -0500, Chris Leonard wrote: > It would be highly desirable for ASLO to reflect the i18n status of an > Activity, ideally with a link to where the L10n of that activity is hosted > (it doesn't have to be translate.sugarlabs.org). Far too many of the > Activities h

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Aleksey Lim
t; > Cc: Aleksey Lim; sugar-devel@lists.sugarlabs.org > > Subject: Re: [Sugar-devel] [ASLO] Tech Report > > > > On 13 February 2011 16:31, David Farning > > wrote: > > > > > > On the content side, the New Zealand testers would be perfect fit &g

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Chris Leonard
It would be highly desirable for ASLO to reflect the i18n status of an Activity, ideally with a link to where the L10n of that activity is hosted (it doesn't have to be translate.sugarlabs.org). Far too many of the Activities hosted in ASLO have not been internationalized / localized and believe t

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread David Farning
> -Original Message- > From: tabitha.m...@gmail.com [mailto:tabitha.m...@gmail.com] On Behalf Of > Tabitha Roder > Sent: Wednesday, March 09, 2011 3:42 AM > To: David Farning > Cc: Aleksey Lim; sugar-devel@lists.sugarlabs.org > Subject: Re: [Sugar-devel] [ASLO] T

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Tabitha Roder
On 13 February 2011 16:31, David Farning wrote: > On the content side, the New Zealand testers would be perfect fit for > editors. Every weekend they could go through the queue of uploaded > activities for the week and approve the one without regressions. > > There would be a strong incentive for

Re: [Sugar-devel] [ASLO] Tech Report

2011-03-09 Thread Aleksey Lim
On Sun, Feb 13, 2011 at 01:21:10AM +, Aleksey Lim wrote: > This is activities.sugarlabs.org report to cover only technical > ASLO aspects. > > == Roadmap == > > The upstream is in process of switching to new AMO code base, django > based (python based framework). We need to do the same. So, t

Re: [Sugar-devel] [ASLO] Tech Report

2011-02-12 Thread David Farning
On Sat, Feb 12, 2011 at 7:21 PM, Aleksey Lim wrote: > This is activities.sugarlabs.org report to cover only technical > ASLO aspects. > > == ASLO maintaining == > > Actually, we didn't have any explicit workflows except just coding ASLO > patch on top of AMO code base, maintaining ASLO servers, an

[Sugar-devel] [ASLO] Tech Report

2011-02-12 Thread Aleksey Lim
This is activities.sugarlabs.org report to cover only technical ASLO aspects. == ASLO maintaining == Actually, we didn't have any explicit workflows except just coding ASLO patch on top of AMO code base, maintaining ASLO servers, and more or less regular approving of new activities by not many pe