Re: Why I won't run for FESCo

[Miroslav Suchý]

Dne 22. 11. 23 v 20:40 Miro Hrončok napsal(a):
*I am tired.* When I joined FESCo 5 years ago, I had the enthusiasm and energy. 


Enthusiasm - I think this is most important part. For anyone considering 
running for FESCO.

If anyone from the audience is considering running for FESCO, but you hesitate that you are not experienced enough... 
you will get experience over time, but you rarely get enthusiasm over time - that it is most precious thing. If you are 
enthusiastic about Fedora, please, please, nominate yourself here:


https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations#Candidate_Nominations

--
Miroslav Suchy, RHCA
Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Co-maintainers for my ham packages

[Matt Domsch]

Richard, as I am no longer able to run or test the above Ham packages, I
will remove myself from them. I've reassigned several open bug reports to
you (you were already on cc and recently addressed one issue with sdrpp -
thank you!).

Thanks,
Matt N5MLD

On Sun, Jun 5, 2022 at 9:22 PM Matt Domsch  wrote:

> Blaise, I appreciate your offer. I regret I won't have time in the next
> several months to be a packaging Elmer myself.
>
> Richard, I've added you as an admin to each of these.  Note that kni also
> is an admin for SoapySDR and swt2c is an admin for CubicSDR.
>
> Thanks,
> Matt N5MLD
>
> On Thu, May 26, 2022 at 10:24 PM Blaise Pabon  wrote:
>
>> Well, I have been wanting to become a fedora packager for a while and I
>> have some of that hardware somewhere around here.
>> I might need an Elmer to help me through the first iteration.
>>
>> -Blaise
>>
>> On Thu, May 26, 2022 at 6:28 PM Richard Shaw 
>> wrote:
>>
>>> On Thu, May 26, 2022 at 1:59 PM Matt Domsch  wrote:
>>>
 Due to an impending move to NYC and related downsizing of my house into
 a 2-bedroom apartment, I'm selling all my ham radio gear. Therefore I won't
 be able to test any of the Fedora packages I maintain with actual
 hardware.  Would anyone be interested in maintaining or co-maintaining
 these?

 - direwolf - Sound Card-based AX.25 TNC
 - CubicSDR - Cross-Platform Software-Defined Radio Panadapter
 - liquid-dsp - Digital Signal Processing Library for Software-Defined
 Radios
 - sdrpp - SDRPlusPlus bloat-free SDR receiver software
 - SoapySDR - A Vendor Neutral and Platform Independent SDR Support
 Library
 - soapy-rtlsdr - SoapySDR module for RTL-SDR hardware

>>>
>>> Whichever ones aren't taken, just give them to me (or orphan them and
>>> let me know).
>>>
>>> But if someone wants them, please take them! I need more packages like I
>>> need a new hole in my head. :)
>>> Thanks,
>>> Richard
>>> K5OIM
>>> ___
>>> devel mailing list -- devel@lists.fedoraproject.org
>>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>>> Do not reply to spam on the list, report it:
>>> https://pagure.io/fedora-infrastructure
>>>
>>
>>
>> --
>> LinkedIn   |  Quora
>>   |  Github
>> 
>> “If you want to go fast, go alone. If you want to go far, go together.” 
>> --African
>> proverb
>>
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Why I won't run for FESCo

[Sérgio Basto]

On Wed, 2023-11-22 at 20:40 +0100, Miro Hrončok wrote:
> The communication channels 

yeah , I had to go back to IRC if I want to communicate with certain
groups.
We went to Matrix because there was a bridge with IRC, but many people
didn't switch from IRC, the bridge collapsed and now we have half the
people on one side and half on the other ...

https://matrix.org/blog/2023/08/libera-bridge-disabled/

Thank you Miro for all the work

Another though , IMO,  we should rethink the packaging rules, I have
always defended, we should avoid the excessive number of packages for
the same software and pack it all in one.
A simple example is rpkg , rpkg-utils , fedpkg and centospkg . I think
it should be one package or two and at most with several sub-packages.
Now, argue to me, that as they are different sources, they must be
different packages, when utils is one or two small files and doesn't
work without the main package rpkg. In my opinion, results in excessive
work without any benefit, just to comply with a rule or a guideline. 

Other example , for example is kmodtools and akmods , one doesn't work
without the other, why we should pack 2 packages, do 2 commits , 2 push
, 2 builds , 2 updates etc etc . and guarantee that versions match ! I
don't see any benefit .

Best regards,
-- 
Sérgio M. B.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

https://releases.pagure.org/ is down

[Tomasz Kłoczko]

Hi,

Is it possible to do something about this?🤔

kloczek
-- 
Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH *
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Why I won't run for FESCo

[Ben Cotton]

There's a lot to be said for knowing when to step away. You've certainly
done more than your share for FESCo — and the broader Fedora community.
Thanks for all of your time on FESCo and the friendship you've shown to me
and countless others.
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Why I won't run for FESCo

[Gwyn Ciesla via devel]

Thank you for your service. You've more than earned a break. :)




\--


Gwyn Ciesla


she/her/hers


\


in your fear, seek only peace


in your fear, seek only love


\-d. bowie







Sent from Proton Mail mobile



\ Original Message 
On Nov 22, 2023, 1:40 PM, Miro Hrončok < mhron...@redhat.com> wrote:

>
> Hello. I won't be running for the Fedora Engineering Steering Committee this 
> time. Several folks already asked me why, so I decided to write it down and 
> share it on this list. \*I am tired.\* When I joined FESCo 5 years ago, I had 
> the enthusiasm and energy. I spent a lot of time working on Fedora. After 
> working hours (mostly spent on Fedora) I was still eager to dive deeper and 
> do more Fedora things. That is no longer the case. An hour-long FESCo IRC 
> meeting at 19:00 no longer excites me. It makes me sleepy. And when it runs 
> over, it makes me feel exhausted. When presented with an opportunity to sit 
> in a couch and watch a movie with my spouse (or take a nap) instead, it's 
> harder and harder for me to choose Fedora. It has always been a matter of 
> balance: I dedicated my time and energy and I got something in return. 
> Excitement for new things, joy of getting things done... Which brings me to a 
> second reason: \*It is no longer rewarding.\* Honestly, it doesn't feel like 
> we are steering anything. Arguing whether we should use a particular compiler 
> flag or drop X11 from KDE is not joyful. And those are the controversial 
> topics. The rest feels like rubber stamping tickets or forever postponing 
> Fedora changes approved years ago. Looking back, either we used to discuss 
> things that mattered to me more, or I started to care less. Either way, it is 
> no longer fun to FESCo at nights and weekends. Unfortunately, \*I don't have 
> time to steer Fedora during my working hours.\* The number of Python packages 
> in Fedora grows every release, and updating Python to a new major version is 
> a year-long challenge for two Red Hat engineers. The technical debt is 
> increasing, while new ideas are dormant. The more Pythons are added to more 
> RHELs, the more CVEs need to be fixed, the more people leave, the fewer 
> people in our team have time to do essential Fedora package maintenance. The 
> pile keeps growing. I must limit my work duties before I crack, and FESCo 
> seems to be the only remaining non-essential one 😞 Lastly, \*I feel lost.\* 
> Multiple people I enjoyed working with (were) moved away. The communication 
> channels I am comfortable with are slowly replaced witch things that make me 
> anxious. A new 2028 Fedora strategy is shaping, yet it is barely visible to 
> me because it happens "somewhere else". I could try harder, but given the 
> other reasons I probably won't. I enjoyed being at FESCo, but I need a break. 
> -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok -- 
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>  devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an 
> email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List 
> Guidelines: https://fedoraproject.org/wiki/Mailing\_list\_guidelines List 
> Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org 
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new\_issue

signature.asc
Description: OpenPGP digital signature
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Why I won't run for FESCo

[Miro Hrončok]

Hello.
I won't be running for the Fedora Engineering Steering Committee this time. 
Several folks already asked me why, so I decided to write it down and share it 
on this list.


*I am tired.* When I joined FESCo 5 years ago, I had the enthusiasm and energy. 
I spent a lot of time working on Fedora. After working hours (mostly spent on 
Fedora) I was still eager to dive deeper and do more Fedora things. That is no 
longer the case. An hour-long FESCo IRC meeting at 19:00 no longer excites me. 
It makes me sleepy. And when it runs over, it makes me feel exhausted. When 
presented with an opportunity to sit in a couch and watch a movie with my 
spouse (or take a nap) instead, it's harder and harder for me to choose Fedora.


It has always been a matter of balance: I dedicated my time and energy and I 
got something in return. Excitement for new things, joy of getting things 
done... Which brings me to a second reason: *It is no longer rewarding.* 
Honestly, it doesn't feel like we are steering anything. Arguing whether we 
should use a particular compiler flag or drop X11 from KDE is not joyful. And 
those are the controversial topics. The rest feels like rubber stamping tickets 
or forever postponing Fedora changes approved years ago. Looking back, either 
we used to discuss things that mattered to me more, or I started to care less. 
Either way, it is no longer fun to FESCo at nights and weekends.


Unfortunately, *I don't have time to steer Fedora during my working hours.* The 
number of Python packages in Fedora grows every release, and updating Python to 
a new major version is a year-long challenge for two Red Hat engineers. The 
technical debt is increasing, while new ideas are dormant. The more Pythons are 
added to more RHELs, the more CVEs need to be fixed, the more people leave, the 
fewer people in our team have time to do essential Fedora package maintenance. 
The pile keeps growing. I must limit my work duties before I crack, and FESCo 
seems to be the only remaining non-essential one 😞


Lastly, *I feel lost.* Multiple people I enjoyed working with (were) moved 
away. The communication channels I am comfortable with are slowly replaced 
witch things that make me anxious. A new 2028 Fedora strategy is shaping, yet 
it is barely visible to me because it happens "somewhere else". I could try 
harder, but given the other reasons I probably won't.


I enjoyed being at FESCo, but I need a break.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Possible deprecation/removal of Initial Setup from Fedora

[Gerd Hoffmann]

On Tue, Nov 21, 2023 at 08:07:06AM -0800, Davide Cavalca wrote:
> On 2023-11-21 04:34, Jiri Konecny wrote:
> > Is Anaconda Initial Setup important for your project or workflow? What
> > functionality is absolutely necessary for you? Do you use the text
> > mode or the graphical mode? Are you aware of any alternatives? Is
> > there anything that would prevent you from migrating to one of the
> > proposed alternatives? Also please feel free to share this mail to any
> > relevant groups.
> 
> The Fedora Asahi Remix uses initial-setup (in text mode) for our Server and
> Minimal variants.

I think this is used by *all* server images.  It offers to set the root
password and add users, so without that you simply can't login ...

take care,
  Gerd
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora rawhide compose report: 20231122.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20231120.n.0
NEW: Fedora-Rawhide-20231122.n.0

= SUMMARY =
Added images:5
Dropped images:  4
Added packages:  29
Dropped packages:0
Upgraded packages:   182
Downgraded packages: 1

Size of added packages:  15.19 MiB
Size of dropped packages:0 B
Size of upgraded packages:   3.11 GiB
Size of downgraded packages: 354.30 KiB

Size change of upgraded packages:   7.00 MiB
Size change of downgraded packages: -272 B

= ADDED IMAGES =
Image: Astronomy_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-Rawhide-20231122.n.0.iso
Image: Scientific vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20231122.n.0.x86_64.vagrant-libvirt.box
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20231122.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20231122.n.0.iso
Image: Scientific vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20231122.n.0.x86_64.vagrant-virtualbox.box

= DROPPED IMAGES =
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20231120.n.0.iso
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20231120.n.0.iso
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20231120.n.0.iso
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20231120.n.0.iso

= ADDED PACKAGES =
Package: bcachefs-tools-1.3.4-3.fc40
Summary: Userspace tools for bcachefs
RPMs:bcachefs-tools
Size:7.19 MiB

Package: golang-cloud-google-bigquery-1.56.0-2.fc40
Summary: Google Cloud Client Libraries for Go for module bigquery
RPMs:golang-cloud-google-bigquery-devel
Size:469.00 KiB

Package: golang-cloud-google-compute-1.23.2-1.fc40~bootstrap
Summary: Google Cloud Client Libraries for Go for module compute
RPMs:golang-cloud-google-compute-devel
Size:797.49 KiB

