Apparently the warning that comes out of failing to assign a bug to the user is more confusing than is helpful. A contributor who hasn't yet to become a committer doesn't really know much about how WebKit Bugzilla works and a scary warning like this one misleads the contributor to think that he needs to ask for edit rights. We should just get rid of this warning message. I've met at least 3 new contributors who have complained about this problem.
Created attachment 192116 [details] Don't encourage new contributors to ask for EditBugs privileges
when does this message show up? with webkit-patch upload? Can we query bugzilla and figure out if the user has editbugs permissions?
(In reply to comment #2) > when does this message show up? with webkit-patch upload? > > Can we query bugzilla and figure out if the user has editbugs permissions? New users are incredibly confused by that message.
(In reply to comment #3) > (In reply to comment #2) > > when does this message show up? with webkit-patch upload? > > > > Can we query bugzilla and figure out if the user has editbugs permissions? > > New users are incredibly confused by that message. new users of what?
(In reply to comment #2) > Can we query bugzilla and figure out if the user has editbugs permissions? We could parse their permissions page, yes. I'm not sure it's worth the effort.
> > New users are incredibly confused by that message. > > new users of what? Of webkit-patch. People who get started on WebKit always ask on IRC about that error.
Honestly, I don't really care. :) We could do something more elegant. I guess I don't notice folks asking for EditBugs. I definitely notice folks who fail to ever ask for it. :) Another solution would be to just get rid of edit bugs.
Comment on attachment 192116 [details] Don't encourage new contributors to ask for EditBugs privileges Clearing flags on attachment: 192116 Committed r145270: <http://trac.webkit.org/changeset/145270>
All reviewed patches have been landed. Closing bug.