NM/FD/DAM TODO-list for Debconf

Debconf11 news
 - minechangelogs FASTER (not packaged, a webservice really)
 - some work done on the new site (using the new web layout of course, for some minutes available at 
 http://10.11.2.216:5000/ if you are at debconf, if you were AM in October, you might use your nm.d.o login credentials, but there is not much to see :)) - help appreciated 
 http://anonscm.debian.org/gitweb/?p=nm/nm.git;a=summary

State of things
 - more AMs than NMs (or almost)
 - NM takes less
 - DAMnation is becoming a thing of the past
 - FD needs help (from AMs)

Things not many people know, but should
 - minechangelogs
 - DDPortfolio (link: ddportfolio.debian.net)

Proposals
 - application timeouts? document a (normally) expected time (so it sets an expectation or a target for AM and applicant) (http://lists.debian.org/debian-mentors/2010/10/msg00005.html actually worked informally without creating a rule that needs to be strictly enforced), provide easy way to set/reset holds or implement timed holds
 - CC-ing conversation to an archiving address: details, can it be done, would it be useful, would it feel natural enough?
   * This helps to understand when and where the application got stuck, without
     having to chase the missing side.
   * Using it only as Cc: or as main mail address (which also forwards things to
     the AM)? The second approach makes conversation more impersonal.
   * Archives public (to DDs? to NM committee?). Someone could be discouraged
     when applying knowing that the discussion will be public.
   * Might bring privacy issues, but could be workarounded by not CCing the
     address when needed.

 - bring out the message that any Debian activity should be visible somehow (example: sponsored NMUs via minechangelogs, BTS patches through BTS archives, ...) (atm package reviews on -mentors aren't, for example). Prompt teams to make sure this happens, because it makes people's NM process as easy as it should be

 - teams as the main entry points
    - document that joining debian *usually* starts with joining a team
    - document that teams should encourage good members in becoming DDs
    - document that you usually start joining NM when other teammates tell you "do it"
     (risk of team attention seekers)
    - means every team decision making process is functionnal?

 - move account name and ID check into activity-poll and even do some automatically at registration time on the website (we want to authenticate the web page users with this account name, even NMs so they can update their personal details if necessary)
 - in documentation, replace acronyms with expanded forms, since acronyms are confusing (NM
   doesn't make you DM, then AM FD DAM and applicants are NMs and so on)


Open questions
 - do we need separate templates for non-uploading DDs? Do we need special templates for special groups (like the webteam?)
   * The AM is anyway supposed to adapt them to the actual candidate
   * At the moment, lots of questions are about packages; teams are asked to
     write other sort of questions regarding their specific job.
   * (right now there is one non-uploading NM in the queue)
 - find a place/workflow for publishing some interesting/useful replies to NM questions, with permission
 - name-mbox@nm.debian.org

Brainstorming
 - unknown bits of Debian hidden from templates
    - debian-email
    - what parts of Debian violate SC "we won't hide problems" and why?