<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">The pagespeed page is neat and all,
but I think that pages like<br>
<a class="moz-txt-link-freetext" href="http://term.ie/oauth/example/client.php">http://term.ie/oauth/example/client.php</a><br>
or <br>
<a class="moz-txt-link-freetext" href="https://developers.google.com/oauthplayground/">https://developers.google.com/oauthplayground/</a><br>
are closer to what we need to offer.<br>
<br>
When I think "Mozilla Developer Dashboard", I'm thinking
something very different. We have a number of services that may
be a tad "tweaky" to use, and sadly tend to be more on the "It
either works or it doesn't" end. <br>
<br>
To pick on my own service rather than someone else's, Push is in
theory simple (run a bit of JS, get a URL, send stuff to URL to
get an even back on the JS), but there's an awfully big "black
box" around things. <br>
* Did I PUT/POST correctly?<br>
* Did the message make it out of the system only to be eaten by
the client?<br>
* Did I properly encrypt the data portion? (Yeah, that's not
going to be fun for folks.)<br>
* Have I run over quota for events?<br>
<br>
Having a dashboard to help answer questions for folks who aren't
intimately familiar with the code and have little interest in
digging into that particular morass would be useful. It's often
difficult for creators of a service to remember, but we're
providing a solution to a much, much larger problem and the less
folks have to think about our services, the happier they'll be
to use them. <br>
</div>
<br>
On 10/9/2015 5:48 PM, William Maggs wrote:<br>
</div>
<blockquote
cite="mid:CAN=9297z+7O2dUJd56ft42JcfehOw184vXOCNU86vWiWYzWbLA@mail.gmail.com"
type="cite">
<div dir="ltr"><a moz-do-not-send="true"
href="https://developers.google.com/speed/pagespeed/insights/?url=mozilla.com">https://developers.google.com/speed/pagespeed/insights/?url=mozilla.com</a><br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 9, 2015 at 5:42 PM, Axel
Kratel <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:akratel@mozilla.com" target="_blank">akratel@mozilla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">This is one of the most popular Google
developer service: <a moz-do-not-send="true"
href="https://developers.google.com/speed/pagespeed/insights/"
target="_blank">https://developers.google.com/speed/pagespeed/insights/</a>
<div><br>
</div>
<div>You might want to check what looks like a really
extensive offering from Google. Some of it is server
side, but at the very least we should have similar
services for web pages. </div>
</div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 9, 2015 at 4:00
PM, William Maggs <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:wmaggs@mozilla.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:wmaggs@mozilla.com">wmaggs@mozilla.com</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>Andy, <br>
<br>
</div>
Perhaps on top of these near-term needs
we can also bring into the discussion
developer services you and Laura have
discussed at various times, including: <br>
<br>
</div>
compatibility<br>
</div>
crash tests<br>
</div>
security <br>
<br>
</div>
Bill <br>
</div>
<div>
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Oct 9, 2015
at 3:37 PM, Christopher Karlof <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:ckarlof@mozilla.com"
target="_blank">ckarlof@mozilla.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div dir="ltr">Hi Andy,
<div><br>
</div>
<div>One topic that has started to
come up more frequently is the
notion of a developer dashboard for
Firefox developer services. We now
have at least a few current and
future use cases:</div>
<div><br>
</div>
<div>1) Add-on management and metrics</div>
<div>2) Push notification management
and metrics</div>
<div>3) FxA Oauth relier management
and metrics</div>
<div><br>
</div>
<div>I think we’re going to need to
start figuring this out. I don’t
feel we’re adequately staffed for
this ATM, and I feel it would be
useful to start thinking about this
soon in advance of our 2016
planning. Please look for a meeting
invite for us to have some initial
discussions.</div>
<div><br>
</div>
<div>thanks,</div>
<div>-chris</div>
<div><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>