<?xml version="1.0" encoding="UTF-8"?>
<!-- name="generator" content="pyblosxom/1.4.1 7/27/2007" -->
<!DOCTYPE rss PUBLIC "-//Netscape Communications//DTD RSS 0.91//EN" "http://my.netscape.com/publish/formats/rss-0.91.dtd">

<rss version="0.91">
<channel>
<title>Блогчетање   </title>
<link>https://danilo.segan.org/blog</link>
<description>Данилово блогче</description>
<language>en</language>
<item>
  <title>GTP Spokesperson training</title>
  <link>https://danilo.segan.org/blog/gnome/gtp-spokesperson-training</link>
  <description><![CDATA[
<p>If you are attending <a href="http://guadec.org">GUADEC</a> in
Birmingham, are interested in <a href="http://gnome.org">GNOME</a> and
<a href="http://live.gnome.org/TranslationProject">translation</a>,
and have an hour or two weekly to spend on GNOME, I'd like to invite
you to the GTP Spokesperson training session:</p>

<center><strong>Friday, 12:30 local time</strong> (right before lunch)<br />
Meet me at the shirt give-away desk</center>

<p>So, the idea is to fix the bottleneck that <a
href="http://menthos.com">Christian Rose</a> and myself are at the
moment: we are too busy with lots of stuff, so new contributors and
administrative tasks revolving around updating teams database, and
module database sometimes stall for too long (for a while, Claude
Paroz has been very helpful with that).</p>

<p>And, if you decide to help out (and I feel I can trust you with
this), it won't involve more than 20 minutes of work every week, and I
hope to get a "GTP Coordination Team" up of at least 5 people who'll
be authorised and familiar with how to manage GNOME translation teams.
And for sacrificing this amount of time, you'll get more fame in GNOME
— of course, I'd expect to already have online trust in you :)</p>

<p>The training session won't take more than 15 minutes, so you'll be
able to get yourself some food before the next session starts.</p>

<h3>Topics to handle</h3>

<dl>
<dt>Module branching</dt>
<dd>Updating status pages with the latest info</dd>
<dt>Translation team changes</dt>
<dd>Handling coordinator changes and new team registrations</dd>
<dt>l10n bugs handling</dt>
<dd>Tracking Bugzilla l10n bugs, updating contacts, documenting
component creation</dd>
<dt>String freeze breakages</dt>
<dd>How to handle string freeze breakages</dd>
</dl>

]]></description>
</item>

</channel>
</rss>
