The FxA Relying Party Checklist <https://docs.google.com/document/d/18l-EKwDyKwnUYUsvtud7j6AwfOe_ZA93YEkrBIjJe1Y/edit#> has already proven its worth when it has been shown to other teams.
Turns out it's not just *other teams* that need a checklist before going to prod, the FxA team needs one too because we regularly forget things like ensuring a client_id is mapped to a human friendly name for metrics purposes, or adding a relying party's domain to the list of domains allowed to call /metrics-flow. With that in mind, I have started a new checklist, the FxA Relying Party Review Checklist <https://docs.google.com/document/d/1ECIzYKRoWVhp6xuP00pRjeamcVOCoN8ycsQ1jn0qjWQ/edit>, this one aimed at FxA developers who are reviewing relying party integrations. It's pretty short right now, I could use help filling it in. What have we, the FxA team, forgotten to do before a relying party went to production? What should we be doing when asked for review? Let's capture that. Thanks, Shane
_______________________________________________ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
