Council election time again

Voting has now opened for the next Maemo Community Council and, once again, I'm standing.

Last year I won, and the council chose me as their chair (hence the quietness of this blog compared with the Council blog, or even MWKN).

Please vote, the Council this next term will be very important in setting the tone of maemo.org, and the way the Maemo community can work with (and, where desired, transition to) the MeeGo community.

You can read my declaration, my response to EIPI's set of questions covering numerous topics. Then, don't forget to vote. Contact Dave Neary if you have not received your voting token.

Running for the Maemo Community Council... again

The election period has started for the next Maemo Community Council election and we have a number of excellent candidates, including - even if I do say so myself - me ;-)

Before I decided to run, I asked each candidate a series of questions - the answers we've given are linked to from the candidate summary page. I'd also encourage other community members to come up with questions for the candidates.

My full candidacy announcement is in the thread. The main point is that the last six months, having stepped back from the council, have given me a new perspective. The biggest issue I've seen is one of communication and clear facilitation. We need to reduce the overhead and streamline community action. Therefore, if elected, I will push for:

• A clear cooperation with the growing MeeGo community through MeeGo's Community Working Group and develop a transition plan to ensure the level of collaboration the council has with Nokia isn't lost in the new world.
• A Moblin/Maemo/MeeGo summit which looks to the present as well as to the future.

• Appropriate support and resources for existing device owners as Nokia transition to MeeGo. Exactly what form this will take will depend on whether running MeeGo is a day-to-day reality for N8x0 and N900 users:

  1. If MeeGo provides a comparable experience, without any loss of functionality, the resources around Maemo can be slowly redirected.

  2. However, if MeeGo for existing devices is - at best - of developer interest only, the existing Maemo community must continue, and must continue to provide support, help and resources to Maemo users.
     

  Mer^2 should help with the final point, and I'm proud to have been on the council which approached Nokia requesting a distmaster role; and suggesting that Carsten (Stskeeps) was the right man for the job.

• Increasing the visibility of the maemo.org sprint process and reducing the burden on volunteers. Niels Breet (X-Fade) being made the maemo.org team leader will help here. Having been involved in the running of an agile project for over 2 years, I believe:

  • Niels should chair the sprint meeting.
  • The meeting participants should be responsible for setting their priorities and what will be included.
  • Input should be provided by Nokia (Tero Kojo) and the community (the Council chair) on their issues and priorities before the meeting which should be taken into account within the prioritisation.

  This will reduce the workload for the volunteers on the council, increase the ownership of the tasks and provide greater accountability of the paid contributors.

• A summary table listing the high-level issues facing the community and who on the council will act as a point of contact for them. An example for the current council could be:

  Extras QA process         VDVsx
  Optification              gcobb
  Community outreach        Texrat
  

• Support for Randall Arnold's community outreach programme, which is trying to grow the Maemo community rather than just the Maemo platform. With the launch of the Ovi store for Maemo, much focus is given to that rather than the community provisions such as Extras.
• Empowering of community members to lead initiatives such as Google Summer of Code, conference attendance etc.
• A monetisation/donation framework for community-provided downloads.

Whether you vote for me, or someone else, I'd encourage you to vote! The transition from Maemo to MeeGo means the community's representatives to Nokia are more important than ever. Voting is open to anyone with a maemo.org account which is older than 3 months, and has accrued more than 10 karma points.

Catorise: auto-organise N900 applications

In a brief break from Hermes-related Maemo work, I was inspired by Manfred Weiss' MyMenu to create an auto-organising menu application for the N900:

Catorise organises the application menu to have top-levels corresponding to the sections in Application Manager. Features:

• Uses the section icons from the current theme, falling back to the default theme if none available.
• Determines an application's section from the same information the packager used when uploading it to Extras.
• Keeps track of application installs/uninstalls.
• Entirely non-destructive: remove the package and everything goes back to how it was before.
• "All" and "Other" sections, just as in the App Manager, to provide additional access routes.

So, with Catorise the section you find an application's icon is the same you used to install it!

It is currently in Extras-devel. This should, therefore, only be tested by people who are willing to suffer potential data loss, hair loss and the eating of babies.

It's largely feature complete, however there are some known problems/future developments:

• Applications installed from Ovi will go into the "Other" section, due to the way Ovi on Maemo has been designed. I've some thoughts on how to work around this, though.
• Changing the theme will only update the icons on the next application install/removal.
• A quick GUI editor could be created to manipulate /opt/catorise/menu which is a simple text file cache to speed-up rebuilding. This would allow the user to shuffle the apps to best suit their use cases.

Maemo Weekly News: a proposal

I've been discussing this idea with a few key contributors over the past few days to make sure it's realistic and feasible. We've polished it and would like to ask for volunteers for a new Maemo Weekly News digest.

Workload: little to some.
Benefits: glory.

Read on for more info...

Background

There are a lot of facets to the Maemo community, whether it's Bugzilla, maemo-developers, #maemo, Planet, Talk or Brainstorm. With the N900 and Maemo 5, there's been a noticeable increase in traffic in all these areas.

There have been suggestions of Maemo magazines before, but they've fallen over because:

1. The people involved haven't been integrated into the community.
2. They've been a lot of work to create.
3. They tried to move away from maemo.org/news/

Similarly, there are blogs (like Reggie's Maemo Talk) which highlight key important things; but some of them also suffer from the same problems above and none yet go into the level of detail I'd like to see.

With the increase in volume, and limits on my own time, I'm finding it harder to be aware of all the things going on. In particular, little asides and so on on talk which are key to the community, but buried in a thread. The old complaint of "too much happening outside of talk.maemo.org" is now reversed, IMHO, but the SNR is too low to follow "New Posts" religiously and develop software at the same time.

Idea

A weekly news digest of key useful/informative/interesting/insightful news from all Maemo news sources. Similar in style and approach to Linux Weekly News.

This is, in many ways, a continuation of Ryan's "Community Highlights" but doing less work, being more encompassing and more repeatable.

This is NOT an attempt to aggregate ALL Maemo-related news, but provide a selection of highlights during the week; of interest to those who are involved in the platform and the community, but without the time to follow enough of the conversations in all the places to find the ones interesting to them. By acting as a filter, more people will be able to be involved in the things which interest them, resulting in an increase of higher quality submissions for members of the community who might not be heard from as much.

Implementation

The key to its success is to produce something which is useful, integrated and deterministic; but without being a massive resource hog.

Produced weekly, every week, with a series of sections - probably similar to those on tmo. Something like:

• Front page
• Applications
• Development
• Community
• Devices
• Maemo in the Wild
• ...

To gather the news, a series of sub-editors/contributors would have access to a Twitter account (@maemoweeklynews, say). The posts to this feed would consist of the section, a few keywords and a link to the content (thread, post, email message, blog) which triggered it. For example, recently this may include:

• Applications - wazd helping qwerty12 on Transmission: http://s56.radikal.ru/i152/0911/34/a388e13890a0.png
• Devices - Release firmware available to download: http://flors.wordpress.com/2009/11/16/maemo-5-final-release-updated-sdk-and-firmware/

Suggestions on content could be directed at it from people's own Twitter accounts. The sub-editors would then be able to pick and choose from these if it's something they'd missed.

As each issue is being pulled together, one or more sub-editors would then review the posts to that Twitter feed for their sections and flesh it out with a longer paragraph/quote. Full-blown stories would also be possible, but I imagine that being a rarity (if ever). There would then be an overall editor(s) making sure there's no duplication and also including things from maemo.org/downloads/ (top 10 apps, and new apps this week) and the bug jars (top 10 activity, probably).

The completed digest would then be posted to a site and syndicated to Planet.

Hopefully this shouldn't be too much work; and sub-editors/contributors would be able to post to the feed during their daily review of their slice of the community.

To collect the sub-editors, I'd suggest a recruitment & screening process of the form "what 3 would you have done for last week?" See more details below.

Getting Involved

I'm now looking for:

1. CONTRIBUTORS: long-standing members of the community to volunteer to highlight content they see during their Maemo day. This could be whilst sat on IRC, reading the mailing lists, watching maemo.org/news/, contributing on Brainstorm or reading Talk. The only extra work you'd have to do was use your favourite Twitter client to post links you thought should be in the digest.

   Approx. number of positions: 20-30

2. SUB-EDITORS: contributors who are also willing to flesh out the links each week by selecting a representative quote. I will be ensuring we have the tools in place to make this as easy as possible.

   Approx. number of positions: 5-10

3. EDITORS: the people with ultimately responsibility. The sub-editors who make sure the whole thing is consistent.

   Approx. number of positions: 2-4

As I want to start it small (it can always grow once we work out the details a bit better and see how it goes), anyone who'd like to be involved can reply to this (it'll be on maemo-community, my blog and talk.maemo.org) with:

• maemo.org username
• Position wanted (contributor/sub-editor/editor)
• Channels you follow
• Preferred section(s) if sub-editor (feel free to make up a new one)
• One/two sentence bio.
• Two or three links you'd've posted in the last 2 weeks.

This is an opportunity to help collaborate and facilitate spreading Maemo news; if you're a long-time contributor to the platform, your insights will be invaluable. If you're a relative newcomer, looking for a way to contribute, this is your chance!

Downloading Ovi Maps without a network connection

Unlike Navicore/Wayfinder on previous Maemo devices, Ovi Maps on the N900 downloads maps on demand. This is obviously a problem if you're going somewhere abroad and don't want to pay extortionate data roaming charges.

Fortunately, S60 Ovi Maps users also have the same problem, and the solution is straightforward:

1. Scroll down this post to Direct Links for Ovi Map Version 00.01.25.114 and download the maps for the countries you are interested in. (EDIT: updated to different blog post)
2. Unzip the maps into cities/diskcache on the big VFAT partition (mounted under MyDocs) on your N900.
3. That's it!

Some of the files you may already have, I've chosen to overwrite them; YMMV.

However, as far as I can tell, searching for locations still requires a network connection :-(

Why I'm not standing for the council... but you should still vote!

As those of you who read maemo-community might know, I've decided not to run for the council this time.

I'm really proud of being a part of the first two councils, and the level of trust Nokia placed in us with the recruitment of the debmaster; chairing the sprint meetings for the gang-of-four; the decisions over the summit and inviting us to the launch of the N900 at Nokia World.

My enthusiasm for Maemo is not diminished; indeed, with the launch of the N900, I'm as excited now as I was waiting for the launch of the 770 back in November 2005. However, after a year on the council, I'm now looking forward to six months as "just" a normal community member. I've not come to this decision easily, and I'm very happy to have had such warm words of encouragement. My reasons are two-fold:

1. There are many other members of the community who should have a chance to represent us. In particular, I'm very happy that Stephen (sjgadsby), Valério (VDVsx) and Graham (gcobb) have chosen to accept my nomination of them. The fact they're joined by the likes of Alan Bruce (qole), Gary Birkett (lcuk) and Jay Carter (zerojay) - and others - is even better.
2. The vitriol and nastiness spewed by a very vocal, but tiny, minority of people on talk.maemo.org - especially regarding the transition of internettablettalk.com to talk.maemo.org - took a lot of the fun away. Given the massive investment of time my role as chair required, taking the fun away removed one of the main motivations for me.

I still plan on being an active (and vocal) community member both as a developer, a community evangelist and as a user. I hope that if you would have voted for me, you consider voting for one of the excellent candidates we have standing (and we have many). In particular, Stephen, Valério and Graham have all been long term contributors in many different ways and are tolerant, helpful people. I will struggle to cast my single transferable vote for them, Gary, Alan and Jay.

However whomever you vote for, please do vote (once you receive your voting tokens)! I think that the Community Council has been far more effective than I ever imagined it could be when I suggested it back in 2008 and I look forward to seeing where this community will go in the next six months

Vala 0.5.7 now in maemo.org Extras

After a bit of a prod; and a delay; mud-builder's vala recipe has been updated to the latest release 0.5.7 and uploaded to Extras-Devel as "vala" - this can now be used in Build-Depends lines in auto-builder packages.

What is Vala?

Vala is a modern, object-oriented programming language with a syntax inspired by C# and Java. However, it compiles to native code (via C), giving the benefits of modern programming languages and the speed of native development.

From its website:

Vala is a new programming language that aims to bring modern programming language features to GNOME developers without imposing any additional runtime requirements and without using a different ABI compared to applications and libraries written in C.

Example

I've also uploaded another little package - vala-sample (basically, HildonSample) - which demonstrates that a Build-Depends: vala line in a package's debian/control can be built using the auto-builder:

This is only in Extras-devel as it's use to end-users is pretty small, however it demonstrates three things:

• How easy it is to package stuff with mud-builder.
• That the auto-builder can build Vala apps.
• That unlike other modern programming languages on Maemo (such as Python, Ruby, Java or C#) there is no additional start-up lag in a Vala application.

A screenshot all the same:

Announcing my standing for council membership

I've set the ball rolling, and put myself forward as a candidate (the first) in the second Maemo Community Council election.

I'm proud to have been a member of the inaugural Community Council. In the last six months, we've seen a sea-change in the way Maemo is progressing:

• the first Maemo Summit, paid for by Nokia;
• community ownership of maemo.org;
• better use of Bugzilla by both Nokia and the community;
• the realistic vision of a community-led "hacker edition" in Mer;
• a webmaster, docmaster, bugmaster and now debmaster all being paid for for us;
• open communication and - importantly - progress indicators like the Maemo 5/Fremantle pre-release SDKs, which would've been unheard of back in 2006/2007.

The Council has been involved in many of these, but would claim credit for few. I believe we've truly fulfilled our role as facilitators and would like to continue my role there. We've not got everything right, but I think we've proved the idea; and that it can be a cohesive force within the community.

I think there's still work to be done, though. Nokia are being more open, and projects like Tracker and Rygel are being developed openly. Yet, Modest has slipped back into internal development; some patches to Application Manager have been merged, but the community's vision for application management in Diablo - and Fremantle - looks unlikely to have been realised. The system as a whole, and the application environment which so clearly defines the Maemo brand, are architected internally. Design decisions are taken internally.

Slowly, hopefully, we can change Nokia management into utilising the enthusiastic talent at their disposal in a way which is truly ground-breaking in the industry; with a root-to-tip collaboration between us all.

Thanks for reading this, and I'll happily answer any questions anyone has.

Maemo-based netbooks?

In the latest Internet Tablet School editorial, The future of Nokia, Maemo and the Internet Tablets, krisse explains why a Maemo-based netbook makes the most sense for Nokia now.

Respectfully, I've never heard a more crazy idea:

• Maemo is a touch-based OS, which doesn't work well with a larger style keyboard.
• People who don't want Windows would find Mac OS X or Ubuntu Netbook Remix a much more compelling user experience on such a device.
• What on earth is the benefit of Maemo here, vs. an alternative OS?!
• The comments when the 770 was released were "where's the phone?", and although Nokia make lots and lots of non-phone devices (such as one of our DVB-T receivers), the comments about Nokia trying to break in to a crowded market (of laptop makers) would be easily compiled into an hilarious book.

IMNSHO, it's just plain bonkers to go down that line instead of a small, tablet form factor - however unproven that may in the end-consumer mainstream.

maemo.org Community Council elections

The call for nominations for the first maemo.org Community Council elections has been open for a couple of weeks now. But I wonder if the wider maemo.org is aware of just how important this could be for the future of the platform.

So, this post'll be syndicated on planet.maemo.org in the hope that we get more candidates putting themselves forward, and interest drummed up in the wider community in terms of asking the candidates more probing questions. Hopefully we can avoid the nastiness associated with the US presidential election :-)

Of course, I'm biased. I've thrown my hat into the ring: my candidature announcement has been sent to maemo-community. I recommend you subscribe if you're interested in shaping the future of Maemo, rather than "just" developing with it.

OpenMoko UI "train wreck"

Picked up from Internet Tablet Talk, there're a couple of videos showing how bad the OpenMoko UI is on basic usability challenges.

What's interesting is that the small comparison with the iPhone shows how poor hardware (pressure-based touchscreen, bezel around the screen) combines with poor software implementation (separate apps => slow start-up times, little thought to the size of a usable target area) to emphasise the poor user experience. And, frustratingly, how many of the issues raised cut quite close to the bone for Maemo devices too :-(

Hopefully the UI changes in Fremantle (for example, #2564) will be a big help; and a concentration on finger usage may allow a more sensitive, different, touchscreen technology to be used in the N900. Will be very interesting to see the UI talks at the summit - see you there!

maemo.org: what next? (part 2)

Following on from my earlier post, maemo.org: what next?, LinuxTag has now happened (and Quim very kindly used my open source triangle), and the 10 days brainstorm for the 100 Days community action plan, and 2010 Agenda have been launched.

My main focus in the earlier post was more related to the 2010 vision: what should Nokia do as soon as possible to really fully utilise an untapped area of the community.

However, what can the community do to organise itself and present more of a consensus view? Consensus by mailing list posts and wiki-edits just means the loudest - or most pushy - individual voices get heard. So, I suggest a Community Council, elected by the maemo community, to act as a filter/co-ordinating body to present a more unified view to Nokia - and therefore help them to help us.

Comments welcome below, or just make changes in the wiki!

maemo.org: what next?

I was invited, but unfortunately had to decline, to speak at the maemo track of LinuxTag 2008. The final topic, maemo.org: what next? is subtitled "mid-term: what Nokia should do + what the community could do". Whilst looking at whether I could attend, I started thinking about this topic. Below is the crystallisation of some of those thoughts which probably would've formed the basis of a few slides to kickstart discussion.

Where are we?

Since November 2005, we've had the N800 and N810; both spaced about a year apart. But whilst the release of the N810 saw its OS backported and released for free for the N800; the release of the N800 saw the 770 dropped in terms of official support.

All three releases had "device programmes" whereby key members of the community could get the devices at severe discounts. This had the advantage of ensuring key software and power-users could deal with the new devices; but meant that hackers who may have maintained support for the earlier devices didn't have to scratch that itch.

Nokia were criticised very heavily for their decision to drop 770 support. However, in their defense they've generally had a fairly open, but unguided approach, to community involvement. It seemed such a large company was having difficulty defining - let alone adjusting to - truly open, community-involved processes.

Recent developments such as the involvement of Niels Breet and Quim Gil have certainly helped here. There've been improvements to the maemo.org website such as karma and rating downloads & news articles which have definitely increased interaction. Quim's contact with the community both through official channels and the Internet Tablet Talk forums has been very well received. These are steps in the right direction, but more needs to be done.

Corporate interests in open source projects

There are three aspects to an open source project, especially when there's corporate sponsorship:

Open source triangle

Community involvement

Pushes sales and reduces costs: more software developed for a device; more community support for users; some aspects of software development being done by the community which can become headline items in sales packages.

Openness

Allows experimentation with a device: new operating systems; backported OSes etc. However may be viewed by suspicion by marketing teams wanting to make a large fanfare for an upcoming release.

Control

Essential for a company: what's going to be in a release, how it's going to be supported; ensuring the package as a whole has a consistent marketing message.

None of these are "better" than the others, and a true open source project - without any control at all - either splinters into a series of forks, or never gets enough traction or user-base to get that far. However, I'd suggest the best corporate-sponsored open source projects sit closer to the middle of the triangle than anywhere else. For example, if the 770 ecosystem was closer to the centre, the "hacker editions" may not have been a cost Nokia needed to swallow.

Are there "good" open source projects with corporate sponsorship? Sure! Amongst many others there are:

• Eclipse (IBM)
• Firefox (Mozilla Corporation)
• OpenOffice.org (Sun)

What Nokia should do

Nokia need to take action to really push community involvement. Nothing's got for free: if Nokia aren't seen to be committed to the community, why should the community be committed to Nokia? I'm sure we can have a discussion about where we are on the triangle, although I suspect there won't be much argument that we're closer to the bottom left than anywhere else.

Is this a bad thing? It depends. Certainly, being further towards the centre would mean - at least - the Hacker Editions could be maintained outside of the maemo.org team; other OSes such as Poky, Mamona and even Ubuntu Mobile could be got running on the device; the experts in the community could provide input into specifications, designs and even provide implementations. This'd mean:

• Somewhat reduced costs on behalf of Nokia;
• More devices being sold. Some people are looking for an entirely open device (see the interest in OpenMoko or Pandora). Others are looking for an open device on which they can run a software stack of their own choosing, such as Poky.
• Contributions from people who are personally devoted to the device, rather than being paid to work on it by their employer. That's not to say that the employees aren't doing a good job, or that they're not devoted to the device; but if someone's willing to do even some work for free, why look that gift horse in the mouth?

These are all good things, both to the end-users, the community and Nokia's bottom-line.

So, to increase openness and community involvement in maemo.org, I suggest the following to Nokia:

Default code position: open

The default position for all ITOS and Maemo code should be open source, unless there are legal and contractual reasons it shouldn't be the case. It should be possible for an external developer to tweak - say - the look and feel of the Media Player (perhaps cover.jpg album art support), rebuild it and share it in the community. Any component which is closed should have a page in the wiki or somewhere else explaining why that is closed source, and details of the API that component is supposed to provide to the system.

Work in the community, not with the community

• Nokia's internal bug tracker should be closed to anything but issues with upcoming, unannounced hardware: all software bugs and development features should be in the maemo.org Bugzilla or component-specific open bug trackers.
• All components should have discussion - even between Nokia staff - on open mailing lists and IRC. All high-level designs should be discussed on maemo-developers to get most involvement and input. Low-level implementation details should be discussed on component-specific mailing lists.
• Discuss software roadmaps on maemo-developers, engage the non-Nokia community to feel like they're not just contributing into a black hole; but are involved in the decision-making, policy-making and strategic direction of the platform on all levels.
• Improve the tooling for people wanting to rebuild an ITOS component, possibly even including the ability for third parties to produce their own FIASCO images. Indeed, for the community to help with the Hacker Editions, this ability is essential.

Raise the bar for third-party developers

Put considerable effort into integrating, homogenising and ensuring consistency between all of the built-in applications. Polish here will encourage application developers to raise their game. I've tried to avoid an iPhone comparison, but look at the quality of third-party iPhone apps, even before the official SDK was launched.

Increase the ease with which applications can be fully Hildonised and integrated into maemo

• It's currently too easy to half complete a port, without any addition of battery-management functionality; proper load notification; proper backgrounding etc.
• Effort could be made, for example, to make GtkMenuBars a more pluggable interface: Hildon would use a plugin which rendered it as a fixed point pop-up, the Mac OS-inspired desktops would use a plugin which rendered it at the top of the screen, the ROX-based distributions could have a fully popped up menu. This should also decrease the effort to port applications.
• Similarly, HildonWindow is a hack to get default themes working. This hack would be better put in the window manager, rather than requiring changes to every application.
• Work closely, and openly, with other companies using Hildon as an interface to effect these changes; such as Intel and Ubuntu; to ensure that Moblin, UME and maemo don't splinter and that porting applications between them, and innovations made by one company can be reused without being dismissed because of "Not Invented Here" syndrome.

Some of these may be too much for Nokia to swallow as a company not used to openness. There will be comments within Nokia that this will open themselves up to too much competition; that if their entire software stack is open someone else will be able to clone it. So what, though? Be a hardware company; be a focal point; sell services to your competitors building similar hardware; sell to consumers a polished device with an active community.

I strongly believe taking these actions will increase the openness of ITOS (and hence maemo) development and massively increase the participation of the non-Nokia community. For example, I and at least a handful of others, would commit to regularly commenting, reviewing and participating in design reviews of high-level (and perhaps even low-level) specifications; if only we were asked.

Nokia have a large, untapped resource of professional, enthusiastic programmers; artists and users, who would be willing to effectively work for Nokia for almost nothing: just an acknowledgement that their input is being listened to, visible changes resulting from their work and - perhaps, just maybe - inclusion in the next device programme ;-)

Non-tablet software in maemo.org downloads

X-Fade's been working hard and bug #2347 has been fixed. This now means that the official maemo.org downloads catalogue can now contain non-tablet software such as tablet-encode.

Hopefully this'll boost the profile of things like mediautils to a wider audience.

Steps are simple:

1. Go to add new application (logging in if necessary) and fill out the fields as detailed.
2. One particularly cool feature is the ability to put in a direct download URL for the "click to install" arrow.
3. Don't try and attach any screenshots until you've first saved the details; there's an issue with that and it's best done when editing the page after the first save.

I've raised a feature request that the download statistics available to extras(-devel) users are picked up from garage.maemo.org for a more integrated system.

tablet-encode v2.18 - with much improved DVD ripping

tablet-encode has had v2.18 released. Notable new features in this release include:

• A new "mplayer" preset with a very high bitrate.
• Ability to define your own presets and options in ~/.tablet-encode.conf.
• Ability to rip all the episodes off a DVD with a single option.
• Add support for Freevo FXD files as pointers to the actual video.

The --episodes option is particularly cool; ripping a TV series' DVD (for, say, a long flight) is now a 3-step process:

1. Attach N810 via USB.
2. Insert DVD to computer.
3. Run:

   tablet-encode --episodes dvd: /media/nokia-sd/Video/
   

It's hard to imagine it being any easier! Of course, at some point the GUI should support showing you thumbnails of each of the titles so you can select the ones you want to rip. If anyone's got any time, and experience with Perl Gtk+, I'd be happy to accept some help in improving the GUI version.

I'd also like to thank GeneralAntilles, rm_you, Marius Gedminas, Mike Lococo and divinerites for all their help with this release.

Improving application start-up: mockup

A quick follow-up to my post on improving application start-up usability. I've done a very rough & ready mockup:

A higher-quality (but not any better put together) AVI can be downloaded (333KB).