1 Fedora Weekly News Issue 183
1.1.1 Fedora Elections
1.1.2 Upcoming Events
1.2 Planet Fedora
1.3.1 Test Days
1.3.2 Weekly meetings
1.3.3 Test Day survey results
1.4.1 New Request System for the Design Team
1.4.2 A Custom Blog Aggregator
1.5 Security Advisories
1.5.1 Fedora 11 Security Advisories
1.5.2 Fedora 10 Security Advisories
1.5.3 Fedora 9 Security Advisories
-- Fedora Weekly News Issue 183 --
Welcome to Fedora Weekly News Issue 183 for the week ending July 5, 2009.
Here are a few highlights from this week's issue. This week is a lighter issue as many
of our writers are enjoying some vacation. In announcements, news that Josh Boyer has been
appointed to the final Fedora Board seat. From the Fedora Planet, photo collections from
the recent FUDCon Berlin, installing Fedora alongside Vista, and much more. In Quality
Assurance news, details on the upcoming Fit and Finish project focusing on display
configuration, more details on the AutoQA activities with rawhide, bugzappers weekly log,
and more. In Design news, a new ticketed request system for Ambassadors' request to
the design team, and details on a new custom blog aggregator, to create a .planet file
just for the Art team. This week's issue completes with security advisory roundup for
Fedora 9, 10, and 11. Enjoy this week's issue!
If you are interested in contributing to Fedora Weekly News, please see our 'join'
page. We welcome reader feedback:
FWN Editorial Team: Pascal Calarco, Adam Williamson
--- Announcements ---
In this section, we cover announcements from the Fedora Project  .
Contributing Writer: Max Spevack
---- Fedora Elections ----
Last week, we announced that Tom Callaway, Mike McGrath, and Dennis Gilmore were elected
to the Fedora Board.
This week, Paul Frields announced that Josh Boyer had been appointed to fill the final
open Fedora Board seat. Said Frields, "Josh is well known around the Fedora community
for his work with release engineering and many other development-oriented groups, as well
as his past work with FESCo and as a maintainer of Fedora on PPC architecture."
As we reported last week, Bill Nottingham, Seth Vidal, Kevin Fenzi, Kevin Kofler, and
Dennis Gilmore were elected to the Fedora Engineering Steering Committee.
---- Upcoming Events ----
Consider attending or volunteering at an event near you!
North America (NA)
Central & South America (LATAM)
Europe, Middle East, and Africa (EMEA)
India, Asia, Australia (India/APJ)
--- Planet Fedora ---
In this section, we cover the highlights of Planet Fedora - an aggregation of blogs
from Fedora contributors worldwide.
Contributing Writer: Adam Batkin
---- General ----
FUDCon wound to a close, and Nicu Buceli and Joerg Simon posted some goodbye
Daniel Walsh asked (but more importantly, answered) the question "How do I tell if
an access was added in the latest policy release?" using the sesearch and audit2why
tools from SELinux.
Dave Jones suggested that unreleased kernels could use some extra testing love.
"Producing RPM builds of the rawhide kernel for our already released Fedoras...What
I’m toying with doing is some devel kernels for Fedora 11 that are built outside of the
Fedora build system."
John Babich explained how to install Fedora along-side Vista.
Adam Williamson described the new policies around the "severity" and
"priority" fields in Fedora's Bugzilla. Additionally, Adam has been working
"to improve and create pages dedicated to explaining how to debug issues in
particular components, and how to provide appropriate information when filing bugs on
those components" as well as a project called Fit and Finish "to work on the
small details that make a polished desktop experience."
Adam John Miller wrote about Firefox and "The progression of popularity and the
stigma of the Geek." The post covers the evolution of Netscape to Firefox and
today's calls for WebKit everywhere.
Jeroen van Meeuwen proposed that Fedora 12 should be supported with an additional
6-month "Extended Life Cycle" consisting of only security fixes, when the
End-Of-Life policy would otherwise be put into place.
As a special bonus, from elsewhere in the blogosphere, Aaron Seigo (of KDE fame)
described some issues around processes and decision making at freedesktop.org
, and how
they might be overcome (this being a particularly auspicious time with the combined
GUADEC+Akademy Gran Canaria Desktop Summit taking place).
Fit and Finish
--- QualityAssurance ---
In this section, we cover the activities of the QA team.
Contributing Writer: Adam Williamson
---- Test Days ----
There was no Test Day last week.
No Test Day is scheduled on the main track next week. However, the new Fit and Finish
Test Day track will be holding its first event, on display configuration (particularly
multiple displays, and projectors). The Test Day page already includes several test
scenarios, and a live CD for testing will soon be available. The Fit and Finish project is
a great effort to improve the details of the Fedora project, so please show up to support
their first event! The Test Day will be held on 2009-07-07 (Tuesday) in IRC
#fedora-fitandfinish (note this is not the same channel where main track Test Days take
If you would like to propose a main track Test Day for the Fedora 12 cycle, please contact
the QA team via email or IRC, or file a ticket in QA Trac.
---- Weekly meetings ----
The QA group weekly meeting was held on 2009-07-01. The full log is available. James
Laska reported that he had not yet been able to update the QA Goals page, but had
started work on it and hoped to have it complete soon. He noted that he had completed his
survey of feedback on the Test Day review questionnaire.
Will Woods reported that he had added two more test cases to the Rawhide acceptance test
plan, based on suggestions received to the initial plan: post-install networking and
Matthias Clasen reported on the new Fit and Finish project, discussed on mailing lists
under the topic 'raising the bar'. He explained it would be based on a series of
Test Days concentrating on user experience rather than developer-driven
'features', and hoped members of the QA team would come along to help drive
testing. Jóhann Guðmundsson suggested that the Test Day pages should provide more
instructions on what information to include with bug reports for the Fit and Finish
Will Woods gave a quick further update on the status of AutoQA (which includes the rawhide
acceptance testing discussed earlier). He noted that the test plan was complete and seven
of twelve test cases had been written. The next step is to start automating cases, which
is waiting on the packaging of autotest. This is being tracked in a ticket. James Laska
and Jesse Keating are working on this together, and making good progress. Will hopes that
by next week, all test cases will be written and one will be automated. He also noted he
was working on how to allow manual test result reports, as there will inevitably be cases
that cannot be automated.
James Laska reported on behalf of Liam Li, on his draft for a installation test event
SOP. This is intended to document the procedure for running an event where multiple
people work together in real time to test installation. James reported that Liam had
produced an initial draft, and it had been revised with help from Christopher Beland and
Finally, Jóhann Guðmundsson reported on his project to improve the quality and quantity of
information contained in bug reports. He had filed an RFE to improve the interface
of abrt (the automated bug reporting tool). Matthias Clasen suggested asking the Design
team for help in further refining the interface, and James Laska pointed out they had come
up with good suggestions for the SELinux troubleshooting GUI design.
The Bugzappers group weekly meeting was held on 2009-06-30. The full log is
Brennan Ashton reported on the status of the triage metric project. He had got FAS
integration and component grouping implemented, but adding some features requested by
James Laska had caused significant breakage which he was working on.
Niels Haase provided an update on his efforts to update the triage critical component
list. He had written a draft for a list based on the critical path component list
being developed for that proposal, and proposed to add components from this list to the
existing list. The group approved this in principle, but pointed out several
components that should be removed as they do not make sense from the triage perspective,
and also noted that any packages which the components in the list depend on should be
considered for addition as well. Niels promised to provide a list of these dependencies
for the next meeting.
Adam Williamson reported on the project to improve (and create) pages explaining how to
debug problems in particular components, and what information to include when reporting
bugs in these components. This had grown out of Jóhann Guðmundsson's 'improve
reporting' proposal. He encouraged all group members to contribute to the page for
their triage components, and create a page if there is not yet one. The page for X.org
was cited as a good example or template. Niels Haase mentioned a page for
NetworkManager currently in draft status. Adam also mentioned he had received a
proposal from Ubuntu's James Westby for the distributions to work together on
combining their pages of this type, and contributing them to the original upstream
projects. The group agreed this was a good idea in principle and they would wait for
further information from James, relayed via Adam.
Matej Cepl reported that the latest rewrite of the triage team GreaseMonkey script was
nearly complete, and appealed for volunteers to help test it.
Adam Williamson reported that the project to implement use of the severity and priority
fields in Bugzilla was now more or less complete, and asked all triagers if they had not
already to begin assessing the severity of bugs when triaging them. He referred to the
instructions on this in the Triage Guide on how to assign severity appropriately.
The next QA weekly meeting will be held on 2009-07-08 at 1600 UTC in #fedora-meeting, and
the next Bugzappers weekly meeting on 2009-07-07 at 1500 UTC in #fedora-meeting.
---- Test Day survey results ----
James Laska posted a round-up of the results of his survey on the Fedora 11 cycle Test
Days. It provides an overview and summary of the feedback received both publicly and
privately in response to the survey.
--- Artwork ---
In this section, we cover the Fedora Design Team.
Contributing Writer: Nicu Buculei
---- New Request System for the Design Team ----
After Frank Murphy asked on @fedora-design about forwarding design requests and
inquiries from the users list "Occasionnally, the other lists get Q? re . Fedora
provided Image apps\formats. Would it be ok, for me to forward those. Without throwing the
teams work-flow" Máirín Duffy pointed to the new created ticket system "I
created a new ticket type 'materials for ambassadors' in the design-team trac
ticket queue. So please encourage the ambassadors to open up tickets for requests like
these". Ian Weller moved all the existing requests from the old wiki page to
the new system and also a mailing list was created for notifications about tickets.
---- A Custom Blog Aggregator ----
Máirín Duffy raised a call for all the members of the Fedora Design Team owning blogs
to submit their data for a blog aggregation, something that was planned for long time
"We need to put together a .planet file so Seth can create a planet just for our
team. I need your help, though: If you think you should/shouldn't be on this list can
you let me know?" and later she figured out everyone can to it by themselves
"Take the chunk of the planet config that pertains to your blog, and copy it into a
.planet.design file in your home directory on fedorapeople.org". With the help of
Seth Vidal from the Infrastructure Team, the aggregator was put up and running, so
those interested in a Fedora Design Team Planet can read it without much additional
--- Security Advisories ---
In this section, we cover Security Advisories from fedora-package-announce.
Contributing Writer: David Nalley
---- Fedora 11 Security Advisories ----
---- Fedora 10 Security Advisories ----
---- Fedora 9 Security Advisories ----
Note: Fedora 9 is nearing EOL; Per FESCo support for Fedora 9 will be discontinued on July
10th 2009 https://www.redhat.com/archives/fedora-announce-list/2009-June/msg00009.html
-- end FWN 183 --
Pascal Calarco, Fedora Ambassador, Indiana, USA