From Fedora Project Wiki


Fedora Weekly News Issue 234

Welcome to Fedora Weekly News Issue 234[1] for the week ending July 14, 2010. What follows are some highlights from this issue.

Our issue starts with announcements from the Fedora Project, including several development announcements and word of another Fedora community gaming session this weekend! In Marketing news, some discussion on the OLPC software strategy, work on finding a new name for Fedora Buzz, and MeeGo Community Metrics. In Fedora In The News, details on some recent Fedora podcasts of interviews with Fedora contributors, and a couple articles from the past week from the trade press. In news from our QA Team, an update on the Proven Testers work that they have been working on the past few weeks, a guide to creating music with Fedora, and a plan to expand desktop validation testing during the Fedora 14 cycle. The Artwork Team brings us news on the Fedora 14 artwork efforts, testing the new Fedora branding Fonts recently developed, and a mockup for the new local communities landing page. Our issue wraps up with security advisories released over the past week. Read on!

The audio version of FWN - FAWN - is back! You can listen to existing issues[2] on the Internet Archive. If anyone is interested in helping spread the load of FAWN production, please contact us!

If you are interested in contributing to Fedora Weekly News, please see our 'join' page[3]. We welcome reader feedback:

FWN Editorial Team: Pascal Calarco, Adam Williamson


In this section, we cover announcements from the Fedora Project, including general announcements[1], development announcements[2] and Events[3].

Contributing Writer: Pascal Calarco

Fedora Development News

Outage: Koji upgrade/migration - 2010-07-09 22:00 UTC

Dennis Gilmore announced[1]:

"There will be an outage starting at 2010-07-09 22:00 UTC, which will last approximately 48 hours.

To convert UTC to your local time, take a look at[2] or run:

date -d '2010-07-09 22:00 UTC'

Reason for outage:

Migrating the underling storage used by koji. as well as upgrading to koji 1.4.0

Affected Services:

Buildsystem -

Unaffected Services:

BFO - Bodhi - CVS / Source Control DNS -, Docs - Email system Fedora Account System - Fedora Community - Fedora Hosted - Fedora People - Fedora Talk - Main Website - Mirror List - Mirror Manager - Package Database - Smolt - Spins - Start - Torrent - Translation Services - Wiki -

Ticket Link[3]

Contact Information:

Please join #fedora-admin in or respond to this email to track the status of this outage."

REMINDER: Test machine resources for package maintainers

Kevin Fenzi reminded[1] the community of the availability of test machine resources for package maintainers:


I'd like to remind package maintainers that there are some test machine resources they can use to help them in maintaining Fedora packages.

See[2] for more information and FAQ.

Recent changes include:

- I have added a RHEL6b2 test machine. This may help EPEL-6 maintainers check for packages or test/debug their packages.

- EOL Fedora release test machines have been taken down, but I still have the disk images, etc. If anyone needs some information about a

 F9, F10, F11 machine, contact me and I will try and bring up the instance for you to use on a temporary basis. 

Please see the above page or contact me directly for any more information.

Happy maintaining!


Fedora 14 Feature Submission deadline is tomorrow (2010-07-13)

John Poelstra reminded[1] the community of the July 13 deadline for features for Fedora 14:

"The Fedora 14 Feature Submission Deadline is TOMORROW. After tomorrow, newly submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo.

Accepted Fedora 14 features so far[2].

Thank you, John

More information:

  Fedora 14 Schedule:
  Fedora Feature Process:

Meeting logs enhancement

Kevin Fenzi announced[1]:


Thanks to some scripting work from Mike Mcgrath, there's a enhancement to our meeting logs site available:

You can now go to[2] and see a per directory listing of meetings grouped by their meeting name. This would allow you for instance to see all the fesco meeting logs and browse them at your leisure, without having to find the right dates for meeting by going to:[3]

It's important that people running IRC meetings use the '#meetingname' command to name their meeting, and always keep the same name there so the logs appear under the same team name moving forward.

