Open Bug 776678 Opened 12 years ago Updated 11 years ago

Update MDN docs for developer in-app payments

Categories

(Developer Ecosystem :: Web Components, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

REOPENED

People

(Reporter: kumar, Assigned: markg)

References

(Blocks 1 open bug)

Details

(Keywords: dev-doc-needed, Whiteboard: u=dev c=doc p=3)

When we have settled on how developers will make payments in either B2G (bug 775802) or desktop/Android/PayPal this document, or something equivalent, needs to explain the new flows: https://developer.mozilla.org/en/Apps/In-app_payments
Keywords: dev-doc-needed
blocking-basecamp: --- → +
First - I don't agree this blocks - in the past, dev doc bugs in the nom queue have received a minus in triage since worst case, they can be taken care of after software complete if push comes to shove. Second - This is a dup of bug 767818's use of dev-doc-needed, which is already tracked on the dev-doc-needed bug for apps (bug 783741). I'm duping on that, as we're duplicating tracking right now of dev-docs for in-app payments.
Status: NEW → RESOLVED
blocking-basecamp: + → ---
Closed: 12 years ago
Resolution: --- → DUPLICATE
(In reply to Jason Smith [:jsmith] from comment #1) > First - I don't agree this blocks - in the past, dev doc bugs in the nom > queue have received a minus in triage since worst case, they can be taken > care of after software complete if push comes to shove. I'm the first one to encourage pragmatic blocking but I want to point out that our release of in-app payments would be greatly hindered if it shipped without docs. The whole point of in-app payments is to enable developers to build apps that accept payments. > > Second - This is a dup of bug 767818's use of dev-doc-needed, which is > already tracked on the dev-doc-needed bug for apps (bug 783741). The nav.mozPay() API is pretty generic so I'm not sure if documenting it is a dupe. This bug was about specifically documenting in-app payments end to end which involve the Marketplace, not just nav.mozPay(). There would however be overlaps in documentation though.
(In reply to Kumar McMillan [:kumar] from comment #2) > (In reply to Jason Smith [:jsmith] from comment #1) > > First - I don't agree this blocks - in the past, dev doc bugs in the nom > > queue have received a minus in triage since worst case, they can be taken > > care of after software complete if push comes to shove. > > I'm the first one to encourage pragmatic blocking but I want to point out > that our release of in-app payments would be greatly hindered if it shipped > without docs. The whole point of in-app payments is to enable developers to > build apps that accept payments. True, but that's more blocking that actual public marketplace launch, which is separate than determining to block ship of the device. In terms of determining if we're stopping ship of the device, this definitely does not block, as dev docs don't affect if a product is software complete or not. > > > > > Second - This is a dup of bug 767818's use of dev-doc-needed, which is > > already tracked on the dev-doc-needed bug for apps (bug 783741). > > The nav.mozPay() API is pretty generic so I'm not sure if documenting it is > a dupe. This bug was about specifically documenting in-app payments end to > end which involve the Marketplace, not just nav.mozPay(). There would > however be overlaps in documentation though. That's a fair statement and I agree. I'll reopen then.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
What needs to happen here? Can someone summarize? Mark Giffin: Can we assign this to you?
(In reply to Fred Wenzel [:wenzel] from comment #4) > What needs to happen here? Can someone summarize? > > Mark Giffin: Can we assign this to you? Yes. I temporarily removed these docs from MDN a while ago per morgamic request. I was waiting until payments were again allowed on the Marketplace. Are they allowed again now?
Not yet. They are in development targeting mid December.
Assignee: nobody → m1879
Whiteboard: u=dev c=doc p=3
Any updates here?
Priority: -- → P2
(In reply to Wil Clouser [:clouserw] from comment #7) > Any updates here? Wil, I have not added the payments docs back to MDN. Is the Marketplace able to do payments now? So I can put the payment docs back?
(In reply to Mark Giffin from comment #8) > (In reply to Wil Clouser [:clouserw] from comment #7) > > Any updates here? > > Wil, I have not added the payments docs back to MDN. Is the Marketplace able > to do payments now? So I can put the payment docs back? Mmm, not in production yet. This may be a bit premature, but only by a couple weeks.
I think we should start to land docs when payments are working on -dev. So they'll be ready by the time they production hit. There's a lot to write :)
(In reply to Andy McKay [:andym] from comment #10) > I think we should start to land docs when payments are working on -dev. So > they'll be ready by the time they production hit. There's a lot to write :) I agree and I'm starting to work on the payments docs. Is there any prediction as to when payments will be on -dev? I think I should just start adding the payments docs back into MDN as soon as I have it.
Component: Developer Pages → Web Components
Product: Marketplace → Developer Ecosystem
Version: 1.0 → unspecified
Wil - do you need me to do something on this? What's up?
Flags: needinfo?(clouserw)
(In reply to Mark Giffin [:markg] from comment #12) > Wil - do you need me to do something on this? What's up? We're turning on a whitelist of users to start testing next week. So, we could probably start documentation around then? We're still landing the final pieces of the UI (bug 868179) before we can really start testing.
Flags: needinfo?(clouserw)
(In reply to Wil Clouser [:clouserw] from comment #13) > We're turning on a whitelist of users to start testing next week. So, we > could probably start documentation around then? We're still landing the > final pieces of the UI (bug 868179) before we can really start testing. Sounds fine. I am already going over all the app payments docs and fixing them up as needed. Did you need something in particular?
You need to log in before you can comment on or make changes to this bug.