Fedora Weekly News #167
by Oisin Feeley
Fedora Weekly News Issue 167
Welcome to Fedora Weekly News Issue 167 for the week ending March 15th,
2009.
http://fedoraproject.org/wiki/FWN/Issue167
This week Announcements links to some helpful "Fedora Classroom IRC
Logs" including one on using mock. PlanetFedora big-ups several posts
including David Lutterkort's explanation of how config file manipulation
can be simplified using XPath to query Augeas. Marketing notes the
latest meeting log. QualityAssurance reports that the last "Test Day"
for Intel graphics chipsets was valuable and advertizes the next for
XFCE. Developments summarizes the "Provenpackager Re-Seed" and watches
aghast as the "Mono Conflagration Jumps to Blog". Artwork listens to
some ideas about a "Theme Song". Virtualization reports the Xen "dom0
Kernel: Better, Still not Ready" and KVM "Snapshot Support Discussed".
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[1]. We welcome reader feedback:
fedora-news-list(a)redhat.com
1. http://fedoraproject.org/wiki/NewsProject/Join
FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala
Contents
1.1 Announcements
1.1.1 Fedora Classroom IRC Logs
1.1.2 Upcoming Events
1.1.2.1 FUDCon Berlin 2009
1.2 Planet Fedora
1.2.1 General
1.3 Marketing
1.3.1 Marketing Meeting Log for 2009-03-10
1.3.2 Fedora 11 Features 80% Complete or Better
1.4 QualityAssurance
1.4.1 Test Days
1.4.2 Weekly Meetings
1.4.3 Bugzappers Wiki Re-organization
1.4.4 Advertising Triage Days
1.4.5 Metrics
1.5 Developments
1.5.1 GSoC InstantMirror
1.5.2 Enhance Anaconda to Enable Repositories As Needed ?
1.5.3 Password Resets and Inactive Accounts
1.5.4 Mono Conflagration Jumps to Blog
1.5.5 Documentation Betas
1.5.6 Provenpackager Re-Seed
1.5.7 Closing Bugs NEXTRELEASE
1.6 Artwork
1.6.1 Theme Song
1.6.2 Artwork for the Beta Release
1.7 Virtualization
1.7.1 Enterprise Management Tools List
1.7.1.1 New Release virt-manager 0.7.0
1.7.1.2 New Release virtinst 0.4.3
1.7.2 Fedora Xen List
1.7.2.1 dom0 Kernel: Better, Still Not Ready
1.7.2.2 Missing Hypervisor Capabilities Restored
1.7.3 Libvirt List
1.7.3.1 Snapshot Support Discussed
1.7.3.2 Memory Ballooning Support for QEMU
== Announcements ==
In this section, we cover announcements from the Fedora Project.
http://www.redhat.com/archives/fedora-announce-list/
http://www.redhat.com/archives/fedora-devel-announce/
http://fedoraproject.org/wiki/FedoraEvents
Contributing Writer: Chris Tyler
=== Fedora Classroom IRC Logs ===
Rahul Sundaram noted [1] that IRC logs were available for the Fedora
Classroom [2] sessions held on March 7-8:
* Introduction to bash shell scripting[3] - Scott McBrien
* Training & Tips for Fedora Ambassadors[4] -- Max Spevack
* Fedora Trademarks[5] -- Paul W. Frields
* Perl Basics[6] -- Doran Barton
* Using the Windows cross-compiler[7] - Richard Jones
* Introduction to mock, the chroot package builder[8] -- Kevin Fenzi
1.
http://www.redhat.com/archives/fedora-announce-list/2009-March/msg00003.html
2. http://fedoraproject.org/wiki/Classroom
3.
http://fedoraproject.org/wiki/Introduction_to_bash_shell_scripting_Classr...
4.
http://fedoraproject.org/wiki/Training_and_Tips_for_Fedora_Ambassadors_Cl...
5.
http://fedoraproject.org/wiki/Fedora_Trademarks_Classroom_%2820090307%29
6.
http://fedoraproject.org/wiki/Perl_Basics_Classroom_%2820090307%29
7.
http://fedoraproject.org/wiki/Using_the_Windows_cross-compiler_Classroom_...
8.
http://fedoraproject.org/wiki/Introduction_to_Mock_Classroom_%2820090308%29
=== Upcoming Events ===
March 21: Free Software Embedded/Hardware workshop in
Thiruvananthapuram, Kerala, India.
March 23-29: LUGM OpenWeek [1] in Manipal, India.
March 25: Document Freedom Day in Kolkata, India.
March 26: Infotech Niagara Beta Awards[2] in Buffalo, NY, USA.
March 26: Ithaca College EdTech Day[3] in Ithaca, NY USA.
1. http://fedoraproject.org/wiki/FedoraEvents/LUGMopenweek
2. http://www.infotechniagara.org/events/?id=193
3. http://www.ithaca.edu/edtechday/
==== FUDCon Berlin 2009 ====
FUDCon Berlin[1] will be held from June 26 - 28 in Berlin, Germany.
1. http://fedoraproject.org/wiki/FUDConBerlin2009
== Planet Fedora ==
In this section, we cover the highlights of Planet Fedora - an
aggregation of blogs from Fedora contributors worldwide.
http://planet.fedoraproject.org
Contributing Writer: Adam Batkin
=== General ===
Dimitris Glezos analyzed[1] how Fedora's Localization community has
grown (hint: a lot).
Will Woods mentioned[2] that in Fedora 11, all of the x86 that were
previously .i386 will be replaced with .i586 (with requisite kernel arch
changes too).
Jef Spaleta asked[3]: "How do we want casual users to do a Fedora
Desktop install?" In other words, should Fedora be pushing new users
towards DVD install media, or installable Live CDs?
Joseph Smidt wrote[4] about the massive number of users downloading
Fedora. According to the statistics[5], around 100,000 new users have
started using Fedora 10 since Fedora 9 (based on unique IPs checking in
using yum).
Jeroen van Meeuwen responded[6] to an earlier post (that may have lacked
context) by explaining how certain dependency checks would be handled in
Cobbler for ris-linux and Windows provisioning.
David Lutterkort explained[7] how you can use Augeas and XPath to easily
and uniformly query a system's configuration files.
Bastien Nocera boasted[8] about the new Gnome Volume Applet.
1.
http://dimitris.glezos.com/weblog/2009/03/08/flp-advancement-study
2. http://qa-rockstar.livejournal.com/7478.html
3. http://jspaleta.livejournal.com/36540.html
4.
http://californiaquantum.wordpress.com/2009/03/10/another-100000-week-for...
5. http://fedoraproject.org/wiki/Statistics
6. http://kanarip.livejournal.com/11912.html
7.
http://watzmann.net/blog/index.php/2009/03/11/querying_system_configuration
8. http://www.hadess.net/2009/03/our-new-volume-feature.html
== Marketing ==
In this section, we cover the Fedora Marketing Project.
http://fedoraproject.org/wiki/Marketing
Contributing Writer: Kam Salisbury
=== Marketing Meeting Log for 2009-03-10 ===
The meeting log of the 2009-03-10 Fedora Marketing Meeting was made[1]
available.
1.
http://fedoraproject.org/wiki/Meeting:Marketing_meeting_2009-03-10
=== Fedora 11 Features 80% Complete or Better ===
The Fedora 11 Features List[1] neared completion.
1. http://fedoraproject.org/wiki/Releases/11/FeatureList
== QualityAssurance ==
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
1. http://fedoraproject.org/wiki/QA
=== Test Days ===
This week's regular test day[1] was on the Intel graphics card driver,
particularly kernel mode setting[2]. Kristian Høgsberg was the developer
present. Several people showed up and provided valuable testing for the
full set of test cases on various chips, giving a good overview of the
current state of the driver in several situations. A follow-up event
will be held before the release of Fedora 11 to check on the progress of
fixes for the identified issues. Further testing in this area is still
very helpful: the Wiki page contains full instructions on performing the
range of tests, and the Results table is still available, so anyone with
an Intel graphics adapter is encouraged to visit the Wiki page, perform
the tests, and file bug reports as appropriate.
Next week will be special, as two test days are scheduled. A special
test day is planned for Tuesday[3], on DeviceKit[4] - the partial HAL
replacement scheduled to be included in Fedora 11. Anyone can help with
this testing, so please come along and help out at the test day! The
regular test day[5] will be on the Xfce desktop environment[6],
particularly the new 4.6 release that will be part of Fedora 11. If Xfce
is your desktop environment of choice, please come along and help make
sure it'll be working properly in Fedora 11.
The DeviceKit test day will be held on Tuesday (2009-03-17) and the Xfce
test day on Thursday (2009-03-19) in the #fedora-qa channel on Freenode
IRC. Please come by to help make sure these features will be in shiny
working order for Fedora 11!
1. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-12
2. http://fedoraproject.org/wiki/Features/IntelKMS
3. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-17
4. http://fedoraproject.org/wiki/Features/DeviceKit
5. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-19
6. http://fedoraproject.org/wiki/Xfce
=== Weekly Meetings ===
The QA group weekly meeting[1] was held on 2009-03-11. The full log is
available[2]. After a bracing discussion on how to send an apparently
empty line to IRC, James Laska reported little progress in his work on
making the Semantic test result reporting extension for mediawiki
available as a package. He also deferred investigation of X.org test
suites for next week. Adam Williamson noted that he had discussed one
such suite, rendercheck, with Ben Skeggs, and he will make a package
available either as a scratch build or in the official repository to be
used in the upcoming nouveau Test Day. The group agreed to see if it
might be useful for other graphics test events.
Jesse Keating and Will Woods reported that they had not had time to look
at a method for identifying bugs caused by GCC 4.4 miscompilation
issues. The group evaluated the response to the known bugs in this area,
and decided that the responses suggested most issues would be resolved
by fixes to GCC itself, and this should not cause major problems.
Adam Williamson reported that he and François Cami had spoken to the
intel and radeon driver developers about holding test days for those
graphics drivers, and were in the process of organizing both events.
Jesse Keating reported that a serious bug in squashfs in the Rawhide
kernel was causing Rawhide installation to be impossible. This was to be
fixed by a kernel update in the following day's Rawhide (which turned
out indeed to be the case). He also reported that initial signing of
packages for F11 was in progress in chunks, in order to ease the
synchronization load for the mirroring system.
Jesse also reported that work on the substantial rewrite of Anaconda's
storage code was in progress. The group agreed that this was quite close
to the beta release, and that it seemed possible there could still be
substantial problems in the code at the time the beta should be
released, so discussed what kind of problems might be acceptable for a
beta release and what might not. Despite some concern on the part of
Will Woods, the group agreed to evaluate issues on a case-by-case basis,
taking care to make sure all issues in this area were added to the beta
release blocker bug so they would be evaluated.
The Bugzappers group weekly meeting[3] was held on 2009-03-10. The full
log is available[4]. John Poelstra reminded the group to evaluate all
bugs with regard to the Fedora 11 blocker ('F11Blocker') and Fedora 11
target ('F11Target') blocker bugs. He also announced that Monday
2009-03-16 will be a bug blocker day, for the maintainers, QA and
release engineering groups to go over the list of blocker bugs.
The group agreed to require a short self-introduction email to
fedora-test-list as the criterion for becoming a member of the
fedorabugs group in FAS. Edward Kirk volunteered to write up this
procedure into an SOP, as discussed at the previous meeting.
The group again discussed the Wiki re-design, particularly how the front
page should be laid out and how the main information flow should work
from there. Everyone agreed that it was important to keep the front page
short and simple and lay out a clear linear path for potential new
members to follow. The group agreed to wait for Adam Williamson to
finish his combination of Edward Kirk's draft[5] and Christopher
Beland's draft[6], with reference to the ideas discussed in the meeting.
The group also discussed the new Tracking page (since re-arranged to
become Components and Triagers [7]), and agreed it was a good layout,
but some of the content that had been merged into it should not have
been. Adam Williamson suggested that the statistics be updated regularly
and automatically via Brennan Ashton's metrics script.
Edward Kirk reported that he had updated the bug workflow graphic[8] to
reflect that NEEDINFO is no longer a status, but some members had
trouble seeing the updated graphic due to caching issues.
The group discussed the potential new meeting time with reference to the
availability matrix[9], but did not yet come to a decision.
The next QA weekly meeting will be held on 2009-03-18 at 1700 UTC (note
changed time, in UTC reference frame) in #fedora-meeting, and the next
Bugzappers weekly meeting on 2009-03-11 at 1500 UTC in #fedora-meeting.
1. http://fedoraproject.org/wiki/QA/Meetings
2.
http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090311.log.html
3. http://fedoraproject.org/wiki/BugZappers/Meetings
4.
http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-10
5. http://fedoraproject.org/wiki/User:Tk009/bugzappers
6. http://fedoraproject.org/wiki/User:Beland/BugZappers
7. http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
8. http://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
9. http://fedoraproject.org/wiki/Bugzappers_meeting_matrix
=== Bugzappers Wiki Re-organization ===
Christopher Beland worked hard to revise several areas of the Wiki,
including a new Tracking page[1] which combined pages on active
triagers, priority triage components, group goals and finding bugs[2].
After feedback from Edward Kirk, John Poelstra and others, this was
reduced simply to the Components and Triagers page[3], leaving the
others separate for now. Christopher updated these pages also. Adam
Williamson submitted his combined new front page draft for the group's
review[4].
1. http://fedoraproject.org/wiki/BugZappers/Tracking
2.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00437.html
3. http://fedoraproject.org/wiki/BugZappers/Components_and_Triagers
4.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00662.html
=== Advertising Triage Days ===
Christopher Beland pointed out that triage days are not advertised
anywhere in the Wiki[1]. Adam Williamson apologized and explained[2]
that this is because he is short on time at present as he is taking an
internal Red Hat training course during his work days. He welcomed any
help from the group in adding information about the triage day events to
the Wiki.
1.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00695.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00713.html
=== Metrics ===
Christopher Beland reported[1] that he could not access the pages for
Brennan Ashton's triage metrics reporting system. Brennan thanked him
for the feedback[2] and explained that there was a hardware issue on the
server. John Poelstra suggested[3] that the code for the metric system
be hosted in the Bugzappers group's git repository.
1.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00693.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00727.html
3.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00739.html
== Developments ==
In this section the people, personalities and debates on the
@fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
=== GSoC InstantMirror ===
Warren Togami asked[1] for any interested parties to get involved with a
GSoC[2] project to improve repository replication to mirrors.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00873.html
2. http://code.google.com/soc/
=== Enhance Anaconda to Enable Repositories As Needed ? ===
Jud Craft reported[1] that installing from the Fedora 10 DVD with the
fedora-updates repository enabled resulted in a broken NetworkManager
due to a missing dependency on libudev.so.0. Jud pointed out[2] that
although he could install the missing library from the DVD the situation
would present a serious problem to anyone that tried "[...] a network
install with updates [...] the result (a system without network access)
can't be fixed without A) network access, or B) another Fedora image
(also possibly requiring more network access)."
In answer to Jef Spaleta's questions Jud revealed[3] that:
"[libudev.so.0] doesn't seem to actually be installed by the stock F10
image. If I do a plain install (no updates), NetworkManager works fine.
Running a `yum update' then pulls down all the updates, as well as
`Install libudev0'. So at some point I suppose NetworkManager picked up
a dependency on libudev0, but for some reason updating during the
installation process doesn't pull this new package in." Kevin Kofler[4]
and Jesse Keating[5] both pointed out that: "[T]he updates repo isn't
the Everything repo. To really do a proper install with updates you have
to enable both the Updates repo and the Everything repo." Kevin added
that this was why the install from DVD with updates enabled was not an
officially supported method.
Several people, including Thorsten Leemhuis, suggested[6] that modifying
the anaconda installer to be aware of which repositories depend on each
other would be useful. Jesse Keating was[7] not averse to the idea as
long as it could be done in a "[...] distro agnostic way. Avoiding
hardcoded hacks specifically for Fedora is one of the goals of anaconda
upstream."
Later Jeremy Katz explained[8] that the thinking behind the installer
ignoring unsatisfiable dependencies in such cases is to "[...] get
someone installed and then let them clean up afterwards[.]"
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00921.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00929.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00938.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00944.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00947.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00953.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00955.html
8.
http://://www.redhat.com/archives/fedora-devel-list/2009-March/msg00976.html
=== Password Resets and Inactive Accounts ===
When Mike McGrath was perturbed[1] that so many FAS account holders had
failed to reset their passwords recently a discussion of the
entanglement of active account status and passwords followed.
Many respondents posted that they had received the email notifications
but had not needed to, or had not had time to, perform their password
reset.
Tom Lane worried that forcing periodic password resets caused people to
weaken security by writing down their passwords but Bruno Wolf III
argued[2] that a potentially bigger threat might be "[...] someone
forging messages from Mike with deceptive URLs that trick people into
changing their passwords using a hostile proxy. Doing things in the
current manner is training people to get fooled." He added that
cryptographically signing the reset messages was important.
Till Maas requested[3] consistent titling of the password reset
notification emails, suggested extending the grace period beyond two
weeks and asked that the notification contains the information that the
contents of the user's fedorapeople.org home would be moved.
Mike McGrath and others explored[4] possible grace periods and numbers
of warning emails.
Patrice Dumas asked why there was a password reset at all and was
answered[5] by Jesse Keating that it was "[...] the best way Infra has
today to discover all the active and inactive accounts." In response
Toshio Kuratomi pointed[6] to an open ticket which nominally deals with
how long accounts should be left open if passwords have expired but had
become[7] an investigation of how account inactivity can be determined.
After Mike McGrath explained that "[...] we've got thousands of
contributors, relatively few of them actually commit to cvs. So we could
go around to figure out how to make all of our various auth points
report back but that's a lot of work. The account system is the only
common point of entry for every contributor [...]" Christopher Aillon
suggested[8]: "So let's require to them to simply _log in_ to FAS to
reset the timer (you need to do that to change passwords, anyway!)."
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00509.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00612.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00710.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00779.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00658.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00677.html
7. http://fedorahosted.org/fedora-infrastructure/ticket/1237
8.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00812.html
=== Mono Conflagration Jumps to Blog ===
Following the FESCo decision not to replace rhythmbox with banshee as
the default media-player in Fedora 11[1] some follow-up clarifications
were made by parties to the discussion and the conflagration jumped
between @fedora-devel and the personal blog of David Nielsen, the
Banshee ex-maintainer and perhaps the main force behind the Mono SIG[2].
Bill Nottingham put forward[3] a concise time-line which attempted to
show that the proposal had been handled in a straightforward and usual
manner. Bill noted that the Desktop SIG had expressed[4] a lack of
enthusiasm early in the process and that the imminent beta-freeze meant
that the decision had to be taken without further prolonged discussion.
AdamWilliamson suggested[5] that because Mono's Microsoft links worried
many F/OSS developers it would have been a good idea to address such
concerns: "[...] explicitly rather than just pretend they don't exist in
your initial proposal (the word 'Mono' does not actually occur a single
time in the initial version of the Wiki page you posted)."
A question put by Jóhann B. Guðmundsson wondered[6] whether there was
anything preventing the Mono SIG from creating their own Fedora spin in
which banshee was given pride of place as the default media-player. Rex
Dieter confirmed that there were no obstacles on this path.
A proposal to adopt a Code of Conduct modeled upon Ubuntu's was[7] made
by Richard W.M. Jones. He also expressed regret that David was leaving
Fedora and apparently moving to Ubuntu as referenced[8] by a blog entry.
Reading the blog suggest that Foresight Linux seems more to David's
taste although one comment does point out[9] that Ubuntu "[...] head
community people have been calling for volunteers to increase the work
surrounding Mono and have a huge love for banshee[10] and Canonical
isnt anti-mono since some of their new job postings desire Mono as a
skill[11]."
Seth Vidal was[12] among those who wondered specifically how such a code
could be enforced and also where specifically the Fedora Project could
be alleged to have engaged in misconduct on this issue. Reading David's
blog seems to suggest both that any rudeness was privately exchanged and
that his perception is[13] that "[...] Mono isn't welcome in Fedora, and
will always be a second class citizen[.]"
1.
http://fedoraproject.org/wiki/FWN/Issue166#Fedora_11_Default_Mediaplayer_...
2. http://fedoraproject.org/wiki/SIGs/Mono
3.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00529.html
4.
http://www.redhat.com/archives/fedora-desktop-list/2009-February/msg00063...
5.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00526.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00523.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00498.html
8.
http://davidnielsen.wordpress.com/2009/03/07/drawing-my-own-conclusion/
9.
http://davidnielsen.wordpress.com/2009/03/07/drawing-my-own-conclusion/#c...
10.
http://castrojo.wordpress.com/2009/01/11/monodevelop-rockstar-needed-inqu...
11. http://webapps.ubuntu.com/employment/canonical_GDOS/
12.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00504.html
13.
http://davidnielsen.wordpress.com/2009/03/07/drawing-my-own-conclusion/#c...
=== Documentation Betas ===
John J. McDonough posted[1] that owners of major features should review
the Beta release notes. Scott Radvan posted[2] that the Security
Guide[3] would benefit from the scrutiny of any interested @fedora-devel
readers.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00835.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00823.html
3. http://sradvan.fedorapeople.org/Security_Guide/en-US/
=== Provenpackager Re-Seed ===
Jon Stanley asked[1] that everyone read the process by which the
"provenpackager" group will be repopulated.
A request by Ralf Corsepius for some definitions led Patrice Dumas to
post[2] that: "provenpackagers are people who can change all the
packages with opened ACLs. Sponsors are the people who can accept new
contributors in fedora." Further discussion led[3] Michael Schwendt to
voice a concern that non-responsive maintainers might be shielded from
feedback if provenpackagers step in to update and upgrade packages.
Kevin Kofler offered[4] the non-responsive maintainer process as a way
to rectify any problems with Bugzilla tickets being ignored.
Michael Schwendt questioned[5] Patrice Dumas in greater detail as to why
provenpackagers and sponsors are not equal sets.
Further details on how to apply to FESCo to become a provenpackager were
elicited[6] from JoshBoyer by Stepan Kaspal.
In a separate thread MichelSalim asked[7] about the preferred way to
become a sponsor.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00555.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00571.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00581.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00718.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00591.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00594.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00871.html
=== Closing Bugs NEXTRELEASE ===
Christoph Wickert requested[1] that all maintainers (and especially Red
Hat developers) would "[p]lease fix your bugs [1] in the release they
were filed against instead of just closing them NEXTRELASE!"
When Rahul Sundaram responded that it depended on the seriousness of the
bug and complexity of back-porting Daniel P. Berrange[2] and Rakesh
Pandit[3] acknowledged that such complex cases might exist but that
suggested that this was often a cop-out which could discourage users.
Jeremy Katz responded[4] "[...] as the person who has apparently pissed
you off this morning [...]" and described the case in point as much more
complex than Christoph had claimed. It seemed that Christoph's ability
to create LiveCD images of Fedora 11 using Fedora 10 as the development
platform had been stymied by changes to syslinux. Jeremy added that even
if this single change were reverted Christoph would need a newer kernel
and squashfs-tools and more.
Later Jeremy clarified[5] that the combination of livecd-creator + mock
were complicated by SELinux but that this had been addressed by recent
work.
One complication is that Bodhi uses NEXTRELEASE even for updates to
stable releases. After some confusion on this point LukeMacken posted[6]
that anyone wanting to change the behavior should file a ticket.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00552.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00575.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00572.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00622.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00777.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00672.html
== Artwork ==
In this section, we cover the Fedora Artwork Project.
http://fedoraproject.org/wiki/Artwork
Contributing Writer: Nicu Buculei
=== Theme Song ===
Subodh Bhagat proposed[1] a new artistic initiative: a Fedora theme
song. Subodh asked: "Do we have something like a theme song for fedora?
Either lyrics or a composition?" The intitiative was saluted by
Konstantinos Antonakoglou[2]: "Sounds great! I got some music skills
(compose and play) too", Henrik Heigl[3]: "I also think of ideas like a
contest", Paul Frields[4]: "I think song in general is a great idea. I'm
a musician myself and an appreciator of songwriters", and Keiran
Smith[5] all of whom have experience in the field.
1.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00060.html
2.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00062.html
3.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00064.html
4.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00065.html
5.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00068.html
=== Artwork for the Beta Release ===
In preparation for the upcoming Beta release, Paolo Leoni started[1] the
work on a website banner by proposing two graphic concepts, a generic
one and another based on the graphics for the Beta wallpaper image "The
first is a non-themed version, while the second uses a part of Mo's
wallpaper mockup." The general opinion was favourable to the themed
version and after a few iterations, Máirín Duffy concluded[2] with a
final version[3], a graphic which all the Fedora enthusiast are invited
to use on their blogs.
On a related note, Paul Frields reviewed[4] the Art's Team release
tasks[5] and produced a short list "the listed splashes, headers and
other art scheduled for March 27 includes" to check the status "Is the
listed date of March 27 enough time to produce these various
derivations?"
1.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00072.html
2.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00088.html
3.
http://fedoraproject.org/wiki/Image:Deepsky-fedora11-beta-banner_2d.png
4.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00075.html
5. http://poelstra.fedorapeople.org/schedules/f-11/f-11-art-tasks
== Virtualization ==
In this section, we cover discussion on the @et-mgmnt-tools-list,
@fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora
virtualization technologies.
Contributing Writer: Dale Bewley
=== Enterprise Management Tools List ===
This section contains the discussion happening on the et-mgmt-tools list
==== New Release virt-manager 0.7.0 ====
Cole Robinson announced[1] a new
image:Echo-package-16px.pngvirt-manager[2] release, version 0.7.0.
Virtual Machine Manager provides a graphical tool for administering
virtual machines for KVM, Xen, and QEmu. Start, stop, add or remove
virtual devices, connect to a graphical or serial console, and see
resource usage statistics for existing VMs on local or remote machines.
Uses image:Echo-package-16px.pnglibvirt as the backend management API.
New features:
* Redesigned 'New Virtual Machine' wizard (Jeremy Perry, Tim Allen,
Cole Robinson)
* Option to remove storage when deleting a virtual machine.
* File browser[3] for libvirt storage pools and volumes, for use
when attaching storage to a new or existing guest.
* Physical device assignment (PCI, USB) for existing virtual
machines.
* Bug fixes and minor improvements.
1.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00058.html
2. http://virt-manager.org/
3.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00045.html
==== New Release virtinst 0.4.3 ====
Cole Robinson announced[1] a new
image:Echo-package-16px.pngpython-virtinst release, version 0.400.3.
virtinst is a module that helps build and install libvirt based virtual
machines. It currently supports KVM, QEmu and Xen virtual machines.
Package includes several command line utilities, including virt-install
(build and install new VMs) and virt-clone (clone an existing virtual
machine).
This is largely a bug fix release.
1.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00057.html
=== Fedora Xen List ===
This section contains the discussion happening on the fedora-xen list.
==== dom0 Kernel: Better, Still Not Ready ====
Itamar Reis Peixoto reported[1] success with Michael Young's latest
image:Echo-package-16px.pngkernel build[2] and wondered when it could be
released.
Michael explained, "The current plan is to wait until basic dom0 support
makes it into the vanilla kernel, which should happen for 2.6.30, and
then decide if dom0 can be enabled and if the patches for full dom0
support can safely be added without affecting ordinary operation."
"At the moment there are still things that are broken such as X support
in some cases, and there are also Fedora patches that have been omitted
because they were tricky to merge, so it is too early to start adding
dom0 support to official Fedora kernels."
1.
http://www.redhat.com/archives/fedora-xen/2009-March/msg00046.html
2. http://koji.fedoraproject.org/koji/taskinfo?taskID=1238587
==== Missing Hypervisor Capabilities Restored ====
There was progress on a bug discovered[1] last week. This missing file
/sys/hypervisor/properties/capabilities has been restored[2], however a
bug[3] remained[4] in libvirt or virt-install.
1.
http://fedoraproject.org/wiki/FWN/Issue166#dom0_Kernel_Inches_Closer
2.
http://www.redhat.com/archives/fedora-xen/2009-March/msg00039.html
3. https://bugzilla.redhat.com/show_bug.cgi?id=489799
4.
http://www.redhat.com/archives/fedora-xen/2009-March/msg00040.html
=== Libvirt List ===
This section contains the discussion happening on the libvir-list.
==== Snapshot Support Discussed ====
In an attempt to make it easier to backup KVM windows guests, Matt
McCowan created[1] a checkpoint virsh function. "Modelled on the
virDomainSave[2] function it takes an optional script which it will
execute (and pass the name of the domain as an argument) while the
domain is paused, then resume the domain." Within this script, a backup
of the guest domain could be created.
The patch was seen as too ad-hoc, and not accepted as-is.
Daniel Veillard commented[3] "I think this can help administrators in a
controlled situation, but I'm hoping a real snapshotting API will be
possible at some point where image:Echo-package-16px.pnglibvirt goes
though the list of storage resources used by the domain and properly
make a snapshot using a storage API or return an error if that's not
possible."
Daniel P. Berrange described[4] what he would like to see. "In terms of
API I think I'd like to see snapshotting[5] available as part of a more
generic save/restore API. I tend to think of the current API as
providing 'unmanaged save/restore'". Libvirt does not track saved
images, so does not know if a snapshot is available to be started at the
restart of libvirtd."
"Thus I think the first step towards a general snapshot facility would
be to provide an API for 'managed save/restore' where we explicitly
track saved images." "With this, you could configure libvirtd, so that
when starting up, it" would "see if the guest was suspended before the
previous host shutdown, and if so, then restore from that saved image
automatically.[6] Or make it skip autostart completely, if any save
images exist, and allow an admin defined initscript to do auto restore
from the save image."
1.
http://www.redhat.com/archives/libvir-list/2009-March/msg00177.html
2. http://libvirt.org/html/libvirt-libvirt.html#virDomainSave
3.
http://www.redhat.com/archives/libvir-list/2009-March/msg00199.html
4.
http://www.redhat.com/archives/libvir-list/2009-March/msg00205.html
5. http://wiki.libvirt.org/page/TodoVMSnapshots
6. http://wiki.libvirt.org/page/TodoDaemonRestart
==== Memory Ballooning Support for QEMU ====
Daniel Berrange patched[1] the libvirt QEMU driver to fully support
memory ballooning. "Memory ballooning allows you to have your guest
dynamically change its memory usage by evicting unused memory during
runtime. This is a useful feature because it reduces the impact your
guest can have on memory usage of your host by giving up unused memory
back to the host."[2]
1.
http://www.redhat.com/archives/libvir-list/2009-March/msg00200.html
2.
http://www.linux-kvm.com/content/memory-ballooning-feature-coming-soon-kvm
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
15 years, 1 month
- 1
- 0
FWN #167 status
by Oisin Feeley
Hi all,
Marketing, Development, Artwork and QA have turned in beats which I've
edited. I'll be around tomorrow (Monday) to get the issue out and look
forward to the usual great contributions.
Best,
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
15 years, 1 month
- 2
- 3
167 qa beat draft up
by Adam Williamson
As usual, my first draft of the beat can be used as-is if no more
modifications occur to me before sunday :) thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
15 years, 1 month
- 1
- 0
next week
by Max Spevack
I won't be able to do the Announcements beat next week. Can someone
cover it for me?
Thanks,
Max
15 years, 1 month
- 2
- 3
Translation Beat takes a break for #167
by Runa Bhattacharjee
Hello,
I would be traveling this week and would not be able to update the
Translation Beat.
Thanks
Runa
15 years, 1 month
- 2
- 1
Can I correct something in 166, or should I wait?
by Larry Cafiero
Hey, all --
I didn't get something quite right in the RIT story in the Ambassadors
report. Is this something I can fix in this edition or should I just correct
it in the next one?
Larry Cafiero
15 years, 1 month
- 2
- 2
Fedora Weekly News #166
by Oisin Feeley
Fedora Weekly News Issue 166
Welcome to Fedora Weekly News Issue 166 for the week ending March 8th,
2009.
http://fedoraproject.org/wiki/FWN/Issue166
A small sample of this issue's stories reflects the imminent release of
Fedora 11! Announcements lists the freeze dates and upcoming Fedora
events. PlanetFedora rounds up essential blog reading including a piece
by Thomas Vander Stichele on "meltdown analysis". Marketing cheers for
"One Million New Fedora 10 Installations". In QualityAssurance a
reminder that the next of the "Test Days" is of interest to Intel video
users is just one of the items reflecting a massive amount of QA
activity. Ambassadors relates some OLPC news from Rochester Institute of
Technology. Developments explains why "Orphans are Purged" and asks are
we "Ready for a New RPM Version?". Translation highlights a "Study about
FLP". Artwork stares at the wallpaper while "Preparing for the Beta
Release". SecurityAdvisories lists stuff to help you avoid a rooting.
Virtualization pops some salient items out of the development maelstrom
including a "New Release of libvirt-0.6.1" and SELinux "sVirt Support
Committed". There's a lot more, so keep reading!
If you are interested in contributing to Fedora Weekly News, please see
our 'join' page[1]. We welcome reader feedback:
fedora-news-list(a)redhat.com
FWN Editorial Team: Pascal Calarco, Oisin Feeley, Huzaifa Sidhpurwala
Table of Contents
1 Fedora Weekly News Issue 166
1.1 Announcements
1.1.1 Fedora 11
1.1.2 Upcoming Events
1.1.2.1 FUDCon Berlin 2009
1.2 Planet Fedora
1.2.1 General
1.2.2 Education
1.3 Marketing
1.4 Marketing Meeting Log for 2009-02-26
1.5 One Million New Fedora 10 Installations!
1.6 Marketing Meeting Log for 2009-03-03
1.7 Ambassadors
1.7.1 RIT Pitches in on OLPC Project
1.7.2 Fedora at CUE
1.7.3 Got Ambassador News?
1.8 QualityAssurance
1.8.1 Test Days
1.8.2 Weekly Meetings
1.8.3 Bugzappers Wiki Re-organization
1.8.4 20 Second Boot Test Day Follow-up
1.8.5 Bugzappers Meeting Schedule
1.8.6 Ubuntu Triage Discussion
1.8.7 Introduction Emails
1.9 Developments
1.9.1 Orphans are Purged
1.9.2 Fedora 11 to Ship Tiger VNC
1.9.3 Ready for a New RPM Version ?
1.9.4 Windows Cross-compiler Added to comps.xml
1.9.5 Anaconda Default of Separate / and /home Partitions
1.9.6 Beta Freeze and String Freeze this Tuesday
2009-03-10
1.9.7 Fedora 11 Default Mediaplayer Not Banshee. Mono to
Blame ?
1.10 Translation
1.10.1 FLP Infrastructure Team Meeting
1.10.2 Statistics Page and Submission Outage
1.10.3 Publican Documents Now on tfp.org
1.10.4 F11 String Freeze Reminder
1.10.5 Study about FLP
1.10.6 New Members in FLP
1.11 Artwork
1.11.1 Echo Weekly News
1.11.2 Preparing for the Beta Release
1.11.3 Working on the Picture Book
1.12 Security Advisories
1.12.1 Fedora 10 Security Advisories
1.12.2 Fedora 9 Security Advisories
1.13 Virtualization
1.13.1 Enterprise Management Tools List
1.13.1.1 Managing Guest OS Types
1.13.1.2 virt-manager Storage Removal
1.13.1.3 virt-install Host Device Assignment Support
1.13.2 Fedora Virtualization List
1.13.2.1 User Interface Makeover for virt-manager
1.13.2.2 New Release virtinst 0.4.2
1.13.3 Fedora Xen List
1.13.3.1 dom0 Kernel Inches Closer
1.13.4 Libvirt List
1.13.4.1 New Release libvirt 0.6.1
1.13.4.2 sVirt Support Committed
1.13.4.3 Secure Guest Migration Between Hosts
1.13.4.4 Hynesim Project Interest in Libvirt
== Announcements ==
In this section, we cover announcements from the Fedora Project.
http://www.redhat.com/archives/fedora-announce-list/
http://www.redhat.com/archives/fedora-devel-announce/
https://fedoraproject.org/wiki/FedoraEvents
Contributing Writer: Max Spevack
=== Fedora 11 ===
Jesse Keating reminded[1] the community that the Fedora 11 Beta
freeze[2] is coming this week. "It is scheduled for Tuesday, March 10th.
They way we've historically enacted the beta freeze is to tag the
content in that day's rawhide into the freeze tag. That is, what gets
reported as rawhide-20090310 is the frozen content. As such, your builds
need to be complete by 0600 UTC March 10 2009 in order to be in the
Beta, without a special request."
The string freeze is also on March 10th.
1.
http://www.redhat.com/archives/fedora-devel-announce/2009-March/msg00006....
2. https://fedoraproject.org/wiki/Beta_Freeze_Policy
=== Upcoming Events ===
March 10-12: FOSE[1] in Washington, DC.
March 13-15: Chemnitzer Linux Tage[2] in Chemnitz, Germany.
1. http://fose.com/
2. https://fedoraproject.org/wiki/FedoraEvents/CLT
=== FUDCon Berlin 2009 ===
FUDCon Berlin[1] will be held from June 26 - 28 in Berlin, Germany.
1. https://fedoraproject.org/wiki/FUDConBerlin2009
== Planet Fedora ==
In this section, we cover the highlights of Planet Fedora - an
aggregation of blogs from Fedora contributors worldwide.
http://planet.fedoraproject.org
Contributing Writer: Adam Batkin
=== General ===
Michael DeHaan responded[1] to a post[2] by Karsten Wade from a few
weeks ago titled "Failure as the secret of success". Michael agreed and
argued that it is usually impossible to build a piece of software that
is 100% perfect for 100% of its users. "Failure is good. Chasing perfect
is bad. Making any one aspect perfect or spending too much time on it
tends to make other aspects of things bad. We need to get close enough
and find some new challenge to work on, so we have more time to iterate
and fail a few more times. We all need more time to fail."
Thomas Vander Stichele described[3] "an approach to doing meltdown
analysis". Also known as a post-mortem analysis, this is a useful
process for "when we've gotten into a bad situation involving multiple
people that we want to learn from and avoid next time".
Harald Hoyer summarized[4] the results from the 20 Seconds Boot Feature
Test Day and offered some suggestions for users and developers alike.
Matthew Daniels offered[5] some ideas to improve the Fedora
documentation by splitting the User Guide into three parts, Practicum,
Theory and Appendices & Glossary.
Mark J Cox published[6] a set of metrics that tracks security
vulnerabilities and the time-to-fix versus their time of disclosure
within RHEL.
John J. McDonough wrote[7] an article about Fedora, the four Foundations
of the project/community and how and why you should join.
Richard Hughes explained[8] some of the issues currently associated with
installing Applications as opposed to Packages (first by explaining the
difference between the terms Application and Package). Along with some
other folks, they published a proposed specification[9] that is
distribution-agnostic and should allow relevant metadata (including
localized content) as well as icons to be efficiently and easily
integrated into the local/distribution-specific software installation
utility.
Scott Williams made[10] The Case for Open Source.
Paul W. Frields announced[11] that after working with the Red Hat legal
department to revise the Fedora Trademark guidelines, a new version has
been released. Among other changes the changes should make building
remixes and unofficial spins easier.
Chitlesh Goorah posted[12] about the goals of Fedora Electronic Lab[13]
(FEL) and also how the project bridges the Open Source software and
hardware communities.
1. http://www.michaeldehaan.net/?p=879
2. http://iquaid.org/2009/02/28/failure-as-the-secret-of-success/
3. http://thomas.apestaart.org/log/?p=783
4.
http://www.harald-hoyer.de/personal/blog/20_Seconds_Boot_Feature_Test_Day
5.
http://danielsmw.wordpress.com/2009/03/03/user-guide-practicum-theory/
6. http://www.awe.com/mark/blog/2009030319.html
7. http://wb8rcr.multiply.com/journal/item/98/Join_Fedora
8. http://blogs.gnome.org/hughsie/2009/03/05/application-installing/
9.
http://cgit.freedesktop.org/packagekit/plain/docs/app-install-v1.draft
10.
http://vwbusguy.wordpress.com/2009/03/05/the-case-for-open-source/
11. http://marilyn.frields.org:8080/~paul/wordpress/?p=1507
12.
http://clunixchit.blogspot.com/2009/03/fels-solutions-for-design-centre.html
13. http://chitlesh.fedorapeople.org/FEL/
=== Education ===
Greg DeKoenigsberg started[1] working on a Sugar activity for 4th Grade
Maths[2] called "Dungeons of Mongo". Remember, you too can potentially
get a free XO as part of the Fedora Developers XO Program[3].
Chris Tyler announced[4] that the TeachingOpenSource.org[5] is open for
business, "a neutral collaboration point for everyone and everything
involved in Teaching Open Source".
Greg DeKoenigsberg congratulated[6] Chris on the new Teaching Open
Source community and provided some points that came up while visiting
with people who are in the trenches trying to teach Open Source. Chris
responded[7] and suggested that anyone interested should join[8] the
mailing list.
(As a related sidenote, Teaching Open Source has its own Planet[9] for
those interested)
Karsten Wade described [10] some of the issues associated with getting
kids interested in computers, Open Source and issues with the US
educational system in general.
Rangeen Basu Roy Chowdhury wrote[11] about a "visit to a high school in
a village located on the outskirts of Durgapur and made famous by the
DGPLUG project . This project set up a computer lab in a village school
where you don't even get proper drinking water and where none of the
students would have never had a chance of so as to even see a computer
if not for this project."
1. http://gregdek.livejournal.com/47069.html
2. http://sugarlabs.org/go/User:Gdk/4th_Grade_Maths
3. https://fedoraproject.org/wiki/Fedora_developers_XO_program
4.
http://blog.chris.tylers.info/index.php?/archives/190-TeachingOpenSource....
5. http://teachingopensource.org/
6. http://gregdek.livejournal.com/47357.html
7.
http://blog.chris.tylers.info/index.php?/archives/191-TeachingOpenSource....
8.
http://teachingopensource.org/index.php/TeachingOpenSource_Mailing_List
9. http://teachingopensource.org/index.php/Planet
10. http://iquaid.org/2009/03/06/stumbling-around-in-the-k-12-space/
11. http://sherry151.blogspot.com/2009/03/blooming-bijra.html
== Marketing ==
In this section, we cover the Fedora Marketing Project.
http://fedoraproject.org/wiki/Marketing
Contributing Writer: Kam Salisbury
=== Marketing Meeting Log for 2009-02-26 ===
The meeting log[1] of the February 26th 2009 Fedora Marketing Meeting is
now available.
1. http://fedoraproject.org/wiki/Marketing_meeting_2009-02-26
=== One Million New Fedora 10 Installations! ===
Paul W. Frields, Fedora project leader, declared that there has been "a
major up-tick in Fedora involvement over the last 6 months. Since the
release of Fedora 10, we've seen about 1 million new installations and
approximately 2 million unique visitors to fedoraproject.org each
month"[1]
1.
http://blogs.computerworld.com/fedora_10_regains_linux_fans?page=1
=== Marketing Meeting Log for 2009-03-03 ===
The meeting log[1] of the March 3rd 2009 Fedora Marketing Meeting is now
available.
1.
http://fedoraproject.org/wiki/Meeting:Marketing_meeting_2009-03-03
== Ambassadors ==
In this section, we cover Fedora Ambassadors Project.
http://fedoraproject.org/wiki/Ambassadors
Contributing Writer: Larry Cafiero
=== RIT Pitches in on OLPC Project ===
The Fedora OLPC project seems to have found a friend at Rochester
Institute of Technology[4]. Fedora Ambassador Karlie Robinson contacted
RIT professor Stephen Jacobs and discussed the project, which spurred
Jacobs' interest in doing a class around the XO.
Karlie brought Professor Jacobs up to speed on what Fedora is doing
around the XO[5], where Fedora is providing XOs to those who will do
development work. The deal revolved around getting XOs for Jacobs
classroom in exchange for the RIT students working on Greg
DeKoenigsberg's 4th Grade Math project[1].
So RIT students got XOs and the project got some more help.
1. https://fedoraproject.org/wiki/Marketing_meeting_2009-02-26
2.
http://blogs.computerworld.com/fedora_10_regains_linux_fans?page=1
3.
https://fedoraproject.org/wiki/Meeting:Marketing_meeting_2009-03-03
4. http://wiki.laptop.org/go/OLPC_Rochester,_NY
5.
http://www.redhat.com/archives/fedora-olpc-list/2009-February/msg00033.html
=== Fedora at CUE ===
Karsten Wade represented Fedora at last week's Computer-Using Educator
(CUE) conference in Palm Springs, California. Karsten gave a talk about
the advantages of bringing a culture of participation to the classroom.
A detailed report of what happened at CUE can be picked up at Karsten's
blog[1], specifically the items entitled "Stumbling around in the K-12
space" and "Moodle as a killer K-12 app."
1. http://iquaid.org/
=== Got Ambassador News? ===
Any Ambassador news tips from around the Fedora community can be
submitted to me by e-mailing lcafiero-AT-fedoraproject-DOT-org and I'd
be glad to put it in this weekly report.
== QualityAssurance ==
In this section, we cover the activities of the QA team[1].
Contributing Writer: Adam Williamson
1. http://fedoraproject.org/wiki/QA
=== Test Days ===
This week's regular test day[1] was on the rewritten handling of storage
devices in Anaconda[2]. Dave Lehman, Chris Lumens and Joel Granados were
the developers present. Several people showed up and provided valuable
testing in a wide range of scenarios, and the developers were able to
identify and resolve several bugs. Further testing in this area is still
very helpful. The wiki page contains instructions for using a
supplementary image while installing Rawhide, to use the new storage
code successfully, but the code will soon be available directly in
Rawhide, so testing can be performed simply by attempting to install
Rawhide in as many different storage scenarios as possible.
Next week's test day[3] is tentatively scheduled for testing Intel
graphics devices, especially the new kernel mode setting support and
identifying performance regressions from Fedora 10. It will be held on
Thursday (2009-03-12) in the #fedora-qa channel on Freenode IRC. If you
use an Intel graphics card, please come by to help make sure it will be
well-supported in Fedora 11 - the more testing, the better the code!
1. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-05
2. http://fedoraproject.org/wiki/Features/AnacondaStorageRewrite
3. http://fedoraproject.org/wiki/QA/Test_Days/2009-03-12
=== Weekly Meetings ===
The QA group weekly meeting[1] was held on 2009-03-04. The full log is
available[2]. Will Woods pointed out that the next week's meeting would
be an hour earlier for most people, after the onset of Daylight Savings
Time. Adam Williamson and Jesse Keating, as the resident West Coast
representatives, led a revolt against having to wake up at 7 a.m., and
the group agreed to move the meetings to 1700UTC from 2009-03-11.
James Laska reported on the progress of the project to make the Semantic
test result plugin for mediawiki available. He reported that he is
currently trying to make the plugin work in his test setup prior to
building a Fedora package for it, as the infrastructure group requires
all software used for Fedora systems be available as a Fedora package.
Adam Williamson offered to help with the packaging.
Will Woods and Jesse Keating reported that there had been no progress on
the autoqa systems this week, as Jesse had been tied up doing the mass
rebuild of Rawhide.
Will Woods reported that 33 of the Fedora 11 proposed features[3] have
not yet been reviewed by the QA group to ensure that they include a
workable test plan, and appealed for help from the group in getting this
process completed. He noted that features for which test days have
already taken place are likely to have workable test plans in place, as
these are generally necessary for a test day to happen, so suggested at
least those features could be quickly reviewed and, most likely,
approved.
Adam Williamson reported that the test day for the new nouveau driver[4]
for NVIDIA hardware was already planned and prepared, but that he was
waiting on developer replies for the planned Intel KMS[5] and automatic
fonts and MIME installer[6] test days. Jóhann Guðmundsson suggested
having a single big graphics test day, but Adam Williamson explained
that he did not want to do that as it would be too large and
unmanageable. James Laska suggested running the Piglit[7] OpenGL test
suite as part of the test days for drivers with usable 3D support
(radeon and intel).
Jesse Keating reported that the mass rebuild of Rawhide was complete.
Adam Williamson pointed out that three large bugs had resulted from GCC
4.4 optimization problems after the rebuild, and Will Woods reported
that this had been discussed during the release engineering meeting.
Will noted that the new hashing system in RPM was not backwards
compatible, the upshot being that those upgrading from Fedora 11 Alpha
to current Rawhide need to run 'yum update rpm' first. He queried why
yum did not automatically update itself and rpm before other packages,
and Jesse Keating explained it was because this would usually bring in
hundreds of other packages via Python and glibc dependencies in any
case, and so was not worth the effort.
Jesse Keating reported that live CD image builds from current Rawhide
were not working very well, and Anaconda is often broken while its
developers are busy working on the storage rewrite and EFI features.
The Bugzappers group weekly meeting[8] was held on 2009-03-03. The full
log is available[9]. The group agreed to make sure the two most
important Greasemonkey scripts for triagers were easily available in a
central place, and this was implemented by making them available
directly from the Wiki Tools page[10].
The group discussed Christopher Beland's plan to re-organize the Wiki
area. It was agreed that a mailing list discussion should take place to
create and agree upon a new front page for the Bugzappers wiki area, and
work could then progress on re-writing and re-arranging other pages
based on the organization system set up by the new front page. The group
also discussed and agreed upon a plan for revising the Components
page[11], and Christopher Beland pointed out that the current bug flow
diagram is incorrect, as it dates from before NEEDINFO was converted
from a bug status into a flag. Edward Kirk bravely volunteered to fix
the picture.
Finally, the group discussed creating SOPs (Standard Operating
Procedures) for Bugzappers, along the lines of those already used by the
Infrastructure group. John Poelstra proposed the first SOP cover the
procedure for gaining membership in the Bugzappers, and further proposed
that it should involve the prospective new member posting a
self-introduction email to the mailing list. Christopher Beland and
Edward Kirk opposed this as they were worried that some new members
would not feel comfortable posting such a message, particularly if it
contained personal information. The group agreed to discuss the proposal
further on the mailing list.
The next QA weekly meeting will be held on 2009-03-11 at 1700 UTC (note
changed time, in UTC reference frame) in #fedora-meeting, and the next
Bugzappers weekly meeting on 2009-03-10 at 1500 UTC in #fedora-meeting.
1. http://fedoraproject.org/wiki/QA/Meetings
2.
http://wwoods.fedorapeople.org/fedora-qa/fedora-qa-20090304.log.html
3. http://fedoraproject.org/wiki/Releases/11/FeatureList
4. http://fedoraproject.org/wiki/Features/NouveauAsDefault
5. http://fedoraproject.org/wiki/Features/IntelKMS
6. http://fedoraproject.org/wiki/Features/AutoFontsAndMimeInstaller
7. http://people.freedesktop.org/~nh/piglit/
8. http://fedoraproject.org/wiki/BugZappers/Meetings
9.
http://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2009-Mar-03
10. https://fedoraproject.org/wiki/BugZappers/Tools
11. https://fedoraproject.org/wiki/BugZappers/Components
=== Bugzappers Wiki Re-organization ===
Christopher Beland made several proposals[1] on reorganizing the
Bugzappers wiki area. This prompted a long discussion. In the end,
Christopher was asked to provide drafts for several of his proposed
changes for the group to evaluate. Both Christopher and Edward Kirk
provided drafts for a new front page. Adam Williamson commented[2] that
both drafts had good elements, and offered to create a new draft to try
and combine the two.
1.
http://www.redhat.com/archives/fedora-test-list/2009-February/msg01223.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00290.html
=== 20 Second Boot Test Day Follow-up ===
Harald Hoyer posted a follow-up email[1] on the previously-held 20
Second Boot test day[2], pointing to a blog post[3] where he summarized
all the useful data he was able to get from the test day.
1.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00057.html
2. https://fedoraproject.org/wiki/QA/Test_Days/2009-02-19
3.
http://www.harald-hoyer.de/personal/blog/20_Seconds_Boot_Feature_Test_Day
=== Bugzappers Meeting Schedule ===
Lalit Dhiri proposed[1] having a second meeting to accommodate those
whose schedules made it impossible for them to attend the regular group
meetings. Adam Williamson said[2] that was not likely to be practical,
but suggested that the meeting time could be moved if a time when more
group members would be able to attend could be identified. Susan Lauber
suggested[3] using the Wiki's meeting matrix template to handle
registering who is available when, and set up a Wiki page[4] for the
purpose.
1.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00131.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00155.html
3.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00165.html
4. https://fedoraproject.org/wiki/Bugzappers_meeting_matrix
=== Ubuntu Triage Discussion ===
Paul Frields pointed out[1] a long discussion on the topic of bug
triaging in Ubuntu[2], and wondered what the lessons for the Bugzappers
might be. Adam Williamson suggested that it showed it is important for
triagers to follow up on bugs they triage, rather than just touching
them once and then never returning, which can leave the reporter more
frustrated than if the bug had never been triaged at all. In the ensuing
discussion, John Summerfield suggested that triagers should try to cover
one area of which they had substantial knowledge rather than attempting
to cover all bugs in all components[3], and that the Bugzappers group
should remember actively to involve package maintainers in the triaging
process[4]. Kevin Kofler explained[5] that, within the KDE SIG,
maintainers and triagers do work together and communicate via IRC.
1.
https://www.redhat.com/archives/fedora-test-list/2009-March/msg00211.html
2. http://lwn.net/Articles/321473/
3.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00312.html
4.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00385.html
5.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00393.html
=== Introduction Emails ===
Adam Williamson mooted the proposal from the weekly meeting that
introduction emails be required for new group members[1]. John Poelstra
supported the proposal[2], as did Edward Kirk[3]. Christopher Beland
suggested[4]that anyone who became active on the mailing list but did
not write a formal self-introduction email should also be accepted.
1.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00266.html
2.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00314.html
3.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00319.html
4.
http://www.redhat.com/archives/fedora-test-list/2009-March/msg00341.html
== Developments ==
In this section the people, personalities and debates on the
@fedora-devel mailing list are summarized.
Contributing Writer: Oisin Feeley
=== Orphans are Purged ===
It sounded[1] like Dickensian cruelty when Jesse Keating announced that
he would be purging the orphans. All that it meant however was that
those packages which were not blocked and had no owners would be "[...]
blocked, and will not be shipped with F11." The initial list mistakenly
listed EPEL packages and a shorter revised list was posted[2].
A follow-up posted[3] states that packages listed therein will be
removed on 2009-03-09 unless volunteers are found to maintain them.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00093.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00103.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00474.html
=== Fedora 11 to Ship Tiger VNC ===
Adam Tkac wrote[1] to explain why he had decided "one minute before the
beta freeze" to replace TightVNC with the TigerVNC fork. Adam has a
history of very actively seeking to merge improvements upstream which in
the past led[2] to the replacement of RealVNC with TightVNC when it
seemed that the latter was more willing to evolve. The glacial pace of
RealVNC development seemed to be correlated with the presence of a
non-Free enterprise edition. Adam reported that unfortunately a lack of
co-ordination of the TightVNC project had led to the TurboVNC and
TightVNC projects deciding that a fork was necessary. An initial mail
posted[3] by PeterÅstrand on @tigervnc-users provides some more details.
One specific outcome anticipated[4] by KingInuYasha was a "[...] proper
implementations of VNC 4 for UNIX like systems [...] Having a VNC
implementation that actually is kept up to date with the VNC protocol
and is optimized with extensions is something I have been waiting for
awhile now."
Another hint of good things which may come from a more rapid pace of
development was revealed[5] when Daniel Berrange asked about Adam's
plans to include the VeNCrypt server-side SSL/TLS extension. This would
result in a "[...] consistent TLS extension that's inter operable across
all the VNC clients & servers in Fedora." Daniel also mentioned that he
had "[...] recently defined & implemented another VNC auth extension
based on SASL. This provides for a good extendable authentication
capability, most importantly including GSSAPI Kerberos for single sign
on. I've got it implemented for QEMU, KVM, GTK-VNC and VINO already, so
again it'd be good to plan for adding it to TigerVNC too so we have a
widely interoperable strong authentication system."
All in all it looks as though contrary to their slogan "The VNC that
bites" TigerVNC will be superb.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00213.html
2.
http://fedoraproject.org/wiki/FWN/Issue119#Baracuda_To_Replace_VNC_.3F
3.
http://sourceforge.net/mailarchive/forum.php?thread_name=alpine.LFD.2.00....
4.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00217.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00221.html
=== Ready for a New RPM Version ? ===
On 2009-02-26 Panu Matilainen asked[1] if it would be possible to
introduce RPM-4.7 at this late stage of the Fedora 11 release cycle.
This new version decreases memory use and improves performance. Panu
emphasized that it was not as large an upgrade as the "[...] 4.4.2.x ->
4.6.0 leap-of-faith upgrade last year [.]"
Bill Nottingham was among those who expressed concern that rpm-4.7 would
be completely ready for the final release of Fedora 11. He also wondered
if there would be incompatibilities with previous rpm version. Panu
answered[2] that rpm-4.7 was expected to be ready for the final release
and that incompatibilities would only result if packagers used the POSIX
file capabilities. This latter is protected against with an rpmlib()
dependency.
A certain amount of disquiet at the idea of "[g]oing with a beta version
of critical infrastructure like RPM [...]" based on the recent changes
to RPM was voiced[3] by Tom Lane. Upon a challenge from Seth Vidal some
problems with the process of upgrading rpm to handle stronger hashes
were listed[4] by Bill Nottingham. These included including "No solution
for handling packages natively on F9" and Tom Lane expanded[5] on the
point: "I'm personally still ticked off that I'm being forced to update
my development workstation to F-10 immediately in order to continue
doing useful work on rawhide packages. I don't have time for that right
now. Since F-9 is still supported, isn't it a management failing to have
allowed this to happen without a plan to make mock on F-9 work?" The
general response seemed to be that developers need to use one of the
virtual machine solutions in order to be able to build for rawhide.
A substantial sub-thread on the rate of change in rawhide and whether or
not developers should use it or stick to the current stable release with
a virtualized instance of rawhide developed[6] following some thoughts
from Adam Williamson.
RahulSundaram asked[7] for more information on the use of LZMA
compression as this is one of the new features of rpm-4.7. Panu
replied[8] LZMA will not be used by default as it would make even the
current Fedora 10 rpm unable to read packages produced with such
compression.
A FESCo decision made on 2009-03-06 confirmed[9] that rpm-4.7 would be
the version shipping in Fedora 11.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02117.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02161.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02134.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02142.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02146.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02213.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02156.html
8.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02173.html
9. http://bpepple.fedorapeople.org/fesco/FESCo-2009-03-06.html
=== Windows Cross-compiler Added to comps.xml ===
Following from a FESCo 2009-03-06 decision Richard W.M. Jones asked[1]
to add a "Windows cross-compiler" group to comps.xml before the rapidly
approaching 2009-03-10 string freeze.
Kevin Kofler asked why Richard did not call it "MinGW cross compiler"
and Richard responded[2] that he wanted to avoid trademarks and leave
open the possibility to broaden support to other non-embedded platforms.
He came up with either "Consumer cross-compilers (CCC) or Consumer
cross-compiler collection (CCCC)." Kevin had some other interesting
questions about the legality of possible OS X cross-compilers and the
desirability of one group per OS. Richard pointed[3] to an earlier
thread on the latter question.
=== Anaconda Default of Separate / and /home Partitions ===
A long-standing bugzilla entry was referenced[4] by Lex Hider as
background for the idea that anaconda should support separate /home and
/ partitions in order to support clean installs during upgrades. Lex's
detailed post included links to relevant previous discussion.
Adam Williamson was very much in favor of the idea and in response to
Jesse Keating suggested[5] some heuristics which might allow anaconda to
determine the relative sizes of the / and /home partitions. Bruno Wolff
III's / partition size (circa 40GB) proved[6] to be surprisingly large
due to multiple languages installed. Michel Salim[7] and Callum
Lerwick[8] both brought up the necessity to have a large / partition in
order to be able to run preupgrade.
Lex elaborated[9] on possible space requirements for such a scheme.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00365.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00384.html
3.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00397.html
4.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg01903.html
5.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg01960.html
6.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg01976.html
7.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02167.html
8.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02021.html
9.
http://www.redhat.com/archives/fedora-devel-list/2009-February/msg02356.html
=== Beta Freeze and String Freeze this Tuesday 2009-03-10 ===
Dennis Gilmore posted[1] a heads up on 2009-03-06 that "[...] anything
that needs translations needs to be done by COB [Tuesday]. This is a
blocking Freeze any packages you need included in the Beta release must
be requested via release engineering [.]"
A brief amount of confusion occurred[2] due to the misnaming of the day
of the week. Till Maas also wondered exactly what Close Of Business
meant exactly for an international project like Fedora.
1.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00430.html
2.
http://www.redhat.com/archives/fedora-devel-list/2009-March/msg00425.html
=== Fedora 11 Default Mediaplayer Not Banshee. Mono to Blame ? ===
A summary of FESCo deliberations posted[1] by BillNottingham stirred
DavidNielsen to object that he had not been alerted (as maintainer) that
discussion of the Banshee media player was to occur. David also
objected[2] that the onus had been placed on him to convince the
maintainer of the competitor Rhythmbox package to allow the replacement.
He also suggested that the use of the Mono language was a stumbling
block due to RHEL eschewing Mono: "[...] RHEL does not ship Mono, if
RHEL wants to ship Rhythmbox that is their decision but what Fedora
ships should not be. What else are we going to be dictated from above..
who else should bother to make proposals for what they preceive to be
improvements?"
Jesse Keating responded[3] that his understanding was that the desire to
avoid mono in Fedora is to avoid bloating the LiveCDs with dependencies.
The IRC logs bore out[4] this interpretation with FESCo members
explicitly stating that "[...] what its written in should have no
bearing on what goes in[.]" It was also clear however that RHEL, as the
largest downstream distributor of an OS directly derived from Fedora,
would not be ignored.
== Translation ==
This section covers the news surrounding the Fedora Translation (L10n)
Project.
http://fedoraproject.org/wiki/L10N
Contributing Writer: Runa Bhattacharjee
=== FLP Infrastructure Team Meeting ===
The second meeting[1] of the FLP Infrastructure team was held on
2009-03-05. The important topics discussed included the enabling of
login via FAS for the Transifex instance, Publican support (statistics),
inclusion of the Transifex RPM files into the yum repositories etc.
Meanwhile, the test instance of http://translate.fedoraproject.org with
a new version of transifex is currently available on
http://publictest14.fedoraproject.org for testing and feedback. The
statistics can be viewed without login. For advanced operations, a
log-in can be created on the server[2].
1.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00033.html
2.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00019.html
=== Statistics Page and Submission Outage ===
Due to a failed refresh process, the translation statistics were not
correctly generated on translate.fedoraproject.org[1]. The error was
fixed rapidly by the FLP Infrastructue Team[2].
Additionally, Xavier Conde Rueda reported[3] failure to submit
authconfig and fedora-web module via the submit page. The error, caused
in the main server, was fixed by the Fedora Infrastructure team[4].
1.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00006.html
2.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00010.html
3.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00050.html
4.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00056.html
=== Publican Documents Now on tfp.org ===
The two publican documents which were requested for translation by
Ruediger Landmann can now be submitted via
translate.fedoraproject.org[1]. Until last week, these files had to be
sent back to Ruediger for submission.
1.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00025.html
=== F11 String Freeze Reminder ===
FLSCo member NorikoMizumoto has sent out a reminder[1] of the upcoming
String freeze[2] date to the Devel team. The string freeze for Fedora 11
is scheduled to be in place on the 10th of March 2009.
1.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00009.html
2.
http://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
=== Study about FLP ===
DimitrisGlezos has put together a study[1][2] about the progess of the
Fedora Localization Project. The discussion includes various aspects of
FLP including the community structure, communication, language coverage,
FLP backend administration and engineering etc.
1.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00051.html
2.
http://dimitris.glezos.com/weblog/2009/03/08/flp-advancement-study
=== New Members in FLP ===
Jorge Gallegos[1], Ricardo Pinto[2], Teemu Vartiainen[3] and Alexey
Vasyukov[4] joined the Spanish, Portuguese, Finnish and Russian
translation teams respectively.
1.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00026.html
2.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00030.html
3.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00036.html
4.
http://www.redhat.com/archives/fedora-trans-list/2009-March/msg00047.html
== Artwork ==
In this section, we cover the Fedora Artwork Project.
http://fedoraproject.org/wiki/Artwork
Contributing Writer: Nicu Buculei
=== Echo Weekly News ===
Martin Sourada announced[1] on @fedora-art a new edition of the Echo
Weekly News [2] "This issue covers February 2009 and contains this
topic: New Icons, Perspective" and a few days later he also advanced[3]
a new design for the "computer" icon.
1.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00012.html
2. http://fedorahosted.org/echo-icon-theme/wiki/MonthlyNews/Issue7
3.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00038.html
=== Preparing for the Beta Release ===
With the Beta release for Fedora 11 nearing, Paul Frields asked[1] about
the wallpaper status "We are a little past that deadline if the
wallpaper is to get into the Beta spin as was originally intended, but
it *can* still happen. I suggest deciding on a candidate by tomorrow. If
the design isn't perfect there is still time to tweak it as we move
toward the Preview Release and the other collateral designs are made"
and Máirín Duffy came[2] with a round of images[3], which gathered the
consensus of the team with the reserve[4] on improving them further
post-Beta. The images were also packaged[5] in a yummable format by
Martin Sourada.
1.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00023.html
2.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00026.html
3. http://fedoraproject.org/wiki/F11_Artwork#Beta_Mockups
4.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00028.html
5.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00030.html
=== Working on the Picture Book ===
After the project was initiated on @fedora-marketing a couple of months
ago, the time came for implementation on @fedora-art and Máirín Duffy
started the process[1] with an acclaimed[2] first mockup "Let the games
begin! :) My concept for the theme of the book here is a guide on how to
be Fedora. There would be 4 chapters, freedom, friends, features, first.
The photos for each chapter will have the model's perspective on the
chapter's four f, talking about how that f affects their life and
affects their role in Fedora. Then below that, per picture, we could
suggest to the readers how they can bring that into their own life with
a suggestion. Kind of a call to action" which was followed by a round of
improvements[3] from Nicu Buculei.
1.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00014.html
2.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00015.html
3.
http://www.redhat.com/archives/fedora-art-list/2009-March/msg00020.html
== Security Advisories ==
In this section, we cover Security Advisories from
fedora-package-announce.
https://www.redhat.com/mailman/listinfo/fedora-package-announce
Contributing Writer: David Nalley
=== Fedora 10 Security Advisories ===
* mediawiki-1.14.0-45.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg000...
* psi-0.12.1-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg000...
* jhead-2.86-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg001...
* wireshark-1.0.6-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg001...
* curl-7.19.4-1.fc10 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg001...
=== Fedora 9 Security Advisories ===
* mediawiki-1.14.0-45.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg000...
* psi-0.12.1-1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg000...
* dkim-milter-2.8.1-1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg001...
* jhead-2.86-1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg001...
* curl-7.19.4-1.fc9 -
https://www.redhat.com/archives/fedora-package-announce/2009-March/msg001...
== Virtualization ==
In this section, we cover discussion on the @et-mgmnt-tools-list,
@fedora-xen-list, @libvirt-list and @ovirt-devel-list of Fedora
virtualization technologies.
Contributing Writer: Dale Bewley
=== Enterprise Management Tools List ===
This section contains the discussion happening on the et-mgmt-tools list
==== Managing Guest OS Types ====
Cole Robinson created[1] a patch to provide a --list-os-options option
to virt-install and virt-convert. Output from this option would be used
to help users determine the appropriate argument for --os-type. The
--os-type option is used to "Optimize the guest configuration for a type
of operating system. This will attempt to pick the most suitable ACPI &
APIC settings, optimally supported mouse drivers and generally
accommodate other operating system quirks."
This touched off a discussion[2] of how such information is managed.
Daniel P. Berrange pointed out shortcomings in the current approach and
perscribed the following fixes, and supplied an example XML file.
* An XML schema for defining all the information wrt to guest OS
distros that is relevant to virt management tools.
* A C library for querying the information in the XML file(s).
* Bindings of the C library into Python/Ruby etc as needed
* Ability for local admins to extend / override the information
either by editing the XML files directly, or a pretty GUI
Cole later dropped[3] his patch and automated[4] the creation of the OS
list in the virt-install man page instead.
1.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00023.html
2.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00028.html
3.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00034.html
4.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00033.html
==== virt-manager Storage Removal ====
A patch[1] from Cole Robinson "adds a storage aware delete dialog to
virt-manager. When deleting a VM, we are presented with a list of
storage attached to it, with an option to remove individual disks as
part of the delete process."
1.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00042.html
==== virt-install Host Device Assignment Support ====
Cole Robinson added[1] "support for host device assignment to virtinst
and virt-install. This adds a --host-device[2] command to "Attach a
physical host device to the guest. HOSTDEV is a node device name as used
by libvirt (as shown by 'virsh nodedev-list')."
Daniel P. Berrange described[3] the management options for host devices.
* "If 'managed=yes' then libvirt will automatically detach the
device from the host driver."
* "If 'managed=no' then libvirt expects that the caller has already
ensured the device is detached from the host before *ALL* attempts
to start the guest, now & in the future."
This change supports the KVM PCI Device Assignment feature[4] in Fedora
11.
1.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00003.html
2.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00006.html
3.
http://www.redhat.com/archives/et-mgmt-tools/2009-March/msg00007.html
4. http://fedoraproject.org/wiki/Features/KVM_PCI_Device_Assignment
=== Fedora Virtualization List ===
This section contains the discussion happening on the fedora-virt list.
==== User Interface Makeover for virt-manager ====
Daniel P. Berrange pointed[1] out "there's a significant redesign of
image:Echo-package-16px.pngvirt-manager in progress" and brought
attention to Cole Robinson's 'New VM' wizard makeover[2]. Daniel added
"Many more design improvements are targetted for the next few
virt-manager releases, impacting nearly every area of the UI, so keep an
eye out for more UI review postings during F12 timeframe too."
1.
http://www.redhat.com/archives/fedora-virt/2009-March/msg00001.html
2.
http://blog.wikichoon.com/2009/02/virt-manager-in-fedora-11-new-vm-wizard...
==== New Release virtinst 0.4.2 ====
Cole Robinson announced[1] a new virtinst release, version 0.400.2.
image:Echo-package-16px.pngpython-virtinst is a module that helps build
and install libvirt based virtual machines. It currently supports KVM,
QEmu and Xen virtual machines. Package includes several command line
utilities, including virt-install (build and install new VMs) and
virt-clone (clone an existing virtual machine).
New features:
* New virt-clone option --original-xml, allows cloning a guest from
an xml file, rather than require an existing, defined guest.
* New virt-install option --import, allows creating a guest from an
existing disk image, bypassing any OS install phase.
* New virt-install option --host-device, for connecting a physical
host device to the guest.
* Allow specifying 'cache' value via virt-install's --disk options
(Ben Kochie)
* New virt-install option --nonetworks (John Levon)
* Lots of backend cleanups and documentation improvements.
1.
http://www.redhat.com/archives/fedora-virt/2009-March/msg00002.html
=== Fedora Xen List ===
This section contains the discussion happening on the fedora-xen list.
==== dom0 Kernel Inches Closer ===
Pasi Kärkkäinen walked[1] the bleeding edge while testing Xen dom0 host
support. Using Fedora 10 with Xen 3.3.1-9 from Rawhide and a custom
built 2.6.29-rc7 pv_ops dom0 kernel the system boots, but virt-install
and virt-manager fail with the error "Unsupported virtualization type
'xen'".
It seems[2] that /sys/hypervisor/properties/capabilities is not present
for some unknown reason.
1.
http://www.redhat.com/archives/fedora-xen/2009-March/msg00017.html
2.
http://www.redhat.com/archives/fedora-xen/2009-March/msg00023.html
=== Libvirt List ===
This section contains the discussion happening on the libvir-list.
==== New Release libvirt 0.6.1 ====
Daniel Veillard announced[1] a new image:Echo-package-16px.pnglibvirt
release, version 0.6.1.
Libvirt is a C toolkit to interact with the virtualization capabilities
of recent versions of Linux (and other OSes).
New features:
* new APIs for Node device detach reattach and reset (Mark
McLoughlin)
* sVirt[2] mandatory access control support (James Morris and Dan
Walsh)
Improvements:
* don't hardcode ssh port (Guido Gunther)
* new test cases and testing infrastructure (Jim Meyering)
* improve the SExpr parser (John Levon)
* proper error reporting on xend shutdown command (John Levon)
* proper handling of errors when saving QEmu domains state (Guido
Gunther)
* revamp of the internal error memory APIs (John Levon)
* better virsh error reporting (John Levon)
* more daemon options to allow running multiple daemons (Jim
Meyering)
* error handling when creating a QEmu domain (Guido Gunther)
* fix timeouts in QEmu log reading (Guido Gunther)
* migration with xend 3.3 fixes (John Levon)
* virsh XML dump flags cleanup (Cole Robinson)
* fix build with loadable drivers (Maximilian Wilhelm)
* internal XML APIs to read long long and hexa values (Mark
McLoughlin)
* function to parse node device XML descriptions and associated test
(Mark McLoughlin)
* generate network bridge names if not provided (Cole Robinson)
* recognize ejectable media in hostdev hal driver (Cole Robinson)
* integration of sVirt (Daniel Berrange)
There were also dozens of cleanups, documentation enhancements,
portability and bug fixes.
With about five weeks since the release of 0.6.0[3], Daniel added "So
quite a bit of changes happened in one month of development, so it's
getting clear we aren't really slowing down and keeping a relatively
fast release cycle is needed. So expect 0.6.2 in a month or so."
1.
http://www.redhat.com/archives/libvir-list/2009-March/msg00144.html
2.
http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control
3.
http://fedoraproject.org/wiki/FWN/Issue161#New_Release_libvirt_0.6.0
==== sVirt Support Committed ====
Daniel P. Berrange applied[1] the sVirt[2] patches to enable selinux
support in libvirt.
1.
http://www.redhat.com/archives/libvir-list/2009-March/msg00092.html
2.
http://fedoraproject.org/wiki/Features/SVirt_Mandatory_Access_Control
==== Secure Guest Migration Between Hosts ====
Chris Lalancette posted[1] a request for comments on secure migration
with an initial focus on Qemu. The proposal included two options. One
leveraged existing RPC while the second created a new well known port to
handle the migration. Using RPC adds a layer of authenitcation which may
possibly be avoided in the second option by simply opening a new port in
a firewall.
Sticking with existing RPC and enhancing[2] the authentication system
for migration seemed to be the consensus.
1.
http://www.redhat.com/archives/libvir-list/2009-March/msg00094.html
2.
http://www.redhat.com/archives/libvir-list/2009-March/msg00148.html
==== Hynesim Project Interest in Libvirt ====
Florian Vichot of the Hynesim[1] project was interested[2] in replacing
their wrappers around KVM, VirtualBox, and OpenVZ with libvirt, and so
asked about support for a number of features including auxiliary TAP
devices in the host to correspond with ethernet devices in the guest.
1. http://www.hynesim.org
2.
http://www.redhat.com/archives/libvir-list/2009-March/msg00115.html
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
15 years, 1 month
- 1
- 0
Some discussion on @fedora-ambassadors about FWN
by Oisin Feeley
Hi all,
A thread[0] from @fedora-ambassadors resulted in what _may_ be some
interest in producing a PDF of FWN. As usual getting someone to commit
to producing this regularly would be the important thing. Susmit
provided[1] a mock-up but seemed to shy away from volunteering to do
this every week.
Thoughts?
[0]
https://www.redhat.com/archives/fedora-ambassadors-list/2009-March/msg002...
[1] http://susmit.fedorapeople.org/FedoraNews/FedoraNews.pdf
Best wishes,
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
15 years, 1 month
- 2
- 1
Ambassadors is done
by Larry Cafiero
Hi, all --
The Ambassadors beat is done for the next edition of FWN.
Larry Cafiero
15 years, 1 month
- 1
- 0
FWN #166 status
by Oisin Feeley
Hi all,
I've edited all the beats in so far and am ready to push out the
mailshot tomorrow. So, Pascal if you want a well deserved break then
take it!
I'll copy all the beats in to the new issue page tomorrow morning and
then touch up the mailshot plaintext.
Thanks everyone for the great contributions. Have a good week.
Best,
--
Oisin Feeley
http://fedoraproject.org/wiki/OisinFeeley
15 years, 1 month
- 2
- 1