Skip to content

Foresight

Elisa Updates

Moosy, an OpenSUSE blog, has a short post up today on Elisa, mentioning that the 0.3 release will be a complete rewrite, and now includes Tango icons.

I look forward to the upcoming release. As I’ve mentioned before, Foresight has the latest Elisa release already in it’s repos, so hopefully we can get an updated version when it’s released. I was this close (holds fingers apart) to trying to reinstall MythTV this morning on my HTPC, but I couldn’t find a surge protector as I’m out of outlets at my home theater. (That should tell me something, shouldn’t it?)

Moosy links to the following Youtube showing off the new icons:

GNOME Documentation – Irony 101

Now that I have a few newsletters under my belt for Foresight Linux and completed the Getting Started user guide on the wiki, my next two big projects for Foresight are porting the Getting Started guide from the wiki to Docbook for inclusion in Yelp on a default Foresight installation, and getting some screencasts recorded and posted to the Foresight wiki.

With newsletter #3 out the door, and an hour or two on my hands, I decided to jump in and start learning some basics of Yelp, Docbook and contributing to GNOME documentation. I started off keeping track of some interesting links I was coming across in Tomboy, and as my frustrations grew, it became a live journal of my research in to contributing to GNOME documentation. What follows is the unedited thoughts that ran through my brain for just over an hour as I looked for content on where to start on this journey.

The good thing I’ve learned in this process is what needs to be updated to make it easier for folks who want to help out GNOME and it’s documentation. Docs are one of the easiest areas for a new volunteer to get involved with, and now that I’ve complained publicly about my experiences, I’ve added it to my to-do list to try and make this better. (But it’s down on my to-do list after Foresight documentation in Yelp and screencasts. And maybe the new Foresight website, we’ll see).

Without further adieu, here are my notes:

**

GNOME Documentation**

Documenting my learnings on contributing to YELP

15:45 – Start looking on the GNOME wiki and Google

http://live.gnome.org/DocumentationProject

(last update in October 2006)

http://live.gnome.org/ProjectMallard (next generation GNOME docs tool in development)

