Changes between Version 14 and Version 15 of SiteUpgradeProposal/UserClearance
- Timestamp:
- Jul 29, 2012, 8:11:22 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SiteUpgradeProposal/UserClearance
v14 v15 9 9 > rationale: upper limit is a bit arbitrary here, but nevertheless should exist 10 10 2:: contains maximum of 3 characters repeated in a row 11 > rationale: depreciate something like 'aaaaa', we already havethat11 > rationale: depreciate something like 'aaaaa', as we already witness several examples for that 12 12 3:: contains maximum of 3 numeric characters 13 13 > rationale: depreciate phone numbers or PGP key-IDs … … 21 21 ==== Informal Part ==== 22 22 * 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 (commonlyin English)23 > a phonetic/all-latin transcription is strongly recommended on the user wiki page to ease developer conversation (commonly done in English) 24 24 25 25 === Enforcement === 26 Ideally we'll implement all rules in the registration procedure provided by AccountManagerPlugin. 26 Ideally 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 27 28 28 29 Of course that doesn't help for existing accounts, and we need to called the following users for clearance: