[opensuse-factory] re-thinking the Bootloader component and looking for a new component owner
Hello openSUSE! We're looking for a new default owner for the bugzilla component Bootloader. Jiri recently started on a new position and would be happy if somebody else would take over the component. He also mentioned that we should consider renaming the component "Bootloader" to grub, as the component sometimes gets bugs relevant to GNOME and so on, but it's intended for issues with boot/pre-boot area. I did check briefly a list of packages and I've seen some open OpenPower related tools for diagnosis but it seems like grub2 is indeed the default bootloader on all of our arches including armv7 and RISC- V. So grub or grub2 to be more precise would make sense. I see that names of our components are mostly generic Basesystem, however, we have also components like GNOME. It would be nice to have some consistent naming policy. So that's most likely the only reason why I'd personally prefer Bootloader. Any thoughts? -- Best regards Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
On Wed, 2020-04-15 at 14:18 +0000, Lubos Kocman wrote:
Hello openSUSE!
We're looking for a new default owner for the bugzilla component Bootloader. Jiri recently started on a new position and would be happy if somebody else would take over the component.
He also mentioned that we should consider renaming the component "Bootloader" to grub, as the component sometimes gets bugs relevant to GNOME and so on, but it's intended for issues with boot/pre-boot area.
I doubt this is going to stop wrong classifications: GNOME also gets all kind of reports which are not GNOME related.
I did check briefly a list of packages and I've seen some open OpenPower related tools for diagnosis but it seems like grub2 is indeed the default bootloader on all of our arches including armv7 and RISC- V.
So grub or grub2 to be more precise would make sense. I see that names of our components are mostly generic Basesystem, however, we have also components like GNOME.
Using Generic names instead of technology names sounds more appealing to me. This allows for changes (e.g. lilo -> grub -> grub2) as they happen all the time. 'GNOME', 'KDE, 'MATE' and the like are also not single packages, but complete sets of desktop environments. Cheers, Dominique
Lubos Kocman composed on 2020-04-15 14:18 (UTC):
He also mentioned that we should consider renaming the component "Bootloader" to grub Some possible reasons to maybe keep the name component name bootloader, and/or avoid calling the component grub:
R-boot coreboot-utils efibootmgr elilo extlinux gfxboot lilo grub legacy grub2 grubby kiwi master-boot-code os-prober perl-bootloader pxeboot python*bootstrap rebootmgr syslinux systemd-boot tftpboot u-boot-tools unetbootin yast2-bootloader yast2-firstboot -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, 2020-04-15 at 11:55 -0400, Felix Miata wrote:
Lubos Kocman composed on 2020-04-15 14:18 (UTC):
He also mentioned that we should consider renaming the component "Bootloader" to grub Some possible reasons to maybe keep the name component name bootloader, and/or avoid calling the component grub:
R-boot coreboot-utils efibootmgr elilo extlinux gfxboot lilo grub legacy grub2 grubby kiwi master-boot-code os-prober perl-bootloader pxeboot python*bootstrap rebootmgr syslinux systemd-boot tftpboot u-boot-tools unetbootin yast2-bootloader yast2-firstboot
Majority of above mentioned do not fit into component bootloader anyways ... Cheers Martin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 15. 04. 20, 17:55, Felix Miata wrote:
Lubos Kocman composed on 2020-04-15 14:18 (UTC):
He also mentioned that we should consider renaming the component "Bootloader" to grub Some possible reasons to maybe keep the name component name bootloader, and/or avoid calling the component grub:
R-boot coreboot-utils efibootmgr elilo extlinux gfxboot lilo grub legacy grub2 grubby kiwi master-boot-code os-prober perl-bootloader pxeboot python*bootstrap rebootmgr syslinux systemd-boot tftpboot u-boot-tools unetbootin yast2-bootloader yast2-firstboot
And most importantly, what about mokutil and shim? All in all, I am against calling the component grub, as it's generally bootloaders, not grub. Here, I am speaking as an ex-grub2 maintainer. thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello team, sounds like we have an agreement on keeping on using Bootloader. What about the new default owner? Is there a volunteer? Please let me know by Friday. Otherwise, I'll reassign the component to the default screening team. Which is not the preferred option as it causes an extra delay. Thank you On Thu, 2020-04-16 at 07:23 +0200, Jiri Slaby wrote:
On 15. 04. 20, 17:55, Felix Miata wrote:
Lubos Kocman composed on 2020-04-15 14:18 (UTC):
He also mentioned that we should consider renaming the component "Bootloader" to grub Some possible reasons to maybe keep the name component name bootloader, and/or avoid calling the component grub:
R-boot coreboot-utils efibootmgr elilo extlinux gfxboot lilo grub legacy grub2 grubby kiwi master-boot-code os-prober perl-bootloader pxeboot python*bootstrap rebootmgr syslinux systemd-boot tftpboot u-boot-tools unetbootin yast2-bootloader yast2-firstboot
And most importantly, what about mokutil and shim?
All in all, I am against calling the component grub, as it's generally bootloaders, not grub. Here, I am speaking as an ex-grub2 maintainer.
thanks, -- js suse labs -- Best regards
Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
Hello team the Default owner and QA was changed to screening-team-bugs@suse.de / qa-bugs@suse.de in both openSUSE Leap and Tumbleweed. Cheers Lubos On Thu, 2020-04-16 at 10:44 +0000, Lubos Kocman wrote:
Hello team,
sounds like we have an agreement on keeping on using Bootloader. What about the new default owner? Is there a volunteer? Please let me know by Friday.
Otherwise, I'll reassign the component to the default screening team. Which is not the preferred option as it causes an extra delay.
Thank you On Thu, 2020-04-16 at 07:23 +0200, Jiri Slaby wrote:
On 15. 04. 20, 17:55, Felix Miata wrote:
Lubos Kocman composed on 2020-04-15 14:18 (UTC):
He also mentioned that we should consider renaming the component "Bootloader" to grub Some possible reasons to maybe keep the name component name bootloader, and/or avoid calling the component grub:
R-boot coreboot-utils efibootmgr elilo extlinux gfxboot lilo grub legacy grub2 grubby kiwi master-boot-code os-prober perl-bootloader pxeboot python*bootstrap rebootmgr syslinux systemd-boot tftpboot u-boot-tools unetbootin yast2-bootloader yast2-firstboot
And most importantly, what about mokutil and shim?
All in all, I am against calling the component grub, as it's generally bootloaders, not grub. Here, I am speaking as an ex-grub2 maintainer.
thanks, -- js suse labs -- Best regards
Luboš Kocman
Release Manager openSUSE Leap
SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany
(HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer ��칻 �&�zf���^�ˬy�������칻 �&ޢ���� ����'��- ���w�zf���^�ˬy�������'z�)z{.��+ -- Best regards
Luboš Kocman Release Manager openSUSE Leap SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer
participants (5)
-
Dominique Leuenberger / DimStar -
Felix Miata -
Jiri Slaby -
Lubos Kocman -
Martin Pluskal