Last modified: 2014-06-02 20:13:42 UTC
OAuth consumer registrations should not be blocked by a human approval process. I've been waiting on approval for a consumer for over a week now and I've had similar problems in the past. This is disruptive to my development work and (I'm pretty sure) not necessary. Expected behavior: OAuth registration requires no approval (like Twitter, for example) Actual behavior: New OAuth consumer registrations take weeks or more to be approved.
I'm not sure what the rationale for having a manual approval process is/was. The Wikimedia stewards are generally very responsive... so I have a feeling that stewards may not yet be in charge of approvals? Or perhaps the queue isn't visible enough. The slow approval process definitely sounds like there's a bug somewhere, though.
We made the decision to have the approval process at first because we weren't sure how it was going to be used, and what way we would need to extend the protocol (for example, Twitter still requires an approval process to us xAuth). We certainly discussed not having approvals in the future. Or having the application send a notification to the admins. We can certainly add a feature flag for it the applications should be approved or not (Patches welcome. Adding features is something I do in my spare time, which I haven't had any of in a while). I'd like to finish turning the process over to the stewards and make sure that's what they want before flipping the switch though.
