New Proposal Template This page has been created from a template that uses "zones." To proceed:
Edit the page
Replace sample content within each zone-data tag with your own content
Remove this notice
Save the page
When you are ready for community review, move this page to the Ready for Review section on the edit page.
No placeholders allowed! Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.
Zend_Service_Instagram is a full implementation of the official Instagram API. It provides an object oriented interface to the API and returns data in JSON format or PHP data objects.
3. Component Requirements, Constraints, and Acceptance Criteria
Most requirements take the form of "foo will do ...." or "foo will not support ...", although different words and sentence structure might be used. Adding functionality to your proposal is requirements creep (bad), unless listed below. Discuss major changes with your team first, and then open a "feature improvement" issue against this component.
This component will fully implement Instagram official API.
This component should namespace the API methods as they are stated in Instagram's API documentation.
This component will not support real-time photo updates.
4. Dependencies on Other Framework Components
Zend_Oauth
Zend_Service_Exception
Zend_Http_Client
Zend_Http_Client_Adapter_Curl
Zend_Http_Client_Exception
5. Theory of Operation
Zend_Service_Instagram will allow a developer an easy interaction with the Instagram API in a object oriented manner, supporting such actions as getting users' information, browse through popular media, manage users' relationships, comments, likes, tags and locations. All data returned can be represented whether in JSON format or as php data objects. Zend_Service_Instagram creates a php client for the Instagram API.
6. Milestones / Tasks
Milestone 1: Proposal, Community Review and Acceptance.
Milestone 2: Unit tests exist, work, and are checked into versioning system.
Milestone 4: Initial documentation exists.
#If a milestone is already done, begin the description with "[DONE]", like this: