Re: [w3ctag/design-reviews] FedCM Auto Re-authentication API (Issue #813)

Hey @hadleybeeman thanks for reviewing this! I replied to @torgo over email, but figured it would be useful to give context here more publicly in case we run into this again.

> Hi @yi-gu. Thanks for opening this review. If you'd like our feedback, could you please draft us a quick explainer to cover how you'd like this to work and why you've chosen that approach above the other approaches you've considered?
> If it helps, our [explainer template](https://github.com/w3ctag/tag.w3.org/blob/main/explainers/template.md) and [explainer explainer](https://tag.w3.org/explainers/) are posted.

We did originally have proposals to extend FedCM in the form of explainers that follow the template (you can still see some of them [here](https://github.com/fedidcg/FedCM/tree/main/proposals)), but we got feedback from Mozilla that it would help their reviews if these were filed as github Issues as opposed to standalone markdown files: making comments in github issues is a much lower hurdle to pay to engage than it is to kick off new github issues or submit pull requests.

> file issues followed by proposals followed by spec PRs, as opposed to explainers, to substantially decrease the cost of engagement (much easier to comment on github issues than to comment on explainers)

https://github.com/fedidcg/FedCM/issues/431#issuecomment-1425025469

That overall makes sense to us (we'll follow whatever makes our reviewers life easier), so we started to slowly port our explainers into github issues.

So, what @yi-gu pointed you to in the TAG request [here](https://github.com/fedidcg/FedCM/issues/429#issuecomment-1424282049) is, in fact, the place in which we explain the problem, the alternatives we considered and the proposal we have an inclination to go for.

I'm sorry if this causes extra work for you all, and we'd be happy to adapt to find ways to make reviews (mozilla's and yours included) as effective as possible, but just wanted to give context as to why these aren't standalone markdown files.

Since we do expect to send you all a few more reviews in the next few weeks/months, let me know if you feel like this isn't a reasonable format and we can work together with Mozilla to figure out something that works, Sam.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/813#issuecomment-1466632934
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/813/1466632934@github.com>