Hopefully this helps people find and review logs of our meetings.


Upcoming Bugzilla Changes: Rawhide Rebase

Jeff Raber announced[1]:


I hope everyone is well. This e-mail is intended to inform you about the upcoming bugzilla changes happening around July 27, 2010 (Rawhide bug rebase) and what you need to do, if anything.

We will be automatically changing the version for most rawhide bugs to Fedora 14. This will result in regular bugs reported against rawhide during the Fedora 14 development cycle being changed to version ‘14' instead of their current assignment, ‘rawhide’. This is to align with the branching of Fedora 14 from rawhide and to more accurately tell where in the lineage of releases the bug was last reported.

Note that this procedure does not apply to bugs that are open for the ‘Package Review’ component or bugs that have the FutureFeature or Tracking keywords set. They will stay open as rawhide bugs indefinitely.

If you do not want your bugs changed to version ‘14‘, add the FutureFeature keyword. If you need help changing a large amount of bugs manually, we’d be glad to help. Stop by #fedora-bugzappers on and we’ll gladly help you.

More about these processes is here[2]

Jeff Raber

Fedora Bugzappers volunteer triage team[3]"

Fedora User Announcements

Community gaming Saturday - Session 6 - Wesnoth

Bruno Wolff III announced[1]:

"There will be another Fedora Community Gaming session this weekend. We will be playing Wesnoth which is a turn based fantasy strategy game.

We will be starting at: UTC: 1700 Saturday July 17, 2010 EDT: 1pm Saturday July 17, 2010

We need people on time for this one as adding people late is difficult.

We'll meet up in #fedora-games. We'll use the Wesnoth lobby to set up the game once we see whose playing. Fedora Talk will be available (x2010) for people that want to try it.

It's not that hard to play for new players.

