Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration

raravind commented

2023-11-14 15:57:01 +00:00

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,

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,

phsmoura commented

2023-11-14 19:10:40 +00:00

Metadata Update from @phsmoura:

Issue tagged with: medium-gain, medium-trouble, ops

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

jnsamyak commented

2023-11-20 17:32:26 +00:00

Owner

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 @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!

raravind commented

2023-11-20 18:22:03 +00:00

Author

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

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 >

ngompa commented

2023-11-20 18:41:32 +00:00

Member

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

raravind commented

2023-11-20 18:58:04 +00:00

Author

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

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 >

jnsamyak commented

2023-11-22 03:31:35 +00:00

Owner

Metadata Update from @jnsamyak:

Issue assigned to jnsamyak

**Metadata Update from @jnsamyak**: - Issue assigned to jnsamyak

jnsamyak commented

2024-05-17 09:40:51 +00:00

Owner

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:

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

Details (please verify):

Name: Bootloader engineering team
Email: bootloader-eng-team@redhat.com

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

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^

raravind commented

2024-05-20 18:58:15 +00:00

Author

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:

Need to make an account initially with some email

Someone from sysadmin-main than will add that to the packager group

Once we do that, we need to change the email address

Finally, that I can reassign those packages

Details (please verify):

Name: Bootloader engineering team

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

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 >

jnsamyak commented

2024-05-22 16:56:06 +00:00

Owner

awesome thanks for confirming!

jnsamyak commented

2024-09-30 23:34:49 +00:00

Owner

@raravind, texted you internally to confirm details and validate the email for the user!

ngompa commented

2024-10-01 11:01:19 +00:00

Member

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

The difference is that the Anaconda team has historically been quite accessible. They have a a Matrix room (#anaconda:fedoraproject.org) and a public mailing list (anaconda-devel@lists.fedoraproject.org) that they can be reached from. I cannot really say the same for the bootloader folks. Most don't know how to get in touch with them (or even who they are), and redhat.com mailing lists nowadays bounce non-RH emails since they switched to Google Groups.

So how do we engage with the bootloader team from the Fedora side? How can we talk to the responsible party in a pinch?

> 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 > The difference is that the Anaconda team has historically been quite accessible. They have a a Matrix room ([`#anaconda:fedoraproject.org`](https://matrix.to/#/#anaconda:fedoraproject.org)) and a public mailing list ([`anaconda-devel@lists.fedoraproject.org`](https://lists.fedoraproject.org/archives/list/anaconda-devel@lists.fedoraproject.org/)) that they can be reached from. I cannot really say the same for the bootloader folks. Most don't know how to get in touch with them (or even who they are), and `redhat.com` mailing lists nowadays bounce non-RH emails since they switched to Google Groups. So how do we engage with the bootloader team from the Fedora side? How can we talk to the responsible party in a pinch?

raravind commented

2024-10-01 12:25:24 +00:00

Author

What is the procedure for creating public mailing list?

As for the Red Hat mailing list issue, I don’t believe the switch to Google Groups automatically blocks non-RH emails for all teams, including "bootloader-eng-team@redhat.com". It’s possible that some groups haven't updated their settings to allow external communication. If you want to verify, you could test it by filing a test Bugzilla report for a Fedora bootloader component using a non-Red Hat email address. That should confirm if non-RH communication is restricted.

Also when it was bugzilla filing for RH we used the same mailing list.Also the same for the now jira.

What is the procedure for creating public mailing list? As for the Red Hat mailing list issue, I don’t believe the switch to Google Groups automatically blocks non-RH emails for all teams, including "bootloader-eng-team@redhat.com". It’s possible that some groups haven't updated their settings to allow external communication. If you want to verify, you could test it by filing a test Bugzilla report for a Fedora bootloader component using a non-Red Hat email address. That should confirm if non-RH communication is restricted. Also when it was bugzilla filing for RH we used the same mailing list.Also the same for the now jira.

ngompa commented

2024-10-01 12:45:31 +00:00

Member

All BZ and Jira emails come from redhat.com domain, so it should pass through regardless.

All BZ and Jira emails come from `redhat.com` domain, so it should pass through regardless.

ngompa commented

2024-10-01 12:46:49 +00:00

Member

What is the procedure for creating public mailing list?

Just file a ticket asking for it in https://pagure.io/fedora-infrastructure.

Here's an example ticket: https://pagure.io/fedora-infrastructure/issue/12111

> What is the procedure for creating public mailing list? Just file a ticket asking for it in https://pagure.io/fedora-infrastructure. Here's an example ticket: https://pagure.io/fedora-infrastructure/issue/12111

raravind commented

2024-10-01 15:20:03 +00:00

Author

No, we have jiras/bz coming from customers/partners, I mean non "redhat.com".You can give a test using your non redhat email id and file a bz

ngompa commented

2024-10-01 15:25:17 +00:00

Member

What I mean is that any email sent by RHBZ from a bug filed would be from bugzilla@redhat.com, not from my actual email address. Thus it makes it through.

What I mean is that any email sent by RHBZ from a bug filed would be from `bugzilla@redhat.com`, not from my actual email address. Thus it makes it through.

raravind commented

2024-10-02 11:21:34 +00:00

Author

okay, I have created a mailing list - bootloader-eng-team@lists.fedoraproject.org

Rows
Columns

Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration #11782