Add Albert as Backend Maintainer

Trainee maintainer issue: #8872 (closed)

I have been at GitLab for over 2.5 years. 6 months in ~"group::pipeline insights", 2+ years in Engineering Productivity before that.

I was previously tooling maintainer on gitlab-org/gitlab when I was in Engineering Productivity. Previously also maintainer of a few Engineering Productivity related projects (gitlab-triage, triage-ops).

I think I am comfortable identify potential breaking changes in APIs or Sidekiq, but I need to be more aware of other forms of breaking changes. For example, CI configuration.
I have not worked much with GraphQL and the area of code I work on don't usually require GraphQL, so I may need additional help when reviewing GraphQL changes.

@gitlab-org/maintainers/rails-backend please chime in below with your thoughts, and approve this MR if you agree.

Developer checklist

Before this MR is merged
- Mention @gitlab-org/maintainers/rails-backend, if not done (this issue template should do this automatically)
- Assign this issue to your manager
After this MR is merged
- Request a maintainer from the #backend_maintainers Slack channel to add you as an Owner to gitlab-org/maintainers/rails-backend
- Consider adding 'backend maintainer' to your Slack notification keywords

Before this MR is merged
- The MR has been open for 5 working days
- More than half of the existing maintainers approve the MR (see the maintainer list)
- There are no blocking concerns raised (if there are, please follow https://about.gitlab.com/handbook/engineering/workflow/code-review/#how-to-become-a-project-maintainer)
After this MR is merged
- Announce the good news in the relevant channels listed in https://about.gitlab.com/handbook/engineering/#keeping-yourself-informed

Edited Jun 03, 2022 by Albert

Assignee

Reviewers

Request review from

Time tracking