Changes between Version 14 and Version 15 of SiteUpgradeProposal/UserClearance


Ignore:
Timestamp:
Jul 29, 2012 10:11:22 PM (2 years ago)
Author:
hasienda
Comment:

start listing status of username check implementation by AccountManagerPlugin

Legend:

Unmodified
Added
Removed
Modified
  • SiteUpgradeProposal/UserClearance

    v14 v15  
    99> rationale: upper limit is a bit arbitrary here, but nevertheless should exist 
    1010 2:: contains maximum of 3 characters repeated in a row 
    11 > rationale: depreciate something like 'aaaaa', we already have that 
     11> rationale: depreciate something like 'aaaaa', as we already witness several examples for that 
    1212 3:: contains maximum of 3 numeric characters 
    1313> rationale: depreciate phone numbers or PGP key-IDs 
     
    2121==== Informal Part ==== 
    2222 * Unicode chars allowed - planned after upgrading to Trac 1.0 
    23 > a phonetic/all-latin transcription is strongly recommended on the user wiki page to ease conversation (commonly in English) 
     23> a phonetic/all-latin transcription is strongly recommended on the user wiki page to ease developer conversation (commonly done in English) 
    2424 
    2525=== Enforcement === 
    26 Ideally we'll implement all rules in the registration procedure provided by AccountManagerPlugin. 
     26Ideally we'll implement all rules in the registration procedure provided by AccountManagerPlugin. Current status: 
     27 4: use `username_char_blacklist = : []` - note the blank in-between 
    2728 
    2829Of course that doesn't help for existing accounts, and we need to called the following users for clearance: