Hi all,
I've recently joined Red Hat in Brno, Czech Republic. I'll be working
part-time in "Plumbers team" and I'll be helping out with maintenance of
low-level packages like systemd, dracut and initscripts.
Best regards,
Jan Macku

Hi,
Still searching for a wdune fedora sponsor.
Who is the fedora sponsor for aqsis ?
wdune (white_dune) can convert VRML/X3D to a RIB file, which can
be used with aqsis to create images (the images can be concatinated
to build a movie).
so long
MUFTI

Hi,
has anyone encountered a problem on F28 when building a package that
uses portaudio? I was building newer version of wireshark a month ago
and -lportaudio worked fine. Now the build with the same version fails
with message 'checking for Pa_Initialize in -lportaudio... no' and
'configure: error: Linking with libportaudio failed'. The build still
works on F29 and in Rawhide, only F28 hits this issue. Anyone else has
seen this happening?
Thanks.
--
Michal Ruprich
Associate Software Engineer
Email: mruprich(a)redhat.com
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 115, 612 00, Brno, Czech Republic

There is currently a problem with the networking of various systems in
our Phoenix data-center which houses most of our build systems. The
problem has knocked off most of our x86_64 build systems and several
of our aarch64/arm systems. Builds will take longer to process during
this time and may queue up for the remaining builders.
There is currently no ETA for when recovery will happen but due to end
of the year schedules, it will not happen until early January. If
things worsen we will see what escalation paths or changes can be
done.
--
Stephen J Smoogen.

I worked with FPL Matthew Miller and our engineering manager Jim
Perrin, among others, to define the various problems we want to solve
in diversifying the Fedora lifecycle. We're seeking review and
feedback from community members. The most salient feedback will be
from those involved in the efforts we describe, but we welcome all
constructive feedback.
Here's the summary from the page, which proposes we pause the release
after F30 for these efforts:
* * *
Fedora’s singular lifecycle has been in place for almost a decade and
a half. During that time, technology users have changed how they
consume platform and applications. Fedora needs to be more toward the
forefront of these changes. But more importantly, Fedora needs to be
more hospitable to community management of lifecycle.
Currently Fedora can’t scale for more community ownership of the
things we release: (1) Only a few people can build and push out
releases; and (2) we manage releases largely based on that staffing.
The Fedora community should be able to run releases of content
themselves, using tools that work well, with only minimal oversight,
and determine their own schedule for doing so.
This implies a great deal of both redesign and reworking of tools and
processes. To unblock the community, several things need to happen. We
need a faster, more scalable compose to enable CI/CD operations; we
need to automate more testing and quality measures; and we need to
update our delivery tools and processes. We also need to track and
coordinate this work across teams, since it involves collaboration
among Fedora infrastructure, QA, applications, release engineering,
CentOS CI, maintainers, and more.
We should skip the F31 release cycle and leave F30 in place longer in
order to focus on improving the tooling and testing changes. These
tooling changes will improve the overall reliability of Fedora, and
will decrease the manual effort and complexities involved in producing
the distribution artifacts. Although we’ve done this before to make
“editions” happen, the intent is to track this multi-team effort more
actively so we can (1) use the time as well as possible, and (2) give
the work maximum transparency.
* * *
The full page is here, with a set of problems, solutions, and actions
proposed. I invite you to take time to read it in detail:
https://fedoraproject.org/wiki/Objectives/Lifecycle/Problem_statements
I also attached that page to the main Lifecycle objective page here,
which was previously approved by the Council:
https://fedoraproject.org/wiki/Objectives/Lifecycle
Rather than try to spin this one email into a thread of doom that
people will give up on reading, I encourage those with feedback to
open a thread for any particular topic. That way the community
discussion should be more useful for all.
I'll collect input and use it both for responses and to help tweak
plans for (hopefully) optimal results. I'm on vacation next week, for
which timing I apologize. But I'll try to look at mail here from time
to time and when I return.
--
Paul

Hi all,
I'm new to the Fedora-project, here is a short introduction. I am a
Clojure/Java developer
residing in Finland and a long time Fedore user, since Fedore Core 5. I
joined the
Fedora project to package Clojure and Java libraries and programs.
I would like to become a owner of a retired package,
clojure-maven-plugin,
and then package libraries (clojure-spec-alpha, clojure-core-specs-alpha
and clojure-pom-contrib) required to update Clojure to the latest
version.
Best regards,
Markku Korkeala

Apparently, the email that I sent (below) was mis-directed. Sorry for
the mistake. I was advised to send this email to you.
--------------------------------------------------------------
I posted a query to https://ask.fedoraproject.en asking how to communicate
a feature request to the Fedora developers. I was told to send this
email. I have included the detailed request as an attachment to this email.
If this email is misdirected, and you want me use an alternate
communication channel, please email me. Also, if you have any questions,
or if anyone wishes to engage me in a challenging discussion, you are also
welcome to email me.
Steve Schooler