This repository is no longer active,
because the Persona service has been shut down.
It remains only for historical purposes.
Realtime Service Status for Mozilla Persona
This repository holds the status reporting system for Mozilla Persona
to be hosted at http://status.persona.org. People who care about
Persona can check the status of the service at that url. People working
on persona can report incidents by adding files to this repository.
How it works
events/ holds a collection of incident reports. An incident report is a directory,
named by convention YYYY.MM.DD-#, containing the following files:
discovery.txt - A textual report of a discovered problem
update_X.txt - any number (zero to infinity) of incremental status updates
resolution.txt - A textual report of the resolution of the problem.
These files have a special first line containing the date of the report, and the rest of the
file is plain text prose. For example:
when: Tue Sep 25 22:13:19 PDT 2012
We've isolated the problem, it's a bogus flux capacitor. We're going to try to stop
in the Aquila System to buy one from the semi-hostile Midorians there.
NOTE: Date parsing is pretty flexible. When an event occurs, type date at your terminal,
and then embed this in your report.
NOTE: The .txt suffixes are totally optional.
NOTE: you can name updates whatever you want. The only hardcoded file names are discovery(.txt)?
and resolution(.txt)?.
Status: Inactive
This repository is no longer active, because the Persona service has been shut down. It remains only for historical purposes.
Realtime Service Status for Mozilla Persona
This repository holds the status reporting system for Mozilla Persona to be hosted at http://status.persona.org. People who care about Persona can check the status of the service at that url. People working on persona can report incidents by adding files to this repository.
How it works
events/holds a collection of incident reports. An incident report is a directory, named by conventionYYYY.MM.DD-#, containing the following files:discovery.txt- A textual report of a discovered problemupdate_X.txt- any number (zero to infinity) of incremental status updatesresolution.txt- A textual report of the resolution of the problem.These files have a special first line containing the date of the report, and the rest of the file is plain text prose. For example:
NOTE: Date parsing is pretty flexible. When an event occurs, type
dateat your terminal, and then embed this in your report.NOTE: The .txt suffixes are totally optional.
NOTE: you can name updates whatever you want. The only hardcoded file names are
discovery(.txt)?andresolution(.txt)?.How you report an incident
create a new directory for it in
events/write a
discovery.txtfilecommit it
push it up to github
build and publish the update to gh-pages:
How you resolve an incident
write a
resolution.txtfile in the directorycommit it
push it up to github
build and publish the update to gh-pages:
Some details
Scripts in
scripts/are responsible for validating the pile of files inevents/, turning them into JSON that the webpage (underhtml/can render)hacking on it