Make Dzmitry Meshcharakou a backend maintainer

Manager Justification

It's hard to specify hard requirements for becoming a maintainer, which is why the documentation consists of flexible guidelines. Reviewers are encouraged to think of their eligibility for maintainership in the terms of "I could be ready at any time to be a maintainer as long as my work as an author and reviewer is consistent with other maintainers".

• The MRs reviewed by the candidate consistently make it through maintainer review without significant additionally required changes.

  1. Add runner tags selection for on-demand scans form (gitlab-org/gitlab!103634 - merged)
  2. Add package_type validation to Packages::Compos... (gitlab-org/gitlab!110777 - merged)
  3. Adds field public_package to package details gr... (gitlab-org/gitlab!111992 - merged)
  4. Add Metrics Dashboard templates viewer to FF (gitlab-org/gitlab!120289 - merged)
  5. https://gitlab.com/gitlab-org/security/gitlab/-/merge_requests/3241+
  6. ModelsController now displays Ml::Model (gitlab-org/gitlab!127011 - merged)
  7. List workItems at the group level MVC 1 (gitlab-org/gitlab!126089 - merged)
  8. Feat: implement report abuse in user profile (gitlab-org/gitlab!127326 - merged)
  9. Refactor Package Pipelines endpoint (gitlab-org/gitlab!127113 - merged)
  10. Add Groups::SshCertificate model to store group... (gitlab-org/gitlab!127856 - merged)

• The MRs authored by the candidate consistently make it through reviewer and maintainer review without significant required changes.

  1. Introduce a model for npm metadata (gitlab-org/gitlab!114312 - merged)
  2. Mitigate the race condition when creating a new... (gitlab-org/gitlab!114317 - merged)
  3. Update the lease key to contain package's version (gitlab-org/gitlab!116782 - merged)
  4. Implement package metadata endpoint on the grou... (gitlab-org/gitlab!119073 - merged)
  5. Implement npm group level endpoints: CRUD tags ... (gitlab-org/gitlab!120900 - merged)
  6. Use metadata cache for npm metadata endpoint at... (gitlab-org/gitlab!122686 - merged)
  7. Remove last_of_each_version scope and add uniqu... (gitlab-org/gitlab!123923 - merged)
  8. Add docker distribution manifest list v2 type t... (gitlab-org/gitlab!127545 - merged)
  9. Create dependency-proxy bucket when setup objec... (gitlab-org/gitlab-development-kit!3291 - merged)
  10. Fix error reporting when user is not authorized (gitlab-org/gitlab!129346 - merged)

@dmeshcharakou has reviewed over 123 merged MRs and authored over 84 merged MRs

Trainee Backend Maintainer issue: Trainee BE maintainer (GitLab) - Dzmitry Meshch... (#14356 - closed)

Backend Maintainer Mentor: @splattael

• Focuses on changes in MR and code quality 1, 2, 3
• Cares about performance impact 1, 2
• Encourages code readability and suggests re-use existing code when possible 1, 2, 3, 4
• Identifies and suggests adding missing tests and improves test quality 1, 2, 3, 4, 5, 6

Before Merging (Manager Tasks)

• Close any relevant trainee maintainer issues with a comment indicating that this merge request is being created, as (they are no longer required to become a maintainer).
• Mention the maintainers from the given specialty with the template below.
• Leave this merge request open for 1 week, to give the maintainers time to provide feedback.
• Ensure we have at least 2 approvals from existing maintainers.

Template call to action

SPECIALITY Maintainers, please review this proposal to make TRAINEE maintainer of PROJECT. 

* If you have blocking feedback adhering [to the documentation](https://about.gitlab.com/handbook/engineering/workflow/code-review/#how-to-become-a-project-maintainer) please share it with me via Slack.
* If you are in agreement please approve or give a 👍 on the MR

After 1 week, if there is no blocking feedback and at least 2 approvals, I will merge this MR.

Once This MR is Merged

1. Join the #backend_maintainers Slack channel
2. Ask the maintainers in your group to invite you to any maintainer-specific meeting if one exists.
3. Let a maintainer add you to @gitlab-org/maintainers/rails-backend with Owner access level.
4. Announce it everywhere
5. Familiarize yourself with documentation for Merging a merge request
6. Keep reviewing, start merging 🤘 😎 🤘