From Fedora Project Wiki

< FWN‎ | Beats

This is an overview of FWN Beats

Fedora Weekly News : Issue 296

Fedora Project welcomes you to the Fedora Weekly News(FWN): Issue 296[1].

Fedora Project is the right and first place to explore your freedom, friends and features(idea, development, contribution) indeed. You can join your particular interest at any time; meantime if you interested in contributing to Fedora Weekly News, please see our 'join' page[2]. FWN welcome readers feedback:

In this August 2012 Issue, Fedora Project news stream covers the changes to the Packaging Guidelines, FUDCon Paris Updates(October 13-15, 2012), Fedora Infrastructure announces about, new bodhi release in production, build F-18 collection packages for all language translators, and Fedora 18 Alpha to slip by another one week.

The trade press and Fedora Marketing stream covers news of 5 most popular Linux distributions where Fedora has been criticized along with RHEL future, and why Fedora 18 Will Be The Practical Choice For Vanilla Enthusiasts.

FWN Editorial Team: Rashadul Islam, Adam Williamson


Fedora Announcements are the place where you can find the major coverage from the Fedora Project including general announcements[1], development announcements[2] and Fedora Events[3].

Contributing Writer: Rashadul Islam

Breaking News of the Week and Month

[Guidelines Change] Changes to the Packaging Guidelines

  • Contributor: [[User:Spot|Tom Callaway][1]
  • Posted Date: Wed Aug 1 19:28:57 UTC 2012[2]

"A new section has been added to the SysV Initscripts section, discussing the proper use of subsys locking. Even though Fedora packages should no longer be using SysV Initscripts as a primary service mechanism, Red Hat Enterprise Linux and EPEL do. Additionally, Red Hat points partners to the Fedora Guidelines when they build for RHEL. [3]


The review guidelines now reflect the use of sha256sum (instead of md5sum) to confirm upstream source integrity. [4]


The PHP Packaging guidelines have been updated to include guidance about when it is appropriate to have an explicit Requires on httpd & mod_php, how to handle explicit Requires on PHP extensions, and how to handle a Requires for a minimum PHP version. [5] [6] [7]


A new section on Macros has been added to the Packaging Guidelines, covering Packaging of Additional RPM Macros. [8]


A new section on the Documentation= field in systemd unit files (F17+) has been added. [9]


A short section on the Group tag in Fedora packages has been added. All current versions of Fedora (and their respective RPM versions) treat the Group tag as optional. Packages may include a Group: field for compatibility with EPEL, but are not required to do so. [10]


The RHEL conditionalization has been removed from the Python3 example spec file, as it is no longer valid. [11]


These guidelines (and changes) were approved by the Fedora Packaging Committee (FPC).

Many thanks to Remi Collet, David Malcolm, Vit Ondruch, Lennart Poettering, Michael Scherer, Dave Sullivan, and all of the members of the FPC, for assisting in drafting, refining, and passing these guidelines.

As a reminder: The Fedora Packaging Guidelines are living documents! If you find something missing, incorrect, or in need of revision, you can suggest a draft change. The procedure for this is documented here: [12]"

Enclosure: Here is one late change to the Fedora Packaging Guidelines:[13] [14] [15]

FUDCon Paris Updates: Subsidy requests opening, hotel reminders

  • Contributor: Fedora Project Leader-[[User:Rbergero|Robyn Bergeron][1]
  • Posted Date: Fri Aug 3 17:00:53 UTC 2012[2]

"Greetings! (...or perhaps I should say.... bonjour!)

I'd like to share a few reminders and announcements regarding the upcoming FUDCon in Paris, France, on October 13-15, 2012.

If you are planning to attend FUDCon and need a travel subsidy to do so, the ticketing system is now open for those requests. Requests will be accepted through August 15, 2012. Please note that funding requests without a ticket will not be considered. Preference will be given to attendees from the EMEA region who are actively contributing to Fedora, and have detailed their participation plans for FUDCon in their request.

To place a subsidy request, please follow these steps:

1: Pre-register at [3] - and put an X in the $$$ column 2: Read about the funding request process and place a funding request ticket in the FUDCon-planning ticket tracker here: [4]

Additionally, a few notes regarding the hotel in Paris:

There are other events in Paris during this time period; most notably, our first day of FUDCon will be taking place at the Open World Forum conference, on the day in which the public is encouraged to participate in and learn about open source projects. OWF had nearly 2000 attendees last year. Accordingly, rooms might be in short supply as we approach FUDCon; please, book your hotel as soon as possible, not only for affordability purposes, but also so that you have a bed to sleep in. :)

We currently have a rate of EUR81 per night at the ibis Paris La Vilette Cite des Sciencesfor the nights of the 12th, 13th, and 14th of October. However, this rate will expire at the end of August, and any remaining rooms in our block will expire.

For instructions on booking your hotel, please read the Lodging/Hotel section of the FUDCon: Paris wiki: [5]"

Fedora Infrastructure announces

  • Contributor: Fedora Infrastructure Leader-[[User:Kevin|Kevin Fenzi ][1]
  • Posted Date: Thu Aug 30 20:31:24 UTC 2012[2]

"I'm happy to announce the general availability of our site.

This site provides an easy way for Fedora contributors and users to check on the status of services provided by Fedora Infrastructure.

The site auto reloads every minute, and also provides a rss feed at [3].

If you run into a problem or issue that is not reflected at, please do report it to us in #fedora-admin on or via ticket at [4] We update the site status information manually so we need to be aware of the issue in order to keep the site accurate.

As with everything in Fedora Infrastructure, this application is open source. Source is available from: [5] and is released under a GPLv2+ license.

This application is hosted at the link[6] to avoid any issues with outages in our infrastructure affecting status reporting. "

Beats are open!

  • Contributor: Fedora Docs Leader-[[User:Bcotton|Ben Cotton][1]
  • Posted Date: Tue Aug 28 15:35:59 UTC 2012[2]

"The Release Notes beats for Fedora 18 are now open: [3]

If you're looking for a way to dip your toes in the water, so to speak, writing a beat is a great way to get started. If you're a regular, don't forget about the checkBeat program: [4]

As a reminder, the wiki drafts of beats are due on 12 September."

Fedora Development News

The Development Announcement[1] list is intended to be a LOW TRAFFIC announce-only list for Fedora development.

Acceptable Types of Announcements

  • Policy or process changes that affect developers.
  • Infrastructure changes that affect developers.
  • Tools changes that affect developers.
  • Schedule changes
  • Freeze reminders

Unacceptable Types of Announcements

  • Periodic automated reports (violates the INFREQUENT rule)
  • Discussion
  • Anything else not mentioned above

New bodhi release in production

  • Contributor: [[User:Lmacken|Luke Macken ][1]
  • Posted Date: Thu Aug 9 21:53:41 UTC 2012[2]

"A new release of Bodhi has just been deployed to production. [3]

Bugs and enhancement requests can be filed here: [4]

Major changes in bodhi 0.9.2

  • fedmsg support! Bodhi now fires off messages for various events that occur. Join #fedora-fedmsg to see it in action. (Ralph Bean)
  • Re-organized the links on the front page, and link to the new Update Feedback Guidelines
  • The submitter of an update can no longer effect the karma (Till Maas)
  • Fix duplicate status change email notifications. (Till Maas)
  • Mention age of updates in testing digest mails (Till Maas)
  • Support e-mail threading in notification e-mails (Till Maas)
  • Add X-Bodhi mail headers (Till Maas)
  • Gracefully handle private bugs (Cole Robinson)
  • Set the default request for new updates to 'testing' in the web form
  • Fix a bug in our critpath policy that occurs when a critical path update to a pre-release reaches the minimum amount of time in testing, but is unable to push to stable.
  • Fixed the input box alignment in the login box (Kalpa Welivitigoda)

Full list of changes since 0.8.7

Kalpa Welivitigoda (1):

     fixed input box alignment issue in login box #579

Luke Macken (25):

     Convert our tags_url to a byte string before passing it to urlgrabber.
     Add a script to detect when older builds become the 'latest' in stable
     Update our test suite to reproduce ticket [ticket:683]
     Fix a bug in our critpath policy ([ticket:683]).
     Set the default request for new updates to 'testing'
     Clean up EOL buildroot overrides in our rmrelease tool (bz#818617)
     Fix a busted unit test (test_push_EPEL_critpath_before_tested)
     Add pkg_resources __requires__ hacks to bodhi tools to mitigate version


     Handle the case where a release doesn't have any overrides
     Change our X-Bodhi-Update-Release header to use the short name
     Apply a modified patch from Cole Robinson to gracefully handle private bugs (#639605)
     Update our unit tests to assume submitters cannot alter karma
     Merge branch 'bodhi1-fedmsg' into feature/bodhi1-fedmsg
     Merge branch 'feature/bodhi1-fedmsg' into develop
     Fix a typo in the metrics tool
     Fix a typo in the new mail headers
     Re-organize our links, and add one to the new update feedback guidelines
     Clean up stray buildroot overrides
     Version bump for 0.9.2
     Our build script uses bz2
     Merge branch 'release/0.9.2'

Mathieu Bridon (6):

     Have bodhi-init create all the tables
     masher: Fix the comparison
     masher: Reuse variable
     setup: Fix the Turbogears version requirement
     Don't version control auto-generated files
     setup: Add missing dependencies

Ralph Bean (19):

     Sending messages with fedmsg.
     No longer using fedmsg schema/validation.
     fedmsg.ini ->
     More detail in the update.complete message.
     More concise send_message calls.
     Ignore dev db.
     Merge branch 'master' into bodhi1-fedmsg
     Updates for the latest fedmsg.  Getting tests passing.
     Merge branch 'master' into bodhi1-fedmsg
     Ignore mashing fedora file.
     Fixed what I think is a regression in login template.
     Merge branch 'master' into bodhi1-fedmsg
     Update to test fedmsg config.  Work with both tests and under WSGI.
     Version bump for fedmsg in staging.
     Only send the comment with a comment is added, not the whole update.
     Using a "bodhi" user/group for mod_wsgi.
     fedmsg+ssl changes to bodhi.spec.
     Use modern fedmsg config format.
     Disable message signing for bodhi tests.

Till Maas (8):

     Add X-Bodhi mail headers
     Support e-mail threading in notification e-mails
     Mention age of updates in testing digest mails
     Use format string instead of string concatenation
     Import exceptions from sqlite3
     Remove files used by mercurial Change karma from Submitter to 0
     Fix notification on automatic status change"

Build F-18 collection packages for all language translators

  • Contributor: Fedora Infrastructure Leader-[[User:Noriko|Noriko Mizumoto][1]
  • Posted Date: Thu Aug 30 09:17:01 UTC 2012[2]

"Hi Fedora package maintainers

Please build and push your package with latest translation file (e.g. pull from Transifex/Zanata) for L10N QA test BY THIS FRIDAY 2012-08-31. Your packages with latest translation will be composed into test live image on 3-Sep Monday. Then various language translators worldwide will test the image in their own languages. Any issue will be filed as bug. This is only one chance for translators to check and modify Localization quality of your packages by checking UI, and we need your help.

Thank you so much.

noriko Fedora Localization Project"

Fedora 18 Alpha to slip by another one week

  • Contributor: [[User:JaroslavReznik|Jaroslav Reznik][1]
  • Posted Date: Thu Aug 30 23:26:35 UTC 2012[2]

"Today at Go/No-Go meeting it was decided to slip Fedora 18 Alpha release by one week due to remaining open blocker bugs[3] and incomplete test matrices for Alpha [4][5][6]. Meeting's full log is at [7].

As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week.

The next Go/No-Go meeting is on Thursday Sep 06, same place but different time (19:00 UTC, 3 PM EDT, 21:00 CEST

  1. fedora-meeting).

If you have an accepted blocker bug, please try to fix it as soon as possible to help us with Fedora 18 Alpha release!"

Fedora Events

The purpose of Fedora Event is to build a global Fedora events calendar, and to identify responsible Ambassadors for each event. The event page is laid out by quarter and by region. Please maintain the layout, as it is crucial for budget planning and press releases.

Upcoming Events (September 2012 - November 2012)

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

Guideline to write Fedora Press Releases[5]

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.

Fedora Press Releases

Fedora press releases will be found at the link:

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: Jason Brooks

The 5 most popular Linux distributions

"...Fedora clearly has its fans. And, if you work on Red Hat Enterprise Linux (RHEL) development, it's a really wise idea to keep a copy of Fedora on hand so you can see RHEL's future."

The full article is available [1].

Why Fedora 18 Will Be The Practical Choice For Vanilla Enthusiasts

Arnav Kalra posted [1]:

"Fedora 18 (Spherical Cow) and future releases — along with RHEL 7 and future CentOS releases — will be the best way to enjoy a vanilla Gnome 3 experience."

The full article is available [2].

Fedora 18 Linux Set To Package Spherical Cow Load of Features

"The clock is starting to tick down on the Fedora Linux release with the feature freeze now in place. As such, now is as good a time as any to take a look at some of the new features that are likely to land when Fedora 18 goes live at the end of the year."

The full article is available [1].

Fedora 18 schedule slips by a week

"At a go/no-go meeting of the Fedora QA Team, the developers decided to postpone the release of the first Fedora 18 alpha by a week. The team unanimously voted to not go forward with the release because of the relatively large number of blocker bugs that are still unresolved."

The full article is available [1].

Planet Fedora

This is the Planet Fedora section, covering news from[1], a collection of blogs from Fedora users spanning the globe.

Contributing Writer: Joel Braun


FudCon Pune 2011

Kishan Goyal posted on his experience on day 2 at FudCon Pune[1].

Joerg Simon posted pictures[2] of the event.

Izhar Firdaus wrote about his experience[3] at FudCon, as well as some thoughts on the atmosphere of the event.

Suchakra also blogged on Fudcon Pune[4].

Kushal Das posted photos[5] of the event to his blog.

Fedora Community

The release of Fedora 16 has been the main topic of the blogroll recently, and it's fair to say that it's being greeted with open arms by many of the users.

Juanjo Martinez blogged on his first impressions of F16, calling it an "impressive release"[6].


Adam Williamson posted about [7]starting work on Fedora 17, and experimentation with the new kernel in a virtualized environment.


This section covers the news surrounding the Fedora Ambassadors Project[1].

Contributing Writer: Buddhika Kurera and Richard A Vijay
For period of days starting from 21 December 2011 to 31 December 2011 (10hrs GMT+5:30) [2]

Fedora Ambassadors Regional Meeting Minutes

Fedora Ambassadors Regional meeting Page[1]

  • APAC

Meeting minutes for 2011-12-24 [2]

  • EMEA

Meeting minutes for 2011-12-28 [3]

Beat this week

Headlines from mailing lists

  • Fedora Linux Google+ page - Admin access by Mohd Izhar Firdaus Ismail
  • Fedora Ambassadors Welcome Week 51 by Joerg Simon
  • FAmSCo meeting log for 2011-12-21 by Neville
  • APAC Bi-weekly meeting logs 2011-12-24 by Buddhika Kurera
  • About Fedora release dinners after release parties by Truong Anh. Tuan
  • Applying to be a mentor by Truong Anh. Tuan
  • We did some sheer awesomeness for 2011. by David Ramsey
  • REMINDER French Fedora Meeting Today 183UTC #fedora-meeting by Reminder
  • FAmSCo Report: November 2011 by Igor Pires Soares
  • REMINDER: EMEA ambassadors meeting tomorrow 2011-12-28 by Christoph Wickert
  • Fedora 16 Release Party / Tokat Report by Onuralp SEZER
  • Tux workshop, MindSpark 2011, CoEP, Pune, India by Shakthi Kannan
  • Some words about FOSDEM (was: fosdem 2012) by Bert Desmet
  • Survey: Red Hat Certifications/Training for FAms by Uditha Bandara Wijerathna
  • EMEA ambassadors meeting 2011-12-28 minutes by Christoph Wickert
  • FAmSco meeting 2011-12-28 minutes by Christoph Wickert
  • talks for clt by S.Kemter
  • A friendly reminder, the next biweekly APAC meeting is on Saturday, January 07th, 2012 at 04:00 UTC by David Ramsey

Welcome New Ambassadors

On behalf of all our Fedora Community and Ambassadors, We are pleased to Welcome our newly sponsored Ambassador group members: from the USA mentored by Mark Terranova from Brazil mentored by Daniel Bruno from Guatemala mentored by Neville A. Cross

We Congratulate them on their success with mentoring program and wish them all success in their endeavour to help Fedora.

Congrats and Wishes to all New members from Fedora Team.

Summary of traffic on Ambassadors mailing list

  • Fedora Linux Google+ page - Admin access by Mohd Izhar Firdaus Ismail


  • Fedora Ambassadors Welcome Week 51 by Joerg Simon


  • FAmSCo meeting log for 2011-12-21 by Neville[3]
  • APAC Bi-weekly meeting logs 2011-12-24 by Buddhika Kurera[4]
  • About Fedora release dinners after release parties by Truong Anh. Tuan[5]
  • Applying to be a mentor by Truong Anh. Tuan


  • We did some sheer awesomeness for 2011. by David Ramsey


  • REMINDER French Fedora Meeting Today 183UTC #fedora-meeting by Reminder


  • FAmSCo Report: November 2011 by Igor Pires Soares


  • REMINDER: EMEA ambassadors meeting tomorrow 2011-12-28 by Christoph Wickert


  • Fedora 16 Release Party / Tokat Report by Onuralp SEZER


  • Tux workshop, MindSpark 2011, CoEP, Pune, India by Shakthi Kannan


  • Some words about FOSDEM (was: fosdem 2012) by Bert Desmet


  • Survey: Red Hat Certifications/Training for FAms by Uditha Bandara Wijerathna


  • EMEA ambassadors meeting 2011-12-28 minutes by Christoph Wickert


  • FAmSco meeting 2011-12-28 minutes by Christoph Wickert


  • talks for clt by S.Kemter


  • A friendly reminder, the next biweekly APAC meeting is on Saturday, January 07th, 2012 at 04:00 UTC by David Ramsey


FAmSCo Meeting

  • FAmSCo meeting log for 2011-12-21 by Neville


  • FAmSCo Report: November 2011 by Igor Pires Soares


  • FAmSco meeting 2011-12-28 minutes by Christoph Wickert


Events reported on Ambassadors mailing list

  • Fedora 16 Release Party / Tokat Report by Onuralp SEZER


  • Tux workshop, MindSpark 2011, CoEP, Pune, India by Shakthi Kannan


  • Some words about FOSDEM (was: fosdem 2012) by Bert Desmet


  • talks for clt by S.Kemter


Regional Meeting Minutes

  • APAC Bi-weekly meeting logs 2011-12-24 by Buddhika Kurera


  • EMEA ambassadors meeting 2011-12-28 minutes by Christoph Wickert


Meeting Reminders

  • REMINDER French Fedora Meeting Today 183UTC #fedora-meeting by Reminder


  • REMINDER: EMEA ambassadors meeting tomorrow 2011-12-28 by Christoph Wickert


  • A friendly reminder, the next biweekly APAC meeting is on Saturday, January 07th, 2012 at 04:00 UTC by David Ramsey


Campus Ambassadors mailing list-Summary of traffic

No news.



In this section the people, personalities and debates on the @fedora-devel mailing list are summarized.

Contributing Writer: Oisin Feeley

Would You Like to Write This Beat ?

Following this issue (FWN#178) I will, with regret, no longer be covering the @fedora-devel list. If you are interested in writing this weekly summary of the deeds and doings on the list then please contact or Pascal Calarco. A short overview of what you may need to do can be obtained by reading the workflow[1] section of the wiki. The @fedora-news list is also extremely open and helpful. Joining[2] the News Project is quite straightforward.

Is gNaughty a Hot Babe ?

Rahul Sundaram posted[1] the results of a survey conducted, primarily on @fedora-list and on the forums, to discover which non-repository-packaged software Fedora consumers were using.

One interesting point is that CMUCL[2] was revealed[3] to be only available for 32-bit systems. However what got people really excited was[4] Rahul's question about what to do concerning the gNaughty package. Its sole purpose seemed[5] to be downloading pornography. Rahul referenced the hot-babe CPU monitor which enjoyed controversy in Debian packaging circles due to its use of female nudity. Rahul wanted to find out "[...] is this allowed in Fedora?"

Amusingly a good deal of the controversy focused on whether the content was freely redistributable, but a predictable moral angle was raised[6] by Muayyad AlSadi who asked for help in producing a spin which removed content deemed objectionable. Muayyad is a Jordanian developer who has been producing an Arabic-localized Fedora spin named "Ojuba" for some time. Muayyad sought a way to make identifying and tagging packages easier to facilitate this spin. Bill Nottingham was[7] skeptical about the chances of tags keeping meaning unless there was some sort of review board. Equally predictable was[8] the reaction typified by Seth Vidal which resisted any attempt to restrict packages according to standards which had nothing to do with licensing or patent issues. Mathieu Bridon thought[9] that the creation of a wiki-page by Muayyad would allow anyone interested in co-ordinating work on "Inappropriate Content" to just go ahead and do it without dragging in bureaucracy.

Chrome9 Vx800 Graphics Support on LiveUSB

Kristaps Viesalgs asked[1] for help in getting the Fedora Live USB to boot correctly on a machine using a Via Vx800 "Chrome9" GPU. Kristaps had some success with the latest upstream version (from their subversion repository) and asked: "Is there any brutal option how to properly boot X with vesa driver, install Fedora, then make openchrome svn installation? Is Fedora planning to make for VIA graphic chipset autoconfiguration utility?"

Adam Jackson asked[2] for a more specific bug report because the chip should be supported. He preferred not to ship an autoconfiguration utility instead of just getting the driver correct. Similar points were made by Adam Williamson and [[User:|Xavier Bachelot]]. The latter asked[3] any interested developers to help out the openchrome project in both the 2D and 3D(Gallium) sides.

Who Wants a Pony?

Kushal Das promised[1] a pony to anyone that would take the trouble to review[2] one of his packages.

Firestarter Retired as Unportable to PolicyKit

Adam Miller asked[1] whether he should just retire the Firestarter[2] package for which he had recently become the maintainer. His query was based on the recent filing of RFEs to integrate Firestarter with PolicyKit. These suggested to Adam that a large amount of work would be needed due to the lack of any upstream activity for four years and the need to grok PolicyKit.

Following confirmation from Rahul Sundaram and Seth Vidal a decision was made[3] by Adam: "I would honestly rather retire the package than do a WONTFIX, if the project as a whole is going the direction of PolicyKit and upstream is dead then I don't want to keep old and busted cruft around the repositories as Fedora continues to look towards the future."

A further suggestion from "Cry" prompted[4] Adam to start filing RFEs against system-config-firewall for any features present in Firestarter but missing in system-config-firewall.

Russian Fedora ?

When Peter Lemenkov asked[1] about the idea of creating a Fedora Foundation outside of the U.S.A. the usual arguments from the past few years were rehashed. Kevin Kofler gave[2] an able summary why this would still present Red Hat with a problem.

An assertion by [[User:|Alexey Torkhov]] that there existed[3] a Red Hat-sanctioned "RussianFedora" spin which contained mp3 codecs and other material excluded from the actual Fedora Project repositories drew demands for proof from Rahul Sundaram.

Will FESCo Revisit Kmods ?

A discussion of why VirtualBox will not be a feature due to its code not yet heading upstream and consequently remaining as kmods drew a statement of support from Kevin Kofler for reverting the current banning of kmods should he become a FESCo member. Upon request from Richard W.M. Jones for a dispassionate summary of the reasons to avoid kmods drew[1] a concise response from Seth Vidal.

Adam Williamson and Matt Domsch (Dell's DKMS mastermind) kicked[2] some ideas back and forth over the advantages of akmods versus kmods.

Upgrade from Fedora 10 to Rawhide (Fedora 11)

Following a report from Uwe Kiewel that a

yum upgrade

had spewed all sorts of errors the supported methods for upgrades were re-stated[1] by Adam Williamson: "[I]f you talk to the people most involved in implementing it (Seth) and testing it (Will) they will tell you that doing live upgrades via yum can't really ever be 100% safe for various reasons, but preupgrade can get very close and is useful in all the same cases. So their position is, we support preupgrade, we don't support yum. If yum works, great, if it doesn't, you can bug people to fix whatever it stopping it working, but it's not 'required' by any policy or guideline."

Advisory Board

In this section, we cover discussion in Fedora Advisory Board.

Contributing Writer: MichaelLarabel




In this section, we cover the Fedora Documentation Project.

Contributing Writer: Jason Taylor

Fedora Content Management System (CMS)

There has been a need for a CMS within the project and there will soon be a decision made in this regard. Karsten posted[0] the reasoning behind moving to a CMS[1] and the need for people with CMS administration experience to lend a hand.




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

Contributing Writer: Runa Bhattacharjee

Translation Credit Loss Problem Resolved

A major issue related to the loss[1] of Translator Credits in modules submitted via has been resolved by the Transifex development team[2]. The problem had also been escalated to the Fedora Legal team[3][4].

Autotranslate Feature Disabled for Fedora Modules on Transifex

The Autotranslate feature on has been disabled for Fedora modules in view of a possible conflict with the Terms of Usage of the Google Translated API that was being used for the feature[1].

FPCA Signing on

All participants to the Fedora Localization Project are required to sign[1] the Fedora Project Contributor Agreement (FPCA) at in addition to signing it on the Fedora Account System[2]

The last date to sign the FPCA is June 17th 2011

Fedora Documentation and Websites missing for F15

A number of Fedora Documentation modules[1] and Fedora Websites[2] modules were not available for translation for Fedora 15 as they could not be migrated to before the release. However, translation can be continued for some of these modules which are being gradually migrated by the writers to

New Members and Teams in FLP

Cindy Ludwig (German)[1], Hung Tran (Vietnamese)[2], Tarun Kumar (Hindi)[3], Anurag Garg (Hindi)[4], Hugo Jiménez Hernández (Spanish)[5], Goran Rakic (Serbian)[6], Nuno Martins (Portuguese)[7], Ricardo Gyorfy (Brazilian Portuguese)[8], Ivan Pomykacz (Czech) [9], Roman Spirgi (German)[10], Florian Masuth (German)[11] joined the Fedora Localization Project recently.


This section contains the discussion happening on the fedora-infrastructure-list

Contributing Writer: Huzaifa Sidhpurwala

Intrusion update

Mike McGrath sent a link [1] to the list about the intrusion which was sent to the fedora-announce-list earlier.[2]

Mike said that he was waiting to discuss authentication mechanisms for the fedora-servers, Since passwords+ssh keys are not the most secure authentication mechanism. Also it seems that fedora does not have the budget for any RSA token like system for authentication.

There was a lot of discussion on this thread, with various people proposing different authentication mechanisms which could be used.

DennisGilmore started a similar thread about Auth Mechanims[3] on which he discussed using etoken or Yubikey for authentication. It was a two factor authentication and therefore was more secure than passphrase or ssh keys.


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

Contributing Writer: Nicu Buculei

FUDCon T-shirt

Emily Dirsh proposed[1] a T-shirt design for the Tempe FUDCon "It's inspired by the art of the Hohokam who once lived in the area" and after an initial warm receive[2] from Máirín Duffy "Wow that is **gorgeous**, I love it! I would love a shirt with that design in it!" she followed[3] with a couple of variations "Ooh, I love the idea of a navy shirt! Yeah, the advantage to a single-color design is it's very easy to adjust the color." Jef van Schendel also proposed[4] a few remixes "Here's a few quick and dirty stabs at a dark shirt version".

Design Team Blog

Máirín Duffy announced[1] a new communication channel for the team "Thanks to Sijis we now have a team blog!! (Yay!!)" and she invited authors to join "Some members of the design team we couldn't add to the blog because their accounts weren't in the Fedora blogs system. If you'd like to be added, please log in to Fedora blogs to create your account, and let me know you've done it so I can request your account be added."

Daily Package

In this section, we recap the packages that have been highlighted as a Fedora Daily Package.

Contributing Writer: ChrisTyler



Security Week

In this section, we highlight the security stories from the week in Fedora.

Contributing Writer: JoshBressers

Phrack 66

Phrack 66[1] came out this week. If you're not aware, Phrack is the longest running hacker zine, it's impressive that after more than 20 years, it's still going.

Firefox 3.0.11

Yet another security update for Firefox was released, be sure to update, it's important. [2]

Security Advisories

In this section, we cover Security Advisories from fedora-package-announce for the period April 1, 2012 - April 11, 2012.

Contributing Writer: User:Astiando

Fedora 15 Security Advisories

Fedora 16 Security Advisories

Fedora 17 Security Advisories

Events and Meetings

In this section, we cover event reports and meeting summaries from various Projects and SIGs.

Contributing Writer: ThomasChung

Fedora Board Meeting Minutes 2008-04-08

Fedora Community Architecture Meeting 2008-04-07

Fedora Ambassadors Steering Committee Meeting 2008-04-11

Fedora Ambassadors Meeting 2008-MM-DD

Fedora Marketing Meeting 2008-MM-DD

Fedora Documentation Steering Committee Meeting 2008-MM-DD

Fedora Engineering Steering Committee Meeting 2008-04-10

Fedora Infrastructure Meeting 2008-04-10

Fedora Localization/Translation Meeting 2008-MM-DD

Fedora Packaging Committee Meeting 2008-04-08

Fedora Release Engineering Meeting 2008-04-07

Fedora Quality Assurance Meeting 2008-MM-DD

Fedora Bug Zappers Meeting 2008-MM-DD

Fedora SIG EPEL Report Week NN/2008

Fedora SIG KDE Meeting 2008-04-08

Fedora SIG Store Meeting 2008-MM-DD

Fedora SIG Astronomy Meeting 2008-MM-DD

Ask Fedora

In this section, we answer general questions from Fedora community. Send your questions to askfedora AT and Fedora News Team will bring you answers from the Fedora Developers and Contributors to selected number of questions every week as part of our weekly news report. Please indicate if you do not wish your name and/or email address to be published.

Writers: Paul W Frields, Rahul Sundaram

What is the official Fedora policy on Mono?

Arthur Pemberton asked: "Fedora traditionally holds fairly strict guidelines for inclusion of software, and the pursuit of Free Software. As such I consider their decisions on such things to be quite important. With that in mind, I would like to ask: what is the official Fedora policy on Mono? Specifically in terms to its FOSS nature and legality."

Paul W Frields, Fedora Project Leader responds:

Until certain ambiguities such as those concerning Mono's patent licensing and redistribution are resolved, there is no formal policy that I'm aware of. We have concerns which are being researched, and any official policy would likely come through Fedora Legal and the Fedora Engineering Steering Committee. The substitution of Gnote for Tomboy on the Desktop Live image and in the default installation for Fedora 12 reduces package load in the standard Fedora Desktop Live image, but for now Mono remains in the Fedora repositories.