Rewrite of nm.debian.org
Due to the high number of bugs and missing features I plan to rewrite nm.debian.org. This page is used to collect and discuss what we should implement. -- bzed
General
- Use the same toolkit and - if possible - template as the new db.d.o web-frontend, which is WIP at the moment, so we can share code and CSS. --bzed
- Users should be held in a generic table
- Users should be able to be members of certain groups (e.g. Applicant, App. Manager, Frontdesk, DAM)
- Should we keep all users except NMs in ldap? NM/DAM groups are available there already -- bzed
- Store First/middle/last name in separate fields as we need that for creating the LDAP accounts. (Middle name should be optional.)
- Better session handling and ACLs (#510605 *cough*)
- Explore the idea raised at DC8 about a single-sign-on solution for nm/bugs/pts/whatever (ask djpig). -- Myon
- As we reuse parts of code of db.debian.org authentication for both should be possible without any larger problems. SSO with pages which don't use python-beaker is more complicated. -- bzed
03:31:32 < luk> password reset should be possible through the website and check for right syntax of email address and URLs (gpg page) should stay or better yet improve
- Automatic checks for AM/NM activity. Unassign NMs which are on AM hold for a longer time automatically, so AMs don't have to take care of pinging etc. them.
- Automatic unassignments sound like a very bad idea - a "remind me" feature asking for a status update is probably more valueable. -- Myon
- Automatic gpg key checks. Also validate email and GPG key by sending an encrypted message.
The page should be translateable -- bzed
Add statistics like http://molly.corsac.net/~corsac/debian/nm/? http://molly.corsac.net/~corsac/debian/nm-time/
- In the past some people advocated (or tried to) themself. This should be more child-safe. E.g. by checking if the avocate account really
- exists. A login for the advocate would be even better to prevent spoofing. -- mkoch
- IRC bot for modifying the #debian-newmaint and #debian-devel channel topics
AM/FD/DAM pages
- Warn before deleting an applicant.
- History of deleted applicants, probably an undelete function.
- Allow to upload mbox files and report instead of sending it by mail??? Probably with imap access to it (yes, I'm crazy). Just an idea.... -- bzed
- I'm not sure that I like the IMAP access idea, but otherwise seconded (as a sidenote, there is a feature request for at least including a link to the public report in the BTS) --aptituz
- DAM would like a cut-and-paste template for RT tickets for account creation.
- Wiki-like template repository?
- There's wiki.d.o, with the DAM templates I meant filled-out forms with first/middle/last name, key fpr, account, email forward -- Myon
- Add DM Information about applicant. -- bzed
- Check if there're MIA entries for an email address (especially interesting for former DDs who want to get their account back) -- bzed
- Automatic created todo lists for FD (like pinging people after some time) - ticket system like -- bzed
NM pages
- Users should be able to register for a proper account to
- Update data (name, email address)
- Upload his/her GPG key
- Currently, such requests are handled by AM/FD. I wouldn't introduce NM logins unless there's a real benefit. -- Myon
- Well, the intention was to add time savers where possible and let such changes happen were they belong, too (IMHO). Is there any strong argument that speaks against accounts? -- aptituz
- I don't really object, I just think it's overkill, data changes don't happen that often, and gpg keys need to be manually associated to the NM anyway. -- Myon
- Well, the intention was to add time savers where possible and let such changes happen were they belong, too (IMHO). Is there any strong argument that speaks against accounts? -- aptituz
- Currently, such requests are handled by AM/FD. I wouldn't introduce NM logins unless there's a real benefit. -- Myon
- Acceptance of SC, DFSG, DMUP etc. could be tested automatically by sending the applicant a mail, which he would need to sign and send back (would also test if the applicant is able to use GPG)
- I think it is much more personal if such tasks are handled by the AM -- bzed
- As above, was only intended as a time saver, but its not really hard to keep this as it is. --aptituz
- I think it is much more personal if such tasks are handled by the AM -- bzed
- Instead of letting the applicant enter an advocates email address, it would eventually make sense to have a link on the NM page ("I want to advocate") where one can enter his/her debian login, which triggers the usual advocation mail exchange.
- That's basically how it currently works. -- Myon
Ooops. Indeed. My mind played tricks with me.
--aptituz
- That's basically how it currently works. -- Myon
- It should be possibly to have multiple advocates for a single applicant (in case we ever decide that more then one advocation is needed)
- Seconded. -- Myon
- Make it possible for people to be processed several times: e.g. DM process, then NM process, or returning emeritus developers
Yes. How about, when someone applies, FD is able to just click the fields needed (P&P1, sign DMUP, T&S etc)? If we added "roles" like DM, returning emeritus, non-uploading DD, uploading DD etc. to it to pre-select fields, that'd be even easier. This way, FD, DAM and the assigned AM share a flexible checklist. -- jhr
- Scan LDAP for newly created accounts, fill account creation date automatically.
List sponsored packages, sponsors and allow sponsors to add their comments. Also add tasks for sponsors to go trough with the NM. See <4A40C536.4070105@debian.org> on debian-project@l.d.o
- Notify NMs when their page was modified
GPG coordination pages
- Idea: make things work without any password, just by gpg-signed email. -- Myon