Closed
Bug 799553
Opened 12 years ago
Closed 11 years ago
build api for posting feedback
Categories
(Input :: General, defect, P2)
Input
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 895675
People
(Reporter: willkg, Assigned: willkg)
References
Details
(Whiteboard: u=dev c=general p= s= )
Currently we have a single feedback form which posts feedback to the site. Firefox Mobile has their own UI and they post the feedback data to Input. This is sort of difficult since the current input (the old one) doesn't have an API. So they're posting as if it came from the Input feedback form. http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/aboutFeedback.xhtml#206 I expect Firefox OS to also want to do their own UI and post the feedback data to Input. For the new Input, we should make this easier for these two projects and provide an API for posting feedback from other user interfaces. Requirements: 1. We need to version the API so that we can make changes, but the old API version will continue to work. 2. The API will be for posting data only at this point--no need for getting data, authenticating, etc. 3. We need to think about spam, but it's probably the case that all we can do is throttle incoming data. 4. Probably easiest to do a REST-based API using JSON.
Assignee | ||
Comment 1•12 years ago
|
||
Making this a P2. I think we should work on this for phase 1 and do it sooner rather than later because we're going to want to help Firefox Mobile transition from what they're doing now to this system when everything is in place. Additionally, putting this in the 2012.20 sprint. As a side note, if I had my druthers, we'd implement our own API and not use Tastypie or something like that. Our needs are pretty small and there's no need to get a API framework like that involved.
Whiteboard: u=dev c=feedback p= s=2012.20
Assignee | ||
Comment 2•12 years ago
|
||
Pretty sure this should be straightforward. It probably involves the following: 1. setting up API urls in routing 2. setting up the API endpoint for submitting feedback 2.1. probably want to explicitly enable forms for API 2.2. we could do that by explicitly adding routes for forms that are enabled 2.3. it'd be nice if we could reuse the form code The primary use case for this is Firefox Mobile. Given that, we need to implement the Mobile db tables first. Thus I'm making this depend on bug #801621 and bumping this into the 2012.21 sprint.
Depends on: 801621
Whiteboard: u=dev c=feedback p= s=2012.20 → u=dev c=feedback p=2 s=2012.21
Comment 3•12 years ago
|
||
Clearing out sprint info.
Whiteboard: u=dev c=feedback p=2 s=2012.21 → u=dev c=feedback p=2 s=
Assignee | ||
Comment 4•11 years ago
|
||
Putting these in my queue for this quarter.
Assignee: nobody → willkg
Whiteboard: u=dev c=feedback p=2 s= → u=dev c=general p= s=input.2013q2
Assignee | ||
Comment 5•11 years ago
|
||
We don't need this right now, so I'm pushing this one off.
Whiteboard: u=dev c=general p= s=input.2013q2 → u=dev c=general p= s=
Assignee | ||
Comment 6•11 years ago
|
||
I pushed this off, but scrumbugz didn't see it for some reason. Pushing it off again.
Whiteboard: u=dev c=general p= s= → u=dev c=general p= s=
Assignee | ||
Comment 7•11 years ago
|
||
Marking this as a dupe of bug #895675 to do the work there.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•