We'll either play team vs team or team vs AI depending on what people want to do. We'll play on a small map so we can finish in less than 2 hours. (I'll move faster this time, I promise.)

We will be using the 1.8 version. People running F12 well need to install a scratch build[2] or perhaps run an F13 live games image for the session.

A bit more information is at[3]

Fedora Events

Fedora events are the exclusive and source of marketing, learning and meeting all the fellow community people around you. So, please mark your agenda with the following events to consider attending or volunteering near you!

Upcoming Events (June 2010 - August 2010)

  • North America (NA)[1]
  • Central & South America (LATAM) [2]
  • Europe, Middle East, and Africa (EMEA)[3]
  • India, Asia, Australia (India/APJ)[4]

Past Events

Archive of Past Fedora Events[1]

Additional information

  • Reimbursements -- reimbursement guidelines.
  • Budget -- budget for the current quarter (as distributed by FAMSCo).
  • Sponsorship -- how decisions are made to subsidize travel by community members.
  • Organization -- event organization, budget information, and regional responsibility.
  • Event reports -- guidelines and suggestions.
  • LinuxEvents -- a collection of calendars of Linux events.


In this section, we cover the happenings for Fedora Marketing Project from 2010-07-07 to 2010-07-13.

Contributing Writer: Neville A. Cross

OLPC Software Strategy

Peter shared[1] a message about OLPC software strategy which confirm ongoing collaboration, specially deploying fedora on a secondary architecture.

A New Name for Fedora Buzz

Luke Slater started[2] brain storming about a new name for Fedora Fuzz[3]. This will be a way to feedback and monitor social networks. Robin Bergeron[4] proposed Hive. Jef van Schendel[5] liked things related to earthquakes and climate. On his side Stephen John Smoogen[6] liked things related with coffee. There was more ideas posted on the wiki.[7]

Carl Gaudreault took the buzz idea one step forward[8], looking to what kind of information we will like to gather for Fedora.

MeeGo Community Metrics

Mel Chua shared [9] a link to MeeGo community metrics. A good text to look at for think about how we will like to expand our own metrics.

Marketing Meeting Minutes 2010-07-13

Sweet MMM (Marketing Meeting Minutes)[10] from July 13th are as usual available to public. There is a review of marketing weekly meeting schedule. You can view the details on Mel Chua's mail[11]

Fedora In the News

In this section, we cover news from the trade press and elsewhere that is re-posted to the Fedora Marketing list[1]

Contributing Writer: Pascal Calarco

Continuing from the recent announcement of new Fedora Project Leader, Jared Smith, this past week saw one more story in the trade press on this. from PC World.

This Week In Fedora Podcasts (Frostbite Media)

Neville A. Cross forwarded[1] a brief posting about the latest interview with him on This Week in Fedora.

Previous podcasts include interviews with Fedora Community Gardener, Karsten Wade, Fedora Design Team lead Máirín Duffy and past Fedora Project Leader, Paul W. Frields.

This and previous interview podcasts are available[2]

10 things that will make you want to use Fedora again (TechRepublic)

Rahul Sundaram forwarded[1] a posting overviewing "top ten" reasons why users should give Fedora 13 a try.

"I will confess that I jumped off the Fedora Linux boat somewhere around Fedora 9. It just seemed the distribution that served as a testing ground for Red Hat Enterprise Linux was too much work to get stable and too prone to falling to pieces. That was then; this is now. Fedora 13 was just released, and I am here to tell you it’s a completely different ball game. Fedora 13 is solid… rock solid. So much so, it has made me a believer in the Hat once again. Here are some of the reasons I think you too will find Fedora 13 ready for your service now."

The full post is available[2].

Open source alternative for Active Directory (ZDNet UK)

Jonathan Nalley forwarded[1] a brief posting about ZDNet UK's mention of the 389 Directory server in Fedora:

"the open source community responded with a product that is full featured, and very powerful. It's currently called the "389 Directory Server", and is developed as part of the Fedora Project (Red Hat's free Linux operating system)."

The full post is available[2].


In this section, we cover the activities of the QA team[1]. For more information on the work of the QA team and how you can get involved, see the Joining page[2].

Contributing Writer: Adam Williamson

Proven testers

The proven testers project was well underway, with most of the mentor requests being handled and many group members actively posting feedback. Aaron Farnes proposed[1] a substantial revision to the wiki page[2] which would incorporate information on joining the group (which was a separate page) and on the mentoring process (which was not yet documented), as well as rewriting the testing instructions. John Dulaney liked it[3], as did James Laska[4]. Adam Williamson thought it was well laid out, but too wordy and too far abstracted to work as a clear set of instructions for prospective proven testers[5]. Later, he posted[6] an alternative draft[7] which made fewer changes from the existing page, adding in information on joining the group and on the mentoring process with minimal disruption to the existing content. Aaron liked it[8].

Mike Cloaked generally liked Aaron's draft[9], but raised a question around kernel testing, and whether it was entirely safe for a single proven tester to 'approve' a kernel update when it was unlikely any single tester could come close to comprehensively testing a kernel. Adam thought[10] that generally proven testers should approve updates which do not break critical path functions for them, but that it might make sense to develop a different policy for the kernel. Rick Stevens suggested requiring positive karma for each specific bug fix[11], but Adam explained that this was impossible under the current Bodhi system[12].

Adam Miller proposed two alternatives[13] for sponsoring new proven testers - either having the whole group vote on proven tester candidates at weekly meetings, or allowing mentors to sponsor candidates when the mentor believes the candidate is ready. Adam Williamson was firmly in favour of the more liberal option[14], and with no disagreement, Adam Miller said he would go ahead and update the documentation to reflect this process[15]. James Laska suggested holding the voting process in reserve in case a need to vet candidates more extensively transpired in future[16].

Musician's guide testing

Christopher Antila wrote to let the group know[1] that the Docs SIG had been working on a guide to creating music with Fedora[2]. He asked for help checking the consistency and language in the guide, and also for testers to try and follow the guide and provide feedback on whether it comprehensively covered the necessary information.

Installation validation test matrix update

In the Trac ticket[1], Rui He reported that she had made considerable progress on re-designing the installation validation test matrix[2], including re-organizing the tests into categories and making the matrices for each category collapsible and re-orderable. James Laska thought the changes looked very good.

Desktop validation testing expansion

Adam Williamson announced[1] a plan to expand desktop validation testing during the Fedora 14 cycle to the Xfce, LXDE and KDE desktops, as well as the default GNOME desktop. He explained that, on an experimental basis, the desktop validation test suite would have to be run against each desktop at each release validation test point, and any release criteria-breaking failure in any desktop would need to be fixed before the release could be made. He noted that he had contacted the leaders of the various desktop SIGs, and they were enthusiastic about the idea. John Dulaney asked[2] whether ISOs would be available for each desktop. Adam explained[3] that each desktop can be installed from the DVD image, and that the automated nightly builds could also be used for testing.


At the QA meeting, Will Woods reported that the AutoQA team was working on a helloworld test (a test test), which would exist to check that watchers and hooks - particularly the bodhi watcher and hook - work correctly. This is a prerequisite for the dependency check test, one of the major AutoQA priorities. Josef Skladanka said he had a test instance of the ResultsDB up and running on one of AutoQA's infrastructure machines, and had rewritten the initscripts and rpmlint tests to store their results in the database. He would continue to work on converting other tests. Kamil Paral announced that he had patched autoqa to use autotest labels correctly, which allows us to configure the actual running of tests in several ways - ensuring they are run on particular machine configurations. He pointed to a mailing list post[1] with a more detailed explanation.

Triage metrics

At the Bugzappers weekly meeting of 2010-07-06[1], Jeff Raber updated his progress with triage metrics. He had been updating the wiki page on his work[2], and working on a patch to python-bugzilla to allow querying bug history data, which is required for some of the planned metrics. Adam Williamson said he would try to take the metrics Jeff had already implemented and work them into a prototype weekly update email format to send to the list for feedback.


In this section, we cover the Fedora Design Team[1].

Contributing Writer: Nicu Buculei

Fedora 14 Artwork

After in the previous week the team decided on the graphic concept to be used for Fedora 14, now is the time to gather feedback and ensure the theme is developed openly and with input from the entire community. For this Kyle Baker created[1] a wiki page[2] to collect it and Máirín Duffy wrote a blog post[3] on the topic. Everyone is invited to comment and spread the word, the deadline for Alpha is 2 weeks away.

Also in Fedora 14 related news, the Design Team is calling for contributions[4] with the supplemental wallpapers[5] where everyone is invited tu submit freely licensed images (CC-BY or CC-BY-SA) and the team will make a selection for inclusion in the distro.

Testing the new Fedora Branding Fonts

The Design Team is testing a new selection of branding fonts[1], Comfortaa as title font instead of MgOpen Modata and Cantarell or Droid Sans as body font, for this the current Bi-Weekly Design Bounty[2] will use those fonts. Also Ryan Lerch[3][4] and Ian Weller[5] wrote blog posts, informing ans asking for feedback about this trial.

Design for the Local Communities Website

Máirín Duffy posted[1] a mockup for the new local communities landing page[2] "So Sijis converted it to the grid we've been looking at using for the upcoming new www.fpo" and Jef van Schendel proposed[3] the use of flags "Maybe flags would be less trouble + take up less space + be clearer." Máirín forwarded the question to the Advisory Board[4] together with Jef's mockup where the general opinion[5] was contrary to such use "Lets avoid the flags, shall we?"

Security Advisories

In this section, we cover Security Advisories from fedora-package-announce.

Contributing Writer: Pascal Calarco

Fedora 13 Security Advisories

Fedora 12 Security Advisories