Skip to content

Blog

Release Day! Foresight 1.3

It’s release day for Foresight Linux 1.3. Nothing gets your adrenaline flowing like release day as you try and get all your tasks done to help out. Not only did we release the latest and greatest version of Foresight Linux, including GNOME 2.18.2 also released today, Issue #3 of the Newsletter is out. Here are some links to keep you busy:

  • Foresight Linux 1.3 release notes
  • Go download Foresight! We have installable CD & DVD images, and lots of Live Media, including VMware images, Parallels / QEMU images, and a LiveCD will be out in the next day or two. Why aren’t you using Foresight Linux yet?
  • Issue #3 of the Newsletter. Including a first look at the next generation version of Foresight Linux, 2.0.
  • The Release Day HOWTO. All the different tasks that go into release day. (Feel free to add whatever we’ve missed!)

Use it, love it, and help us make Foresight even better. Stop by #foresight on FreeNode in IRC – we won’t bite, I promise.

Site5 Issues

I’ve been hosted on Site5 for just shy of two years, and up until last week, the service has been great. Unfortunately, I’ve had 4 outages in the last week alone, and folks over at Webhostingtalkforums are saying similar things about Site5. I’ve only done a cursory glance at other webhosts, as I would have no idea where I would go. I see a lot of technical folks and blogs hosted at Mediatemple, but their reviews aren’t much better. After the two outages in the last 24 hours, I left a heated post in the Site5 forums this morning:

I’m very disappointed with the recent downtime on Peony. I have a Multisite plan currently, and on Tues, May 22nd, Peony first appeared to go down. I let it go and it seemed to be up within an hour of me noticing it was down. The sites were unresponsive, and then they were back up, with the exception of MySQL, so a couple of my sites were displaying database couldn’t connect errors, such as my blog or forums on different domains.

The next day, May 23rd, it happened again, and I opened a trouble ticket. I was told due to several users monopolizing server resources my sites were down, and this was being addressed.

Yesterday, Sunday the 27th, my sites were down again, and I opened another trouble ticket. I was told that due to bots spamming SSH logins the server was down again and it was fixed. I wake up this morning, and my sites are still down, even though the trouble ticket said it was fixed.

I’ve been a happy Site5 customer just shy of 2 years – these are the kinds of things that have driven me to new webhosts over the years.

What disturbs and disappoints me the most is the lack of communication from the Site5 staff. If a server goes down 4 times in a week, I expect a level of personal communication showing the staff is on top of it and fixing it. In addition, in the Current Services Disruptions forum, not once is Peony listed as having a disruption. I would expect that bots flooding SSH logins would be listed as a disruption, as that is approaching a DDoS style attack.

At the minimum, it made me feel better, and a few hours later a Sysadmin posted to mention they’ve added 2GB of RAM to the server and some kernel modifications and “are going to be monitoring the server very closely now to ensure it remains stable.”

Let’s hope so. And sorry about the downtime.

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.

Derivative Works

Big Media is nothing if not two-faced about the creation of derivative works. From the music industry busting re-mix artists – the same artists paid by the industry to promote their artists in dance clubs, to the film industry’s penchant for remakes. And how many movies made today are born from an original idea? Even this year’s Best Picture winner, The Departed, is a remake of a Hong Kong film.

Techdirt takes a look at this issue, using the story of the fans who re-made Raiders of the Lost Ark shot for shot starting in 1981 and taking the next 7 summers to complete it. As Techdirt points out, this couldn’t be done today. The author does a great job in pointing out the irony in the movie business on the subject of copyright.

Click here to read the article.

Mark Shuttleworth: In defense of independent governance

Mark Shuttleworth, founder of Canonical and Ubuntu Linux, has a stirring blog post up titled In defense of independent governance.

I cannot due a summary justice, but Mr. Shuttleworth’s extremely well written words on culture, democracy and free speech have moved me, and I encourage you to read it.

I’ll leave you with this from Mark Shuttleworth:

At times like these, we are our own worst enemy. We hear what we want to hear. It is painful to hear that one might be wrong, that oneÂ’s hero might have flaws, that oneÂ’s leaders might not be all that we wished them to be. The awful truth of the media is that it pays to tell people what they want to hear, much more than it pays to tell people what they need to hear, and so society can whip itself into a frenzy of mistaken greed or fear or anger, and make poor decisions.

It takes great courage to speak out, when these basic principles are at risk. In a free society, there is nevertheless pressure to conform, to stay with the herd. In a society that is not free, one speaks out at some considerable personal cost to life and liberty. I salute those who do.