Outage: SSL Cert - 2010-07-31 12:00 UTC
by Mike McGrath
There will be an outage starting at 2010-07-31 12:00 UTC, which will last
approximately 3 hours?
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2010-07-31 12:00 UTC'
Reason for outage:
Our wildcard cert expired. Yes we've monitored this in the past. No we
don't know why we weren't alerted this time, researching. The new
purchase is in the works but we've run into some logistical issues. Will
have it replaced as soon as possible.
Affected Services:
Bodhi - https://admin.fedoraproject.org/updates/
Docs - http://docs.fedoraproject.org/
Email system
Fedora Account System - https://admin.fedoraproject.org/accounts/
Fedora Community - https://admin.fedoraproject.org/community/
Main Website - http://fedoraproject.org/
Mirror List - https://mirrors.fedoraproject.org/
Mirror Manager - https://admin.fedoraproject.org/mirrormanager/
Package Database - https://admin.fedoraproject.org/pkgdb/
Spins - http://spins.fedoraproject.org/
Start - http://start.fedoraproject.org/
Translation Services - http://translate.fedoraproject.org/
Wiki - http://fedoraproject.org/wiki/
Unaffected Services:
BFO - http://boot.fedoraproject.org/
Buildsystem - http://koji.fedoraproject.org/
CVS / Source Control
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
Fedora Hosted - https://fedorahosted.org/
Fedora People - http://fedorapeople.org/
Fedora Talk - http://talk.fedoraproject.org/
Smolt - http://smolts.org/
Torrent - http://torrent.fedoraproject.org/
Ticket Link:
https://fedorahosted.org/fedora-infrastructure/ticket/2300
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to
track the status of this outage.
13 years, 9 months
- 1
- 0
Package update notifications fixed
by Jared K. Smith
Recent updates to Fedora introduced two unexpected bugs, either of
which results in users no longer seeing notifications of or being able
to apply new updates.
Updates to the relevant packages have been shipped to fix these
issues, but users will not receive notifications for them unless they
first apply the pending fixed updates using the "yum" tool. (Please
note that these issues should only affect Fedora 13. Fedora 12 does
not appear to be affected.) Packages fixing these issues were pushed
to the Fedora software repositories around July 22, 2010. Users who
have done a manual "yum update" since that push may have already
received these fixes.
To fix the issue, please:
1. Open a Terminal (Applications > System Tools > Terminal)
2. Type either of the following commands and enter the password for
the root user when prompted.
a. To choose to apply all pending updates now:
su -c "yum -y --skip-broken update"
b. To choose to apply updates fixing only the specific issues mentioned above:
su -c "yum -y --skip-broken update gnome-packagekit selinux-policy"
3. Log out and and then log back in, or reboot your computer. Note
that logout/login will complete the fix for the notification issue.
However, if you applied all updates in the previous step, you may need
to reboot for other updates that require it.
We apologize for the inconvenience, and we are working on further
improvements to our testing and quality assurance processes to avoid
this and similar problems in the future.
If you have any further questions or require additional assistance,
please refer to
https://fedoraproject.org/wiki/Communicating_and_getting_help for ways
to get additional help from the Fedora community.
--
Jared Smith
Fedora Project Leader
13 years, 9 months
- 1
- 0
Fedora Weekly News 236
by Pascal Calarco
* 1 Fedora Weekly News Issue 236
o 1.1 Announcements
+ 1.1.1 Fedora Announcement News
# 1.1.1.1 F13 Release Events - Mission completed!
+ 1.1.2 Fedora Development News
# 1.1.2.1 Red Hat Bugzilla 3.6 Upgrade Public Beta
# 1.1.2.2 Fedora 14 branching and dist-git roll out
# 1.1.2.3 Fedora 14 Feature Freeze is tomorrow (2010-07-27)
# 1.1.2.4 f14 boost-1.44.0 upgrade: pushed
# 1.1.2.5 Outage: Build System - 2010-07-28 07:15 UTC
* 1.1.2.5.1 Reason for outage
* 1.1.2.5.2 Affected Services
* 1.1.2.5.3 Unaffected Services
* 1.1.2.5.4 Ticket Link
* 1.1.2.5.5 Contact Information
+ 1.1.3 Fedora User Announcements
+ 1.1.4 Fedora Events
# 1.1.4.1 Upcoming Events (June 2010 - August 2010)
# 1.1.4.2 Past Events
# 1.1.4.3 Additional information
o 1.2 Fedora In the News
+ 1.2.1 Fedora 13: what you need to know (techradar.com/Linux Format)
+ 1.2.2 Fedora vs Ubuntu (MyBroadband - South Africa)
+ 1.2.3 My Linux: Fedora 13 for Software Developers (University of
Auckland New Zealand Linux User Group)
o 1.3 QualityAssurance
+ 1.3.1 QA metrics
+ 1.3.2 Localization testing
+ 1.3.3 Boot menu release criterion proposal
+ 1.3.4 Bootloader menu release criterion
+ 1.3.5 Lessons learned about update process
o 1.4 Design
+ 1.4.1 Fedora 14 Alpha Artwork
+ 1.4.2 Design Team Weekly Meeting
+ 1.4.3 The Comfortaa Font
+ 1.4.4 New Join Page
o 1.5 Security Advisories
+ 1.5.1 Fedora 13 Security Advisories
+ 1.5.2 Fedora 12 Security Advisories
- Fedora Weekly News Issue 236 -
Welcome to Fedora Weekly News Issue 236[1] for the week ending July 28,
2010. What follows are some highlights from this issue.
In announcements from the Fedora Project, a thank you and reward from
FAMSCO on the many recent Fedora 13 release events, details on the Red
Hat Bugzilla 3.6 upgrade public beta, and branches and feature freezes
for the Fedora 14 tree. In Fedora In the News, a South African
comparison between Fedora and Ubuntu projects, Fedora 13 review from a
New Zealand LUG, and a Fedora article from Linux Format UK reposted.
Quality Assurance brings news on QA statistics efforts, localization
testing using Nitrate, and work on the F14 boot menu and bootloader. In
Design Team news, decisions on Fedora 14 Alpha artwork, discussion
around the Comfortaa font as a secondary branding tool, and work on a
new Join page for the Design Team. Security Advisories completes this
issue of FWN, with many security-related packages for Fedora 12 and 13
released over the past week.
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(a)lists.fedoraproject.org
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue236
2. http://www.archive.org/search.php?query=subject%3A%22FWN%22
3. 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
Events[3].
Contributing Writer: Rashadul Islam
1. http://lists.fedoraproject.org/pipermail/announce/
2. http://lists.fedoraproject.org/pipermail/devel-announce/
3. http://fedoraproject.org/wiki/Events
--- Fedora Announcement News ---
---- F13 Release Events - Mission completed! ----
Joerg Simon[1] on Monday, July 26 at 10:26:52 UTC 2010 announced[2],
"FAmSCo want to thank all of you who held a F13 Release Party[3]!
A special thank you goes out to all of you who posted Event Reports
before the DeadLine[4]!
Now it is Dinner-Time ;) pick 5 of your regional Fellows and/or Friends
and have a great Evening -
we will pay for your Food and Drinks as a Thank You.
* Bert Desmet [5]
* Pierros Papadeas [6]
* René Jr Purcell [7]
* Truong Anh Tuan [8]
* Nilesh Vaghela [9]
* Rangeen Basu Roy [10]
* David Ramsey [11]
* José López [12]
* Edna Rheiner [13]
* Neville A. Cross [14]
We want to make sure that you have no trouble in getting the money and
that you get it fast - so please have a proper receipt, that you can
send to me FAS:jsimon"
1. Joerg Simon
2. http://lists.fedoraproject.org/pipermail/announce/2010-July/002841.html
3. https://fedoraproject.org/wiki/F13_release_events
4.
http://meetbot.fedoraproject.org/fedora-meeting-1/2010-06-07/fedora-meeti...
5. http://fedoraproject.org /wiki/Release_Party_F13_Ghent#Reports
6. http://pierros.papadeas.gr/?p=133
7. http://arsenicks.wordpress.com/2010/06/17/fedora-13-release-party-quebec/
8. http://www.iwayvietnam.com/en/success-of-the-1st-vietnam-open-day.html
9.
http://www.vglug.info/forums/vglug-discussion/fwd-fedora-13-release-party...
10. https://fedoraproject.org/wiki/Release_Party_F13_Bangalore#Reports
11.
http://diamondramsey.wordpress.com/2010/07/20/release-party-f13-tokyo-rep...
12. http://www.taygon.com/?p=397
13. http://www.fedora.org.gt/linux-party-una-verdadera-fiesta-de-distros/
14. http://www.taygon.com/?p=409
--- Fedora Development News ---
---- Red Hat Bugzilla 3.6 Upgrade Public Beta ----
James Laska[1] on Thu Jul 22 11:55:49 UTC 2010 announced[2],
"I am sending this on behalf of Dave Lawrence and the bugzilla team at
Red Hat. Please forward this on to any appropriate lists that were missed.
Greetings,
The Red Hat Bugzilla team is happy to announce the first public beta
release of the next version of Red Hat Bugzilla based on the upstream
3.6 code base.
Please test drive[3].
Over the years Red Hat has made substantial customizations to Bugzilla
to fit into the Engineering tool chain. Over time the upstream has
incorporated some of these customizations or solved them in different
ways. Upgrading reduces our customization footprint (and thus
maintenance) while bringing many bug fixes & enhancements.
The main area of focus for our public betas is stability. Functionality
that currently works in our 3.4 code base should continue to work as
expected in the new 3.6 release. These include various ajax
optimizations, needinfo actor support, frontpage.cgi, product browser,
several various UI enhancements, and of course the XMLRPC API.
Please feel free to point your various scripts and third party
applications that use the XMLRPC API at the test server to make sure
they continue to function properly.
There are numerous other changes behind the scenes that we haven't>
listed. The goal is to make sure that functionality that people have
come to expect in 3.4 is possible in the new system.
There are also numerous new features/fixes that are part of the upstream
3.6 release. For more detailed information on what has changed since the
last release, check out the release notes page at [4] .
The database is a recent snapshot of the live database so should be
useful for testing to make sure the information is displayed properly
and changeable. Also with a full snapshot it is possible to test for any
performance related issues. Email has been disabled so that unnecessary
spam is not sent out. So feel free to make changes to bugs to verify
proper working order.
We are asking for everyone to get involved as much as possible with
testing and feedback on the beta releases to help us make this the most
robust and stable release possible.
Please file any enhancement requests or bug reports in our current
Bugzilla system at [5] . File them under the Bugzilla product and
relevant component with the version 3.6. With everyone's help we can
make this a great release.
Thanks The Red Hat Bugzilla Team"
1. James Laska
2.
http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000639....
3. https://partner-bugzilla.redhat.com
4. https://partner-bugzilla.redhat.com/page.cgi?id=release-notes.html
5. https://bugzilla.redhat.com
---- Fedora 14 branching and dist-git roll out ----
Jesse Keating[1] on Sat Jul 24 06:54:53 UTC 2010 announced[2],"Hey all!
It's that time again, we're gearing up to branch for Fedora 14 this
coming Tuesday! There is a major twist this time around, we're going to
attempt a roll out of dist-git!
Dist-git is our replacement for the CVS system we are currently using.
This is a pretty big deal, but we're going to try to make it as smooth
as possible. In the next few days I'll be finalizing our git server
setup and polishing up the user interface tool you all will be using to
interact with the source control and build system.
The conversion will take a couple days, which means our normal short
outage for branching will be a bit extended. I wish there was another
way, but converting over 9K cvs repos into git repos does take sometime.
I really feel that this move is worth the extended outage.
The tool you all will use to interact with git and the buildsystem is
called "fedpkg". It comes from the fedora-packager package. There is a
version of it available now in all active Fedora and EPEL releases,
although it is built to work against our staging environment where we
have been testing the setup for a while. This setup is slightly
different than the final version, but you can install it and poke around
the help system to get a feel for what's going on. Most of the make
targets have made it over and are named the same; build, sources, srpm,
etc... Many of the targets can take arguments and options. Where the
make system used shell variables, fedpkg uses options and arguments.
Each target takes a --help argument that will show any available
options. Fedpkg does not yet have a man page, that may be coming soon.
We're also going to be working on wiki pages to document the new stuff
and archive the old stuff. We're going to need help on this too, so if
you want to pitch in, by all means!
As I mentioned above, this is an attempt. We are trying this pretty
early, which I wouldn't normally do. However we have a good roll back
plan. We are going to keep the CVS server as is, although turned
read-only during and after the dist-git rollout. If something fails
beyond reasonable repair with the dist-git attempt we will re-enable
write access to the CVS server (after we branch it for Fedora 14).
Otherwise we will keep it around, in some capacity, as a read-only
reference point.
I'm certain we will run into some bumps along the way, and some wrinkles
to iron out. I ask that you are patient with us as we work through
these, and as we either get updates pushed out of fedpkg or make
adjustments to the git repos on the git server. This transition has been
a long time coming, and I'm really happy to be the one to make it
happen. Keep in mind that this will be the first iteration of our
transition, and it will operate mostly the same as dist-cvs did with a
few improvements. Later on we will start to explore more interesting
advancements such as automatic patch management with exploded sources,
linking to upstream source repositories, automatic %changelog generation
from git changelogs, or things I haven't even thought about. Most of
all, we won't be using CVS any more and that feels really good to me.
If you're curious about how the new system will work or have concerns,
or want to help, you can reply to this email thread or find me on IRC as
"Oxf13" (that's an o, not a zero). If you run across bugs in fedpkg, you
can file them in the fedora-packager hosted trac space [3] or just find
me on IRC as well.
Thanks again for your patience, both in waiting so long for us to make
this move, and for bearing with us during the transition."
1. Jesse Keating
2.
http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000640....
3. https://fedorahosted.org/fedora-packager/
---- Fedora 14 Feature Freeze is tomorrow (2010-07-27) ----
John Poelstra[1] on Mon Jul 26 20:59:07 UTC 2010 announced[2],"A
friendly reminder that tomorrow, Tuesday, July 27, 2010, is Feature
Freeze for Fedora 14.
Feature Freeze means that all accepted features for Fedora 14 must be
*significantly* "feature complete", ready for testing, and have a
current status.
[3] [4]
If you have a feature that will not be feature complete by tomorrow that
is okay. Simply change the wiki page category to
Category:FeatureReadyForWrangler (edit text at the very bottom of the
page) and include the reason and your plans in the commit comment. I'll
see that your feature is targeted for Fedora 15 instead."
1. John Poelstra
2.
http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000641....
3. https://fedoraproject.org/wiki/Feature_Freeze_Policy
4. https://fedoraproject.org/wiki/Features/Policy/Milestones#Feature_Freeze
---- f14 boost-1.44.0 upgrade: pushed ----
Benjamin Kosnik[1] on Tue Jul 27 17:19:25 UTC 2010 announced[2],"The
boost maintainers have updated the boost package to the current release
(1.44.0) in rawhide for F14. More info here:
[3]
Rebuilds for devel packages that require boost are mandatory, as SONAME
was bumped. Help from package maintainers with rebuilding packages with
boost dependencies is appreciated."
1. Benjamin Kosnik(bkoz at redhat.com)
2.
http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000642....
3. https://fedoraproject.org/wiki/Features/F14Boost144
---- Outage: Build System - 2010-07-28 07:15 UTC ----
Jesse Keating[1] on Wed Jul 28 07:05:27 UTC 2010 announced[2],"There
will be an outage starting at 2010-07-28 07:15 UTC, which will last
approximately 48 hours.
To convert UTC to your local time, take a look at [3] or run:
date -d '2010-07-28 07:15 UTC'
----- Reason for outage -----
dist-git migration and Fedora 14 branching
----- Affected Services -----
Buildsystem - [4] CVS / Source Control
----- Unaffected Services -----
All others
----- Ticket Link -----
N/A
----- Contact Information -----
Jesse Keating <jkeating at redhat.com> or Oxf13 on IRC
Please join #fedora-admin in irc.freenode.net or respond to this email
to track the status of this outage."
1. Jesse Keating
2.
http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000643....
3. http://fedoraproject.org/wiki/Infrastructure/UTCHowto
4. http://koji.fedoraproject.org/
--- Fedora User Announcements ---
The list[1],Fedora User Announcements, provides community assistance,
encouragement, and advice for Fedora users.
1. http://lists.fedoraproject.org/pipermail/users/2010-July/thread.html
--- 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]
1.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29
2.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2
3.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3
4.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4
---- Past Events ----
Archive of Past Fedora Events[1]
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]
http://fedoraproject.org/wiki/Marketing
Contributing Writer: Pascal Calarco
1. http://lists.fedoraproject.org/pipermail/marketing/
--- Fedora 13: what you need to know (techradar.com/Linux Format) ---
Kara Schlitz forwarded[1] a repost from Linux Format about Fedora 13,
from the blog techradar.com:
"Corporate backing and a large supportive community – almost all Linux
distributions can boast of at least one half of that.
Fedora, since its inception in late 2003 as Red Hat's community
distribution, has nurtured around itself a devoted community. It has
achieved this after providing, release after release, an innovative and
complete distribution that demands attention and respect.
Being a rather large distribution (the number of DVD distributions now
pales in comparison to single CD variants), Fedora 13 has something for
just about every variety of Linux user."
The full post is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013266.html
2.
http://www.techradar.com/news/software/operating-systems/fedora-13-what-y...
--- Fedora vs Ubuntu (MyBroadband - South Africa) ---
Rahul Sundaram forwarded[1] a posting comparing Fedora and Ubuntu
project approaches to creating linux distributions:
"The difference between Ubuntu and Fedora lies primarily in their
approaches to the end product they produce. Ubuntu's approach is to
produce an easy-to-use desktop alternative to Windows. While not a
Windows clone it is designed to be used by anyone keen to leave Windows
behind. And in this it is remarkably successful.
Fedora, on the other hand, strives to make a desktop operating system
that offers the best that the world of free and open source software has
at the time. It routinely includes software that many other
distributions consider too experimental to use and yet, somehow, manages
to team that with stability."
The full post is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013253.html
2. http://mybroadband.co.za/news/software/13806-Fedora-Ubuntu.html
--- My Linux: Fedora 13 for Software Developers (University of Auckland
New Zealand Linux User Group) ---
Rahul Sundaram forwarded[1] a posting from a New Zealand LUG about
Fedora 13, from the perspective of an engineer:
"This is (hopefully) the first in a series of posts in which members of
the LUG will detail their personal Linux set-ups and what they use them
for. I’m going to start out by detailing my set-up which is based on
Fedora 13. As a Computer Systems Engineer use my system(s) largely for
developing software, both for desktop platforms and embedded systems.
Therefore this article isn’t really for those new to computers, but it
should be of use to those who are tech-savvy on other platforms. I’ll
start by giving a quick overview of how I came to be a Fedora user, give
a description of Fedora as a distribution and then give an overview of
my system."
The full post is available[2].
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013252.html
2. https://ualug.ece.auckland.ac.nz/archives/246
-- 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
1. http://fedoraproject.org/wiki/QA
2. http://fedoraproject.org/wiki/QA/Join
--- QA metrics ---
Kamil Paral asked for feedback[1] on the topic of gathering statistics
on QA activities, as part of a Fedora-wide 'Fedora Hall Of Fame'
project[2]. He asked what would be the most important tools to monitor
and the most important characteristics to gather. Jóhann Guðmundsson
pointed out some of the pitfalls that can come with trying to measure
and reward voluntary contributions[3]. James Laska pointed out that
gathering statistics would be valuable in ways beyond trying to reward
contributors[4]. Jóhann clarified that he was only concerned with the
'Hall of Fame' concept and agreed that statistics could be useful in
monitoring and improving overall team performance[5]. Kamil thought that
in practice the negative effects Jóhann feared would not be so
pronounced[6]. Jóhann followed up with some concrete suggestions of
areas and numbers that would be interesting[7].
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092196.html
2. http://fedoraproject.org/wiki/User:Kparal/Idea:Fedora_Hall_of_Fame
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092198.html
4. http://lists.fedoraproject.org/pipermail/test/2010-July/092200.html
5. http://lists.fedoraproject.org/pipermail/test/2010-July/092205.html
6. http://lists.fedoraproject.org/pipermail/test/2010-July/092214.html
7. http://lists.fedoraproject.org/pipermail/test/2010-July/092215.html
--- Localization testing ---
Following on from last week's coverage of Igor Pires Soares's
localization testing discussion[1], Noriko Mizumoto suggested[2] using
the newly open-sourced Nitrate tool[3] for tracking the tests. Igor
asked[4] if the tool was yet packaged for Fedora and deployed in Fedora
Infrastructure. James Laska reported[5] that it was not, but said he
thought it would be a good candidate to be included. Later, Igor
announced[6] that he had made an initial set of updates to the
template[7] for Fedora 14.
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092029.html
2. http://lists.fedoraproject.org/pipermail/test/2010-July/092193.html
3. http://fedorahosted.org/nitrate/
4. http://lists.fedoraproject.org/pipermail/test/2010-July/092201.html
5. http://lists.fedoraproject.org/pipermail/test/2010-July/092203.html
6. http://lists.fedoraproject.org/pipermail/test/2010-July/092219.html
7. http://fedoraproject.org/wiki/QA:Fedora_14_l10n_Results_Template
--- 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.
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092147.html
2. http://lists.fedoraproject.org/pipermail/test/2010-July/092148.html
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092152.html
4. http://lists.fedoraproject.org/pipermail/test/2010-July/092150.html
--- Bootloader menu release criterion ---
Adam Williamson announced[1] that, following the list discussion, he had
added the simpler version of the proposed release criterion mentioned in
last week's issue to the Fedora 14 Alpha release criteria[2]. Rui He
added a validation test to check this[3].
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092231.html
2.
http://fedoraproject.org/wiki/Fedora_14_Alpha_Release_Criteria#Alpha_Rele...
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092248.html
--- Lessons learned about update process ---
Kevin Fenzi announced[1] that he had created a page to track lessons
learned from problems in the update process[2], and asked the group to
document any serious issues they had experienced involving updates to
stable releases so that FESCo could benefit from the information in
planning changes to the update processes and tooling.
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092236.html
2. http://lists.fedoraproject.org/pipermail/test/2010-July/092236.html
-- Design --
In this section, we cover the Fedora Design Team[1].
Contributing Writer: Nicu Buculei
1. http://fedoraproject.org/wiki/Artwork
--- Fedora 14 Alpha Artwork ---
As scheduled, at the latest weekly IRC meeting[1] the Design Team
decided on the "winning" concept for Fedora 14 "We decided to go with
Kyle Baker's latest iteration for the alpha". The team is interested in
receive feedback as early as possible, so Martin Sourada wrote a blog
post[2] pushed to Planet[3]. The package is being built and will land
into Rawhide soon.
1.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002995.html
2.
http://mso-chronicles.blogspot.com/2010/07/f14-laughling-wallpapers-packa...
3. http://planet.fedoraproject.org/
--- Design Team Weekly Meeting ---
Máirín Duffy started a debate[1] about the efficiency of the Design Team
weekly IRC meetings "Are you able to make the meetings? Are you going?
If not, how come? Is there anything we could change about the meetings
to make them easier for you to attend? How can we make the meetings more
fun?". Jef van Schendel supported[2] extended talks "I think the idea of
having extended discussions after the meetings would be great", Martha
Benitez pointed[3] to them as a good learning experience "I find the
meetings a good way to learn more about all this and they are certainly
an opportunity to get more involved" and Nicu Buculei encouraged[4] more
the social part "I think we should do more socializing at those
meetings, even if we do less work done."
1.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002961.html
2.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002965.html
3.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002973.html
4.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002966.html
--- The Comfortaa Font ---
Fabian A. Scherschel reopened[1] the talk about introducing Comfortaa as
the new secondary font for Fedora branding with a complaint about the
shape of one letter "As I mentioned in the meeting yesterday, I love the
way Comfortaa looks and I think it goes well with the Fedora logo, the
only problem I have with it is the way the capital 'i' looks" and at the
latest IRC meeting[2], after a few weeks of evaluation, the Design Team
decided in favor of Comfortaa, the evaluation for the body text is still
open "We still need to make a Droid Sans vs. Cantarell decision."
1.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002940.html
2.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002995.html
--- New Join Page ---
After Michael Beckwith created[1] a new 'Join Page' for the Design
Team[2] and Emily Dirsh added[3] a round of improvements from the
perspective of a new contributor, the page went live[4], there is
hopping this will make easier for new people to start contributing.
1.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002745.html
2. http://fedoraproject.org/wiki/Join_the_Design_Team
3.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002989.html
4. http://fedoraproject.org/wiki/Design#Joining_the_Design_Team
-- Security Advisories --
In this section, we cover Security Advisories from fedora-package-announce.
http://lists.fedoraproject.org/pipermail/package-announce
Contributing Writer: Pascal Calarco
--- Fedora 13 Security Advisories ---
* turba-2.3-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04459...
* mingw32-libpng-1.2.44-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04458...
* xulrunner-1.9.2.7-2.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04458...
* mysql-5.1.48-2.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04454...
* libvirt-0.8.2-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04452...
* pidgin-2.7.2-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04451...
* openttd-1.0.3-0.1.RC1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04451...
* imp-4.3.7-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04451...
* horde-3.3.8-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04450...
* sunbird-1.0-0.26.b2pre.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04448...
* thunderbird-3.1.1-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04448...
* galeon-2.0.7-30.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04445...
* gnome-python2-extras-2.25.3-20.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04445...
* perl-Gtk2-MozEmbed-0.08-6.fc13.15 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04445...
* gnome-web-photo-0.9-10.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04445...
* mozvoikko-1.0-12.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04444...
* firefox-3.6.7-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04445...
* xulrunner-1.9.2.7-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04444...
* bind-9.7.1-2.P2.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04444...
* seamonkey-2.0.6-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04442...
--- Fedora 12 Security Advisories ---
* mingw32-libpng-1.2.44-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04459...
* libvirt-0.8.2-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04457...
* cups-1.4.4-5.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04456...
* xulrunner-1.9.1.11-2.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04456...
* openttd-1.0.3-0.1.RC1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04456...
* horde-3.3.8-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04455...
* imp-4.3.7-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04454...
* turba-2.3-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04452...
* galeon-2.0.7-24.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04448...
* gnome-python2-extras-2.25.3-19.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04447...
* perl-Gtk2-MozEmbed-0.08-6.fc12.14 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04448...
* mozvoikko-1.0-11.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04448...
* gnome-web-photo-0.9-8.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04448...
* firefox-3.5.11-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04447...
* xulrunner-1.9.1.11-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04447...
* seamonkey-2.0.6-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04446...
* sunbird-1.0-0.23.20090916hg.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04446...
* thunderbird-3.0.6-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04446...
- end FWN 236 -
13 years, 9 months
- 1
- 0
F13 Release Events - Mission completed!
by Joerg Simon
Dear Fellows!
FAmSCo want to thank all of you who held a F13 Release Party[1]!
A special thank you goes out to all of you who posted Event Reports
before the DeadLine[2]!
Now it is Dinner-Time ;) pick 5 of your regional Fellows and/or Friends
and have a great Evening -
we will pay for your Food and Drinks as a Thank You.
Bert Desmet http://fedoraproject.org /wiki/Release_Party_F13_Ghent#Reports
Pierros Papadeas http://pierros.papadeas.gr/?p=133
René Jr Purcell
http://arsenicks.wordpress.com/2010/06/17/fedora-13-release-party-quebec/
Truong Anh Tuan
http://www.iwayvietnam.com/en/success-of-the-1st-vietnam-open-day.html
Nilesh Vaghela
http://www.vglug.info/forums/vglug-discussion/fwd-fedora-13-release-party...
Rangeen Basu Roy
https://fedoraproject.org/wiki/Release_Party_F13_Bangalore#Reports
David Ramsey
http://diamondramsey.wordpress.com/2010/07/20/release-party-f13-tokyo-rep...
José López http://www.taygon.com/?p=397
Edna Rheiner
http://www.fedora.org.gt/linux-party-una-verdadera-fiesta-de-distros/
Neville A. Cross http://www.taygon.com/?p=409
We want to make sure that you have no trouble in getting the money and
that you get it fast - so please have a proper receipt, that you can
send to me FAS:jsimon!
[1] https://fedoraproject.org/wiki/F13_release_events
[2]
http://meetbot.fedoraproject.org/fedora-meeting-1/2010-06-07/fedora-meeti...
--
Joerg (kital) Simon
jsimon(a)fedoraproject.org
http://fedoraproject.org/wiki/JoergSimon
http://kitall.blogspot.com
Key Fingerprint:
3691 0989 2DCA 58A2 8D1F 2CAC C823 558E 5B5B 5688
13 years, 10 months
- 1
- 0
Fedora Weekly News 235
by Pascal Calarco
* 1 Fedora Weekly News Issue 235
o 1.1 Announcements
+ 1.1.1 Fedora Announcement News
# 1.1.1.1 Fedora Board IRC Meeting 1800 UTC 2010-07-16
# 1.1.1.2 UTOSC 2010 Call for papers extended through August 1st!
+ 1.1.2 Fedora Development News
# 1.1.2.1 Reminder: Fedora 14 Feature Freeze is Next Week (2010-07-27)
+ 1.1.3 Fedora User Announcements
# 1.1.3.1 Fedora at South African Software Freedom Day
# 1.1.3.2 F13 Security Lab
# 1.1.3.3 PostgreSql question
# 1.1.3.4 F 13 installation trouble
# 1.1.3.5 Sun Java double-click interval
# 1.1.3.6 how to uninstall preload?
# 1.1.3.7 F13: Empathy stop working after 'yum update'
# 1.1.3.8 Fedora 13 installation, does not boot
# 1.1.3.9 Yum oddness
+ 1.1.4 Fedora Events
# 1.1.4.1 Upcoming Events (June 2010 - August 2010)
# 1.1.4.2 Past Events
# 1.1.4.3 Additional information
o 1.2 QualityAssurance
+ 1.2.1 Instructions and process for moving bug reports upstream
+ 1.2.2 Rawhide acceptance testing
+ 1.2.3 Proven testers
+ 1.2.4 AutoQA package acceptance testing
+ 1.2.5 Localization testing
+ 1.2.6 Boot menu release criterion proposal
o 1.3 Translation
+ 1.3.1 Fedora 14 Tasks
+ 1.3.2 L10n QA Template
+ 1.3.3 New Module Publican Site_Tech
+ 1.3.4 Publican 2 Released
+ 1.3.5 Transifex Mojo
+ 1.3.6 New Members in FLP
o 1.4 Artwork
+ 1.4.1 Slide Template Bounty
+ 1.4.2 Front Page Redesign
o 1.5 Security Advisories
+ 1.5.1 Fedora 13 Security Advisories
+ 1.5.2 Fedora 12 Security Advisories
- 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 fedoraproject.org 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: news(a)lists.fedoraproject.org
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue235
2. http://www.archive.org/search.php?query=subject%3A%22FWN%22
3. 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
Events[3].
Contributing Writer: Rashadul Islam
1. http://lists.fedoraproject.org/pipermail/announce/
2. http://lists.fedoraproject.org/pipermail/devel-announce/
3. http://fedoraproject.org/wiki/Events
--- 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!"
1. Paul W. Frields
2. http://lists.fedoraproject.org/pipermail/announce/2010-July/002838.html
---- 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?"
1. Clint Savage
2. http://lists.fedoraproject.org/pipermail/announce/2010-July/002839.html
3. http://2010.utosc.com
4. http://2010.utosc.com/speaker/papers/
--- 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."
1. John Poelstra
2.
http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000638....
3. https://fedoraproject.org/wiki/Feature_Freeze_Policy
4. https://fedoraproject.org/wiki/Features/Policy/Milestones#Feature_Freeze
--- 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 "
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378616.html
2. http://wiki.softwarefreedomday.org/2010/Africa/SouthAfrica/Pretoria
---- F13 Security Lab ----
[1]Mentioned by Thom Paine
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378736.html
---- PostgreSql question ----
[1] Mentioned by Nermin Celik
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378740.html
---- F13 installation trouble ----
[1]Mentioned by Ankur Sinha
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378754.html
---- Sun Java double-click interval ----
[1]Mentioned by Pasan
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378763.html
---- how to uninstall preload? ----
[1]Mentioned by Parshwa Murdia
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378765.html
---- F13: Empathy stop working after 'yum update' ----
[1]Mentioned by Marco Guazzone
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378775.html
---- Fedora 13 installation, does not boot ----
[1]Mentioned by Vincent Onelli
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378781.html
---- Yum oddness ----
[1]Mentioned by Patrick O'Callaghan
1. http://lists.fedoraproject.org/pipermail/users/2010-July/378782.html
--- 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]
1.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29
2.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2
3.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3
4.
http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4
---- Past Events ----
Archive of Past Fedora Events[1]
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.
-- 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
1. http://fedoraproject.org/wiki/QA
2. http://fedoraproject.org/wiki/QA/Join
--- 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].
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092018.html
2. http://lists.fedoraproject.org/pipermail/test/2010-July/092036.html
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092040.html
4. http://lists.fedoraproject.org/pipermail/test/2010-July/092091.html
--- 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'.
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092095.html
2. http://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan
3.
http://fedoraproject.org/wiki/Test_Results:Fedora_14_Pre-Alpha_Rawhide_Ac...
--- 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].
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092075.html
2. http://fedoraproject.org/wiki/Proven_tester
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092101.html
--- 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].
1. http://fedoraproject.org/wiki/QA/Meetings/20100712
2. http://fedoraproject.org/wiki/QA:Package_Update_Acceptance_Test_Plan
3. http://fedorahosted.org/autoqa/roadmap
--- 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].
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092029.html
2. http://fedoraproject.org/wiki/QA:Fedora_13_l10n_Results_Template
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092094.html
4. http://lists.fedoraproject.org/pipermail/test/2010-July/092096.html
--- 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.
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092147.html
2. http://lists.fedoraproject.org/pipermail/test/2010-July/092148.html
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092152.html
4. http://lists.fedoraproject.org/pipermail/test/2010-July/092150.html
-- Translation --
This section covers the news surrounding the Fedora Translation (L10n)
Project[1].
Contributing Writer: Runa Bhattacharjee
1. http://fedoraproject.org/wiki/L10N
--- 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.
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007816.html
--- 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].
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007802.html
2. http://lists.fedoraproject.org/pipermail/trans/2010-July/007806.html
3. http://lists.fedoraproject.org/pipermail/trans/2010-July/007821.html
4. http://lists.fedoraproject.org/pipermail/trans/2010-July/007825.html
--- New Module Publican Site_Tech ---
The 'Site Tech' page that is used in webpages generated by Publican has
been in included in translate.fedoraproject.org, to allow translation
submissions[1].
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007800.html
--- 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.
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007799.html
--- 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.
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007817.html
--- New Members in FLP ---
Mohammad AlHobayyeb (Arabic)[1] and Takuma Yoshida (Japanese)[2] joined
the Fedora Localization Project recently.
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007805.html
2. http://lists.fedoraproject.org/pipermail/trans/2010-July/007827.html
-- Artwork --
In this section, we cover the Fedora Design Team[1].
Contributing Writer: Nicu Buculei
1. http://fedoraproject.org/wiki/Artwork
--- 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
"http://lists.fedoraproject.org/pipermail/design-team/2010-July/002914.html"
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."
1.
http://mairin.wordpress.com/2010/07/09/fedora-design-bounty-fedora-slide-...
2.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002868.html
3.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002910.html
--- Front Page Redesign ---
Jef van Schendel created[1] a page reviewing[2] the content of the
fedoraproject.org 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]
1. http://fedoraproject.org/wiki/User:Schendje/FPOcontent/
2. http://fedoraproject.org/wiki/User:Schendje/FPOcontent/
3.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002886.html
4.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002929.html
5.
http://lists.fedoraproject.org/pipermail/design-team/2010-July/002924.html
-- Security Advisories --
In this section, we cover Security Advisories from fedora-package-announce.
http://lists.fedoraproject.org/pipermail/package-announce
Contributing Writer: Pascal Calarco
--- Fedora 13 Security Advisories ---
* python-cjson-1.0.5-5.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04434...
* libpng10-1.0.54-1.fc13 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04428...
--- Fedora 12 Security Advisories ---
* w3m-0.5.2-17.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04440...
* libpng10-1.0.54-1.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04439...
* python-cjson-1.0.5-5.fc12 -
http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04431...
- end FWN 235 -
-----
Pascal Calarco
Fedora Ambassador, Indiana, USA
13 years, 10 months
- 1
- 0
UTOSC 2010 Call for papers extended through August 1st!
by Clint Savage
I meant to send the original call for papers announcement back in
June, but this will have to do.
Clint
-------------
Time goes by quickly, so quickly in fact that top priorities get set
to 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 http://2010.utosc.com and when your ready to submit your
proposal simply create an account and visit
http://2010.utosc.com/speaker/papers/ 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?
13 years, 10 months
- 1
- 0
Fedora Board IRC Meeting 1800 UTC 2010-07-16
by Paul W. Frields
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!
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
13 years, 10 months
- 1
- 0
Fedora Weekly News 234
by Pascal Calarco
* 1 Fedora Weekly News Issue 234
o 1.1 Announcements
+ 1.1.1 Fedora Development News
# 1.1.1.1 Outage: Koji upgrade/migration - 2010-07-09 22:00 UTC
* 1.1.1.1.1 Reason for outage:
* 1.1.1.1.2 Affected Services:
* 1.1.1.1.3 Unaffected Services:
# 1.1.1.2 REMINDER: Test machine resources for package maintainers
# 1.1.1.3 Fedora 14 Feature Submission deadline is tomorrow (2010-07-13)
# 1.1.1.4 Meeting logs enhancement
# 1.1.1.5 Upcoming Bugzilla Changes: Rawhide Rebase
+ 1.1.2 Fedora User Announcements
# 1.1.2.1 Community gaming Saturday - Session 6 - Wesnoth
+ 1.1.3 Fedora Events
# 1.1.3.1 Upcoming Events (June 2010 - August 2010)
# 1.1.3.2 Past Events
# 1.1.3.3 Additional information
o 1.2 Marketing
+ 1.2.1 OLPC Software Strategy
+ 1.2.2 A New Name for Fedora Buzz
+ 1.2.3 MeeGo Community Metrics
+ 1.2.4 Marketing Meeting Minutes 2010-07-13
o 1.3 Fedora In the News
+ 1.3.1 This Week In Fedora Podcasts (Frostbite Media)
+ 1.3.2 10 things that will make you want to use Fedora again (TechRepublic)
+ 1.3.3 Open source alternative for Active Directory (ZDNet UK)
o 1.4 QualityAssurance
+ 1.4.1 Proven testers
+ 1.4.2 Musician's guide testing
+ 1.4.3 Installation validation test matrix update
+ 1.4.4 Desktop validation testing expansion
+ 1.4.5 AutoQA
+ 1.4.6 Triage metrics
o 1.5 Artwork
+ 1.5.1 Fedora 14 Artwork
+ 1.5.2 Testing the new Fedora Branding Fonts
+ 1.5.3 Design for the Local Communities Website
o 1.6 Security Advisories
+ 1.6.1 Fedora 13 Security Advisories
+ 1.6.2 Fedora 12 Security Advisories
- 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: news(a)lists.fedoraproject.org
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue234
2. http://www.archive.org/search.php?query=subject%3A%22FWN%22
3. 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 Events[3].
Contributing Writer: Pascal Calarco
1. http://lists.fedoraproject.org/pipermail/announce/
2. http://lists.fedoraproject.org/pipermail/devel-announce/
3. http://fedoraproject.org/wiki/Events
--- 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 - http://koji.fedoraproject.org/
----- Unaffected Services: -----
BFO - http://boot.fedoraproject.org/
Bodhi - https://admin.fedoraproject.org/updates/
CVS / Source Control
DNS - ns1.fedoraproject.org, ns2.fedoraproject.org
Docs - http://docs.fedoraproject.org/
Email system Fedora Account System - https://admin.fedoraproject.org/accounts/
Fedora Community - https://admin.fedoraproject.org/community/
Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Fedora Talk - http://talk.fedoraproject.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Translation Services - http://translate.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/
Ticket Link[3]
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000633....
2. http://fedoraproject.org/wiki/Infrastructure/UTCHowto
3. https://fedorahosted.org/fedora-infrastructure/ticket/2266
---- REMINDER: Test machine resources for package maintainers ----
Kevin Fenzi reminded[1] the community of the availability of test machine resources for package maintainers:
"Greetings.
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!
kevin"
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000634....
2. https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintai...
---- 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: https://fedoraproject.org/wiki/Releases/14/Schedule
Fedora Feature Process: https://fedoraproject.org/wiki/Features/Policy
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000635....
2. https://fedoraproject.org/wiki/Releases/14/FeatureList
---- Meeting logs enhancement ----
Kevin Fenzi announced[1]:
"Greetings.
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.
kevin"
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000636....
2. http://meetbot.fedoraproject.org/teams/
3. http://meetbot.fedoraproject.org/teams/fesco
---- Upcoming Bugzilla Changes: Rawhide Rebase ----
Jeff Raber announced[1]:
"Greetings,
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 irc.freenode.net and we’ll gladly help you.
More about these processes is here[2]
Jeff Raber
Fedora Bugzappers volunteer triage team[3]"
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000637....
2. https://fedoraproject.org/wiki/BugZappers/HouseKeeping
3. https://fedoraproject.org/wiki/BugZappers
--- 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]
1. http://lists.fedoraproject.org/pipermail/users/2010-July/377809.html
2. http://koji.fedoraproject.org/koji/taskinfo?taskID=2316236
3. https://fedoraproject.org/wiki/Community_Gaming#Upcoming_game_sessions
--- 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]
1. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29
2. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2
3. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3
4. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4
---- Past Events ----
Archive of Past Fedora Events[1]
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.
-- Marketing --
In this section, we cover the happenings for Fedora Marketing Project from 2010-07-07 to 2010-07-13.
http://fedoraproject.org/wiki/Marketing
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]
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013219.html
2. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013223.html
3. https://fedoraproject.org/wiki/Fedora_Buzz
4. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013224.html
5. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013228.html
6. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013232.html
7. https://fedoraproject.org/wiki/Fedora_Buzz#Overview
8. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013238.html
9. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013239.html
10. http://meetbot.fedoraproject.org/fedora-meeting-1/2010-07-13/marketing_me...
11. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013243.html
-- 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
1. 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.
--- 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]
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013222.html
2. http://www.frostbitemedia.libsyn.com/rss/twifogg
--- 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].
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013220.html
2. http://blogs.techrepublic.com.com/10things/?p=1659
--- 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].
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013218.html
2. http://www.zdnet.co.uk/blogs/the-open-source-revolution-10014902/open-sou...
-- Quality Assurance --
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
1. http://fedoraproject.org/wiki/QA
2. http://fedoraproject.org/wiki/QA/Join
--- 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].
1. http://lists.fedoraproject.org/pipermail/test/2010-July/091860.html
2. http://fedoraproject.org/wiki/User:Dafrito/Proven_tester
3. http://lists.fedoraproject.org/pipermail/test/2010-July/091861.html
4. http://lists.fedoraproject.org/pipermail/test/2010-July/091879.html
5. http://lists.fedoraproject.org/pipermail/test/2010-July/091887.html
6. http://lists.fedoraproject.org/pipermail/test/2010-July/091984.html
7. http://fedoraproject.org/wiki/User:Adamwill/Draft_proventesters
8. http://lists.fedoraproject.org/pipermail/test/2010-July/091985.html
9. http://lists.fedoraproject.org/pipermail/test/2010-July/091938.html
10. http://lists.fedoraproject.org/pipermail/test/2010-July/091943.html
11. http://lists.fedoraproject.org/pipermail/test/2010-July/091954.html
12. http://lists.fedoraproject.org/pipermail/test/2010-July/091956.html
13. http://lists.fedoraproject.org/pipermail/test/2010-July/091881.html
14. http://lists.fedoraproject.org/pipermail/test/2010-July/091883.html
15. http://lists.fedoraproject.org/pipermail/test/2010-July/091917.html
16. http://lists.fedoraproject.org/pipermail/test/2010-July/091918.html
--- 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.
1. http://lists.fedoraproject.org/pipermail/test/2010-July/091987.html
2. http://fedoraproject.org/wiki/User:Crantila/FSC/Testing
--- 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.
1. http://fedorahosted.org/fedora-qa/ticket/95
2. http://fedoraproject.org/wiki/QA:Fedora_14_Install_Results_Template
--- 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.
1. http://lists.fedoraproject.org/pipermail/test/2010-July/092010.html
2. http://lists.fedoraproject.org/pipermail/test/2010-July/092011.html
3. http://lists.fedoraproject.org/pipermail/test/2010-July/092012.html
--- 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.
1. http://fedorahosted.org/pipermail/autoqa-devel/2010-June/000742.html
--- 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.
1. http://meetbot.fedoraproject.org/fedora-meeting/2010-07-06/bugzappers.201...
2. http://fedoraproject.org/wiki/User_talk:Jraber
-- Artwork --
In this section, we cover the Fedora Design Team[1].
Contributing Writer: Nicu Buculei
1. http://fedoraproject.org/wiki/Artwork
--- 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.
1. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002838.html
2. http://fedoraproject.org/wiki/F14_Artwork_Feedback
3. http://mairin.wordpress.com/2010/07/13/fedora-14-theme-preview/
4. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002839.html
5. http://fedoraproject.org/wiki/F14_Artwork_Supplemental_Wallpapers_Submiss...
--- 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.
1. http://fedoraproject.org/wiki/Design/Fedora_Branding_Fonts
2. http://mairin.wordpress.com/2010/07/09/fedora-design-bounty-fedora-slide-...
3. http://ryanler.wordpress.com/2010/07/12/fedora-branding-fonts-trial/
4. http://ryanler.wordpress.com/2010/07/14/update-on-the-fedora-branding-fonts/
5. http://ianweller.org/2010/07/12/another-double-post-fedoras-fonts-and-mor...
--- 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 960.gs 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?"
1. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002819.html
2. http://www.fedoracommunity.org/
3. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002821.html
4. http://lists.fedoraproject.org/pipermail/advisory-board/2010-July/008666....
5. http://lists.fedoraproject.org/pipermail/advisory-board/2010-July/008670....
-- Security Advisories --
In this section, we cover Security Advisories from fedora-package-announce.
http://lists.fedoraproject.org/pipermail/package-announce
Contributing Writer: Pascal Calarco
--- Fedora 13 Security Advisories ---
* w3m-0.5.2-18.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04395...
* gv-3.7.1-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04394...
* kernel-2.6.33.6-147.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04394...
* rpm-4.8.1-2.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04388...
* bugzilla-3.4.7-2.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04387...
* python-mako-0.3.4-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04386...
* libgdiplus-2.6.4-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04405...
* mono-basic-2.6.2-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04405...
* mono-2.6.4-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04404...
* xsp-2.6.4-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04405...
* mod_mono-2.6.3-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04405...
* mono-tools-2.6.2-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04404...
* gtksourceview-sharp-2.0.12-11.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04405...
* gnome-sharp-2.24.1-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04404...
* qt-4.6.3-8.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04402...
--- Fedora 12 Security Advisories ---
* gv-3.7.1-1.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04391...
* python-mako-0.3.4-1.fc12- http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04389...
* kernel-2.6.32.16-141.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04406...
* mono-2.4.3.1-2.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04405...
* qt-4.6.3-8.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04403...
- end FWN 234 -
13 years, 10 months
- 1
- 0
Fedora Weekly News 233
by Pascal Calarco
* 1 Fedora Weekly News Issue 233
o 1.1 Announcements
+ 1.1.1 Fedora Announcement News
# 1.1.1.1 Fedora Board IRC Meeting 1800 UTC 2010-07-02
+ 1.1.2 Fedora Development News
# 1.1.2.1 Outage: PHX2 outage - 2010-07-05 01:00 UTC
* 1.1.2.1.1 Reason for outage:
* 1.1.2.1.2 Affected Services:
* 1.1.2.1.3 Unaffected Services:
# 1.1.2.2 Fedora 14 Feature Submission Deadline is One Week Away (2010-07-13)
# 1.1.2.3 Licensing Guidelines Update - Please Read
* 1.1.2.3.1 FAQ
+ 1.1.3 Fedora Events
# 1.1.3.1 Upcoming Events (June 2010 - August 2010)
# 1.1.3.2 Past Events
# 1.1.3.3 Additional information
o 1.2 Fedora In the News
+ 1.2.1 Fedora Gets New Leader (PC World)
o 1.3 QualityAssurance
+ 1.3.1 Proven testers
+ 1.3.2 AutoQA
+ 1.3.3 Triage metrics
+ 1.3.4 Request for old DeltaISOs
+ 1.3.5 VERIFIED Bugzilla status
o 1.4 Translation
+ 1.4.1 Fedora 14 Schedule
+ 1.4.2 Translation File Archives Now Available
+ 1.4.3 New Wiki Translation Policy
+ 1.4.4 Links for Untranslated Fedora Documents
+ 1.4.5 New Members in FLP
o 1.5 Artwork
+ 1.5.1 Custom GTK+ Theme
+ 1.5.2 Better Hackergotchis
+ 1.5.3 Fedora Branding Fonts
+ 1.5.4 Fedora 14 Concept Decision
o 1.6 Security Advisories
+ 1.6.1 Fedora 13 Security Advisories
+ 1.6.2 Fedora 12 Security Advisories
- 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 announcements from the Fedora Project, including notice of this past week's Fedora Board IRC meeting, details of a PHX2 outage on 7/5/2010 and changes on Red Hat's Licensing Guidelines, as well as a listing of Fedora Events globally. Fedora In the News brings one new story in PC World on Jared Smith' appointment as Fedora Project Leader. Quality Assurance is up next, with details on the Proven Testers project that they have been working on recently, updates on AutoQA work, triage metrics amongst other activity. In Translation news, an update on the Fedora 14 schedule for translation related work, a new wiki translation policy and more. In Artwork/Design Team news, details on a custom GTK+ theme, better hackergotchis, Fedora branding fonts, and decisions on Fedora 14 graphic concept. This week's issue wraps up with security-related packages for Fedora 12 and 13 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(a)lists.fedoraproject.org
FWN Editorial Team: Pascal Calarco, Adam Williamson
1. http://fedoraproject.org/wiki/FWN/Issue232
2. http://www.archive.org/search.php?query=subject%3A%22FWN%22
3. 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 Events[3].
Contributing Writer: Pascal Calarco
1. http://lists.fedoraproject.org/pipermail/announce/
2. http://lists.fedoraproject.org/pipermail/devel-announce/
3. http://fedoraproject.org/wiki/Events
--- Fedora Announcement News ---
---- Fedora Board IRC Meeting 1800 UTC 2010-07-02 ----
Paul W. Frields, Fedora Project Leader, announced[1]:
"The Board is holding a public IRC meeting on Friday, July 2, 2010 at 1800 UTC on IRC Freenode. For this meeting, the public is invited to do the following:
* Join #fedora-board-meeting to see the Board's conversation.
* Join #fedora-board-questions to discuss topics and post
questions. This channel is read/write for everyone.
This meeting will last approximately 60 minutes. The Board has reserved some time at the top of the hour to cover agenda items as appropriate. Following that we'll take questions from the community.
The moderator will voice people from the queue, one at a time, in the #fedora-board-meeting channel. We'll limit time per voice as needed to give everyone in the queue a chance to be heard. We look forwardto seeing you at the meeting!"
1. http://lists.fedoraproject.org/pipermail/announce/2010-July/002835.html
--- Fedora Development News ---
---- Outage: PHX2 outage - 2010-07-05 01:00 UTC ----
Mike McGrath announced[1]:
"There is an ongoing outage at this time in PHX2. The exact start time is not yet known and the ETA to be fixed is not yet known.
To convert UTC to your local time, take a look at[2] or run:
date -d '2010-07-05 01:00'
----- Reason for outage: -----
Several people are experiencing issues connecting to various Fedora services (see below). The cause for these issues seems to be network related and it is impacting different people differently. Some see packet loss, other see complete connectivity loss and other still aren't having any issues at all.
Some services listed as unaffected would have been impacted previously to this announcement but as we became aware of the issue have made some changes to bring those services back online. Those services include bodhi, the account system, pkgdb, main website/wiki, community and mirrormanager.
----- Affected Services: -----
Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ CVS / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Email system
----- Unaffected Services: -----
Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ BFO - http://boot.fedoraproject.org/ Docs - http://docs.fedoraproject.org/ Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Fedora Talk - http://talk.fedoraproject.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Translation Services - http://translate.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/
Ticket Link[3]
Contact Information:
Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage."
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000629....
2. http://fedoraproject.org/wiki/Infrastructure/UTCHowto
3. https://fedorahosted.org/fedora-infrastructure/ticket/2255
---- Fedora 14 Feature Submission Deadline is One Week Away (2010-07-13) ----
John Poelstra reminded[1] the community of the upcoming Fedora 14 feature submission deadline:
"This email serves as the last reminder for the Fedora 14 Feature Submission Deadline--Tuesday, July 13, 2010. After this date newly submitted features will be targeted for Fedora 15 unless an exception is granted by FESCo.
Accepted Fedora 14 features so far[2]
If you are a current feature page owner, thank you for submitting your feature for Fedora 14 and contributing to the next release of Fedora. If you haven't updated your feature page in the last month it would be a great help to every one if you would do so now.
As we start to reach deadlines and test releases for Fedora 14, more and more people will query the feature pages. We'd love to know that what they find is current and correct.
Thank you, John
More information:
Fedora 14 Schedule[3]
Fedora Feature Process[4]
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000630....
2. https://fedoraproject.org/wiki/Releases/14/FeatureList
3. https://fedoraproject.org/wiki/Releases/14/Schedule
4. https://fedoraproject.org/wiki/Features/Policy
---- Licensing Guidelines Update - Please Read ----
Tom "spot" Callaway announced[1] a revised Red Hat licensing guidelines:
"Hello Fedora!
Please take a moment and read this email. There's cake in it for you.
Upon the advice of Red Hat Legal, we have slightly amended the Fedora Licensing Guidelines[2]. The following section has been added:
Subpackage Licensing
If a subpackage is dependent (either implicitly or explicitly) upon a
base package (where a base package is defined as a resulting binary
package from the same source RPM which contains the appropriate
license texts as %doc), it is not necessary for that subpackage to
also include those license texts as %doc.
However, if a subpackage is independent of any base package (it does
not require it, either implicitly or explicitly), it must include
copies of any license texts (as present in the source) which are
applicable to the files contained within the subpackage.
Basically, what this means is this: If you maintain a package, and that package generates subpackages, then each subpackage must either include a copy of the appropriate licensing texts (as available in the source), or it must Require (either implicitly or explicitly) another subpackage which does include the appropriate licensing texts.
Unfortunately, there is no good way for us to determine which packages are out of compliance with this new guideline and will need to be fixed. (If http://rpm.org/ticket/116 was ever implemented, it would be possible...) However, we can identify packages which are likely candidates to be affected by this change. Thanks to Seth Vidal, I was able to generate a list of packages and subpackages, sorted by maintainer. The list was generated by querying rawhide for a list of source packages where:
* At least one subpackage was generated that did not have an exact name match to the source package name AND
* That subpackage did not depend on any other source packages.
Maintainers should look at the bottom of this email for the list.
-- FAQ
Q. Why are we doing this? A. The intent is to ensure that the appropriate license texts (as available in the source) are installed on the running system for all binary packages.
Q. Should I add explicit Requires: to another subpackage for the sole reason of complying with this new guideline? A. No. You should not add Requires simply for this licensing requirement. Instead, you should include duplicate copies of the relevant license texts (as available in the source).
Q. I thought duplicating files in a spec was forbidden? A. This is a permitted exception to that.
Q. You keep saying "as available in the source", what does that mean? A. It means you do not need to manually add license texts if they are not included by the upstream in the source tarball. However, if they are missing, you should ask upstream to add them.
Q. My package generates a -docs (or -javadocs) subpackage, which doesn't depend on any of the other subpackages, but the docs are under a different license from the code in the other subpackage(s), what should I do? A. You should make sure that the -docs/-javadocs subpackage has the correct License: tag, matching the files included, and be sure that the appropriate license texts are included as %doc in the -docs/-javadocs.
Q. My package generates a foo and foo-libs package. foo has the license files, and foo depends on foo-libs, but foo-libs doesn't have any license files in it. What should I do? A. You have two options here. You can either move the license texts from foo to foo-libs or duplicate the license texts in both packages. Moving the license texts is an acceptable option in this case because it ensures that if foo-libs is installed, the license texts are present, and if foo is installed, it will pull in foo-libs, thus, the license texts are present.
Q. What is the capital of the Republic of Ghana? A. Accra.
Q. What happens if I don't do this? A. Well, eventually, I'll go through and make the change myself. You will also suffer a horrible horrible curse.
Q. Do I need to make this change in stable branches? A. No, but you can if you want to. Rawhide is the only place that is a MUST fix.
Q. Do I need to push an update for this change? A. No, please don't. If you're already working on an update for other reasons and you want to do this (say, to keep the spec in sync with rawhide), you can.
Q. Do I need to build (not just commit) this change in rawhide? A. Please do. Don't forget to bump the release and add a changelog entry.
Q. Why can't we just have a "fedora-licenses" package which has copies of all the licenses in Fedora and just always install it? A. Maintaining that package would be a huge pain. We have a LOT of licenses in Fedora and they change all the time, often without notice. However, if you'd like to write some code to help us minimize duplicate license files on the filesystem with a "common-licenses" package, then you should look at<re>http://rpm.org/ticket/116</ref>. Have I mentioned that I'd like that functionality added to rpm?
Q. Why don't you add that functionality to rpm? A. Everytime I look at the rpm source code, blood starts dripping from my eyes, and it scares my newborn son, Jimmy. It also makes it hard to see the code.
Q. Some of the packages on your list don't need any changes to meet this guideline, what should I do? A. I'm sure there are some false positives here. Heck, _most_ of my packages which were flagged by this script did not need any changes, but some of them did. The only way to be sure was to have an informed human check. Just let me know that you checked them and they're okay. Please do this by sending me email, either by replying to this email on the list or emailing me directly. Telling me via IRC/AIM/Twitter/Facebook/Identi.ca/LinkedIn/MySpace/ICQ/CarrierPigeon just means I will forget about it.
Q. Hey, one of my packages didn't end up on your list, but it needed to be fixed to meet this guideline, why wasn't it on the list? A. There are plenty of other situations that we couldn't account for where a package would need to be changed to meet this guideline. If you think about it for a while, I'm sure you can come up with some. The case that Seth scripted was simply the most common one I could think of.
Q. I fixed my packages! Now what? A. Please email me (either in reply to this email on the mailing list, or in private) and let me know which packages you fixed.
Q. What about the packages owned by "orphan"? A. Well, it sure would be nice if a provenpackager could check these packages and fix them as appropriate, then let me know (via email). Thats the sort of thing that makes me feel like buying you a drink the next time our paths cross. But hey, if no one does it, I'll get to it eventually.
Q. What about new packages? A. All packages from this moment onward must meet this requirement. New packages, old packages, red packages, blue packages.
Q. I have another question which you did not answer here? A. Ask me, I'll do my best to answer.
Q. I'm confused by all of this? A. Sorry. Let me know what you don't understand and I'll try to make it clearer.
Q. Why are you always making me do things? A. Because I can! No, really, this is one of those "things we should have been doing all along", so we need to just bite the bullet and get it done.
Q. Hey you promised me cake, I read all this way! Where is my cake? A.
)
(.)
.|.
l7J
| |
_.--| |--._
.-'; ;`-'& ; `&.
& & ; & ; ; \
\ ; & &_/
F"""---...---"""J
| | | | | | | | |
J | | | | | | | F
`---.|.|.|.---'
What? You thought the cake was a lie?
Okay. Here's the list of packages that I think might be affected by this. Reminder: You need to check these packages and fix any which need fixing, then email me and let me know which ones you checked/fixed. Thanks!
Ed.: please see the original posting[3] for the list of packages, as it is quite long.
~spot"
1. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000631....
2. https://fedoraproject.org/wiki/Packaging:LicensingGuidelines
3. http://lists.fedoraproject.org/pipermail/devel-announce/2010-July/000631....
--- 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]
1. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29
2. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_2
3. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_3
4. http://fedoraproject.org/wiki/Events#FY11_Q2_.28June_2010_-_August_2010.29_4
---- Past Events ----
Archive of Past Fedora Events[1]
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]
http://fedoraproject.org/wiki/Marketing
Contributing Writer: Pascal Calarco
1. 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]
1. http://lists.fedoraproject.org/pipermail/marketing/2010-July/013206.html
2. http://lists.fedoraproject.org/pipermail/announce/2010-June/002832.html
3. http://www.jaredsmith.net
4. http://talk.fedoraproject.org
5. http://www.pcworld.com/businesscenter/article/200210/fedora_gets_new_lead...
-- 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
1. http://fedoraproject.org/wiki/QA
2. http://fedoraproject.org/wiki/QA/Join
--- 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].
1. http://fedoraproject.org/wiki/QA/Meetings/20100628
2. http://lists.fedoraproject.org/pipermail/test/2010-June/091746.html
3. http://fedoraproject.org/wiki/User:Jdulaney/Proven_Tester
4. http://lists.fedoraproject.org/pipermail/test/2010-July/091820.html
5. http://lists.fedoraproject.org/pipermail/test/2010-June/091745.html
6. http://lists.fedoraproject.org/pipermail/devel/2010-June/138008.html
7. http://lists.fedoraproject.org/pipermail/test/2010-June/091781.html
8. http://lists.fedoraproject.org/pipermail/test/2010-June/091793.html
9. http://lists.fedoraproject.org/pipermail/test/2010-June/091794.html
10. http://lists.fedoraproject.org/pipermail/test/2010-June/091800.html
11. http://lists.fedoraproject.org/pipermail/test/2010-July/091815.html
12. http://lists.fedoraproject.org/pipermail/test/2010-July/091845.html
--- 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.
1. 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.
1. http://meetbot.fedoraproject.org/fedora-meeting/2010-06-29/bugzappers.201...
2. http://fedoraproject.org/wiki/User_Talk:Jraber
--- 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.
1. 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.
1. http://fedorahosted.org/fedora-qa/ticket/91
2. https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow#VERIFIED
-- Translation --
This section covers the news surrounding the Fedora Translation (L10n) Project[1].
Contributing Writer: Runa Bhattacharjee
1. 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].
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007796.html
2. http://lists.fedoraproject.org/pipermail/trans/2010-July/007798.html
--- 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].
1. http://lists.fedoraproject.org/pipermail/trans/2010-July/007791.html
2. https://fedorahosted.org/fedora-infrastructure/ticket/2135
--- 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].
1. http://lists.fedoraproject.org/pipermail/trans/2010-June/007765.html
2. http://lists.fedoraproject.org/pipermail/trans/2010-June/007772.html
3. http://lists.fedoraproject.org/pipermail/trans/2010-June/007784.html
--- 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].
1. http://fedoraproject.org/wiki/FWN/Issue228#Links_for_Untranslated_Books_M...
2. http://lists.fedoraproject.org/pipermail/trans/2010-July/007797.html
--- New Members in FLP ---
?ukasz Jerna? (Polish)[1], Dirgita (Indonesian)[2] joined the Fedora Localization Project recently.
1. http://lists.fedoraproject.org/pipermail/trans/2010-June/007769.html
2. http://lists.fedoraproject.org/pipermail/trans/2010-June/007773.html
-- Artwork --
In this section, we cover the Fedora Design Team[1].
Contributing Writer: Nicu Buculei
1. 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."
1. http://lists.fedoraproject.org/pipermail/design-team/2010-June/002702.html
2. http://lists.fedoraproject.org/pipermail/design-team/2010-June/002703.html
3. http://fedorahosted.org/nodoka/
4. http://lists.fedoraproject.org/pipermail/design-team/2010-June/002706.html
5. http://lists.fedoraproject.org/pipermail/design-team/2010-June/002710.html
--- 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."
1. http://lists.fedoraproject.org/pipermail/design-team/2010-June/002716.html
2. http://jefsblog.wordpress.com/2010/07/04/introducing-hackergotchi-ribbons/
3. http://nicubunu.blogspot.com/2010/07/good-hackergotchis-for-everyone.html
4. http://planet.fedoraproject.org/
5. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002756.html
--- 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.
1. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002726.html
2. http://fedoraproject.org/wiki/Design/Fedora_Branding_Fonts
3. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002775.html
--- 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.
1. http://fedoraproject.org/wiki/F14_Artwork_Theme_Concepts
2. http://lists.fedoraproject.org/pipermail/design-team/2010-July/002772.html
-- Security Advisories --
In this section, we cover Security Advisories from fedora-package-announce.
http://lists.fedoraproject.org/pipermail/package-announce
Contributing Writer: Pascal Calarco
--- Fedora 13 Security Advisories ---
* avahi-0.6.25-7.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04382...
* mediawiki-1.15.4-54.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04380...
* mingw32-libtiff-3.9.4-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04376...
* gcc-4.4.4-10.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04372...
* cups-1.4.4-5.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04366...
* libtiff-3.9.4-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04366...
* libpng-1.2.44-1.fc13 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04363...
--- Fedora 12 Security Advisories ---
* mediawiki-1.15.4-54.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04385...
* mingw32-libtiff-3.9.4-1.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04383...
* avahi-0.6.25-7.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04380...
* mediawiki-1.15.3-53.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04379...
* libtool-2.2.6-18.fc12.1 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04378...
* gcc-4.4.4-10.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04378...
* rpm-4.7.2-2.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04374...
* libpng-1.2.44-1.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04373...
* python-2.6.2-8.fc12 -http://lists.fedoraproject.org/pipermail/package-announce/2010-July/043726.html
* bugzilla-3.4.7-1.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04371...
* libtiff-3.9.4-1.fc12 - http://lists.fedoraproject.org/pipermail/package-announce/2010-July/04371...
-- end FWN 233 --
13 years, 10 months
- 1
- 0
Fedora Board IRC Meeting 1800 UTC 2010-07-02
by Paul W. Frields
The Board is holding a public IRC meeting on Friday, July 2, 2010 at
1800 UTC on IRC Freenode. For this meeting, the public is invited to
do the following:
* Join #fedora-board-meeting to see the Board's conversation.
* Join #fedora-board-questions to discuss topics and post
questions. This channel is read/write for everyone.
This meeting will last approximately 60 minutes. The Board has
reserved some time at the top of the hour to cover agenda items as
appropriate. Following that we'll take questions from the community.
The moderator will voice people from the queue, one at a time, in the
#fedora-board-meeting channel. We'll limit time per voice as needed
to give everyone in the queue a chance to be heard. We look forward
to seeing you at the meeting!
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
Where open source multiplies: http://opensource.com
13 years, 10 months
- 1
- 0