Coding CC Rights Expansion: Adolfo Brandes

Working Groups Core Contributors
1

Hi all,

As part of an update to OEP-54 Core Contributors, we have codified a nomination process for coding CCs looking to expand their commit rights. Following this procedure, I am nominating @arbrandes for commit rights to the following foundational frontend repos:

  • frontend-platform
  • frontend-template-application
  • frontend-build
  • frontend-component-header
  • frontend-component-footer

Adolfo has been a community member for seven years; he joined the Core Contributor program in June of 2021 and has commit rights to the following repos: frontend-app-library-authoring & edx-platform, as well as all release branches.

Adolfo has been a valued member of the Build Test Release guild, a prolific contributor of code, and a highly active community member. He has recently joined the team at tCRIL, serving as our team’s Principal Frontend Engineer. He has jumped into frontend stuff - he is currently working with the frontend working group and the tCRIL product manager to get better grounding in our current state and work to chart a course for a frontend ecosystem that works for the whole community.

Per the updated OEP, the comment period will be active for 1 week given that Adolfo already has experience with frontend code and is already a core contributor on a frontend-app repo. Please provide review comments by February 18. Thanks!

7 Likes
2

@sarina @arbrandes Sounds good to me! :+1: I don’t work with the repos being discussed, but knowing @arbrandes he has always acted responsibly with the rights he was given, and done good things with his responsibilities, so it sounds like a good idea. :slight_smile:

1 Like
3

I think that this makes sense. That’s a yes from me although I don’t have cc rights to the repos involved. Still, Adolfo’s contributions so far in the community have always been of very high quality and I know it will continue to be so.

2 Likes
4

I’m not a CC, but I’ll chime in with a wholehearted endorsement. :smile:

1 Like
5

@djoy you very much do get a vote. As we clarified here, anyone who can commit to a repo should weigh in. This is vitally important for repos like these, where there are no non-2U core contributors.

I already clarified this for Robert in another thread, and in my post to #frontend-working-group, I did say people who have commit rights to the repos in question should be part of the decision. Is there a way I could make this clearer to your team?

6

Seems pretty clear now; I just hadn’t seen the update to the OEP when it flew by, nor today’s Slack message.

I don’t have an offhand suggestion about how to make folks aware of OEP updates they didn’t see and/or get a notification for. I imagine that may spread by word of mouth a bit and some folks may sometimes have gaps in their understanding like I did.

1 Like
7

@djoy Ahhh I assumed you saw the message in the working group channel. Great, thanks. I will keep trying to advertise things :slight_smile:

8

I don’t have write access to those repos (I’m just a CC for other repos).
If I have a vote then I vote yes.

We need at least a CC on every repo used by the platform and MFEs.

2 Likes
9

I worked with @arbrandes on frontend-app-library-authoring as part of BD-14 (blockstore-backed content libraries). I can attest that he is a competent and thoughtful frontend developer, and I support his access to all of these repositories :+1:

3 Likes
10

Yes vote from me. We’ll all benefit from @arbrandes having expanded commit rights on these repos.

3 Likes
11

@giovannicimolin I’m not sure the best way to advertise the following more widely, do you have any idea?

Per OEP-54 Nomination Process specification:

1 Like
12

The formal comment period is closed. Thank you everyone for your consideration!

Results

@arbrandes congrats!

Note: Voting is done, but you can still post additional congratulations. :wink:

6 Likes
13

Thanks for the vote(s) of confidence, everybody!

1 Like