Added point to address timely responses

Why is this change being made?

Speaking from my time at GNOME, it was super hard to get out timely responses because we didn't have a clearly defined process and felt like we needed legal review for our external comms. We started to streamline it towards the end of my time on the board, because we empowered our Executive Director to get these out, but I imagine other orgs may still need to think through that part.

I saw that you added a DRI model at the end of the page and I love that. With open source orgs, having a DRI isn't entirely possible. I also wonder if there are additional tips around legal approvals we may want to mention, keeping in mind a lot of orgs may not have in-house counsel?

If it doesn't make sense to include this bullet or something like it, that's totally fine! I've been trying to be more MR-first, so that's why I decided to add this suggestion as an MR. Feel free to close if you don't think it's relevant!

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack