From Fedora Project Wiki


Fedora Weekly News Issue 235

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

Announcements from the Fedora Project starts us off, with news on an extension for paper submissions to UTOSC 2010, a reminder about the upcoming Fedora 14 feature freeze next week, and great coverage of various discussion from the Fedora user list. From the Quality Assurance team, coverage of discussion on moving bug reports upstream, results of the first automated Rawhide acceptance testing, and discussion of two alternative ways to cover boot menu functionality in the release criteria. In Translation news, an update on Fedora 14 tasks for the team, details on work on the L10n QA template for F14, and a couple Publican-related items. In Design team news, a new design bounty and details on review of the content and future redesign. Security Advisories completes this issue of FWN with Fedora 12 and 13 security-related patches this past week. Enjoy!

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: Rashadul Islam

Fedora Announcement News

Fedora Board IRC Meeting 1800 UTC 2010-07-16

Paul W. Frields[1] announced[2] on Thursday, July 15, 2010 on 22:07:53 UTC,

" I'm sending this note on behalf of Jared Smith, who is in Chile right now for FUDCon Santiago 2010.

The Board is holding a public IRC meeting on Friday, July 16, 2010 at 1800 UTC on IRC Freenode. The Board is trying an open meeting on IRC, and if they agree it helps conversation work more effectively, it may retain this format. Although there won't be a formal protocol for this initial meeting, all attendees are asked to be courteous to their fellow contributors during the conversation.

For this meeting, the public is invited to simply join #fedora-board-meeting to talk to the Board.

The meeting will last approximately 60 minutes. In response to community inquiries, the meeting will start with a Q&A session. After approximately 40 minutes, depending on how the session is going, Board members may reserve some time for agenda items and questions for the new FPL. Jared will be there provided that Internet connectivity allows. In the event he isn't available, I'll facilitate.

We look forward to seeing you at the meeting!"

UTOSC 2010 Call for papers extended through August 1st!

Clint Savage[1] announced[2] on Tuesday, July 20, 2010 on 20:52:18 UTC,

"Time goes by quickly, so quickly in fact that top priorities get setto the side and suddenly become missed opportunities. Fortunately submitting a proposal for a presentation at the 2010 Utah Open Source Conference doesn’t have to be one of them!

The deadline for paper submission has been extended until August 1st, 2010, just in time to sit down inside a nice cool coffee shop, sip some of the great local roast and think about what to share with the community.

Really it only takes a minute or two to place a submission and you might find it so easy and fun that you submit more then one.

Don’t worry about not having a full presentation prepared, all that needs to be submitted by the deadline is the proposal, a basic outline of what would be presented to the community at the conference. The next step is easy: sit back, relax and wait to hear if your proposal was selected by vote for the conference. Once selected the entire presentation(s) should be laid out and created.

Don’t have anything to talk about? That’s not what I’ve heard!

Topics can be as wide ranging as are the members of the Utah Open Source community at large (and that is pretty gosh darn diverse!) and should include a variety of experience levels. While one presenter may submit a presentation on Building a Better Community Through Statistics another (and an excellent presentation I attended in 2009,) might be Advanced GIMP: The Digital Diet.

So don’t be afraid to submit a proposal to talk about your favorite open source program(s) that just does silly things or maybe does nothing at all!

Has anyone ever submitted a presentation on an open source pet rock? No? Hhmm…

All ideas are welcome, but please remember to keep with the 2010 theme: its better when its free*.

Being free is so easy that my open source pet rock was free!

Interested? Want more details? Visit the Utah Open Source Conference website at [3] and when your ready to submit your proposal simply create an account and visit [4] to submit your paper.

You could put it off again, but then you will have to pay to attend and where’s the fun in that?"

Fedora Development News

Reminder: Fedora 14 Feature Freeze is Next Week (2010-07-27)

John Poelstra[1] announced[2] on Wednesday, July 21 at 04:18:16 UTC 2010,

"It's hard to believe, but the window for full blown feature development closes soon. A friendly reminder that next Tuesday, July 27, 2010 is Feature Freeze for Fedora 14.

Feature Freeze means that all accepted feature for the release are *significantly* "feature complete", ready for testing, and have a current status.

[3] [4]

If you have any questions about what this means, please ask now.

Features which are not significantly feature complete at Feature Freeze will be be allowed to remain on an exception basis by FESCo or deferred to Fedora 15."

Fedora User Announcements

Fedora at South African Software Freedom Day

Neil Thompson on Tuesday, July 20 at 11:12:10 UTC 2010 mentioned[1] "I'm not a Fedora Ambassador or anything, but the folks at my local SFD committee know I use Fedora and were wondering about a Fedora stall at the SFD meeting - [2]

Is there a South African Ambassador? Or does anyone have advice for organising something like this.

Unfortunately, just about everyone at our local LUGS is an UBUNTU fan "

F13 Security Lab

[1]Mentioned by Thom Paine

PostgreSql question

[1] Mentioned by Nermin Celik

F 13 installation trouble

[1]Mentioned by Ankur Sinha

Sun Java double-click interval

[1]Mentioned by Pasan

how to uninstall preload?

[1]Mentioned by Parshwa Murdia

F13: Empathy stop working after 'yum update'

[1]Mentioned by Marco Guazzone

