[request_renewal.md] doesn't require responsible individual about data-review

[chutten]

Optionally, we could highlight in the template that the short form cannot be used to "renew to permanent". This is how I've been treating it (to make an expiring metric permanent requires The Full Form) as an act with some small organizational friction encouraging renewal over "permanentizing"

[willkg]

That makes sense to me.

I don't know how decisions work here, but I can make the change when it's decided.

[chutten]

There are async and sync ways:

ASYNC

Post a link to this thread (and a precis) with a timeline ("If I don't hear objections by Thursday EOD, I'll be making this change on Friday") to Slack#data-stewards and/or #data-stewards:mozilla.org, and without objection ship your change (I'll happily review).

SYNC

Wait for the next Data Steward monthly meeting and add this as an agenda item. You can get assent from attendees. Without objection ship your change (I'll happily review).

---

All else fails, if someone's on PTO and objects later we can come in and revert. Mutability works both ways : )