This year, the first-ever Fedora Appreciation Week will run from Monday,
November 5th to Sunday, November 11th. Fedora Appreciation Week is an
annual event organized by the Fedora Community Operations (CommOps)
team. It’s a week-long event to celebrate efforts of Fedora Project
contributors and to say “thank you” to each other.
This year, the Appreciation Week runs during the fifteenth anniversary
of the Fedora Project. The Fedora Project has changed in many ways since
2003, but not the importance of our contributor community. This is a
week to celebrate the friends, colleagues, and contributors who are part
of this fifteen-year open source saga. Learn more about the event here.
Justin W. Flory
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com...
Note: Funding is probably available for this event for Fedora related
talks and helpers. Please coordinate with mitzie and/or Mindshare.
Please also distribute this to people and lists which you know would
find it interesting?
The Distributions devroom will take place Sunday 3 February 2019 at
FOSDEM, in Brussels, Belgium at the Université Libre de Bruxelles.
As more and more workloads are being considered for containerization in
the future and are finally landing in virtualized environments today,
distributions remain a critical success factor and are more important
than ever. Containers, like virtual machines, are not magical and
rely on piles of software being assembled in a way that is repeatable,
reliable, and functional. This is at the very heart of the problem that
distributions have always solved.
Each distribution is responsible for building, testing, and releasing
software as well as managing the lifecycle of each application in the
collection. Additionally, distributions do very important work in ensuring
that various versions of upstream software work well together and can
co-exist. Distributions are also, often responsible, for "de-vendoring"
upstream software so that security fixes can be applied more quickly.
We welcome submissions targeted at contributors interested in issues
unique to distributions, especially in the following topics:
# Topics and Areas of Focus
## Focus Areas
- The ways that distribution technologies can be leveraged to allow
for easier creation of a multi-verse of artifacts from single source
trees. This includes the increasing move toward self-contained
applications and providing multiple non-parallel installed versions
- Efforts being made in shared environments around Build/Test/Release
- Topics related to the delivery problem as it impacts updates in
terms of both size and rollback/reliability are expected to be featured.
## Additional Topic Ideas
- Distribution and Community collaborations, eg: how does code flow from
developers to end users across communities, ensuring trust and code
- Automating building software for redistribution to minimize human
involvement, eg: bots that branch and build software, bots that
participate as team members extending human involvement
- Cross-distribution collaboration on common issues, eg: content
distribution, infrastructure, and documentation
- Growing distribution communities, eg: onboarding new users, helping
new contributors learn community values and technology, increasing
contributor technical skills, recognizing and rewarding contribution
- Principals of Rolling Releases, Long Term Supported Releases (LTS),
Feature gated releases, and calendar releases
- Distribution construction, installation, deployment, packaging and
- Balancing new code and active upstreams verus security updates, back
porting and minimization of user breaking changes
- Delivering architecture independent software universally across
architectures within the confines of distribution systems
- Effectively communicating the difference in experience across
architectures for developers, packagers, and users
- Working with vendors and including them in the community
- The future of distributions, emerging trends and evolving user demands
from the idea of a platform
Ideal submissions are actionable and opinionated. Submissions may
be in the form of 25 or 50 minute talks, panel sessions, round-table
discussions, or Birds of a Feather (BoF) sessions.
Submission Deadline: 02-Dec-2018 @ 2359 GMT
Acceptance Notification: 7-Dec-2018
Final Schedule Posted: 14-Dec-2018
How to submit
1.) If you do not have an account, create one here
2.) Click 'Create Event'
3.) Enter your presentation details
4.) Be sure to select the Distributions Devroom track!
What to include
- The title of your submission
- A 1-paragraph Abstract
- A longer description including the benefit of your talk to your target
audience, including a definition of your target audience.
- Approximate length / type of submission (talk, BoF, ...)
- Links to related websites/blogs/talk material (if any)
We will be live-streaming and recording the Distributions Devroom.
Presenting at FOSDEM implies permission to record your session and
distribute the recording afterwards. All videos will be made available
under the standard FOSDEM content license (CC-BY).
If you have any questions, feel free to contact the
devroom organizers: distributions-devroom(a)lists.fosdem.org
Brian Exelbierd (twitter: @bexelbie) and Brian Stinson (twitter:
@bstinsonmhk) for and on behalf of The Distributions Devroom Program
Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com
Fedora Community Action & Impact Coordinator
@bexelbie | http://www.winglemeyer.org
During Fedora Workstation 29 installation there are some banners being
shown like the ones on
In the svg code i see some of the banners are translate into multiple
I would like to translate the banners for a more complete translation of
the installer but where are the instructions/translations?
With RHEL 7.6 out, a new version of Xorg has been delivered, which made xorgxrdp package that I maintain binary incompatible. Given that build overrides are not possible with EPEL (AFAIK), could someone with enough privileges please update the build environment for rhel7.