Comment 4 for bug 276488

Revision history for this message
Curtis Hovey (sinzui) wrote : Re: No way for an admin to override a reserved name for a project

I think it is time to workout how to do this in the UI. We are blocked on field validation. We want admins and registry admins to have permission to name projects.

We commonly create alternate fields (with different validation rules) in views when we want to violate the behaviour of a field. I would like to solve this a different way. If this is just an web issue, then we could allow the view to remove the validation error after performing a secondary check that the user has permission. I do not think this is about the web UI, I might want to create several projects using Lp API. I want allow BlacklistableContentNameField to check if the user has permission to ignore the blacklist. Fields to not know about the user though. validation is separate from permission.