One of the things I like most about Fedora is the orderly way in which
people are able to move in and out of leadership positions within our
community. Each development cycle, we have a set of elections for the
steering committees and for the Fedora Board. The next election cycle
is nearly upon us, so I'd like to take this opportunity to share the
details of the upcoming elections with you.
As quick reminder, the nomination period for this election cycle will
open on 25 October 2011, and will close promptly on 5 November 2011 at
23:59:59 UTC. The full elections schedule, along with more details
about the elections, can be found at
I strongly encourage you to consider running for an open position in
one of the elections. This is one way to serve your fellow community
members and help move Fedora forward at the same time. Additionally,
I'm looking for a few volunteers to help with the coordination of the
candidate questionnaires and town hall meetings. If you're willing to
help, please let me know.
== Fedora Board ==
This election cycle will fill two elected seats for the Board (seats
E1 and E2). Prior to the election I will also announce the first of
two appointed seat in this cycle (seats A1 and A2), with the second
appointment announcement to follow after the election. For more
information on nominations, and the process refer to:
== FESCo ==
This cycle will also see four candidates elected to open seats in the
Fedora Engineering Steering Committee. For information on the
nominations and elections:
== FAmSCo ==
This election cycle will also see candidates elected to fill all all
seven seats on the Fedora Ambassadors Steering Committee. For more
information, refer to:
== Candidate Questionnaire and Town Hall meetings ==
Additionally, the nomination period also serves as the time for the
community to present questions to be posed to candidates. If you wish
to ask questions to be answered by candidates, you can add them at
will have the questions posed to them and responses made available to
the community before the voting period begins.
As we get closer to the elections, we will try to schedule several
Town Hall Meetings in IRC to help you get to know the candidates
better, and to ask them additional questions.
As always, I'm thankful to those who have given their time, talents,
and abilities to serve the Fedora community.
Fedora Project Leader
Greetings, FUDCon friends, near and far:
As you are probably aware, the 2012 North American FUDCon will be held
in Blacksburg, Virginia, on the campus of Virginia Tech. If you are
planning on attending, it's never too early to pre-register, and to
start thinking about your travel plans. FUDCon Blacksburg will take
place January 13-15, 2012.
I'm happy to announce that we are officially accepting subsidy requests
for travel to Blacksburg. If you are requesting a subsidy, we just have
a few steps that we ask you to follow:
1: Register on the FUDCon: Blacksburg wiki page in the pre-registration
2: Put an X in the $$$ column.
3: Create a funding request ticket in the FUDCon trac at:
General information about being sponsored can be found at
Requests are processed in a first-come, first-served manner, though
generally prioritization is giving to local travel over international
travel first. Requests will be reviewed by fellow Fedora community
members at FUDCon subsidy request meetings over the next few weeks.
The first subsidy meeting will take place on Wednesday, November 9th.
The time and IRC channel will be announced as we approach that day.
As always, participation both in planning as well as subsidy granting is
ALWAYS welcome. Please join us on the fudcon-planning mailing list for
information about meetings, as well as for general FUDCon updates, and
see the "meetings" section of your FUDCon's wiki page for meeting
FUDCon Blacksburg Meetings:
Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30
All existing users of the Fedora Account System (FAS) at
https://admin.fedoraproject.org/accounts are required to change their
password and upload a NEW ssh public key before 2011-11-30.
Failure to do so may result in your account being marked inactive.
Passwords changed and NEW ssh public keys uploaded after 2011-10-10
will meet this requirement.
Backgound and reasoning:
This change event has NOT been triggered by any specific compromise or
vulnerability in Fedora Infrastructure. Rather, we believe, due to the
large number of high profile sites with security breaches in recent
months, that this is a great time for all Fedora contributors and users
to review their security settings and move to "best practices" on their
machines. Additionally, we are putting in place new rules for passwords
to make them harder to guess.
New Password Rules:
* Nine or more characters with lower and upper case letters, digits and
* Ten or more characters with lower and upper case letters and digits.
* Twelve or more characters with lower case letters and digits
* Twenty or more characters with all lower case letters.
* No maximum length.
Some Do's and Don'ts:
* NEVER store your ssh private key on a shared or public system.
* ALWAYS use a strong passphrase on your ssh key.
* If you must store passwords, use an application specifically for this
purpose like revelation, gnome-keyring, seahorse, or keepassx.
* Regularly apply your operating system's security related updates.
* Only use ssh agent forwarding when needed ( .ssh/config:
* DO verify ssh host keys via dnssec protected dns. ( .ssh/config:
* DO consider a seperate ssh key for Fedora Infrastructure.
* Work with and use security features like SELinux and iptables.
* Review the Community Standard Infrastructure security document (link
Q: My password and ssh private key are fine and secure!
Can't I just skip this change?
No. We believe the new guidelines above provide an added measure of
security compared to the previous requirements. We want all users of
our infrastructure to follow the new guidelines to improve one aspect
of security across the systems they share. Awareness is also an
aspect of good security. By requiring these changes, we also hope to
maintain and improve awareness of the process for changing passwords
Q: Can I just change my password and re-upload my same ssh public key?
Or upload a bogus ssh public key and then re-upload my old one?
A: No. We've installed safeguards to ensure that your new ssh public
key is different from your old one. Additionally, some of our
contributors may have had accounts on compromised high profile Linux
sites recently, and we want to make sure no ssh private keys or
passwords used in Fedora Infrastructure were obtained via those
Q: This is a hassle. How often is this going to happen?
A: The last mass password change in Fedora was more than 3 years ago.
Absent a triggering event, these mass changes will be infrequent.
Q: The new password length requirements/rules are too strict.
How will I remember passwords that are that long?
A: You can employ a password storage application (see above), or
use a method like diceware (see below), or construct a memorable
sentence or phrase.
Q: How do I generate a new ssh key? How do I use it for just Fedora
A: See http://fedoraproject.org/wiki/Cryptography and use a
~/.ssh/config file to match fedoraproject.org hosts for that key.
Q: I never uploaded a ssh key to the Fedora Account System, nor am I
in a group that needs one, do I still have to upload a new one?
A: No. If you don't have a ssh public key uploaded or desire to do so,
you can just change your password.
The voting has concluded for the Fedora 16 release name, and the
results are in! Thank you to the Fedora community members who made
name suggestions and participated in the voting.
The Fedora 16 release name is: Beefy Miracle
Voting period: Tuesday 2011-11-04 00:00:00 UTC to Monday 2011-10-10
Number of valid ballots cast: 292
Using the range voting method, each release name candidate could
attain a maximum of (292*8) = 2336 votes.
Votes :: Name
1182 :: Beefy Miracle
1035 :: Liege
881 :: Never
791 :: Gernsback
641 :: Rocky Ripple
628 :: Alpharabius
550 :: Panguipulli
505 :: Tubeteika
Fedora Project Leader
Mark your calendars, and get ready to go exploring: The release of
Fedora 16, codenamed "Verne," is scheduled for release in early
November. Fedora is the leading edge, free and open source operating
system that continues to bring everyone fresh, innovative features
with each release, delighting users worldwide every six months.
We are proud to announce the availability of the Beta release of Fedora 16.
Come see why we love Fedora so much. We are betting you will, too.
Download it now:
== What is the Beta Release? ==
The Beta release is the last important milestone of Fedora 16. Only
critical bug fixes will be pushed as updates leading to the general
release of Fedora 16 in early November. We invite you to join us in
making Fedora 16 a solid release by downloading, testing, and
providing your valuable feedback.
Of course, this is a beta release, meaning that some problems may
still be lurking. A list of the problems we already know about is
found at the Common F16 bugs page, seen here:
== Features ==
This release of Fedora includes a variety of features both over and
under the hood that show off the power and flexibility of the
advancing state of free software. Examples include:
* System Boot. Fedora 16 introduces GRUB2, the long-awaited
next-generation boot-loader for Linux. GRUB2 automatically recognizes
other operating systems, supports LVM2 and LUKS partitions, and is
more customizable than the previous version. In this release, only x86
systems with a BIOS uses GRUB2 by default. Work is ongoing for making
GRUB2 the default for other architectures and systems.
* Services Management. Fedora 15 introduced the Systemd services
management program. This release features better integration of
Systemd via conversion to native systemd services from legacy init
scripts in many software components -- for desktop users, this means
faster boot times; for system administrators it means more powerful
management of services.
* Desktop Updates. The two major desktop environments have been
updated to the latest releases: KDE Software Compilation 4.7 and GNOME
3.1 development release.
* SELinux Enhancements. SELinux policy package now includes a
pre-built policy that will only rebuild policy if any customizations
have been made. A sample test run shows 4 times speedup on installing
the package from 48 Seconds to 12 Seconds and max memory usage from
38M to 6M. In addition to that, SELinux file name transition allows
better policy management. For instance, policy writers can take
advantage of this and write a policy rule that states, if a SELinux
unconfined process creates a file named resolv.conf in a directory
labelled etc_t, the file should get labeled appropriately. This
results is less chances of mislabeled files. Also, from this release
onwards, selinuxfs is mounted at /sys/fs/selinux instead of in
/selinux. All the affected components including anaconda, dracut,
livecd-tools and policycoreutils have been modified to work with this
* System Accounts. Fedora now standardizes on login.defs as
authority for UID/GID space allocation, and has moved boundary between
system and user accounts from 500 to 1000 to match conventions
followed by several other Linux distributions. Upgrading from a
existing release will not be affected by this change and you can use
kickstart to override this change during installation if necessary.
* HAL Removal. HAL, a hardware abstraction layer which has been a
deprecated component for several releases, has been completely removed
from all Fedora spins and DVD. Software components using HAL have
moved over to using udisks and upower as well as libudev for device
discovery. This results in faster system bootup and faster startup for
applications depending on device discovery.
* Cloud Updates. Fedora now includes a number of new and improved
features to support cloud computing, including HekaFS, a "cloud ready"
version of GlusterFS, including additional auth*/crypto/multi-tenancy;
pacemaker-cloud, application service high availability in a cloud
environment; and IaaS implementations such as Aeolus and OpenStack.
* Virtualization. Once again Fedora raises the bar on
virtualization support, including expanded virtual network support, an
improved Spice for managing virtual machines, restored Xen support, a
new virtual machine lock manager, and improved ability to browse guest
* Developer Improvements. Developers get many goodies with Verne,
including updated Ada, Haskell and Perl environments, a new Python
plugin for GCC and a number of new and improved APIs.
And that's only the beginning. A more complete list and details of all
the new features in Fedora 16 is available here:
We have nightly composes of alternate spins available here:
== Contributing to Fedora ==
For more information on common and known bugs, tips on how to report
bugs, and the official release schedule, please refer to the release
There are many ways to contribute beyond bug reporting. You can help
translate software and content, test and give feedback on software
updates, write and edit documentation, help with all sorts of
promotional activities, and package free software for use by millions
of Fedora users worldwide. To get started, visit
The election for the Fedora 17 release name is about to begin. The
Fedora community has submitted quite a few suggestions for the Fedora
17 release name, and that list has been narrowed down to the final
eight potential names. In a couple of hours, the election will begin
and you'll be able to vote on these names and assist in the final
selection for the successor to Fedora 16 ("Verne").
This vote begins 4 October 2011 and runs until 10 October 2011 at
23:59:59 UTC. Other important facts:
* We are using the Range Voting method
* Ballots may be cast on the Fedora Elections System at
* If this is the first time you've used the voting system, you might
want to read the Fedora Elections Guide, currently located at
* In order to vote, you must have a valid Fedora Project Contributor
Agreement (FPCA) on file and be a member of at least one non-CLA
Please don't hesitate to log in at
https://admin.fedoraproject.org/voting/about/relnamef17 and vote for
your favorite names today.
Thank you to everyone who helped by contributing names for
consideration and reviewing the names for the final ballot.
Fedora Project Leader