Here are a few highlights from this week's issue. This past week marked the end of life for Fedora 9, and the launch of a new logging tool to help facilitate reporting for Fedora IRC meetings. In news
from the Fedora Planet, an overview of the development changes for Fedora 12, and several posts around Mono in light of Microsoft's recent Community Promise. In Ambassador news, coverage of recent Fedora release events in Vancouver, Washington, Malaysia and
India. In Translation news, a new Fedora 11 Users' Guide is now available in Bosnian, changes in Transfix, and new members of the Fedora Localization Project. In Design news, details on a new Gallery test instance for development of in-process works by the
Art Team. Also some new wallpapers, and more theming discussion around Fedora 12 'Constantine.' The issue rounds out with news from virtualization-related efforts, including news of more device support in virt-manager, announcement of a new list for discussion
of "libguestfs/guestfish/virt-inspector discussion/development." These are but a sampling of this week's Fedora Weekly News -- we hope you enjoy it!

If you are interested in contributing to Fedora Weekly News, please see our 'join' page[2]. We welcome reader feedback:
fedora-news-list redhat com

A new tool for IRC meeting management[1] is available for Fedora channels on Freenode. Jon Stanley[2] explained that the tool "was developed by our friends over at Debian, who are using it to record
their meetings as well. We would like all Fedora meetings to be recorded using this mechanism, such that there's one format for all of the logs."

Kevin Fenzi[1] has "setup some machines/virtual instances here to assist maintainers that might not have access to all versions/arches Fedora runs on."[2]. If you want more information, see the appropriate
wiki page[3].

Steven Fernandez asked[3] "Is Red Hat really an Open Source company?" Steven explained the background behind the post: "This question keeps cropping up every once in a while on different LUG lists
where I lurk. It is a fairly established fact now in the FOSS world (or for that matter in the software world) that businesses can be both Open Source as well as commercial (ie: for profit). However, the specifics of the mechanism for doing this is still not
well understood."

There was a bit of discussion in the blogosphere around Microsoft's recent decision[4] to apply their Community Promise[5] (covenant not to sue) to the C# language specification and Common Language
Infrastructure (CLI). Ismael Olea excerpted[6] an excited e-mail from the fedora-mono mailing list. Not everyone was quite so optimistic however.

Michael DeHaan reminded[7] us that only the core language and libraries are covered under the promise, and notably absent are some of the components that would make it useful including Windows Forms
and ADO. Michael added "My long held theory is that mono was never to be considered a legal threat, it is a tool to be used in a strategy of erosion … insert a compelling technology, then provide a migration path by adding on proprietary extensions. It erodes
Linux and it erodes OSS… and advocacy for it, even in purely legal/ethical ways, using just the free bits, and so forth, help enhance that position and acceptability."

Alex Hudson pointed out[8] that "this is going to have a surprisingly negative effect within the community, however. It validates the arguments of people worried about Mono, and this proposed split
of Mono into “Standard bits covered by MCP” and “Other bits not covered by MCP” is actually going to fuel the flames: inevitably, people will assume the non-MCP bits are a total patent mine-field, no matter what is actually in that area. Parts that people
are quite happily shipping right now - such as ASP.net - will be targetted next by people “anti” Mono. And for the parts covered by MCP; well, I expect not much to change: certainly, it’s not likely to convert many people to Mono."

David Woodhouse shared[9] an amusing (true) story about trying to recover the cost of Windows Vista, from a brand new laptop.

Michael DeHaan trialed[10] Ubuntu Netbook Remix on a netbook and found a number of areas where Fedora may be able to improve its user experience.

Vincent Danen discussed[11] the idea of "responsible disclosure" in response to rumors of a mysterious OpenSSH 0-day exploit floating around the internet.

Chitlesh Goorah announced[13] that the Fedora Electronic Lab will be switching the default desktop from KDE to Gnome.

Scott Williams built[14] a set of RPMs containing drivers for some ATI Radeon HD video cards, from a new experimental branch that contains 3D support. "You will need both the driver and the mesa package
to enjoy all the 3d stuffs. Again, experimental – use at your own risk."

Kevin Higgins reports that the Fedora 11 release event in Vancouver, Washington, was the first Fedora event of any kind there, and the first Linux event in Clark County since June 4th, 2005. Matt McKenzie
also reports from the event as well

Izhar Firdaus reports that on 4th July 2009, the Fedora Malaysia Team, in collaboration with Saito College held a Fedora 11 Release Event on campus in Petaling Jaya, Malaysia. Izhar says that they
had more than 90 people attend.

Nilesh Govande reports that July 5 was a celebration day at Red Hat’s Pune Marigold office — courtesy of the Fedora 11 release. The event was totally informal where the developers and college students
had a chance to interact with each other. Attendees asked questions and the answers came from actual contributors of distribution.