Package: golang-cloud-google-compute-metadata-0.2.3-2.fc40
Summary: Google Cloud Client Libraries for Go for module compute/metadata
RPMs:golang-cloud-google-compute-metadata-devel
Size:36.33 KiB

Package: golang-cloud-google-datacatalog-1.18.2-2.fc40
Summary: Google Cloud Client Libraries for Go for module datacatalog
RPMs:golang-cloud-google-datacatalog-devel
Size:175.25 KiB

Package: golang-cloud-google-datastore-1.15.0-1.fc40~bootstrap
Summary: Google Cloud Client Libraries for Go for module datastore
RPMs:golang-cloud-google-datastore-devel
Size:128.54 KiB

Package: golang-cloud-google-firestore-1.14.0-2.fc40
Summary: Google Cloud Client Libraries for Go for module firestore
RPMs:golang-cloud-google-firestore-devel
Size:207.63 KiB

Package: golang-cloud-google-iam-1.1.4-2.fc40
Summary: Google Cloud Client Libraries for Go for module iam
RPMs:golang-cloud-google-iam-devel
Size:100.68 KiB

Package: golang-cloud-google-kms-1.15.4-2.fc40
Summary: Google Cloud Client Libraries for Go for module kms
RPMs:golang-cloud-google-kms-devel
Size:98.71 KiB

Package: golang-cloud-google-logging-1.8.1-2.fc40
Summary: Google Cloud Client Libraries for Go for module logging
RPMs:golang-cloud-google-logging-devel
Size:143.06 KiB

Package: golang-cloud-google-longrunning-0.5.3-2.fc40
Summary: Google Cloud Client Libraries for Go for module longrunning
RPMs:golang-cloud-google-longrunning-devel
Size:47.20 KiB

Package: golang-cloud-google-monitoring-1.16.2-2.fc40
Summary: Google Cloud Client Libraries for Go for module monitoring
RPMs:golang-cloud-google-monitoring-devel
Size:195.87 KiB

Package: golang-cloud-google-osconfig-1.12.3-2.fc40
Summary: Google Cloud Client Libraries for Go for module osconfig
RPMs:golang-cloud-google-osconfig-devel
Size:193.64 KiB

Package: golang-cloud-google-pubsub-1.33.0-1.fc40~bootstrap
Summary: Google Cloud Client Libraries for Go for module pubsub
RPMs:golang-cloud-google-pubsub-devel
Size:193.52 KiB

Package: golang-cloud-google-secretmanager-1.11.3-2.fc40
Summary: Google Cloud Client Libraries for Go for module secretmanager
RPMs:golang-cloud-google-secretmanager-devel
Size:55.73 KiB

Package: golang-cloud-google-spanner-1.51.0-2.fc40
Summary: Google Cloud Client Libraries for Go for module spanner
RPMs:golang-cloud-google-spanner-devel
Size:424.20 KiB

Package: golang-cloud-google-storage-1.33.0-2.fc40
Summary: Google Cloud Client Libraries for Go for module storage
RPMs:golang-cloud-google-storage-devel
Size:210.53 KiB

Package: golang-cloud-google-trace-1.10.3-2.fc40
Summary: Google Cloud Client Libraries for Go for module trace
RPMs:golang-cloud-google-trace-devel
Size:57.17 KiB

Package: hipblas-5.7.1-1.fc40
Summary: ROCm BLAS marshalling library
RPMs

Re: Possible deprecation/removal of Initial Setup from Fedora

[Jiri Konecny]

Hi Simon,

I guess I'm not able to answer this question well. I'm not part of the 
Gnome Initial Setup development. We should probably ask Gnome Initial 
Setup maintainers and other maintainers.


Best Regards,
Jirka

Dne 21. 11. 23 v 13:48 Simon de Vlieger napsal(a):

Hi Jiri,

On Tue, Nov 21, 2023, at 1:34 PM, Jiri Konecny wrote:

Hello everyone,

* There are already alternatives: Gnome Initial Setup,
systemd-firstboot, and preparation for KDE solution of initial setup. So
the ecosystem changed from the time when Initial Setup was introduced.

How about functionality loss for spins and editions that do not run a desktop
environment which provides its own initial setup?

Are any of the things (currently) being done by Anaconda Initial Setup 
unsupported
by Gnome Initial Setup or its counterparts?

Regards,

Simon
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue