Meeting, UDS Meeting and Roadmap for Saucy Salamander. We need you!

[Pierre Slamich]

I'm cc-ing ubuntu-translators.* Most people will want to read from the 4th
point.* The first 3 are for David :-)

It's basically about *preparing this week's meeting and the virtual Ubuntu
Desktop Summit next week, which is our chance to grab developer attention
and push forward the big issues for Saucy Salamander.* I think that we're
gonna fail *unless we're very prepared and able to grab developer's
attention, put our points and request clearly and in a short way*.

Here's the* link for the Saucy Salamander Roadmap. We'll use it this week
in our translators meeting, so fill it in right now, link the annoying
bugs, your wild ideas, prioritize, brainstorm, wish as much as your want
AFTER reading point 4 below :-)*

https://docs.google.com/document/d/11Xzp6depA75AZ7m5M8y29AJarrjWHi7GR0efF8xrBA4/edit

-------------------
1. Thanks a lot for the fix on the statistic tools :-)
2. I meant a similar installation to the current statistics install that
would track instead of Ubuntu the 4 templates (main,multiverse, restricted
and universe) of the DDTP in all languages (available here:
http://translations.launchpad.net/ddtp-ubuntu/raring)
3. The different use cases are (I've tested those for a month on the French
team on a weekly newsletter, and it's been VERY efficient) :
- generate for teams each week a snippet for their language (that could be
automatically sent to the team leader or directly to the mailing list),
including: Absolutes & WoW change for Ubuntu translated, to be reviewed,
Absolute & WoW changes for each pool of the DDTP, as well as being able to
export from your tool the untranslated packages for each language,
 Absolutes & WoW change (for translated & to be reviewed).
- generate for the UWN (that could be automatically sent to them) each week
a snippet and on Top 5 languages (to get an overview of the important
locales), and on top 5 top movers (to stimulate smaller teams).
----------------------
4. For the UDS, can we expect to have actual developers listening (either
Canonical or non Canonical) and willing to take action, or will it just be
a time to realize the sorry state of affairs and wish we could code/had
more time ?

The translations warrant a full track. I'm unsure if we should do:
-a general session,
-a session for each bug that we turn into a blueprint
-a session for each "General Issue" with the risk of having to leave stuff
behind

Will our session slots conflict with more "important slots" ?
We have filed all the bugs required, and it's just attention grabbing. Can
we hijack other slots to push requests as needed ?

We can have a very clear and detailed general roadmap by then, we can turn
the bugs into blueprints if that's going to change things, and then it's
mostly bug fixing and hacking.

I have a couple of ideas, a couple of devs I would like to get my hand on.
There's the trello, the ubuntu-translators coordinators
MVO for the packaging stuff,
MPT for the frontend integration of the translations, and a way to
contribute more easily,
the guy from the Online App Catalog to do the same as MPT,
some folks from Launchpad to give us details on how to solve timeouts,
developper X for the automation of langpacks,
and a truckload of things I have in a dream vision…


Pierre Slamich
pierre.slamich at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-translators/attachments/20130509/a4de4725/attachment.html>