Who needs to review and sign-off of the main blog post?

[jieyouxu]

Question

Zulip discussion: #council > main rust blog policy, but I can't tell if there is an actual agreed decision.

This has came up several times by now, it would be good to have a policy so we don't need to ask about it each time. The latest of such example is the Google Summer of Code public-facing blog post (rust-lang/blog.rust-lang.org#1599), where we have no idea who needs to sign-off of such a blog post (e.g. T-compiler leads have merge permissions but does not necessarily mean that is sufficient, as there is currently no clear guidelines on this).

[Mark-Simulacrum]

I'll own updating various docs + getting some automation (triagebot posts on PRs) going.

As a concrete proposal, combining what Eric is saying with the policy today, we could say that anyone on the leadership council or a team lead can approve, but the responsible person to approve would be your LC rep. And maybe we could set up triagebot to ping the right person.

[tshepang]

does rust-lang/rust-forge#845 mean this can be closed