Hamish Willee

@yoavweiss FYI only at some point you added a yarn.lock and package, which is not a good idea. I've rebased to remove those so we can cleanly rebase update when...

@yoavweiss Thanks for this. Good changes. I made a number of updates which I will try explain inline in https://github.com/mdn/content/pull/39815/commits/fb00c7a7c23684e52c16e5b3d23e91052f544157 The main point is to better cross link to the...

> > This all looks good except for the missing `IntegrityViolationReportBody`, which should be a peer of https://developer.mozilla.org/en-US/docs/Web/API/CSPViolationReportBody > > Let me know if you're planning to do this. If...

> If we're documenting it as a dictionary, won't it make the most sense to document it inline (either with the headers, or the broader feature), give that it won't...

> @hamishwillee maybe it's best if you give it a go, as I'm being distracted by the next shiny object.. I'll give it a go. Thank you for this. Looking...

FYI only, I reduced this to only a few commits. The merge history made it hard for me to update and track what was going on. Some loss of "who...

@auturgy @peterbarker Can we get some movement on this? ONly a year and a half late .... Plan is to move current deprecated to superseded unless they are "really" deprecated....

Hi @peterbarker The intent here is to reduce confusion in the naming so that we can move towards a lifecycle. Currently we use the term deprecated to mean both: -...

> could you provide some concrete examples on where this would be applied, please? Initially I would move everything that is deprecated to superseded in one PR. Then we would...

> I was more after specific messages. Yes I know. OK, then I will mark every single message that is currently deprecated as superseded :-). The ones that will then...