-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove "cal" from restricted_usernames #184
Conversation
People's names can have "cal" in them. For example, reasonable names like "mattmcal" would be rejected for having cal as a substring.
Maybe keep it only for groups
2019年8月28日(水) 16:01 fydai <notifications@github.com>:
… People's names can have "cal" in them. For example, reasonable names like
"mattmcal" would be rejected for having cal as a substring.
------------------------------
You can view, comment on, or merge this pull request online at:
#184
Commit Summary
- Remove "cal" from restricted_usernames
File Changes
- *M* ocflib/account/creation.py
<https://github.com/ocf/ocflib/pull/184/files#diff-0> (2)
Patch Links:
- https://github.com/ocf/ocflib/pull/184.patch
- https://github.com/ocf/ocflib/pull/184.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#184?email_source=notifications&email_token=AAFTUFAGHHJEP3MLQM626DDQGYPDXA5CNFSM4IQ4YITKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HH2YCQA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAFTUFDHXLSHODU7SSPZV4DQGYPDXANCNFSM4IQ4YITA>
.
|
These names are still allowed, they just go through manual approval. We almost never have to manually approve names so I'd rather play this safe and keep it in. |
We never have to manually approve these names because there's a huge yellow warning saying "Username contains restricted words". It is very reasonable for names to contain the substring "cal". So I think it's reasonable to default-allow these names. |
Perhaps an alum from before my time can give more context on why we have this policy in the first place? |
The university doesn't like it when student groups use one of its trademarks (e.g. Cal, Berkeley, ...) IIRC we have traditionally extended this rule to apply to usernames. (Thus an acapella group, for example, can't create an account called In general, I believe it's wise to respect the university's wishes regarding matters like these. *.berkeley.edu domain names for student groups are, after all, a privilege from the University, one they could take away (and in summer 2013, actually contemplated doing so). On the other hand, we have persistently had a Scunthorpe Effect problem here. Perhaps we should look into fixing that? |
All group accounts are manually created (by a staff running approve). As such, I think a suitable compromise would be to remove "cal" from restricted_usernames (allowing users to use a "cal" syllable) and put a (overridable) check into the approve script prompting for confirmation if the username begins with the substring "cal". What do you all think of this idea? |
IIRC, at least at my time, we had an aversion to individuals picking usernames containing "cal". Perhaps @daradib could shed some light on whether I understood this rule correctly and if it is still useful? If not I would have no objection to restricting only for group accounts. |
Did you read the 8 other comments on this PR? |
This makes sense to me. For non-group accounts, things will get caught by the real name checker (a la https://failure.ocf.berkeley.edu/rebuild/2019-11-26#319881). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved pending ocf/approve#25
People's names can have "cal" in them. For example, reasonable names like "mattmcal" would be rejected for having cal as a substring.