Update mhamda.yml projects for trainee_maintainer
I feel fortunate to have three of GitLab's top engineers mentoring me in various areas, such as Databases, Scalability, and Full-stack development.
Following a conversation with @reprazent, he recommended that I be added as a trainee maintainer for labkit-ruby
.
Similarly, @ahegyi suggested that I become a Database reviewer for customers-gitlab-com
during our discussion.
Finally, @dstull recommended that I become a trainee maintainer for GitLab Project
during our conversation.
Some may question whether I have the capacity to handle these additional responsibilities. However, I believe that since labkit-ruby
doesn't require as many merge requests as the GitLab project and the Database changes in CDot are also not as intensive, I can manage the workload without creating too much noise. Furthermore, I believe that taking on these responsibilities will help me achieve exponential growth in various areas.
Finally, I am thrilled to have the opportunity to learn from such talented individuals, and I look forward to gaining valuable insights and knowledge from my mentors at GitLab.
Author Checklist
-
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
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.