15:55 join IRC (#docs on GIMPnet)

Continue to use the Wiki and Google:

http://live.gnome.org/DeveloperGuides (could be a gold mine, lots of links)

http://live.gnome.org/IdealDeveloperDocumentation (A wishlist of perfect documentation, last updated last August)

http://developer.gnome.org/projects/gdp/handbook/gdp-handbook/index.html (last update 2003, this had to be the bible for doc developers once upon a time)

http://www.ibiblio.org/oswg/oswg-nightly/oswg/en_US.ISO_8859-1/articles/DocBook-Intro/docbook-intro/ (Linked from the GDP handbook above, it’s from 1999!)

16:05: Edit the GNOME wiki with a broken link to the non-existent style guide:

http://live.gnome.org/DeveloperGuides

16:10 Ask for help in IRC (no response, but I’m patient)

16:15 Find new links that look helpful:

http://live.gnome.org/DocumentationProject/Contributing

http://live.gnome.org/DocumentationProject/Contributing/SubmittingPatches

16:18 Complain in #foresight about the irony in that getting started with the GNOME documentation team isn’t really documented

16:24 Realize the link above on SubmittingPatches is also horribly outdated as GNOME has moved to subversion

Make mental note that I should be probably updating the GNOME documentation personally with these learnings. Add to to-do list in Tomboy

16:29 Thilo agrees with me in IRC, and reinforces an opinion I have too:

thilopfennig: pcutler_: yeah

thilopfennig: thats true

even simple links are broken

and nobody cares really

That last sentence bothers me, as I had the same thought. Perception is reality.

16:31 Pull up the GNOME SVN wiki page and prepare to checkout some help files to browse through as a base:

http://live.gnome.org/SubversionFAQ

16:36 first 2 projects svn co doesn’t work, try with epiphany, but it pulls the whole source, and not the help files. keep reading through LGO. Quite frustrated.

16:43 Pull down Gedit files. Realize that I was pulling the help files correctly with SVN, but still can’t find english versions. Mistakenly ask for help in IRC, when I did do it right.

16:46 Remind self it’s a holiday weekend in US on a Sunday afternoon, of course no one is going to respond.

16:48 Open Gedit, and start browsing through source files. In the Help directory, the “C” subdirectory has “gedit.xml” – I found the file! Why is it in the C directory if it’s American English? Who thinks of these things? All the other files I pulled down were correct as well.

16:55 Finish scrolling through gedit.xml after opening the files in Yelp for comparison. Docbook looks fairly sane, if just overly, well, there’s a lot to it, but it’s fairly logical. Overwhelmed by the sheer amount of work porting the userguide from the wiki to Docbook will be, but it’s doable.

16:56 Walk away. Remind self to blog this.

Lovin' Feedburner

About 6 months ago, I burned my blog’s RSS feed to Feedburner. I was using WP-Shortstat as a WordPress plugin, and the RSS feed subscribers didn’t look realistic (and they weren’t!) as it was over reporting on the number of subscribers. I’ve been happy with Feedburner since, and it provided a very simple view to my feed’s statistics, and there was a plugin to view the statistics right in my WordPress dashboard.

When I was syndicated on Planet Foresight, I created a Linux feed on Feedburner so those users weren’t subject to my entertainment and copyright rants, and later I burned a feed of the Foresight Linux Newsletter as well.

Since then, I continue to learn more about Feedburner and its features, in no particular order:

  • Feedburner takes over Steve Smith’s WordPress plugin for Feedburner stats, renames it Feedsmith.
  • Rick @ Feedburner recaps why partial feeds are a bad thing. I couldn’t agree more – I’m too lazy to follow links out of my feedreader just because a site wants hits. I’ll usually end up unsubscribing after a while unless the site has really, really good content, like TV Squad.
  • It might be fun to create a Headline Animator – if I could do a non-cheesy looking one, might be a good way to market the Foresight newsletter
  • I can’t believe I didn’t know about FeedFlares until today – what a great concept. Add little tags to the end of your posts, such as “add to del.icio.us”, “email author” etc. See the whole list here. I’ve already updated my feed. And the have an open FeedFlare API to create your own.

I also use Feedburner as tool combined with the Foresight Wiki based on Confluence. Confluence gives you the ability to build a feed right from the dashboard, but it’s really only useful for tracking a whole space, and not independent pages.

The first feed I built was the Foresight Linux Newsletter. Using Confluence, I created a RSS 2 feed based on any news post in the Newsletter space. Confluence gave me me a feed that looks like this:

<br /> http://issues.foresightlinux.org/confluence/createrssfeed.action?types=blogpost&statuses=created<br /> &spaces=newsletter&labelString=&rssType=rss2&maxResults=10&timeSpan=180<br /> &publicFeed=true&title=Foresight+Linux+Newsletter+RSS+Feed

Not necessarily human readable, or easy for a subscribe to type in to their feedreader, though possible using cut and paste.

I took that feed, and burned it in Feedburner, and got this:

http://feeds.feedburner.com/foresightnewsletter

Much better, and now I have statistics tracking for our subscribers (Which we need more of!)

The second feed I created in Confluence, was for the Package Request page on the Wiki. On this page, users can request software packages to be added to the Foresight repository, so they can install them via Conary, instead of building and compiling the software by hand.

Confluence doesn’t give you an option, at least that I could find, to build a feed for a specific page. First, I gave the the wiki page a specific label, “package-requests”. I then went to the Feed Builder, and chose to build a feed in the Developer space, with a label “package-requests” and to show all new edits and comments on the page. Confluence gave me the feed:

http://issues.foresightlinux.org/confluence/createrssfeed.action?types=page&types=comment<br /> &statuses=created&statuses=modified&spaces=kitchen&labelString=package-requests<br /> &rssType=rss2&maxResults=10&timeSpan=5&publicFeed=true&title=Foresight+Linux+Package+Requests+RSS+Feed<br />

I burned that in Feedburner and came up with:

http://feeds.feedburner.com/fl-packagerequests

So if you want to add that to your feedreader, you will see all requests and comments for new packages, as well as edits to the page when someone marks a package as added to the repository.

I’m really starting to dig the power of Feedburner.

Elisa

With the recent announcement of Ubuntu forming a Media Center team focusing on Elisa as it’s media center platform, I took another look at Elisa as a potential solution for my home theater PC. (Sidenote: I’m way too lazy and need a gook kick in the butt. I’ve had my HTPC built and ready to go for a year, and have barely tried to fix the last few issues I have with it. Shame on me. Though since I got my dual-tuner HD-DVR from DirecTV, when combined with my Sonos and Xbox 360, I haven’t really needed all the features of a HTPC that I originally planned on).

Elisa was already available in the Foresight repository, but it was version 0.0.1. Asking nicely in IRC, Ken Vandine updated the version to Elisa’s current release, 0.1.6. Ken was unable to run it because of an ATI or Xorg issue in 1-devel with 3D effects, but it started right up for me.

I’ll do a more formal review later, I’ve only played with it for maybe 30-60 minutes tops over the last day and a half, but for a very, very early release, Elisa looks promising. After some user error on where you edit different file locations in the ~/elisa/elisa.conf file, I was able to browse my music and photos.

To be clear, it’s a program to manage your media – it does not have DVR functionality built-in. And for me, that may just be perfect. It will manage your movies & videos, play DVDs, photos, and music. It has built-in support already for Streamzap remotes. (I don’t know what that is yet, but I’m going to find out).

One obvious bug, is when I start Elisa from a terminal or Alt-F2, there is no window border. Changing Elisa to fullscreen with the “F” key and back to a windowed version, brings up a window. This tip is useful, because if you don’t, and you lose focus of Elisa, none of the shortcut keys work if the window border isn’t there.

I’m going to play with it more this weekend, and will post more thoughts on Elisa early next week. For now, here are some screenshots of Elisa in action, with bigger versions available on my Flickr account.

elisa

elisa2

elisa-photos

Bluetooth (Headset / ALSA) update

A follow-up to last night’s post about Bluetooth adapters on Linux to use a headset with my desktop:

_

Breaking News: Foresight Developers can read minds!_

Serendipity struck, that within an hour of posting, Ken Vandine pinged me in IRC on #foresight to let me know that earlier in the day, he had already updated the Bluetooth ALSA packages on Foresight to make this project work.

So not only will Foresight developers package up software if you ask nicely in IRC, I have now learned that Foresight Developers have the ability to read minds, and package software they know their users will want later in the day.

Can your distribution’s developers read minds? Get Foresight today!

(Now I’m off to pickup a bluetooth adapter later today!)

Gaming on (Foresight) Linux

Linux seems to always get a knock when it comes to gaming. I know personally I believed the FUD, before making the switch to Linux full time 2 years ago and learning otherwise. What Linux doesn’t have in quantity as a gaming platform, it does make up in quality.

A lot of the open source and freeware get the publicity, but id software and Epic, among other developers, makers of Quake and Unreal Tournament respectively, continue to put out native Linux binaries of their software.

With the upcoming Enemy Territory: Quake Wars release, I installed Quake IV, Doom 3 and the original Wolfenstein: Enemy Territory on my desktop today. Since I did a clean install of Foresight a couple months ago, I wanted to make sure I work out any kinks before ET:QW’s release.

Everything worked like a champ – I downloaded the Linux installation files from id software’s bittorrent server, installed those in /home/silwenae/games (I’m lazy, didn’t feel like chmod’ing /usr/games), copied the pak files over, and ran Doom 3 and Quake IV. Mapped my keys, cranked the video settings, and I was online in minutes fragging away.

The only small glitch I ran into with Quake IV, and this hasn’t happened in my two or three previous installs, was that it started in Spanish. A quick Google search turned up the fix: Go into your home folder, and in the .quake4 directory (which is hidden, hit ctrl-h in Nautilus to view hidden files and directories), and then the q4base directory, and edit the Quake4Config.cfg file with your favorite text editor, and change the value of sys-lang to english, and you’re all set.

Everything worked great out of the box, I didn’t have the funky Alsa / OSS sound issue I had in the past with Ubuntu, even that worked flawlessly.

Who said you couldn’t game on Linux? Come get some!

Getting Started with Foresight Linux User Guide

I’m pleased to announce the 1.0 release of the Getting Started with

Foresight Linux User Guide:

[http://wiki.foresightlinux.com/confluence/display/docs/Getting+Started+with+Foresight+Linux

]1

The User Guide provides a high level overview of Foresight Linux, including:

  • Download and Installing Foresight Linux
  • Post-Installation Configuration
  • Using Applications
  • Updating Foresight / Adding & Removing Programs
  • Getting Help
  • Getting Involved with Foresight Linux

The User Guide is intended for users new to Linux or new to Foresight,

though advanced users may learn something as well.

The User Guide currently lives on the Foresight Wiki, so if you have

any updates or see any errors, feel free to update it, I would love to

have some more eyes looking at it. I hope to export it to HTML and /

or Docbook in the next month or so.

Foresight Linux 1.2 Released

Foresight Linux 1.2 has been released, day and date with GNOME 2.18.1!

Foresight Linux 1.2 builds on the success of last month’s 1.1 release, and features a new default GDM theme, updated hardware support, and a fix for importing photos.

Foresight Linux is an innovative, stable distribution with default applications such as Banshee for music, F-Spot for photo management, Epiphany web browser, and Brasero for burning music and data discs. Foresight also comes with Compiz enabled (depending on your video card), and propietary codecs installed including MP3 and DVDs.

Foresight has a beautiful green theme and features Conary, a next generation packaging tool, to manage your software and software updates.

Visit the download page to download Live Media, including LiveCDs, VMWare images and more to test out Foresight, or download the installation discs on one DVD or two CDs.

View the release notes or the downloads page. Give Foresight a try – in the 2 months I’ve been using it, I can speak very highly enough of the packaging, the distribution and the community.

A big shout out to the developers for another timely, and stable, release.

Foresight To-Do List

Stuff I’m currently working on:

  1. Getting Started with Foresight Linux: A user’s guide to start using Foresight Linux. Currently it’s about 50% complete, but I expect to have it 90% complete by the end of the weekend. Includes installing Foresight, configuring, overview of the most used applications, updating Foresight, getting help and contributing. Feel free to contribute. Long term, I want to convert it to html and / or docbook as well.
  2. Foresight Newsletter. The first newsletter was well received, but was done in less than week of it’s release. It should have content being added consistently through out the month, which I need to start doing, and find a way to get more volunteers to add content such as highlighting a package or doing an interview.
  3. Gaming – Since I did a clean install of Foresight, I need to reinstall my games (Second Life, Quake IV, Doom 3, UT2k4). Lots of Quake 3 total conversions have been in the news the last week or two, wouldn’t mind trying those out as well. I probably should add some content to the wiki about gaming on Foresight.
  4. Foresight Calendar – There’s a rumor that a Google Calendar exists for Foresight. I’m thinking I may poke at it, it may be an interesting exercise to add key dates to it, such as GNOME releases, Foresight releases, etc. It may make adding content to the newsletter more structured and give users an idea of key dates.
  5. WordPress-MU theme: There is some interest in adding blogs to foresightlinux.org. There’s still a question around where to publish the newsletter, though the wiki seems to be working for that, but also to offer developers blogs who may not have their own webspace. First, we’re going to need a theme, so I may hack at that – my html-foo is poor, so I’ve been putting that off, and then we need to get it on the webserver. I’m more than happy to admin it for folks who want blogs. I’ll probably throw WordPress-MU up on my webspace this weekend and poke at it to see what the admin interface is like.
  6. Screencasts: Based on a discussion in IRC on Saturday, I thought I’d give creating screencasts a shot. I played with Istanbul a little over the weekend, and it will work, though the audio quality was pretty poor, and I have a very nice Plantronics headset. A big thanks to pscott for re-packaging Jokosher and packaging Pitivi. My current plan is take the Getting Started guide pages on Applications, and create screencasts that match the write-ups I did for the apps. (See the Banshee page for a good example). I’ll record the screencast in Istanbul, then the audio in Jokosher, and use Pitivi to edit them together. It’s a little more long term, as the screencasts will need to be well scripted, both the video capture and the audio narration.

That’s it for now – I don’t want to put too much on my plate and get burned out, so I’m trying to take it in chunks and stay focused. The newsletter and Getting Started guide are definitely the short term focus.