2 ms·

I was surprised by the volume of the handbook material that applies to the role of CEO shadow. To me it implied a high level of formality and expectation of rig

I was surprised by the volume of the handbook material that applies to the role of CEO shadow. To me it implied a high level of formality and expectation of rigid adherence. Then I found this: > CEO shadows label the handbook MRs they create with the ceo-shadow label. It's a point of competition between CEO shadows to try to best the previous shadows' number of merge requests. I am no longer surprised by the length of this section of the handbook.

lbotos 4y ago
As a shadow, you would contribute anywhere, not just on the CEO Shadow process. I see them often on slack updating various random pages: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests?scope=all&state=merged&label_name[]=ceo-shadow https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_request...