# CC Rights Expansion: members of the BTR working group **URL:** \ **Category:** Core Contributors\ **Created:** [May 26, 2022, 8:53pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346 "2022-05-26T20:53:39Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![pdpinch](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/pdpinch/32/36_2.png) [@pdpinch](https://discuss.openedx.org/u/pdpinch)\ **Post date:** [May 26, 2022, 8:53pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/1 "2022-05-26T20:53:39Z")
Following the procedure outlined in [OEP-54](https://open-edx-proposals.readthedocs.io/en/latest/processes/oep-0054-core-contributors.html#expansion-of-core-contributor-responsibilities), I’d like to nominate the core-contributor members of the Build-Test-Release (BTR) working group to expand their rights to include closing and assigning issues the [build-test-release-wg](https://github.com/openedx/build-test-release-wg) repository. working group members who are core contributors and need their rights expanded: - Dean Jay Mathew DeanJayMathew - Ghassan Maslamani ghassanmas - Jhony Avella jfavellar90 - Maria Grimaldi mariajgrimaldi - Peter Pinch pdpinch - Pierre Mailhot sambapete - Régis Behmo regisb (Note that this nomination includes myself. If I’ve missed anyone, let me know.) ## Motivation Allowing the members of the working group to assign and close [issues in the repository](https://github.com/openedx/build-test-release-wg/issues) will make us much more efficient and improve communications. In particular, it will allow us to assign issues to ourselves and close them when they are done. ## Prior work All our relevant work to this request is [GitHub · Where software is built](https://github.com/openedx/build-test-release-wg/issues) **Please provide review comments by June 9th.** ---
**Author:** ![BbrSofiane](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/bbrsofiane/32/561_2.png) [@BbrSofiane](https://discuss.openedx.org/u/BbrSofiane)\ **Post date:** [May 27, 2022, 10:01am UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/2 "2022-05-27T10:01:16Z")
+1 From me. This remove a lot of bottlenecks in the BTR group processes! ---
**Author:** ![antoviaque](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/antoviaque/32/32_2.png) [@antoviaque](https://discuss.openedx.org/u/antoviaque)\ **Post date:** [May 27, 2022, 3:02pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/3 "2022-05-27T15:02:07Z")
+1 from me too – it makes sense for the group members to be able to edit issues, and everyone in the list definitely deserves it! 👍 I think on the OpenCraft side @mtyaka is looking to join the group – sorry for the shuffle on our side for the group membership. ---
**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:** [May 27, 2022, 7:17pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/4 "2022-05-27T19:17:39Z")
Hi @pdpinch I mostly agree with this, however, Dean, Pierre, & Ghassan have joined the CC program as _non-technical contributors_, meaning they have not been approved to have write access to a GitHub repo - their roles are non-technical so this would not be a rights expansion request, this would be a new role request. I do not know the best way to resolve this. We would need to induct Dean, Pierre, & Ghassan as Core Contributors (committer) to grant this access, and would likely want to go through a separate process for each candidate to discuss them holding this role. Legally, there will be a separate document to sign in order to have write access to a repo. ---
**Author:** ![pdpinch](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/pdpinch/32/36_2.png) [@pdpinch](https://discuss.openedx.org/u/pdpinch)\ **Post date:** [May 27, 2022, 7:38pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/5 "2022-05-27T19:38:31Z")
There’s nothing technical in [GitHub - openedx/build-test-release-wg: Open edX Build / Test / Release Working Group](https://github.com/openedx/build-test-release-wg) Contents of the repo is just a few decision records. It mostly exists for the issue tracker and the project board. ---
**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:** [May 27, 2022, 8:05pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/6 "2022-05-27T20:05:42Z")
While I understand that, from a technical and legal perspective they would be getting write access to repos which requires you to join the CC program as a committer. With that write access they could possibly commit any amount of code that did anything - so need to be covered by Committers Agreement. ---
**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:** [May 27, 2022, 8:11pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/7 "2022-05-27T20:11:22Z")
Technically, correct me if am wrong, I am one of those special cases because I am both non-technical (translations working group) and technical (built-test-release working group)? As far as I know, I don’t have access to any repository right now… ---
**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:** [May 27, 2022, 8:22pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/8 "2022-05-27T20:22:55Z")
@sambapete ah I’m sorry, I missed you. You’ve joined the CC program as a non-technical contributor. Being a member of a working group is not the same as being part of the CC program as a committer. ---
**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:** [May 27, 2022, 8:25pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/9 "2022-05-27T20:25:31Z")
No problem. That’s what I originally thought when you didn’t mention me. Still, I am the quality assurance manager for the tests. I guess this is partially technical but not committers technical. ---
**Author:** ![BbrSofiane](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/bbrsofiane/32/561_2.png) [@BbrSofiane](https://discuss.openedx.org/u/BbrSofiane)\ **Post date:** [May 27, 2022, 8:40pm UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/10 "2022-05-27T20:40:35Z")
For the BTR WG, some of us have write permissions on the release branches of repos we are not CC by the way of a GitHub action. Can we use a similar solution? Beyond the BTR WG, is the situation the same for all WG? By situation I mean, some active members of a working group need permissions that are only granted to CCs. ---
**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:** [May 28, 2022, 1:00am UTC](https://discuss.openedx.org/t/cc-rights-expansion-members-of-the-btr-working-group/7346/11 "2022-05-28T01:00:15Z")
> [@BbrSofiane](#): > > Beyond the BTR WG, is the situation the same for all WG? Yes, it would be the same case. I know how it seems, but the legal around who can write to repos is pretty strict. I think it may take an amount of backflipping to try to somehow craft legal language to separate one type of commit access from another. Also I bet, a fair amount of time. > [@BbrSofiane](#): > > For the BTR WG, some of us have write permissions on the release branches of repos we are not CC by the way of a GitHub action. Can we use a similar solution? I am not certain the same concept would apply. I don’t know how Projects or that API or permissions work there. For the releasers, your account doesn’t have write access - the bot does - and it checks the command against an allowlist of people. I guess it may be possible to write a github action or bot that monitors comments and performs actions based on an allow list of users, but that would certainly involve understanding the projects API which I don’t know. Are you using an old style project or a beta project? I’d be hesitant to write bespoke tooling for an old style project when the majority of Open edX projects are beta style.