Fedora 11 was released on Tuesday, June 9, and with it a variety of activities around the release will be forthcoming. As such, with the upcoming release of Fedora 11, this is a reminder that posting
your event on Fedora Weekly News can help get the word out. Contact FWN Ambassador correspondent Larry Cafiero at lcafiero-AT-fedoraproject-DOT-org with announcements of upcoming events -- and don't forget to e-mail reports after the events as well.

--- Setroubleshoot translations are inconsistent with original messages ---

Domingo Becker reported presence of setroubleshoot audit strings in English inspite of complete translation in the particular language[1]. The rapid changes in the module cause the .pot files to be changed frequently. Some of the possible reasons
for the inconsistency are: the strings have not been marked for translation or inclusions, the translations have not been merged when the .pot files have been updated[2]. Piotr Drąg also informed that the translations may not have been included with the latest
builds of the module[3].

Máirín Duffy informed[1] on @design-team about a test instance of a gallery software, something being a wishlist item for a long time, and asked about ways to use it "How do you think we should proceed
with it?". Martin Sourada suggested[2] using it for a while "perhaps make it accessible to design team members and start filling it with extra wallpapers and see how it works? And hold a session after some time (perhaps a month) to discuss whether the test
instance works as we'd like or not" and [[User:luya|Luya Tshimbalanga] proposed[3] some categories "Could it be used to display past Fedora release wallpapers, contributors wallpaper like Martin mentioned similar to what Fedora Forum used to have until vBulletin
upgrade, sketches."

María Leandro asked for feedback[1] on @design-team about a few wallpaper concepts, which were received positively, as for example by Máirín Duffy[2] "I think these works are a very good start start;
I think the shading and coloring on mosaico2 is very suitable for a background. It's not too high-contrast, or stark, or distracting which is good for a wallpaper" along with a number of improvement ideas from various members of the team, on which Maria based
a second iteration[3], also received positively[4] "This one is great. The lighting is perfect."

María also showed[5] a number of wallpaper proposals she did for the Education SIG[6], which, as Máirín Duffy observed[7], didn't comply with the logo usage guidelines[8] "I have a concern here with
the logo - we're not supposed to change the Fedora logo like that, it's really really against the guidelines". On a tangent, a sub-logo for the education SIG was created[9] by Máirín.

Máirín Duffy reviewed a stalled conversation about creating a theme linked to the Fedora 12 codename, a good opportunity for Paul Frields[1] and Nicu Buculei [2] to chime-in with their (to long for
this report) replies on the issue.

On the same 'Constantine' concept Samuele Storari explored[3] a column "maybe we can work on the Roman Art Style and not only havin focus on the mosaic, there're the basrelief or the Monumental sketch
or the Bas-relief decoreting the Constantine Column" and Angella Inzinga with a coin[4] "I've been toying with a coin-imagery based idea of the campgate. [...] I'm hoping to have something up to post soon."

Both these features were added to virt-install[3]. Serial ports can be directed to sockets listening on remote hosts. For example: --serial udp,host=192.168.10.20:4444. That may come in handy for the
F12 Hostinfo feature[4].

Guido Günther noted[1] that virt-install disables ACPI and APIC for Windows XP guests. Adding, that it seems "that Windows XP is working fine with acpi/apic enabled which has the immediate advantage that poweroff via ACPI works as expected. So does it make
sense to handle winxp the same win2k3?". Windows 2003 guests have ACPI enabled.

Pasi Kärkkäinen went to the xen-devel list and confirmed[2] and relayed "Keir Fraser replied that ACPI with Windows has been working properly at least since Xen 3.1.0 days". Pasi then updated the Xen
wiki page[3].

Richard Jones announced[1] the creation of a new list[2] dedicated to "libguestfs/guestfish/virt-inspector discussion/development".

The current release is now 1.0.57[3], but Richard is so fast that may change by the time you read this.

Recent new features:

virt-df - like 'df' for virtual machines
New Perl library called Sys::Guestfs::Lib
Now available for EPEL
Tab completion in guestfish now completes files and devices
Big change to the code generator
Lots more regression tests
guestfish commands: time, glob, more, less
new commands: readdir, mknod*, umask, du, df*, head*, tail*, wc*, mkdtemp, scrub, sh, sh-lines.
Debian native[4] (debootstrap, debirf) support
See previous release announcement for 1.0.14 in FWN#179[5] and be sure to see the project homepage[6] for extensive usage examples.

create and destroy NPIV support (David Allan)
networking in UML driver (Daniel Berrange)
HAL driver restart thread safety (Daniel Berrange)
capabilities and nodeinfo APIs for LXC (Daniel Berrange)
iNUMA API for VBox (Daniel Berrange)
dynamically search and use kvm-img qemu-img or qcow-create (Doug Goldstein)
fix qemu and kvm version parsing (Mark McLoughlin)
serial number for HAL storage (Dave Allan)
improve error reporting for virConnectOpen URIs (Daniel Berrange)
include OS driver name in device XML (Daniel Berrange)
fix qemu command flags fetching (Cole Robinson)
check that qemu support -drive format= (Cole Robinson)
improve emulator detection (Cole Robinson)
changes to config parser to accomodate VMX syntax (Matthias Bolte)
update network schemas and driver for missing elements (Satoru SATOH)
avoid changing file context if not needed (Tim Waugh)
skip labelling if no src path (Cole Robinson)
add arm emulation if qemu-system-arm is present (C.J. Adams-Collier)
libvirt 0.6.4 was released[4] on May 29. Daniel Veillard is "shooting for a slightly smaller development cycle, in order to be able to push the next version in time for Fedora 12 Beta, this means a new release at the end of July, so only a bit more than a couple
of weeks for pushing the changes, I really hope we will be able to include a first version of the ESX driver and Power Hyprvisor, if it's the case I think it will be worth bumping the release name to 0.7.0."

