Fwiw, I have two somewhat conflicting thoughts related to this:
1. The email service needs to grow rate-limiting soon and if there's a
standalone service available to use already, that will probably save me
some time.
2. Historically I've found the customs server code hard to grok. Part of me
We just had the front-end catch-up. It was a tiny little tiddler of a
meeting today, these are the notes:
# Action items from last time
vlad to deploy web sessions to box
not done
shane to move sms feature doc to github
not done
shane to ask if we can release the sms feature in canada
Just to clarify one tiny thing in here:
On Tue, Jan 31, 2017 at 1:11 PM, Vijay Budhram wrote:
> * pb followed up on a demo about fxa-test [4]. He created a custom
> organization for this testing. If you would like access, ask pb. The
> repository has the potential to be
Works for me, although the 2nd half of the morning meeting would clash with
the monthly internal meeting in that case (but I don't mind watching the
recording).
On Fri, Jan 13, 2017 at 9:39 AM, Shane Tomlinson
wrote:
> Hey all, you probably all saw Potch's email about it
Hey everyone,
We just had our regular backend catch-up. It was not recorded but I did
take some stream-of-consciousness notes on what we discussed:
* train 74 was cut on time!
* but the deploy doc was empty!
* a db migration was not mentioned
* some config changes weren't mentioned
* we
Hey all, we just had our regular product meeting for Firefox Accounts.
Somebody else will reply to this in due course with a link to the
recording. In the meantime, here are the notes:
* Toronto work week
* The plan was to try and brainstorm what to work on ahead of time, but
some key people
Hey all, we just had our regular Thursday FxA front-end meeting.
I don't have a link to the recording or know where to get it from, but I'm
confident that one of my excellent compadres will reply to this email with
the link on my behalf.
I do have notes though. These are they:
* Toronto work
My $0.02: I'm pro-validation but ambivalent about JSON Schema specifically.
However it should be straightforward for the auth server to convert from
JSON Schema to Joi validation objects via, e.g.
https://www.npmjs.com/package/enjoi, provided we can stick to the subset
that is implemented there
8 matches
Mail list logo