Fedora Weekly News 282

Pascal V. Calarco pcalarco at nd.edu
Fri Jul 22 16:27:57 UTC 2011

     1 Fedora Weekly News Issue 282
         1.1 Announcements
             1.1.1 Fedora Announcements
        Changes to the Packaging Guidelines
             1.1.2 Fedora Development News
        Call for Test Days for Fedora 16
             1.1.3 Fedora Events
        Upcoming Events (June - August 2011)
        Past Events
        Additional information
         1.2 Fedora In the News
             1.2.1 Fedora 16 planned to come with Systemd and Btrfs as 
default (German)
             1.2.2 The Five Best Linux Netbook Distributions: 2011 Edition
         1.3 Ambassadors
             1.3.1 Beat this week
             1.3.2 Welcome New Ambassadors
             1.3.3 Summary of traffic on Ambassadors mailing list
             1.3.4 FAmSCo Meeting
             1.3.5 Events reported on Ambassadors mailing list
             1.3.6 Campus Ambassadors mailing list-Summary of traffic
         1.4 QualityAssurance
             1.4.1 Test Days
             1.4.2 Release criteria and validation testing
             1.4.3 Separation of release validation and feature processes
             1.4.4 Shortening blocker bug review meetings
             1.4.5 QA group meeting SOP
             1.4.6 AutoQA
         1.5 Security Advisories
             1.5.1 Fedora 15 Security Advisories
             1.5.2 Fedora 14 Security Advisories

- Fedora Weekly News Issue 282 -

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

In this week's issue, we begin with changes in packaging guidelines and 
a call for Fedora 16 Test Days in Announcements. Fedora In The News 
offers two pointers to articles about Fedora, including a German Fedora 
16 preview and Linux.com's Top 5 distros of 2011. In Ambassador news 
this week, news from EMEA and APAC Ambassadors, planning for FUDCon 
Pune, India and FAmSCo updates. In Quality Assurance news, draft 
standard operating procedures for QA meetings, validation testing 
updates and more. FWN 282 finishes off this week with a few security 
advisories released for Fedora 14 and 15. Enjoy!

An audio version of some issues of FWN - FAWN - are available! 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: news at lists.fedoraproject.org

FWN Editorial Team: Pascal Calarco, Adam Williamson

     * http://fedoraproject.org/wiki/FWN/Issue282
     * http://www.archive.org/search.php?query=subject%3A%22FWN%22
     * http://fedoraproject.org/wiki/NewsProject/Join

-- Announcements --

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

Contributing Writer: Pascal Calarco

     * http://lists.fedoraproject.org/pipermail/announce/
     * http://lists.fedoraproject.org/pipermail/devel-announce/
     * http://fedoraproject.org/wiki/Events

--- Fedora Announcements ---

---- Changes to the Packaging Guidelines ----

Tom Callaway announced[1]:

"Here are the latest changes to the Fedora Packaging Guidelines:


Some rpm versions pass pathnames to the automatic filtering macros, so a 
section has been added to the guidelines to help packagers deal with it[2]


For a while, Fedora considered mono packages to be 
architecture-specific, and installed assemblies to %{_libdir}. However, 
after discussions with upstream, we now consider mono packages to be 
architecture (and platform) independent. This means that mono packages 
should be correctly installed into the GAC in /usr/lib or installed into 

As a notable exception, any ELF binary libraries generated in a mono 
package must be correctly installed into %{_libdir}, because these files 
are architecture-specific.

Also, even though we consider mono packages to be architecture 
independent, they must not be marked as "noarch". Although the 
assemblies are the same, the files may differ due to strings referring 
to the build architecture.[3]


It was decided that gnome shell extension packages should have the 
prefix gnome-shell-extension (with no "s" on the end).[4]


The section in the Fedora Packaging Guidelines concerning libexecdir has 
been improved and expanded[5].


The Fedora Java Packaging Guidelines have been updated to reflect the 
latest macros for Maven 3.[6]


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

Many thanks to Christian Krause, Aleksandar Kurtakov, Petr Pisar, 
Stanislav Ochotnicky, 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[7].



     * https://fedoraproject.org/wiki/Packaging:Mono#File_Locations
     * https://fedoraproject.org/wiki/Packaging:Guidelines#Libexecdir
     * https://fedoraproject.org/wiki/Packaging:Java

--- 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)
     Anything else not mentioned above

     * https://admin.fedoraproject.org/mailman/listinfo/devel-announce

