Closed (duplicate)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
15 Jun 2011 at 19:43 UTC
Updated:
31 Aug 2018 at 14:27 UTC
Jump to comment: Most recent
Comments
Comment #1
sylvain lecoy commentedHang on it actually need more work..
Comment #2
dave reidCan you explain "The module mainly differes from OAuth module because it is modeled on a PECL." more? What does this mean? The existing OAuth module has needed lots of help and we could greatly benefit from one *good* OAuth module.
Comment #3
sylvain lecoy commentedI know but sadly my support request for PECL OAuth was refused, so when people refuse your help, you write your own isn't it ?
This module is designed it so that if you install the appropriate PECL module, nothing changes except that stuff gets faster. That's an approach we are using throughout core: Model on a PECL. That provides a known, non-Drupal-specific API (easier for new people coming to Drupal) as well as a very easy way for Sites With Root(tm) to speed up their Drupal site.
It also use native drupal entities, each application is an entity, and type can be for instance Twitter, Facebook, etc. Exactly like node type, you can define new OAuth based application type, either by code, or by admin interface. I like the way I did, a lot more extensible than the OAuth module, and much more flexible as well: If you want to use Zend library than PECL OAuth extension, you can. You can also implement your own OAuth library or wrap an already existing library.
Comment #4
jthorson commentedIt appears that there have been multiple project applications opened under your username:
Blizzard Community Platform API: http://drupal.org/node/1351312
OAuth API: http://drupal.org/node/1189680
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue.
With this in mind, I have marked your secondary applications as 'closed(duplicate)', and left one application open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one I that I have left open, then please feel free to close the 'open' application as a duplicate, and re-open one of the other project applications which I had closed.
Thanks in advance for your patience and understanding!
Comment #5
sylvain lecoy commentedYes sure no problem about that :)
Comment #6
avpaderno