#11782 Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration
Opened 7 months ago by raravind. Modified a month ago

Could you please change the following bootloader components listed below bugzilla assignee to Bootloader engineering team - bootloader-eng-team@redhat.com ?

The reason for this request is multiple engineers work on issue for same package and all can get awareness when someone files the bug;.also RH BZ and Jira  they uses / used this mailing list as default assignee.

bootloader components: efibootmgr,efivar,gnu-efi, grub2, grubby, mokutil, pesign, shim,syslinux,


Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

7 months ago

Hello @raravind!

thanks for opening the request but Please note that we require a FAS (Fedora Account System) entity for this purpose as we cannot directly assign issues to an email address. Within the FAS account entity system, we need to determine, based on the use case, whether the requirement necessitates multiple recipients or a single recipient. Toddlers, an automation tool, can directly access this information once we add the maintainer for the corresponding FAS account to the respective repository using https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/packager_bugzilla_sync.py.

In consideration of the assignment process, we have two potential approaches:

Dedicated FAS Account: Establishing a single dedicated FAS (Fedora Account System) account explicitly for this purpose. This dedicated account can be utilized internally to manage assignments for bootloader components.

Individual FAS Accounts for Team Members: Alternatively, each member of the Bootloader Team can create separate FAS accounts. Subsequently, these individual accounts can then be added to a dedicated FAS group specifically designated for the Bootloader Team. This method allows for a more distributed and personalized assignment structure while maintaining the collective association within the designated group.

Please consider these options in determining the most suitable approach for efficient assignment management within the Bootloader Team. As per your response we will try to act forward!

Hello Samayak,

I think moving forward Dedicated FAS Account for this purpose will be
good.

Regards,
Reshmi.

On Mon, Nov 20, 2023 at 6:32=E2=80=AFPM Samyak Jain pagure@pagure.io wrot=
e:

jnsamyak added a new comment to an issue you are following:
``
Hello @raravind!

thanks for opening the request but Please note that we require a FAS
(Fedora Account System) entity for this purpose as we cannot directly
assign issues to an email address. Within the FAS account entity system, =
we
need to determine, based on the use case, whether the requirement
necessitates multiple recipients or a single recipient. Toddlers, an
automation tool, can directly access this information once we add the
maintainer for the corresponding FAS account to the respective repository
using
https://pagure.io/fedora-infra/toddlers/blob/main/f/toddlers/plugins/pack=
ager_bugzilla_sync.py
.

In consideration of the assignment process, we have two potential
approaches:

Dedicated FAS Account: Establishing a single dedicated FAS (Fedora
Account System) account explicitly for this purpose. This dedicated accou=
nt
can be utilized internally to manage assignments for bootloader component=
s.

Individual FAS Accounts for Team Members: Alternatively, each member
of the Bootloader Team can create separate FAS accounts. Subsequently,
these individual accounts can then be added to a dedicated FAS group
specifically designated for the Bootloader Team. This method allows for a
more distributed and personalized assignment structure while maintaining
the collective association within the designated group.

Please consider these options in determining the most suitable approach
for efficient assignment management within the Bootloader Team. As per yo=
ur
response we will try to act forward!
``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/11782

So, how we do know who is responsible for a package, then?

Neal,

I'm not sure about that.

But, if you take a look here: https://src.fedoraproject.org/rpms/anaconda
you will find out that anaconda has default assignee as their mailing list
(anaconda-maint)
The advice I got in this matter is to file an issue on rel-engs so they
will create that user and change it to your mailing list.

Exactly the same thing(mailing list) we are using for redhat bz / Jira.
For example RH bz's like this -
https://bugzilla.redhat.com/show_bug.cgi?id=3D2186493
https://bugzilla.redhat.com/show_bug.cgi?id=3D2203203

-Reshmi

On Mon, Nov 20, 2023 at 7:41=E2=80=AFPM Neal Gompa pagure@pagure.io wrote=
:

ngompa added a new comment to an issue you are following:
So, how we do know who is responsible for a package, then?

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/11782

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

7 months ago

Hello @raravind;

So the workaround to it is, that need to create the initial account, but then need someone to add it to Packager and change the address on it to the list, then log in once to src.fedoraproject.org with it so it knows it's in Packager and exists and finally gives those packages to it.;

Breaking it:
1. Need to make an account initially with some email
2. Someone from sysadmin-main than will add that to the packager group
3. Once we do that, we need to change the email address
4. Finally, that I can reassign those packages

Details (please verify):
1. Name: Bootloader engineering team
2. Email: bootloader-eng-team@redhat.com

I'll then start from step one, once I have a confirmation about above details from you^

On Fri, May 17, 2024 at 11:40=E2=80=AFAM Samyak Jain pagure@pagure.io wro=
te:

jnsamyak added a new comment to an issue you are following:
``
Hello @raravind;

So the workaround to it is, that need to create the initial account, but
then need someone to add it to Packager and change the address on it to t=
he
list, then log in once to src.fedoraproject.org with it so it knows it's
in Packager and exists and finally gives those packages to it.;

Breaking it:
1. Need to make an account initially with some email
2. Someone from sysadmin-main than will add that to the packager group
3. Once we do that, we need to change the email address
4. Finally, that I can reassign those packages

Details (please verify):
1. Name: Bootloader engineering team
2. Email: bootloader-eng-team@redhat.com

I'll then start from step one, once I have a confirmation about above
details from you^

Details are right, Samyak; maybe you can keep name as
"bootloader-eng-team" (just a suggestion)

``

To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/11782

awesome thanks for confirming!

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog