[WG: I18N & L10N] [Management] Sakai 3 Q1 Status

[Beth Kirschner]

Hi Ian and others,

   I've heard conflicting reports on whether or not the Google Gadgets spec completely implemented in regards to dynamic Message formatting, so it would be nice to hear directly from someone in the Sakai3 UI implementation group on its status. 

Thanks!
- Beth

On Oct 1, 2010, at 12:38 PM, Ian Boston wrote:

> Jean-Francois,
> 
> On a technical level:
> Could you comment on where the Google Gadgets specification for i18n and i10n [1] falls short of your needs, as this this is the standard that has been adopted.
> 
> Please also remember that this standard is used to reformat the templates before processing so will accept parameterized i18n and i10n replacements.
> 
> I did ask at Denver and afterwards but didn't get a response and forgot to follow up.
> 
> Thanks
> Ian
> 
> 1 http://code.google.com/apis/gadgets/docs/i18n.html
> On 30 Sep 2010, at 09:36, Jean-Francois Leveque wrote:
> 
>> Hi Alan,
>> 
>> Could you tell me about the internationalization efforts done since the 
>> Denver conference?
>> 
>> Thanks
>> 
>> J-F
>> 
>> --
>> Jean-Francois Leveque
>> Australe CTO (local Sakai)
>> University Pierre and Marie Curie
>> France
>> 
>> Alan Marks a écrit :
>>> As you may know, 30 September (tomorrow, here) is the official deadline 
>>> to be complete with the Q1 deliverable for the Sakai 3 project [1]. If 
>>> you're on the UI Dev or Nakamura lists, it'll be no surprise that we're 
>>> not finishing tomorrow. So, how are we doing? Actually, in my book, 
>>> pretty well. The dev teams have been killing huge numbers of bugs over 
>>> the past couple of weeks (something like 200 bugs this week, yes that 
>>> includes dupes etc.). Also, folks doing QA have been a great job of 
>>> filing them. We're currently at 65 UI bugs and 9 Kern. I actually LOVE 
>>> to see that kind of churn at this stage. 
>>> 
>>> When you consider that we have been doing parallel design and 
>>> development, and ramping the team up at the same time, I feel great 
>>> about where we are.
>>> 
>>> And, IMO, the product is looking more functional and stable every day. 
>>> My feeling, and this is based both on functionality as well as bug 
>>> trends, is that we're narrowing in and not far away. But I'm not brave 
>>> enough to put a date in this email. 
>>> 
>>> I will however, send more frequent updates as to how we're doing to keep 
>>> people apprised. I know I've been heads down for a bit.
>>> 
>>> So, what's next? Well, we're going to keep chugging along, getting the 
>>> bug count down to zero, continuing QA. As well, to help with getting to 
>>> zero bugs, we'll be applying a higher bar to bug acceptance, starting 
>>> tomorrow. 
>>> 
>>> Additionally, we'll be holding some bug bashes, where we will ask folks 
>>> to come together for an hour and bang on the product together, to try to 
>>> find lots of bugs. Look for an invite soon.
>>> 
>>> Send any questions my way, 
>>> 
>>> Thanks
>>> 
>>> Alan
>>> 
>>> 1. http://sakaiproject.org/blogs/alan-marks/sakai-3-project-schedule
>>> 
>>> -- 
>>> 
>>> Alan Marks | Sakai 3 Project Director
>> 
>> _______________________________________________
>> sakai-ui-dev mailing list
>> sakai-ui-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
> 
> _______________________________________________
> sakai-ui-dev mailing list
> sakai-ui-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
> 
>