---- Call for Test Days for Fedora 16 ----

Adam Williamson announced[1]:

"Hi, folks. The Test Day cycle for Fedora 16 will open shortly, and 
we're putting out the call for anyone who has an idea for a Test Day. 
There are many open slots on the schedule[2] - and if they all fill up 
or you would like to run a set of Test Days on related topics, we can 
organize events outside of the scheduled Thursday windows too.

It's often a good idea to have a Test Day for a major change or new 
feature you're introducing to the distribution, but we can run a Test 
Day on just about any topic. There is a full guide to organizing Test 
Days available[3] - and the QA team is happy both to help you run a Test 
Day and to butt out and let you run it yourself, whichever you prefer! 
If you're interested in running a Test Day, please contact QA via the 
test mailing list, file a ticket in QA trac[4] and/or pencil in your 
event on the schedule, create a Wiki page based on the template (see the 
SOP for details), and get down to work. Thanks!

-- Adam Williamson Fedora QA Community Monkey IRC: adamw 

     * https://fedoraproject.org/wiki/QA/Fedora_16_test_days
     * https://fedoraproject.org/wiki/QA/SOP_Test_Day_management
     * https://fedorahosted.org/fedora-qa

--- Fedora Events ---

The purpose of 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. Events can be added to this page whether or 
not they have an Ambassador owner. Events without an owner are not 
eligible for funding, but being listed allows any Ambassador to take 
ownership of the event and make it eligible for funding. In plain words, 
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 - August 2011) ----

     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]

     * http://fedoraproject.org/wiki/FedoraEvents/PastEvents

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

     * http://lists.fedoraproject.org/pipermail/marketing/

--- Fedora 16 planned to come with Systemd and Btrfs as default (German) ---

Vinzenz Vietzke forwarded[1]:


German Linux Magazine and it's partner Site linux-community.de have a 
short feature summary of upcoming Fedora 16 including Systemd, Btrfs and 
many tools for virtualization:

"[...] Wie andere Distributionen soll Fedora 16 auf HAL verzichten und 
auf Grub 2 als Bootloader umsteigen. Systemd wird zum 
Standard-Init-System, Btrfs zum Standard-Dateisystem. Als 
Desktopumgebungen sind Gnome 3.2 und KDE Plasma Workspaces 4.7 
vorgesehen. [...]"

The full articles are available[2][3]

Regards, vinz. -- Vinzenz Vietzke Fedora Ambassador / Coordination 
German L10N Team"


--- The Five Best Linux Netbook Distributions: 2011 Edition ---

Jared K. Smith forwarded[1] a review of current linux distributions 
suitable for netbooks, with the following comment on Fedora:

"Fedora and GNOME Shell make a pretty nifty netbook OS. Fedora, of 
course, has all the software you'd expect for a full-blown Linux distro."

The full post is available[2].


-- Ambassadors --

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

Contributing Editor: Richard A Vijay For days of the week starting from 
13th July 2011 to 21th July 2011 [2]

     * http://fedoraproject.org/wiki/Ambassadors
     * http://lists.fedoraproject.org/pipermail/ambassadors/

--- Beat this week ---

---- Headlines from mailing lists ----

- EMEA Ambassadors 13th July Minutes

- APAC Wednesday meeting

- Graphics into our Ambassadors Joining Process

- FUDCon India Planning

- Design Team Joining Process

- Biweekly APAC Meeting 30 July 2011 Reminder

- FAD APAC Meeting and Survey

- Ambassador Survey Results on FAmSco

- Reminder for FAD APAC on 27th July

---- Welcome New Ambassadors ----

This week the Fedora Ambassadors Project had a couple of new members 

Each and everyone of us in Fedora Community is happy to have you as part 
of our Ambassadors team. We wish you very best in your endeavors.

https://fedoraproject.org/wiki/User:Karbafosss from Russia mentored by 
Robert Scheck

https://fedoraproject.org/wiki/User:Lovenemesis from China mentored by 
Caius 'kaio' Chance

Congrats and Wishes to all New members from Fedora Team. Thanks Joerg 
(kital) Simon for inviting them with welcome message.
Summary of traffic on Ambassadors mailing list

---- EMEA Ambassadors 13th July Minutes ----

Minutes: [1] Minutes (text): [2] Log: [3]

Buddhike Chandradeepa Kurera,Fedora Ambassador from Sri Lanka shared his 
ideas [4]

Vinzenz Vietzke, Fedora Ambassador / Coordination German L10N Team 
shared his views on graphical approach for ambassadors join process [5]

S.Kemter, Christian Bryant,  Vinzenz Vietzke, Joerg Simon,  Pierros 
Papadeas, Buddhika Kurera, Jukka Palander,
Kaesar ALNIJRES,  Gregory Fenton,  Zoltan Hoppar, S.Kemter,  María 
Leandro, inode0,  María Leandro,  Cheng-Chia Tseng Shared their views

Inode shared his points in a thread later [6]

David Ramsey sent out a reminder for Meeting on 16th July at 4:00 UTC, 
Buddhika wrote to lists inviting discussions with FUDCon Pune organisers 
and FAms hosting FAD all around APAC. [7]

FUDCon India Planning meeting reminder sent by Rahul pointing to channel 
on IRC for Planning [8]

APAC bi-weekly meeting held on 16th July 2011. Please find the meeting 
notes from the below URLs.

Minutes: [9] Minutes (text): [10] Log: [11]

Biweekly APAC Meeting reminder - 30th July 2011 [12] Agenda [13] Log: [14]

Log (text): [15]

FAD APAC Meeting Notes and Survey Minutes: [16]

Minutes (text): [17]

Survey [18]

---- FAmSCo Meeting ----

FAmSco looked into understand better the view of ambassadors and here 
are the results:

Firts is the general responses: [19] Second, if you want to see the 
comments: [20] Then we have divided by regions: [21] If you want to 
smash data in your own, here is a spread sheet with all the responses. [22]

FAD APAC Meeting reminder on 27th July 2011 [23] For any proposed 
changes to the draft agenda, then please update - [24]
Events reported on Ambassadors mailing list

Events Ninja Task List from Vinz 

---- Campus Ambassadors mailing list-Summary of traffic ----

The mailing list did not have any traffic this week except a Linkedin 
invitation from Sara singh. Editor likes to know if someone is 
regulating/monitoring this list?


     * http://www.doodle.com/y9gbw44kdbrc23mq#table
     * http://yn1v.fedorapeople.org/Documents/survey/comments_to_survey.pdf
     * http://yn1v.fedorapeople.org/Documents/survey/results-survey-full.ods
     * http://lists.fedoraproject.org/pipermail/campus-ambassadors/

-- QualityAssurance --

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

     * http://fedoraproject.org/wiki/QA
     * http://fedoraproject.org/wiki/QA/Join

--- Test Days ---

The Fedora 15 Test Day track is now finished, and the main Fedora 16 
Test Day track has not yet started. If you would like to propose a main 
track Test Day for the Fedora 16 cycle, please contact the QA team via 
email or IRC, or file a ticket in QA Trac[1]. Noriko Mizumoto proposed a 
localization Test Day for 2011-08-22[2].

     * http://fedorahosted.org/fedora-qa/
     * http://fedorahosted.org/fedora-qa/ticket/222

--- Release criteria and validation testing ---

Rui He worked on adding new release validation tests and extending 
existing ones in response to the results of the Beta release criteria / 
validation test concordance survey Adam Williamson performed the 
previous week (see FWN 282)[1] [2] [3] [4].

Athmane Madjoudj put the security lab spin validation matrix he had been 
working on into production[5]. Adam Williamson did the same with the 
base validation matrix he had been working on, and emailed the list with 
details of the two new matrices and some related changes he had made to 
the validation testing wiki pages at the same time[6].

     * http://fedorahosted.org/fedora-qa/ticket/216
     * http://fedorahosted.org/fedora-qa/ticket/217
     * http://fedorahosted.org/fedora-qa/ticket/218
     * http://fedorahosted.org/fedora-qa/ticket/219
     * http://fedorahosted.org/fedora-qa/ticket/207#comment:3
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101284.html

--- Separation of release validation and feature processes ---

