Skip to content

Update issues guidelines to include single DRI

Jackie Gragnola requested to merge jax-pm-issues-single-dri into master

Why is this change being made?

In reviewing the issue guidelines, we don't make a mention of DRIs, which seems a critical piece of ensuring issues are scoped correctly and to avoid mega issues with multiple DRIs for different sections.

The section on checkboxes is clear, but doesn't quite get to the why of driving to a specific deliverable and accountability of the individual assigned, which I think aligns to the concept of Commitment we will work toward.

@dplanella @johnjeremiah @cfoster3

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

Merge request reports