Weekly Report on Debian New Maintainers
          =======================================

For week ending 02 Aug 2009.

Weekly Summary Statistics
=========================
6 more people applied to become a Debian Developer
0 applicants became maintainers.


Applicants with no advocate
===========================

Random checks
===============
The following applicants have completed all checks but are not
approved by their AM:


The following applicants are not AM approved but have an inactive AM:

  [email protected] (adeodato)
  [email protected] (luk)

The following applicants have been on hold longer than 6 months:

  [email protected] (bas)                                     2007-08-20
  [email protected] (bas)                     2007-08-20
  [email protected] (madcoder)                                  2007-11-10
  [email protected] (adn)                                 2007-11-17
  [email protected] (bruno)                           2008-03-16
  [email protected] (bas)                                       2008-04-18
  [email protected] (bzed)                                      2008-06-29
  [email protected] (lucas)                                  2008-07-13
  [email protected] (luk)                                         2008-10-19
  [email protected] (brlink)                                   2008-10-31
  [email protected] ()                                           2009-01-12
  [email protected] (bzed)                                  2009-01-15
  [email protected] (bzed)                            2009-01-18
  [email protected] (bzed)                                           2009-01-22
  [email protected] (anibal)                                    2009-01-23


Database inconsistency errors
-----------------------------
  AM name is in brackets.
AM confirm date occurs before AM assignment date
  [email protected]: 2009-06-23 occurs after 2007-06-25 (bzed)
  [email protected]: 2009-06-23 occurs after 2008-05-03 (bzed)


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to