Skip to content

2009

GNOME.org revamp

After lots of stops and starts over the last few years, which really isn’t worth recapping, the GNOME web team is moving forward with a new www.gnome.org.

After lots of chatter on the gnome-web mailing lists the last couple months, Lucas organized a meeting, a set of tasks to be completed, and the timeline.

Personally, I’m helping with the content team – do we have the right pages for the new www.gnome.org? Is the sitemap correct with how those pages flow? From there we’ll work on adding the content, and then editing.

Want to help? This is a great area to jump in and help – you don’t have to know how to code, just help us write some paragraphs!

Join the GNOME Marketing mailing list and get involved!

GUADEC!

I’m going to GUADEC this year!

In all my travels, I’ve visited almost all 50 states in the U.S., but I’ve never travelled internationally. Now in the span of 30 days, I’ll be visiting both Canada and Europe – and both are related for GNOME events. And I’d like to say a big thank you to GNOME for helping subsidize my travel to both events.

The initial GUADEC schedule was posted this morning, and I’m excited (and nervous) that Stormy’s and my Birds of a Feather session on GNOME marketing was accepted! (Thursday, 10:00 a.m.). I was hoping to fly back home Friday morning, but now I need to find a way to stay to see Davydā€˜s talk on Documentation Friday morning.

In related GUADEC news, we at the GNOME Journal are publishing a GUADEC special edition. Are you going to GUADEC? Have an interesting idea for an article – maybe from a talk you want to attend to learn about (and share about with the GNOME Journal audience!) or someone you might want to interview face to face while at Gran Canaria? Let us know, more info is available here.

I’ll be seeing you in July in Gran Canaria.

GNOME Journal Issue 14 released!

Just in time for your weekend reading pleasure, for the first time since December 2007, a new GNOME Journal has been published!

Articles featured include:

I’m especially proud of this issue, as it is my first herding cats as release coordinator. I’ve written an article and edited others before, but this is my first one as a major contributor to the team.

What are you waiting for? Go read it now!

GNOME Updates

Lots of stuff going on in the world of GNOME for me!

Attended a few meetings last week with GNOME related projects.

This past Sunday, April 19th, the Documentation team met for the first time in a while. Shaun gave an update on the status of Mallard, the new markup language for GNOME Docs; a possible change to how we license docs; an introduction to Pulse and some brainstorming on new ways to bring guides to users.

On Tuesday, the Tomboy team met to discuss the road to a 1.0 release. More exciting though is the news on the work being done around syncing for Tomboy, including a potential online syncing service for users. As someone who’s lazy, and not that technical, but owns multiple computers that use Tomboy, I’m very excited about the potential a syncing service has. (And if you want to help update the Tomboy end user website, please let me know!)

Related to the Documentation news though, I’m happy to announce I’ll be attending the first ever Open Source Documentation conference, Writing Open Source, in June in Owen Sound, Canada. The GNOME Foundation is graciously covering my lodging, and three other GNOME Documentation team members, including Shaun, will be there. In addition to the tracks on Friday, there is an unconference on Saturday, and we will be having a documentation hackfest on Sunday. The hackfest might also be the first public unveiling of Mallard as we start working on all new documentation for GNOME 3.0.

I booked my flight and paid for the conference this weekend, now comes the hard part – the waiting until June.

KVM & Virtual Machine Manager in Foresight

Foresight has long been a proponent of KVM over other virtualization technologies such as Xen or Virtualbox.

If you, like me, aren’t a guru on the command line and prefer using a GUI, Virtual Machine Manager is available in the Foresight repositories. If you’ve used Virtualbox or VMWare, you’ll find virtual-manager very familiar. The only downside (for some), is that you will need a modern processor that supports Intel VT or AMD-V.

Let’s get started:

In this example, we will use an ISO of a Linux distribution. Go ahead and download an ISO of a Linux distro you’d like to try out.

From a command line install the tools you’ll need:

sudo conary update virt-manager libvirt

You’ll want to install it from the command line, as PackageKit has a bug that it doesn’t pull in libvirt:runtime for some reason. (FL-2050)

Start the service:

sudo service libvirtd start

Go to Applications -> System Tools and choose Virtual Machine Manager.

PolicyKit will prompt you for your password. Enter it and Virtual Manager will start.

Click on localhost.

Then click File -> Add Connection and click Connect.

Click New in the bottom right hand corner. You will be prompted to enter the name of your new Virtual Machine.

You will now be present with 5 steps to create your Virtual Machine:

Step 1: Enter the name of VM you wan to create

Step 2: Click on ā€œUse ISO Imageā€ and then ā€œBrowseā€ and chose the ISO you downloaded earlier. Then from the drop down boxes choose Linux, and in the second drop down box you can check if the distro you’re trying is available.

Step 3: Choose how much RAM and how many CPUs the VM can use

Step 4: The defaults should work – choose to enable storage, and how much hard drive space the VM can use. (I’ve learned that hard drive space is important – these VMs need more than you think they will!)