Fedora 13 installation, does not boot

[1]Mentioned by Vincent Onelli

Yum oddness

[1]Mentioned by Patrick O'Callaghan

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 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

Instructions and process for moving bug reports upstream

Ankur Sinha began a discussion[1], [2] on providing instructions for users on the Wiki for reporting bugs to upstream bug trackers. Jóhann Guðmundsson felt that this was the wrong approach[3] and that it should be the responsibility of package maintainers to submit reports upstream when appropriate. In general, though, the group felt that providing instructions for users would be helpful in at least some cases, and Ankur said he would work on a draft of such a page[4].

Rawhide acceptance testing

James Laska reported[1] on the first automated Rawhide acceptance test plan[2] run for Fedora 14, and linked to the full results[3]. The run exposed four bugs, which were significant enough that the test images could not be declared 'last known good'.

Proven testers

Adam Williamson announced[1] that he had updated the Wiki proven testers material, making the main page[2] cover all aspects of the project (based on his previous draft mentioned in last week's issue) and turning the JoinProvenTesters page into a redirect to it. Later in the week he updated the instructions again[3].

AutoQA package acceptance testing

During the QA weekly meeting of 2010-07-12[1], Will Woods explained that the AutoQA team had decided to consider automating the package update acceptance test plan[2] as its highest priority. They felt this would provide a very visible and useful example of the potential of AutoQA as soon as possible. Automated package acceptance testing would prevent packages with certain types of serious problems, such as broken dependencies, from being accepted as updates. Will had identified clear areas of focus which are necessary to implement automated package acceptance testing, and these can be tracked on the AutoQA roadmap[3].

Localization testing

Igor Pires Soares announced[1] that he would be working to update the Fedora 13 localization results template[2] for Fedora 14 use at FUDCon Santiago, and asked for feedback and ideas on improving it. James Laska suggested[3] a page to explain the general testing procedure, and asked where test results are recorded. Igor accepted the general procedure idea, and explained that the template was intended to allow local teams to record results in whatever way they felt most appropriate[4].

Boot menu release criterion proposal

After a contentious first Fedora 14 blocker bug review meeting[1], Adam Williamson proposed two alternative ways to cover boot menu functionality in the release criteria[2]. He suggested either having a basic test of essential functionality (the installer eventually boots without manual interaction) at the Alpha stage and a more advanced test (the graphical boot menu appears as intended) at Beta or Final stage, or simply having the more advanced test at Alpha stage. James Laska[3] and Jesse Keating[4] both came down in favour of simply requiring the menu to work correctly at Alpha stage.


This section covers the news surrounding the Fedora Translation (L10n) Project[1].

Contributing Writer: Runa Bhattacharjee

Fedora 14 Tasks

John Poelstra informed[1] the list about the upcoming tasks for Fedora 14. At present, the translation for the Fedora Guides in the previous release branch is underway.

L10n QA Template

Igor Pires Soares requested[1] for suggestions to put together the L10n QA Template for Fedora 14 during the FUDCon at Santiago. James Laska from Fedora QA Team wanted to know more about the test coverage that was expected for L10n and I18n[2]. Noriko Mizumoto suggested[3] the use of Nitrate and also provided some test cases that could be used to build up the test template. However, Nitrate is not currently available in Fedora and has not been deployed in the Fedora Infrastructure yet[4].

New Module Publican Site_Tech

The 'Site Tech' page that is used in webpages generated by Publican has been in included in, to allow translation submissions[1].

Publican 2 Released

Ruediger Landmann announced[1] the release of Publican 2. this release incorporates the web-publishing component which will allow the use of Publican for the entire process to publish a document from raw XML to a live website. Also included are several bug fixes.

Transifex Mojo

Dimitris Glezos announced the release of Transifex 0.9 (Mojo)[1]. This release includes new features like an Extension Engine, Team Sharing, i18n directory structure in sync with LC_MESSAGES locale standard, Project Widgets for easy depiction of translation statistics, enhanced handling of VCS exceptions, improved project searches etc.

New Members in FLP

Mohammad AlHobayyeb (Arabic)[1] and Takuma Yoshida (Japanese)[2] joined the Fedora Localization Project recently.


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

Contributing Writer: Nicu Buculei

Slide Template Bounty

Máirín Duffy launched a new design bounty on her blog[1] and a new contributor Emily Dirsh applied[2] for the 'ninja' title "I uploaded the template to the wiki. If anyone wants to take a look at the template file and the svg mockup file I used for all the extra graphics, you can get them here" and then followed[3] with an improved version "Based on the feedback I've gotten so far, I worked up a new revision of the slide template." Máirín was happy with the result "" and the announcement is due the next days "If you're happy with the change, let me know because I'd like to announce you as the latest bounty winner sometime this week."

Front Page Redesign

Jef van Schendel created[1] a page reviewing[2] the content of the front page, as part of the on ongoing redesign effort "Everyone's free to track it and change/add/corrent stuff as they like", Paul Frields reminded[3] about the existing design ideas "We should probably be referring back to the mockups Mairin did a while back and revising where necessary to get them more in line with the spins.fp.o design and other recently mocked-up designs" and Máirín Duffy provided[4] fresh mockups. The topic was also discussed in depth at the weekly team IRC meeting[5]

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