# Core Contributor Nomination: Brian Smith **URL:** \ **Category:** Core Contributors\ **Tags:** cc-nomination\ **Created:** [January 19, 2023, 2:38pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166 "2023-01-19T14:38:13Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\ **Post date:** [January 19, 2023, 2:38pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/1 "2023-01-19T14:38:13Z")
I’d like to nominate @brian.smith as a new core contributor with both coding rights to frontend-related repositories as well as admin rights to the openedx org, as described and justified below. ### Introducing Brian Brian was hired by tCRIL as a frontend engineer and has been with us since September 2022. We’re very happy with his work! In addition to his consistent participation in the Paragon and Frontend working groups, evidence of his skills can already be found in two key areas of the codebase: Library authoring and components: - Merged [8 PRs](https://github.com/openedx/frontend-app-library-authoring/pulls?q=is%3Apr+author%3Abrian-smith-tcril+is%3Amerged) to frontend-app-library-authoring, in an effort to clear tech debt and make the MFE more customizable - Merged [a PR](https://github.com/openedx/frontend-component-header/pull/271) to frontend-component-header to make the Studio header more flexible Translations: - Added [a JS translations job](https://github.com/openedx/openedx-translations/pull/18) to openedx-translations - Refactored openedx-atlas [to use bash](https://github.com/openedx/openedx-atlas/pull/5), so that it could be used by frontend repositories that don’t contain any python code Brian is also currently working on making the Libraries v2 components easily installable in a production-like environment via Tutor plugins. ### Access sought #### Coding rights to frontend repositories One of the hurdles contributors to the project face is the time it takes for code to be reviewed and then merged. In order to help reduce that time, tCRIL encourages its hand-picked engineering team to comb through PRs and push them forward. Brian would be a key addition to this effort, but to do so effectively he needs the community to grant him coding rights to the relevant repositories given his area expertise. These would be: - frontend-platform - frontend-template-application - frontend-build - frontend-app-\* (all MFEs) - frontend-component-\* (all MFE components) - frontend-lib-\* (all MFE libraries) - frontend-enterprise-\* (all frontend Enterprise repositories) - studio-frontend - edx-platform (limited to frontend code) - frontend-wg (Edit: Added after initial posting after [a suggestion](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/3) below.) - paragon - eslint-config - stylelint-config-edx - browserslist-config - edx-bootstrap - edx-ui-toolkit - cypress-e2e-tests - brand-openedx > On logistics: we intend to group frontend-related repositories on Github to make managing access to them easier. For instance, **frontend-mfes-all** will include all MFEs, components, and libraries, whereas **frontend-all** would add `edx-platform`, `studio-frontend`, and others. #### Coding rights to translations repositories To continue his work on frontend translations, Brian is also nominated for coding rights on the following repositories: - openedx-translations - openedx-atlas #### Org-level admin In order for Brian to be able to help the tCRIL team with our [on-call rotation](https://openedx.atlassian.net/wiki/spaces/COMM/pages/3344957577/tCRIL+Engineering+On-Call), he’s going to need org-wide admin rights for `openedx` on Github. This will give him access to configure settings on the organization and all of its repositories, all of which are required to complete related maintenance tasks. Technically, this would also allow him to push to any repository - not just frontend ones - at any time. The right to do so, however, would not be granted by this nomination process. ### Commitment Like all tCRIL engineers, Brian will be devoting on average 80% of his time to work directly related to his core contributor role. ### Comment period For this nomination to pass, Brian needs 5 positive votes and no un-addressed objections **by February 2, 2023** : two weeks from this posting. ---
**Author:** ![sarina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sarina/32/2308_2.png) [@sarina](https://discuss.openedx.org/u/sarina)\ **Post date:** [January 19, 2023, 2:42pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/2 "2023-01-19T14:42:14Z")
I’m probably biased as Brian’s manager, but in my time working with him he’s been thoughtful about his approaches to code, full of ideas about ways to improve, and enthusiastic about the frontend community. He works closely with Adolfo and the rest of the tCRIL team, so I know he has the support he needs. 👍 from me! ---
**Author:** ![AdamStankiewicz](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/adamstankiewicz/32/2822_2.png) [@AdamStankiewicz](https://discuss.openedx.org/u/AdamStankiewicz)\ **Post date:** [January 19, 2023, 3:29pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/3 "2023-01-19T15:29:25Z")
I’m in support of this nomination for Brian! As mentioned, Brian has made positive contributions to both the Paragon and Frontend Working Groups. By getting additional resources with merge rights, we can continue to address and improve upon the review bottleneck. A follow-up question… Should the following repos also be included, given it seems this list intends to be encompassing of all frontend-related repos? paragon, eslint-config, stylelint-config-edx, browserslist-config, edx-bootstrap, edx-ui-toolkit, cypress-e2e-tests, etc.? Regardless, Brian’s got my vote! 👍 ---
**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\ **Post date:** [January 19, 2023, 4:19pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/4 "2023-01-19T16:19:35Z")
> [@AdamStankiewicz](#): > > paragon, eslint-config, stylelint-config-edx, browserslist-config, edx-bootstrap, edx-ui-toolkit, cypress-e2e-tests, etc.? I think those make sense as well, but was on the fence about paragon: given it’s going on the Maintainer’s Pilot, I figured that could eventually be a separate nomination for specific consideration of the maintainer. On second thought, though, the fact a repository has a maintainer as defined by the pilot shouldn’t really affect the core contributor’s role in it. In other words, I’ll add them to the list. Thanks! ---
**Author:** ![AdamStankiewicz](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/adamstankiewicz/32/2822_2.png) [@AdamStankiewicz](https://discuss.openedx.org/u/AdamStankiewicz)\ **Post date:** [January 19, 2023, 4:53pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/5 "2023-01-19T16:53:33Z")
> [@arbrandes](#): > > given it’s going on the Maintainer’s Pilot, I figured that could eventually be a separate nomination for specific consideration of the maintainer. Ah, fair point. I suppose this statement is in line with what’s written in the Maintainers OEP, too, i.e.: > Selection and approval of Core Contributors with commit rights to their repositories, by participating in the comment period for Core Contributor nominees nominated to commit code to their repo(s), as part of the [Core Contributor Program](https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0054-core-contributors.html) I suppose it could be treated as a separate nomination thread altogether, or it could also be including Paragon in the original nomination but draw the attention of the Maintainer for the repository to the nomination thread (as with this thread). Either way, as the technical Maintainer for Paragon, Brian’s still got my approval 😉 Oh, here’s another potential repo to add to the mix as well: [GitHub - openedx/brand-openedx](https://github.com/openedx/brand-openedx). ---
**Author:** ![feanil](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/feanil/32/37_2.png) [@feanil](https://discuss.openedx.org/u/feanil)\ **Post date:** [January 19, 2023, 6:56pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/6 "2023-01-19T18:56:49Z")
Brian has done amazing work across various front end repos and I’ve really appreciated his balance of communication and curiosity with taking action to get things moving. 👍 from me! ---
**Author:** ![gabrieldamours](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/gabrieldamours/32/5569_2.png) [@gabrieldamours](https://discuss.openedx.org/u/gabrieldamours)\ **Post date:** [January 19, 2023, 7:13pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/7 "2023-01-19T19:13:01Z")
I haven’t had the opportunity of working with Brian (yet), but seeing your comments I definitely support his nomination 👍 ---
**Author:** ![sarina](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sarina/32/2308_2.png) [@sarina](https://discuss.openedx.org/u/sarina)\ **Post date:** [January 19, 2023, 7:32pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/8 "2023-01-19T19:32:21Z")
@arbrandes could you be sure to update the top level post with the additional repos you’re adding to the request? ---
**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\ **Post date:** [January 19, 2023, 7:36pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/9 "2023-01-19T19:36:01Z")
> [@sarina](#): > > be sure to update the top level post with the additional repos you’re adding to the request Yup, I’ve been taking care to do it while also making it clear they were added afterwards. ---
**Author:** ![cmuniz](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/cmuniz/32/3482_2.png) [@cmuniz](https://discuss.openedx.org/u/cmuniz)\ **Post date:** [January 20, 2023, 3:55pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/10 "2023-01-20T15:55:05Z")
Brian Smith is a hard worker with a short but varied history of contribution. I absolutely 100% support his nomination as a Core Contributor. 👍 I would also like to add the repositories [openedx-translations](https://github.com/openedx/openedx-translations) and [openedx-atlas](https://github.com/openedx/openedx-atlas) to the list of repos Brian should be a core contributor of. ---
**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\ **Post date:** [January 20, 2023, 4:40pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/11 "2023-01-20T16:40:41Z")
> [@cmuniz](#): > > I would also like to add the repositories [openedx-translations](https://github.com/openedx/openedx-translations) and [openedx-atlas](https://github.com/openedx/openedx-atlas) to the list of repos +1 I’ve added them to the top post. ---
**Author:** ![Felipe](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/felipe/32/60_2.png) [@Felipe](https://discuss.openedx.org/u/Felipe)\ **Post date:** [January 23, 2023, 6:58pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/12 "2023-01-23T18:58:47Z")
I have not yet worked with Brian but I am aware of the good work happening through him in the MFEs space. I think he has demonstrated the 3Cs so far and I vote **yes** to this nomination. ---
**Author:** ![dcoa](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/dcoa/32/3246_2.png) [@dcoa](https://discuss.openedx.org/u/dcoa)\ **Post date:** [January 23, 2023, 10:20pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/13 "2023-01-23T22:20:49Z")
Hi everyone, I’m not CC and I haven’t worked with Brian directly but I support this nomination because I am aware of the contributions in the different repos and discussions around Frontend in open edx, I think he has good ideas to improve the code and experience of the platform. ---
**Author:** ![ndespujol](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/ndespujol/32/4701_2.png) [@ndespujol](https://discuss.openedx.org/u/ndespujol)\ **Post date:** [January 27, 2023, 1:56pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/14 "2023-01-27T13:56:56Z")
Given his list of achievements in such a short time and former comments I also support his nomination. ---
**Author:** ![sambapete](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/sambapete/32/4100_2.png) [@sambapete](https://discuss.openedx.org/u/sambapete)\ **Post date:** [January 27, 2023, 3:40pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/15 "2023-01-27T15:40:06Z")
I also supports this nomination. ---
**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\ **Post date:** [February 2, 2023, 7:38pm UTC](https://discuss.openedx.org/t/core-contributor-nomination-brian-smith/9166/16 "2023-02-02T19:38:04Z")
The comment period has elapsed, with 10 yesses, and 0 noes. Welcome to the Core Contributor program, @brian.smith!! Thank you for taking the time to give your impressions, everybody!