Service notices for RPs / IDPs

[Francois Marier]

When you sign up for an API key (e.g. Flickr, Twitter, etc.), the
organization that you sign up with gets your email and therefore a way
to get in touch with all of the developers using their APIs. I've also
seen Open Source projects offer an easy way to "register your site" so
that you can get be reached if something important comes up.

I can imagine two things about Persona that every RP out there would
want to know about:

1- there is a major in the protocol and you need to change your code
(and/or upgrade the library/plugin you're using) right now

2- this API has been deprecated and will be removed in 2 months, make
sure you switch to the new one before then (or upgrade library/plugin)

Maybe it would be useful for us to maintain an optional (but strongly
recommended) register of users. Something that is so limited in terms of
traffic that every RP/IDP out there will want to sign up. (It could even
be the last step of our getting started guide: "Register your site".)

I'm specifically not thinking of an dev-identity-announce list where new
features and other things would be posted. I think our existing blog is
fine for that. Instead, what I'm envisioning is something we would use
only when an action is required on the part of RPs and IDPs.

So if you are an RP or an IDP, does this sound useful to you? Would you
register/sign-up? Is it too limited (e.g. would you prefer to receive 1
status email twice a year)? Would you want to be notified of planned or
unscheduled outages too?

Cheers,
Francois

[Lloyd Hilaiel]

Could this be something that would be appropriate for status.persona.org?

Your one-stop-shop for current system status, recent history, and
upcoming events.

Laser focused on getting people who rely on persona information they care
about.

I'd think that this information could be sync'd or syndicated with a twitter
feed to give folks an alternative means of receiving "push" style notifications.

lloyd

> _______________________________________________
> dev-identity mailing list
> dev-id...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-identity

[David Illsley]

Sounds good. Would be good to improve on [1] as it doesn't feel 'current' to me (possibly just because of the lack of a timestamp). I'm also interested in the notion of 'planned downtime'…. what's the expectation on volume, notice, and timezone of planned downtime?
David

[1] https://services.mozilla.com/status/

[Ozten]

On Monday, May 21, 2012 12:07:40 PM UTC-7, DavidIllsley wrote:
> Sounds good. Would be good to improve on [1] as it doesn't feel 'current' to me (possibly just because of the lack of a timestamp). I'm also interested in the notion of 'planned downtime'…. what's the expectation on volume, notice, and timezone of planned downtime?
> David

I don't think Persona will have planned downtime.

With every change, we invest extra engineering resources to make sure it's release doesn't require a downtime or maintenance period.

[Francois Marier]

On 22/05/12 05:56, Lloyd Hilaiel wrote:
> Could this be something that would be appropriate for status.persona.org?
>
> Your one-stop-shop for current system status, recent history, and
> upcoming events.
>
> Laser focused on getting people who rely on persona information they
> care about.

That's what I was hoping status.persona.org would be. A targeted source
of information for people who rely on Persona but don't want to follow
all development discussions.

So I would expect more information on status.p.o than what is absolutely
necessary to know, which is what I was thinking of when I was thinking
of "site registration" / "service notices". It would be nice to have a
history of past events and others things like that even though it
doesn't require an RP to do anything about it.

Thinking about the last 12 months, what sorts of things were so
important that we would have liked to email every RP out there? I can
think of the (upcoming) move to watch/request.

> I'd think that this information could be sync'd or syndicated with a twitter
> feed to give folks an alternative means of receiving "push" style notifications.

Good point. So perhaps we need three formats: email, Twitter, RSS.

I guess my proposal wasn't so much about format, but rather about
reaching out people who are busy and do not want to hear from us unless
it's absolutely necessary. But maybe that's a bit too narrow?

Cheers,
Francois

[Mike G]

Id like to subscribe to a SNS topic. But not sure if amazon is an enemy.

[Francois Marier]

On 24/05/12 10:49, Mike G wrote:
> Id like to subscribe to a SNS topic. But not sure if amazon is an enemy.

Pardon my ignorance, but what's SNS? A service from Amazon?

Cheers,
Francois

[Mike G]

Yes for notifications just like this. Many ways to subscribe, email, sms,
direct api, etc.
http://aws.amazon.com/sns/

[Daniel Mills]

Whoa! That service looks really sweet!

On May 23, 2012, at 4:25 PM, Mike G <mike...@gmail.com> wrote:

> Yes for notifications just like this. Many ways to subscribe, email, sms,
> direct api, etc.
> http://aws.amazon.com/sns/

[Andrew Chilton]

On 24 May 2012 11:59, Daniel Mills <thu...@mozilla.com> wrote:
> Whoa! That service looks really sweet!

It has it's upsides and downsides but generally it's nice to play
with. It's kinda weird that when you subscribe to a topic via email,
you're essentially dealing with an Amazon webpage to confirm your
subscription. If you'd like a play via the API, I have written an
interface for the majority of the Amazon Web Services in Node.js
including SNS. See here for more details :
https://github.com/appsattic/node-awssum/ (it's also on NPM).

However (keeping on topic), I actually think that something like a
text message for this kind of update would be too much. I suspect that
a regular blog (with RSS), and an announcement mailing list would be
all that is necessary. A lot of infrastructure for just one or two
messages a year might be a little bit overkill.

Cheers,
Andy

--
contact: Andrew Chilton
website: http://www.chilts.org/blog/