From 302622cfa84a18840dc86a8eff5c07a84351af11 Mon Sep 17 00:00:00 2001
From: Tom Collingwood <tom.collingwood@stfc.ac.uk>
Date: Thu, 13 Jan 2022 18:29:10 +0000
Subject: [PATCH] remove gitlab templates

---
 .gitlab/issue_templates/Bug.md                | 40 -----------
 .gitlab/issue_templates/Documentation.md      | 43 ------------
 .gitlab/issue_templates/Feature proposal.md   | 68 -------------------
 .../Productivity Improvement.md               | 47 -------------
 .gitlab/issue_templates/QA failure.md         | 68 -------------------
 .gitlab/issue_templates/Refactoring.md        | 41 -----------
 .../merge_request_templates/Documentation.md  | 41 -----------
 7 files changed, 348 deletions(-)
 delete mode 100644 .gitlab/issue_templates/Bug.md
 delete mode 100644 .gitlab/issue_templates/Documentation.md
 delete mode 100644 .gitlab/issue_templates/Feature proposal.md
 delete mode 100644 .gitlab/issue_templates/Productivity Improvement.md
 delete mode 100644 .gitlab/issue_templates/QA failure.md
 delete mode 100644 .gitlab/issue_templates/Refactoring.md
 delete mode 100644 .gitlab/merge_request_templates/Documentation.md

diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md
deleted file mode 100644
index 120d7ad..0000000
--- a/.gitlab/issue_templates/Bug.md
+++ /dev/null
@@ -1,40 +0,0 @@
-<!---
-Please read this!
-
-Before opening a new issue, make sure to search for keywords in the issues
-filtered by the "bug" label and verify the issue you're about to submit isn't
-a duplicate.
---->
-
-### Summary
-
-(Summarize the bug encountered concisely)
-
-### Steps to reproduce
-
-(How one can reproduce the issue - this is very important)
-
-### Example Project
-
-(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
-
-(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
-
-### What is the current *bug* behavior?
-
-(What actually happens)
-
-### What is the expected *correct* behavior?
-
-(What you should see instead)
-
-### Relevant logs and/or screenshots
-
-(Paste any relevant logs - please use code blocks (```) to format console output,
-logs, and code as it's tough to read otherwise.)
-
-### Possible fixes
-
-(If you can, link to the line of code that might be responsible for the problem)
-
-/label ~bug
diff --git a/.gitlab/issue_templates/Documentation.md b/.gitlab/issue_templates/Documentation.md
deleted file mode 100644
index 43ee7cd..0000000
--- a/.gitlab/issue_templates/Documentation.md
+++ /dev/null
@@ -1,43 +0,0 @@
-<!--
-
-* Use this issue template for suggesting new docs or updates to existing docs.
-  Note: Doc work as part of feature development is covered in the Feature Request template.
-
-* For issues related to features of the docs.gitlab.com site, see
-     https://gitlab.com/gitlab-org/gitlab-docs/issues/
-
-* For information about documentation content and process, see
-     https://docs.gitlab.com/ee/development/documentation/ -->
-
-### Problem to solve
-
-<!-- Include the following detail as necessary:
-* What product or feature(s) affected?
-* What docs or doc section affected? Include links or paths.
-* Is there a problem with a specific document, or a feature/process that's not addressed sufficiently in docs?
-* Any other ideas or requests?
--->
-
-### Further details
-
-<!--
-* Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab?
-* Include use cases, benefits, and/or goals for this work.
-* If adding content: What audience is it intended for? (What roles and scenarios?)
-  For ideas, see personas at https://design.gitlab.com/research/personas or the persona labels at
-  https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A
--->
-
-### Proposal
-
-<!-- Further specifics for how can we solve the problem. -->
-
-### Who can address the issue
-
-<!-- What if any special expertise is required to resolve this issue? -->
-
-### Other links/references
-
-<!-- E.g. related GitLab issues/MRs -->
-
-/label ~documentation
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md
deleted file mode 100644
index 2bbef72..0000000
--- a/.gitlab/issue_templates/Feature proposal.md	
+++ /dev/null
@@ -1,68 +0,0 @@
-### Problem to solve
-
-<!-- What problem do we solve? -->
-
-### Intended users
-
-<!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
-
-* [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager)
-* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
-* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
-* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
-* [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer)
-* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
-* [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
-* [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst)
-* [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst)
-* [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test)
-* [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops)
-
-Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->
-
-### Further details
-
-<!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->
-
-### Proposal
-
-<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey -->
-
-### Permissions and Security
-
-<!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?-->
-
-### Documentation
-
-<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html
-Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements
-If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. -->
-
-### Availability & Testing
-
-<!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.
-
- What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?
-
-Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
-* Unit test changes
-* Integration test changes
-* End-to-end test change
-
-See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning -->
-
-### What does success look like, and how can we measure that?
-
-<!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. -->
-
-### What is the type of buyer?
-
-<!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers -->
-
-### Is this a cross-stage feature?
-
-<!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features -->
-
-### Links / references
-
-/label ~feature
diff --git a/.gitlab/issue_templates/Productivity Improvement.md b/.gitlab/issue_templates/Productivity Improvement.md
deleted file mode 100644
index 89505cd..0000000
--- a/.gitlab/issue_templates/Productivity Improvement.md	
+++ /dev/null
@@ -1,47 +0,0 @@
-## What is the productivity problem to solve?
-
-<!--
-Please describe the productivity problem that needs to be solved backed by charts from
-https://about.gitlab.com/handbook/engineering/quality/engineering-productivity-team/#engineering-productivity-team-metrics.
--->
-
-### Problem identification checklist
-
-- [ ] The root cause of the problem is identified.
-- [ ] The surface of the problem is as small as possible.
-
-## What are the potential solutions?
-
-<!--
-Please provide potential solutions here. Example solutions could be:
-
-- Dogfood a feature.
-- Refactor/improve some workflow code.
-- Throw more money at the problem.
-
-Please provide pros/cons and a weight estimate for each solution.
--->
-
-- [ ] All potential solutions are listed.
-- [ ] A solution has been chosen for the first iteration: `PUT THE CHOSEN SOLUTION HERE`
-
-## Who and when will the solution be implemented?
-
-<!--
-For history reason, please list the person that will implement the solution and
-the planned milestone/date.
--->
-
-## Verify that the solution has improved the situation
-
-<!--
-Ideally, looking at the charts from the first part, we should see an improvement
-after the implementation is merged/deployed/released.
--->
-
-- [ ] The solution improved the situation.
-  - If yes, check this box and close the issue. Well done! :tada:
-  - Otherwise, create a new "Productivity Improvement" issue. You can re-use the description from this issue, but obviously another solution should be chosen this time.
-
-/label ~"Engineering Productivity" ~meta
-/cc @gl-quality/eng-prod
diff --git a/.gitlab/issue_templates/QA failure.md b/.gitlab/issue_templates/QA failure.md
deleted file mode 100644
index e1b3eec..0000000
--- a/.gitlab/issue_templates/QA failure.md	
+++ /dev/null
@@ -1,68 +0,0 @@
-<!---
-Before opening a new QA failure issue, make sure to first search for it in the
-QA failures board: https://gitlab.com/groups/gitlab-org/-/boards/1385578
-
-The issue should have the following:
-
-- The relative path of the failing spec file in the title, e.g. if the login
-  test fails, include `qa/specs/features/browser_ui/1_manage/login/log_in_spec.rb` in the title.
-  This is required so that existing issues can easily be found by searching for the spec file.
-- If the issue is about multiple test failures, include the path for each failing spec file in the description.
-- A link to the failing job.
-- The stack trace from the job's logs in the "Stack trace" section below.
-- A screenshot (if available), and HTML capture (if available), in the "Screenshot / HTML page" section below.
---->
-
-### Summary
-
-
-
-### Stack trace
-
-```
-PUT STACK TRACE HERE
-```
-
-### Screenshot / HTML page
-
-<!--
-Attach the screenshot and HTML snapshot of the page from the job's artifacts:
-1. Download the job's artifacts and unarchive them.
-1. Open the `gitlab-qa-run-2020-*/gitlab-{ce,ee}-qa-*/{,ee}/{api,browser_ui}/<path to failed test>` folder.
-1. Select the `.png` and `.html` files that appears in the job logs (look for `HTML screenshot: /path/to/html/page.html` / `Image screenshot: `/path/to/html/page.png`).
-1. Drag and drop them here.
--->
-
-### Possible fixes
-
-
-<!-- Default due date. -->
-/due in 2 weeks
-
-<!-- Base labels. -->
-/label ~Quality ~QA ~test
-
-<!-- Test failure type label, please use just one.-->
-/label ~"failure::broken-test" ~"failure::flaky-test" ~"failure::stale-test" ~"failure::test-environment" ~"failure::investigating"
-
-<!--
-Choose the stage that appears in the test path, e.g. ~"devops::create" for
-`qa/specs/features/browser_ui/3_create/web_ide/add_file_template_spec.rb`.
--->
-/label ~devops::
-
-<!--
-Select a label for where the failure was found, e.g. if the failure occurred in
-a nightly pipeline, select ~"found:nightly".
--->
-/label ~found:
-
-<!--
-https://about.gitlab.com/handbook/engineering/quality/guidelines/#priorities:
-- ~P1: Tests that are needed to verify fundamental GitLab functionality.
-- ~P2: Tests that deal with external integrations which may take a longer time to debug and fix.
--->
-/label ~P
-
-<!-- Select the current milestone if ~P1 or the next milestone if ~P2. -->
-/milestone %
diff --git a/.gitlab/issue_templates/Refactoring.md b/.gitlab/issue_templates/Refactoring.md
deleted file mode 100644
index cd0ce84..0000000
--- a/.gitlab/issue_templates/Refactoring.md
+++ /dev/null
@@ -1,41 +0,0 @@
-## Summary
-
-<!--
-Please briefly describe what part of the code base needs to be refactored.
--->
-
-## Improvements
-
-<!--
-Explain the benefits of refactoring this code.
-See also https://about.gitlab.com/handbook/values/index.html#say-why-not-just-what
--->
-
-## Risks
-
-<!--
-Please list features that can break because of this refactoring and how you intend to solve that.
--->
-
-## Involved components
-
-<!--
-List files or directories that will be changed by the refactoring.
--->
-
-## Optional: Intended side effects
-
-<!--
-If the refactoring involves changes apart from the main improvements (such as a better UI), list them here.
-It may be a good idea to create separate issues and link them here.
--->
-
-
-## Optional: Missing test coverage
-
-<!--
-If you are aware of tests that need to be written or adjusted apart from unit tests for the changed components,
-please list them here.
--->
-
-/label ~backstage
diff --git a/.gitlab/merge_request_templates/Documentation.md b/.gitlab/merge_request_templates/Documentation.md
deleted file mode 100644
index 901228e..0000000
--- a/.gitlab/merge_request_templates/Documentation.md
+++ /dev/null
@@ -1,41 +0,0 @@
-<!-- Follow the documentation workflow https://docs.gitlab.com/ee/development/documentation/workflow.html -->
-<!-- Additional information is located at https://docs.gitlab.com/ee/development/documentation/ -->
-<!-- To find the designated Tech Writer for the stage/group, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers -->
-
-<!-- Mention "documentation" or "docs" in the MR title -->
-<!-- For changing documentation location use the "Change documentation location" template -->
-
-## What does this MR do?
-
-<!-- Briefly describe what this MR is about. -->
-
-## Related issues
-
-<!-- Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. -->
-
-## Author's checklist
-
-- [ ] Follow the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).
-- [ ] If applicable, update the [permissions table](https://docs.gitlab.com/ee/user/permissions.html).
-- [ ] Link docs to and from the higher-level index page, plus other related docs where helpful.
-- [ ] Apply the ~documentation label.
-
-## Review checklist
-
-All reviewers can help ensure accuracy, clarity, completeness, and adherence to the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).
-
-**1. Primary Reviewer**
-
-* [ ] Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
-
-**2. Technical Writer**
-
-* [ ] Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable [DevOps stage](https://about.gitlab.com/handbook/product/categories/#devops-stages).
-
-**3. Maintainer**
-
-1. [ ] Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
-1. [ ] Ensure a release milestone is set.
-1. [ ] If there has not been a technical writer review, [create an issue for one using the Doc Review template](https://gitlab.com/gitlab-org/gitlab/issues/new?issuable_template=Doc%20Review).
-
-/label ~documentation