Fedora Weekly News Issue 233

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

Issue 232 begins with . . . This week's issue wraps up with security-related packages from the past week. Enjoy FWN 233!

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: news@lists.fedoraproject.org

FWN Editorial Team: Pascal Calarco, Adam Williamson

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]

http://fedoraproject.org/wiki/Marketing

Contributing Writer: Pascal Calarco

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

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.

Fedora Gets New Leader (PC World)

Kara Schlitz forwarded^[1] a brief posting about Jared Smith's appointment in PC World:

"The Fedora Project will be getting a new leader next month, as Jared Smith takes over the helm from current head Paul Frields, Frields announced^[2] Tuesday on the Fedora mailing list.

Smith^[3], who will become a Red Hat employee next month, has participated in the Fedora community since 2007, primarily devoting time to the project's infrastructure and documentation teams. He also helped build a free Voice Over IP-based audio conference system for Fedora developers, called Fedora Talk^[4], and participated in Fedora-themed conferences."

The full post is available^[5]

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

Proven testers

At the QA weekly meeting of 2010-06-28^[1], John Dulaney offered to work on combining the two proven testers pages (concerning joining the proven testers, and how to conduct testing) into a single page and provide a draft to the list for review. John subsequently submitted^[2] his draft^[3]. Adam Miller liked it^[4].

Meanwhile, Adam Williamson proposed^[5] activating the proven testers group before Bodhi was changed to activate the requirement for proven tester feedback, as a way to make sure the process worked smoothly and get in some 'practice'. The response was generally positive. The proposal was, however, overtaken by events. Luke Macken announced the next day^[6] that a new version of Bodhi had been put in place which enabled the proven tester feedback requirement, so Adam quickly announced^[7] the activation of the proven testers group and asked members to start testing immediately.

He also promised to start the ball rolling on the mentoring process, and sent out a proposal^[8] the next day for a rough plan for proven tester mentoring. He suggested existing proven testers take sponsorship requests, ask the applicants to read the appropriate instructions, and then confirm that they are familiar with enabling updates-testing and posting feedback on updates, before sponsoring them into the proven testers group. Jesse Keating suggested^[9] asking applicants in general to take the initiative and start reading instructions and providing feedback, and link to some of their feedback on their application ticket, so their membership could be quickly approved as soon as a mentor got around to looking at the ticket. Adam thought^[10] this was a good idea, but felt that in practice it should be possible to personally pick up every current mentor request very quickly, given the number of requests and the number of existing proven testers.

Bob Lightfoot wrote about his proven tester testing process^[11], in case it was of use to others, or anyone could suggest improvements for him. Till Maas suggested a simplication^[12].

AutoQA

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.

↑ http://fedorahosted.org/pipermail/autoqa-devel/2010-June/000742.html

Triage metrics

At the Bugzappers weekly meeting of 2010-06-29^[1], Jeff Raber updated his progress with triage metrics. He had created a wiki page^[2] to track his goals and progress, and had discussed some modifications to python-bugzilla with Will Woods. The group discussed the specific metrics Jeff was targeting, and made a few adjustments.

Request for old DeltaISOs

Andre Robatino asked^[1] for anyone who had old DeltaISO files he had provided for various releases to seed the corresponding torrents so he could retrieve them, for the purpose of creating an archive of all previous DeltaISOs, making it easier to reconstruct particular test releases from the past whenever this might prove useful.

↑ http://lists.fedoraproject.org/pipermail/test/2010-June/091775.html

VERIFIED Bugzilla status

Aaron Farnes proposed an update^[1] to the bug workflow wiki page^[2] regarding the VERIFIED state. James Laska reviewed and approved his changes, which were also discussed at the weekly meeting. Aaron made it clear that triagers and reporters should manually set the status when they checked that a pending update would resolve an issue, leaving the Bodhi update system or the maintainer to close the bug.

Translation

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

Contributing Writer: Runa Bhattacharjee

↑ http://fedoraproject.org/wiki/L10N

Fedora 14 Schedule

John Poelstra has updated the Fedora 14 schedule as per the changes suggested by Noriko Mizumoto^[1]. Presently, translation and updation of the documentation in the earlier released branch is scheduled^[2].

Translation File Archives Now Available

The complete set of translation files for a language can now be downloaded as an archive from translate.fedoraproject.org^[1]^[2].

New Wiki Translation Policy

After gathering feedback from the Translation team, the newly drafted wiki translation process has been established as a policy by Ian Weller^[1]. Further, Tetsuya Morimoto suggested^[2] that for new pages marked for translation, the English content be copied automatically over when a new page link is clicked.

The new policy has also been added in the Translation Quick Start Guide^[3].

Links for Untranslated Fedora Documents

As a result of an earlier discussion^[1], the publican source has been modified to include a feature to display the list of the untranslated documents for a particular language in the respective language page on docs.fedoraproject.org. Ruediger Landmann has rebuilt the Fedora Documentation site to reflect this new feature^[2].

New Members in FLP

Łukasz Jernaś (Polish)^[1], Dirgita (Indonesian)^[2] joined the Fedora Localization Project recently.

Artwork

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

Contributing Writer: Nicu Buculei

↑ http://fedoraproject.org/wiki/Artwork

Custom GTK+ Theme

Marcus Moeller shared^[1] with the Design Team a custom GTK theme he is working on "I tried to make it look visually unique and eye friendly. It fits with the current GNOME icon set" about which Nelson Marques was very enthusiastic^[2] "My personal position is that any brand (such as fedora) should have a strong visual identity, which eventually brings up the theming" and also pointed to Martin Sourada's work on theming Fedora with Nodoka^[3]. Martin joined^[4] the opinion about a visual identity "I also think Fedora should have its own visual identity" while Nicu Buculei remained bitter and skeptical^[5] about such a possibility "In fact we go the other way, rejecting icon themes, GTK themes, notification themes or any other visual identity produced by the Design Team."

Better Hackergotchis

As an action item following the past week team IRC meeting, Jef van Schendel posted^[1] the development for hackergotchi ribbons and also wrote^[2] a blog post with a tutorial for using them. Also as an action point, Nicu Buculei wrote^[3] a long blog post with good practices for hackergotchi creation, examples and instructions, intended to make Planet Fedora^[4] a better looking place. Papadeas Pierros informed^[5] about his work in identifying and improving bad images "After compiling the lists (the ugly and the missing) I will make an generic email for each list and send to all owners.. thus we will provide assistance, point to guidelines or simple clear up."

Fedora Branding Fonts

Máirín Duffy assembled^[1] a wiki page^[2] collecting info for the intended change in Fedora branding fonts for character coverage "MgOpen Modata doesn't support accent marks very well. For example, I (Máirín) can't write my own name in MgOpen Modata" and move to consistence. After the weekly IRC meeting she announced^[3] the team's decision "At our team meeting today we decided to trial Comfortaa as the headline/titling font and Droid Sans as the body text font" which is going to be tested.

Fedora 14 Concept Decision

With the deadline reached, at the weekly IRC meeting the Design Team decided on the graphic concept for Fedora 14^[1], which was announced^[2] by Máirín Duffy on the Design Team mailing list "I double- and triple-counted our votes today - each voter picked their top 3 concepts - and the winner is Kyle Baker's concept for Fedora 14 with 9 votes." The next step is turning this concept in an usable wallpaper image and including in into the Fedora 14 Alpha release to gather feedback.

Security Advisories

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

http://lists.fedoraproject.org/pipermail/package-announce