Skip to content
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

Merged
merged 1 commit into from
Apr 7, 2020
Merged

Conversation

fydai
Copy link
Contributor

@fydai fydai commented Aug 28, 2019

People's names can have "cal" in them. For example, reasonable names like "mattmcal" would be rejected for having cal as a substring.

People's names can have "cal" in them. For example, reasonable names like "mattmcal" would be rejected for having cal as a substring.
@nattofriends
Copy link
Member

nattofriends commented Aug 28, 2019 via email

@dkess
Copy link
Member

dkess commented Aug 28, 2019

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.

@fydai
Copy link
Contributor Author

fydai commented Oct 30, 2019

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.

@dkess
Copy link
Member

dkess commented Oct 31, 2019

Perhaps an alum from before my time can give more context on why we have this policy in the first place?

@kpengboy
Copy link
Member

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 calacapella or something like that.)

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?

@fydai
Copy link
Contributor Author

fydai commented Nov 27, 2019

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?

@kpengboy
Copy link
Member

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.

@nattofriends
Copy link
Member

Did you read the 8 other comments on this PR?

@cg505
Copy link
Member

cg505 commented Dec 29, 2019

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".

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).

Copy link
Member

@ja5087 ja5087 left a 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

@fydai fydai merged commit fcd0bba into master Apr 7, 2020
@fydai fydai deleted the not-a-github-web-branch branch April 7, 2020 03:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants