clean out issues not related to about.gitlab.com from www-gitlab-com project/repo
This issue is being opened to discuss the action plan for project management cleanup of https://gitlab.com/gitlab-com/www-gitlab-com
The Problem
The www-gitlab-com project has become a bit of a catch-all bucket for issues over the years, probably because it was one of the first company-wide repos. As a result, it is filled with many issues that probably need to be moved to their respective projects in order to get attention.
It is difficult to triage issues actually related to the content of the repo: the marketing website.
This also came up because we want to have a bug bash company-wide on the marketing site (@shanerice leading this) but it is too difficult for people to come here and pick up open issues. We also have > 900 open MRs.
Desired Outcome
As the DRI for the Marketing Website, I would like to limit the use of the www-gitlab-com repo and project to the purpose of its codebase:
- marketing website
- handbook
- docs
This will enable better hygiene across the project, including using GitLab's plan and create features and analytics as intended to track burndows, roadmaps, productivity, etc.
Recommended Solution
Move all issues and MRs for non about.gitlab.com work to their respective projects organized in https://gitlab.com/gitlab-com
Background Info
How Other Teams Are Using
The GitLab Product
Our handbook instructions for how to file an issue against our products, and how they are triaged, are handled here https://about.gitlab.com/handbook/engineering/quality/issue-triage/
Other Departments
all the issues present on the board (https://gitlab.com/gitlab-com/www-gitlab-com/-/boards/980804) have the Engineering Management label on them. So it might be trivial to just exclude that label from the triage process
Other departments have tags in here as well.
There is a risk that these issues are getting orphaned, and never being looked at.
There are community contributions issues and MRs, which I am actively searching for to reply and resolve, that are getting lost.
How Other Teams Use GitLab to Work
There are many projects organized within the GitLab.com base project at https://gitlab.com/gitlab-com
This does not conflict with the www-gitlab-com repo
--
Next Steps
-
@dmor clarify the purpose of this repo/project on the description -
establish a triage process for new issues filed in this repo -
review MR merge permissions for the public-facing marketing site -
review CODEOWNERS for the public-facing marketing site -
reach out to Engineering Management about moving their (~99) open issues to a separate project -
update the handbook in all necessary places so that people start creating issues in the correct places -
communicate these changes in Slack