Fixes for Plan:Project Development Handbook page
Why is this change being made?
Part of my onboarding task on GitLab Training was to find any fixes I could make to my team page. I found some issues, so I'm suggesting the changes below for the Plan:Project Management team page:
-
Fixed
Plan stage
broken URL -
Moved team page to
Plan Stage
directory to be in the proper folder with other Plan teams- Updated
CODEOWNERS
file as pipeline was failing because of the file path change, so I updated the path onCODEOWNERS
file as well
- Updated
-
Removed use of
project-development-be
path as page doesn't exist -
Also fixed
Plan stage
broken URL forKnowledge
team page
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - 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
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Update 2 files
- /content/handbook/engineering/development/dev/plan-project-management.md
- /content/handbook/engineering/development/dev/plan/plan-project-management.md
Edited by Fernanda Toledo