* some familiarity with the Sugar Labs git repository.
* some familiarity with the Sugar Labs git repository.
* some awareness of how Pootle interacts with the git repository.
* some awareness of how Pootle interacts with the git repository.
−
: for instance [[Translation_Team/i18n_Best_Practices#Do_not_touch_anything_inside_your_po_directory]] means the developer should not directly push PO files to the /po directory in hte git repository as it can cause errors to be generated by Pootle. Developers submitting localization of their own Activities should still work through the Pootle interface to submit string localizations of PO files.
+
: For instance:
+
:* The git tree needs to be set up in a standard form so that Pootle can easily be configured to commit PO files.
+
:*[[Translation_Team/i18n_Best_Practices#Do_not_touch_anything_inside_your_po_directory]] means the developer should not directly push PO files to the /po directory in the git repository as it can cause errors to be generated by Pootle. Developers submitting localization of their own Activities should still work through the Pootle interface to submit string localizations of PO files.
+
:* As stated below, developers will need make user:pootle a committer on their Activity's git repository.
== User:Pootle (in Sugar Labs git software repository) ==
== User:Pootle (in Sugar Labs git software repository) ==