After James Laska announced the first Fedora 16 blocker bug review 
meeting[1], Bruno Wolff asked what was to be done[2]. with the large 
amount of proposed blocker bugs relating to the Fedora 16 feature of 
porting core system services from SysV to systemd[3]. Adam Williamson 
noted that the group had lately been consistent in rejecting proposed 
blockers which related simply to the implementation of features, 
preferring to keep the feature and release validation processes 
separate, and consider the release blocker system part of the release 
validation process. He proposed that the proposed blocker bugs related 
to this feature should be rejected en masse, and suggested that the 
separation between the feature and release validation processes should 
be made more explicit[4]. He clarified this idea in a subsequent 
message[5]. The idea met with the approval of James and Jóhann 
Guðmundsson[6], so Adam proposed it to FESCo (as the stewards of the 
feature process) via the development mailing list[7].

     * http://lists.fedoraproject.org/pipermail/test/2011-July/101303.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101304.html
     * http://fedoraproject.org/wiki/Features/SysVtoSystemd
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101305.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101316.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101320.html
     * http://lists.fedoraproject.org/pipermail/devel/2011-July/154345.html

--- Shortening blocker bug review meetings ---

Tim Flink kicked off an effort to reduce the length of blocker bug 
review meetings with several ideas[1]. Adam Williamson chipped in with 
some comments. At the blocker bug review meeting of 2011-07-15[2], those 
present at the meeting discussed Tim's ideas, and came away with a plan 
of following up on the idea of trying to provide more information in the 
bug reports outside of meetings in a more informal way than Tim had 

     * http://fedorahosted.org/fedora-qa/ticket/221

--- QA group meeting SOP ---

James Laska posted[1] a draft SOP (standard operating procedure) for 
running the QA group meetings[2]. Gerard Braad suggested it could be 
applied more generally[3]. Bruno Wolff, Gerard and James elaborated this 
into a plan to provide a general meeting SOP and customized, 
group-specific versions using Wiki templates[4]. Matthias Clasen thought 
the idea of an SOP for one of 'the most basic things' was 
unnecessary[5], but James disagreed[6], and Bruno and John Dulaney said 
they had found themselves hosting the group meetings in the past, and 
would have found such a guide valuable [7] [8].

     * http://lists.fedoraproject.org/pipermail/test/2011-July/101253.html
     * http://fedoraproject.org/wiki/User:Jlaska/QA:SOP_IRC_meeting
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101256.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101261.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101268.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101270.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101272.html
     * http://lists.fedoraproject.org/pipermail/test/2011-July/101273.html

--- AutoQA ---

Kamil Paral continued to work on the SOP for AutoQA releases[1] with 
input from Tim Flink[2] and James Laska[3].

The group also continued to work on planning for AutoQA 0.6. They held 
an IRC planning meeting on 2011-07-14, and Tim sent the minutes to the 

Tim suggested having a custom 404 page for the AutoQA results site, 
containing information likely to be useful to people hitting missing 
pages, which are likely to be old logs which are no longer retained[5].

Tim was also working on improving automated self-testing of AutoQA, and 
proposed identifying situations that would make for good functional 
regression tests[6] and creating mockups of AutoQA's external 
dependencies (other systems without which it is difficult to run or test 
AutoQA correctly)[7].

Pausing only for a coffee and a handful of amphetamines, Tim continued 
with a demo of AutoQA documentation converted to use the Sphinx 
system[8]. Kamil Paral[9], Josef Skladanka[10] and John Dulaney[11] 
provided feedback and suggestions. A side thread[12] provided a venue 
for a discussion on a more general level of the correct approach to 

James Laska announced the availability of AutoQA 0.5.1 packages in the 
testing repository [13]

     * http://fedoraproject.org/wiki/AutoQA_Release_Process
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002536.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002530.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002594.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002546.html
     * http://fedorahosted.org/autoqa/ticket/352
     * http://fedorahosted.org/autoqa/ticket/353
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002569.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002575.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002576.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002580.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002571.html
     * http://fedorahosted.org/pipermail/autoqa-devel/2011-July/002603.html

-- Security Advisories --

In this section, we cover Security Advisories from 
fedora-package-announce for the period June 8- June 15, 2011.


Contributing Writer: Pascal Calarco

--- Fedora 15 Security Advisories ---

     libpng-1.2.46-1.fc15 - 
     thunderbird-3.1.11-1.fc15 - 
     mingw32-libpng-1.4.3-3.fc15 - 
     drupal7-7.4-1.fc15 - 
     phpMyAdmin- - 
     krb5-appl-1.0.1-7.fc15 - 

--- Fedora 14 Security Advisories ---

     mingw32-libpng-1.4.3-2.fc14 - 
     phpMyAdmin- - 
     drupal7-7.4-1.fc14 - 

- end FWN 282 -

Pascal Calarco,
Fedora Ambassador, Ontario, Canada

More information about the news mailing list