Step 5: The defaults should work here as well, but you can click on Advanced Options if you want to change the Networking options. I’ve never had to change anything here, and Networking has worked out of the box.

And that’s it! Now under ā€œlocalhostā€ double click the name of the VM you created, and it will boot up, just like a computer was booting up. You’ll install the Linux distro, just like you would on to a hard drive. One thing I’ve noticed, is that after an installation, it needs to reboot. My experience is the VM shuts down, rather than rebooting, but just starting it up again, the VM will boot up th eOS after your install.

To use the mouse, just click your mouse inside the virtual machine. To regain control of your mouse, press control and alt and your mouse will work normally inside Foresight again.

Here is a screenshot of Virtual Machine Manager running while the GNOME Dev Kit loads (note I have created VMs for the Dev Kit and the betas of Fedora 11 and Ubuntu 9.04:

GNOME Dev Kit

This screenshot shows the GNOME Dev Kit and Fedora 11 running side by side (One interesting thing about running Fedora is that i don’t have to release the mouse via ctrl-alt, it’s automatic within the OS. I’m not sure why, maybe it’s because Virtual Machine Manager is developed by Red Hat?):

Virtual Machines

If you have a modern processor, the hard drive space, and some memory to spare, I highly recommend Virtual Machine Manager. It makes creating and running different operating systems a breeze.

GNOME Documentation Meeting

There is a GNOME Documentation Team meeting this Sunday, at 17:00 UTC.

I am a sucker volunteered to help Shaun McCance facilitate the meeting. Here is the meeting announcement I just sent to the mailing list:

Are you a seasoned and wily Docbook veteran? New to writing documentation and don’t know where to start? Now is a great time to join the team!

There is not a formal agenda, but we will start with Shaun giving a brief update on Project Mallard (http://live.gnome.org/ProjectMallard) and a question and answer session. I will do my best to help facilitate the Q&A, but there may be questions that we won’t be ableto answer and have to come back to at a later date.

I also recommend reading Shaun’s latest blog post with his personal goals for GNOME – http://blogs.gnome.org/shaunm/2009/04/14/my-goals/.

Lastly, if you have a blog or micro-blog, spread the word about the meeting and let’s see if we can’t get some new faces to come. We have lots of work to do as we work towards GNOME 3.0!

Thanks in advance to everyone who is coming, and for those who can’t make this time, I will keep notes and publish them.

Hope to see you there!

Microblogging on Foresight

I’m a big fan of microblogging, using both Twitter and identi.ca. Microblogging, if you don’t know, is sending a short message that is 140 characters or less – so you have to be short and sweet in your message. (Did I mention it’s been 2 years since I started using Twitter? Where does the time go!?)

My favorite microblogging client for the Linux desktop is Gwibber. Unfortunately there is a nasty bug with WebKit and Gwibber that has caused Gwibber to stop working. This is affecting most distributions, not just Foresight. Unfortunately, when we ship Foresight 2.1.1 (probably) later this week, Gwibber won’t work anymore, as I found out Monday when I updated to the QA version of Foresight.

Thanks to misa, I found out earlier this afternoon that there is a stopgap solution using Pidgin and the microblog-purple plug-in for Pidgin.

In Foresight, click on Applications -> Add / Remove Software and search for ā€œpidgin-microblogā€ or in a terminal, do:

sudo conary update pidgin-microblog

Then in Pidgin, go to Tools – Plugins and enable the ā€œTwitginā€ plugin. Then go to Accounts -> Add, and add your Twitter or Identi.ca account like you would add a new IM account.

When Twitter or Identi.ca updates, it will open a new window, just like any other IM conversation, with your friends’ updates. I just leave the window open, and notify-osd shows me the updates in my notification window. You can also post your updates from within that same window.

If you, like me, were or will go through withdrawal from microblogging when you get hit with the Gwibber / Webkit bug, try the Pidgin plugin out, works pretty well. (And if you’re daring, there is a newer version in the fl:2-devel repo you can try too).

If you want to follow my microblogging, I’m on Twitter as paul_cutler and identica as pcutler. (Giving my silwenae nick a rest for the moment).

ul class=ā€deliciousā€li

div class=ā€delicious-linkā€a href=ā€http://xmlsoft.org/xmllint.htmlā€xmllint/a/div

div class=ā€delicious-extendedā€Use xmllint to check if an XML file is valid XML/div

div class=ā€delicious-tagsā€(tags: a href=ā€http://delicious.com/Silwenae/docsā€docs/a)/div

/li/ul

ul class=ā€deliciousā€li

div class=ā€delicious-linkā€a href=ā€http://www.4thstreetfantasy.com/ā€Fourth Street Fantasy Convention/a/div

div class=ā€delicious-extendedā€A fantasy convention held in Minneapolis/div

div class=ā€delicious-tagsā€(tags: a href=ā€http://delicious.com/Silwenae/conventionsā€conventions/a)/div

/li/ul