* teams:
  [ ] track translation team inactivity
      - File bugs for issues reported to web-translators [yavor]
      - Generate status reports from team leaders' reports and bugs
        handling [yavor]
  [ ] get reports by team leader
      - We have to decide about the frequency and format, perhaps
        make a recommended template [yavor]

* procedures:
  Draft procedures to be discussed with the team leaders before they
  become official, see draft-procedures.txt [yavor]
  [ ] finding a translation team
  [ ] joining an existing team
  [ ] create a new team
  [ ] becoming a team leader
  [ ] granting write CVS access
  [ ] requirements to publish a translation (e.g. number of reviews needed)

* resources:
  [ ] mailing lists
  [ ] savannah projects
  [ ] cvs repos
  [ ] mail aliases
  [ ] rt queue

* pending tasks (some of them listed as bugs or tasks in trans-coord):
  [ ] update /server/translations
  [ ] update or move /server/standards translation related content
  [ ] important languages w/o teams
      - Probably keep a list at /server/takeaction [yavor]
  [ ] recruit more volunteers as web-translators staff
      - We're currently 4 people for ~20 teams (many of them inactive,
        though).  In case the revamping of the coordination process is
        followed by an influx of more teams and more activity, we'll
        have to think about recruitment.  For now, we need more
	translators :-) [yavor]
  [ ] update web-translators-?? mail aliases
  [ ] announce translation priorities page (www, trans-coord and rms)

* ideas:
  [ ] priority translations page (usually requested by rms)
  [ ] evaluate new leaders
      - Questionnaire [yavor]
  [ ] request team project planning
      - This is a bit touchy area, better to discuss on the ML [yavor]
  [x] create a page with translation priorities
  [ ] Regarding /software: communicate with the GNU maintainers and
      maintain a list of packages where we have blanket permission to
      commit translations without specific approval.  To make
      translators' life easier, maintain a list of such packages.
      Encourage team leaders to give warm welcome to such occasional
      contributors (translators of /software) and eventually recruit
      them as regular team members. [yavor]