Development of libvirt recently moved[1] to git as the source control management system. Daniel Berrange announced[2] "I have created a libvirt project[3] on gitorious which has a mirror of the master
branch of the libvirt.git repository. This mirror is *readonly* and updated automatically every 15 minutes. The purpose of this mirror is to allow people to easily publish their personal libvirt working repos to the world. The master upstream repository for
libvirt does not change[4]".

Hugh Brock described[1] a client's desire to make "libvirtd be a one-stop shop for everything they need to do on a virtualization host, including things we have traditionally held out-of-scope for libvirt. A partial list of those things would
include:"

In-depth multipath config management
Hardware lifecycle management (power-off, reboot, etc.)
HA configuration
Hugh then asked "why *not* expand the scope of libvirtd to be a one-stop shop for managing a node? Is there a really good reason it shouldn't have the remaining capabilities libvirt users want?"

Daniel Berrange replied[2] "This is essentially suggesting that libvirtd become a general purpose RPC layer for all remote management tasks. At which point you have just re-invented QPid/AMQP or CIM
or any number of other general purpose message buses. libvirtd has a core well defined goal:"

Provide a remote proxy for libvirt API calls
"If you want todo anything more than that you should be considering an alternative remote management system. We already have 2 good ones to choose from supported with libvirt"

QPid/AMQP, with libvirt-qpid[3] agent + your own custom agents
CIM, with libvirt-CIM[4] + your own custom CIM providers
"Furthermore, adding more plugins to libvirtd means we will never be able to reduce its privileges to an acceptable level, because we'll never know what capabilities the plugins may want."

Hugh countered [5] "given a libvirt-qpid daemon on the node that handles RPC over QMF (for example), is there not some value in having libvirt expose a consistent API for the operations people want
to do on a host regardless of whether they have directly to do with managing a virtual machine or not?"

Daniel Berrange didn't "really see any value in that" "You're just putting in another abstraction layer where none need exist. Just have whatever QMF agent you write talk directly to the thing you
need to manage."

Hugh "I will note that when I presented the large client with the option of QMF talking to multiple agents on the node but exposing (effectively) a single API and a single connection, they seemed much
happier. So perhaps the right way to attack this is with the ovirt-qpid[6] daemon we are currently working on."

Daniel Veillard was[7] "a bit synpathetic to the suggestion though." "I think libvirt API should help run those virtualization nodes, I would not open the gate like completely, but if we could provide
all APIs needed to manage the node on a day by day basis then I think this is not really beyond our scope. I think that netcf(FWN#170[8]) is an example of such API where we start to add admin services for the purpose of running virtualization. Things like
rebooting or shutting down the node would fit in this, maybe editing a drive partition too."

"Basically if we take the idea of a stripped down Node used only for virtualization, then except for operations which are first time setup options or maintainance, I think we should try to cover the
requirements of normal operations of that node. To some extend that means we would step on the toes of CIM, but we would stick to a subset that's sure."

Cole Robinson submitted[1] a patch series which "implements cloning for LVM and disk backends. Most of the functionality is already here, it just needed some reorganization to be accessible for every backend."

This section contains the discussion happening on the fedora-xen list.

---- Xen dom0 Forward Ported to Latest Kernel ----

Previously, Xen dom0 support in Fedora was provided by forward porting the Xensource patches from kernel 2.6.18 to the version found in the Fedora release at the time. This consumed developer resources and led to separate kernel and kernel-xen
packages for a time. As of Fedora 9[1] this practice was deamed[2] untenable, and support for hosting Xen guests was dropped from Fedora.

Work has since focused on creating a paravirt operations dom0[3] kernel based on the most recent upstream vanilla kernel. This work is incomplete and not expected to be done before F12 or even F13. However, experimental dom0 kernels[4] have been
created for the adventurous.

Pasi Kärkkäinen tells[5] us the Xen 2.6.18 patches have now been forward-ported to the current 2.6.29 and 2.6.30 kernel. "Forward-porting has been done by Novell for OpenSUSE. Novell also has a forward-port to 2.6.27 for SLES11."

The patches can be found here[6] here [7] and here[8].

Pasi added "These patches are still more stable and mature than the pv_ops dom0 code.. Also, these patches have the full Xen feature set (pv_ops still lacks some features)."