Learn more about these different git repos.
Other Git URLs
The group releng-team is not mentioned here: https://docs.pagure.org/releng/sop_adding_new_release_engineer.html#adding-a-new-release-engineer
releng-team
Currently it seems to be used to allow git push override access on pagure-dist-git instead of cvsadmin which was previously used: https://pagure.io/pagure-dist-git/issue/19
cvsadmin
It needs to be clarified what the group is meant for and it should be documented.
Current team members: @acarter, @ausil, @katec, @kellin, @kevin, @limb, @maxamillion, @mohanboddu, @parasense, @pbrobinson, @puiterwijk, @ralph, @rlaliber
It is a different set of people that documented here: https://docs.pagure.org/releng/index.html#team-composition
And I meant to post https://pagure.io/pagure-dist-git/issue/19#comment-465170 here:
Acccording to @ausil it is meant to be a tracking group, however I also noticed that it seems to grant administrative permissions in Bodhi according to ansible:
$ ag releng-team roles/fas_client/files/aliases.template 343:releng-team: ausil,mohanboddu,parasense roles/bodhi2/base/templates/production.ini.j2 438:important_groups = proventesters provenpackager releng-team security_respons packager bodhiadmin virtmaint-sig kde-sig eclipse-sig infra-sig gnome-sig python-sig robotics-sig qa-tools-sig nodejs-sig lxqt-sig astro-sig 441:admin_packager_groups = provenpackager releng-team security_respons roles/bodhi2/base/templates/staging.ini.j2 400:important_groups = proventesters provenpackager releng-team security_respons packager bodhiadmin virtmaint-sig kde-sig eclipse-sig infra-sig gnome-sig python-sig robotics-sig 403:admin_packager_groups = provenpackager releng-team security_respons
@mohanboddu will look at this.
Metadata Update from @syeghiay: - Issue assigned to mohanboddu
@mohanboddu reports that we might need to work with the Infra team to identify what are the groups and what permissions they should have.
This is on @mohanboddu 's list for documentation. Hopes to complete this month.
Too late to document in F31, setting F32 tag.
Metadata Update from @syeghiay: - Issue tagged with: f32
The ways of contacting the releng team are here: https://pagure.io/group/releng rel-eng@lists.fedora.org
https://docs.pagure.org/releng/#contact-information has team composition and this information will be updated here via pull request.
Closing this ticket now.
Metadata Update from @amoloney: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.