Hildon Migration to GNOME

Modules Status

This is current list of modules that are expected to migrate for now.

Accounts Status

OlavVitters: All listed Bugzilla users have been given editbugs+canconfirm. Missing: gschulhof, risun

Wiki

LucasRocha: If you're reading this page, this is almost done. We still need to move the relevant content from Maemo wiki to l.g.o.

Pages that still need to be moved from maemo wiki (list to be completed).

We also need to decide what to do with the pages under http://live.gnome.org/Maemo - are they maemo? Hildon?

Continuous integration

In practice, this involves creating a stable jhbuild moduleset which allows people to build and use the full Hildon stack. This work is partially done in:

• https://stage.maemo.org/svn/maemo/projects/haf/jhbuild_modules

Instructions are here:

• http://maemo.org/community/wiki/HildonDesktopPortability

We could propose to have this moduleset in upstream Jhbuild. Also, would be nice to have our modules being continuously built by the GNOME buildbot. For more info about the GNOME Build Brigade, see BuildBrigade.

Mailing list

Mailing list created:

• http://mail.gnome.org/mailman/listinfo/hildon-list

IRC

LucasRocha: Let's use the #hildon channel at Gimpnet (irc.gnome.org).

Website

The idea is to have a very basic/static website at the standard place for GNOME projects websites:

• http://www.gnome.org/projects/hildon

We would use the GNOME project website template with some modifications. Besides this, there's a need for a more dynamic and content-rich website. This website would only be editable by Hildon developers. The idea is to have a blog-like website with relevant Hildon development news. This website would be available at http://www.hildon.org or http://www.hildon-project.org.

LucasRocha: two options in terms of implementation of this website:

1. MediaWiki: it would roughly follow the same aproach as F-Spot or Beagle. The main page would have some latest news. The drawback is that you don't have archives for the news and have no support for comments on the news.

2. Wordpress: more blog-oriented software. Support comments on news.

TommiKomulainen: It should be possible to list news headlines with MediaWiki (see Generated lists) and you could embed comments on pages with Embed page (All MediaWiki pages have a related page for discussion)

LucasRocha: Now that GNOME has a deployed Wordpress-MU, we could use it. I'm migrating GnomeJournal to use Wordpress now and it's working quite nicely.

The website content would be co-maintained by all Hildon developers.

Artwork

LucasRocha: it would be nice to have a website to share Hildon-compatible artwork. So, why not using Art GNOME? Art GNOME is being revamped as a SummerOfCode2007 project. There could be Hildon themes and smaller backgrounds for "mobile desktops". I'll talk with ThomasWood (Art GNOME maintainer) to know what he thinks about this idea.

MichaelDominic: Lucas, I was thinking about this a bit, and I think we should rather go for our own system at maemo.org. Here is my reasoning:

• The whole hildon migration is such a huge task already that it makes sense to focus it only on things relevant to developers, and keep end-user oriented stuff at maemo.org (and trust QuimGil to promote it).

• I don't think that in the forseable future there will be such a thing as "hildon-compatible artwork". Rather, we'll have a lot of stuff compatible with OS200X, maemo XXXY, device ZZZZ etc. (think about themes for example). Since this is so much specific to us (nokia/maemo) it makes sense to keep the mess in our own garden.
• We'll have a lot of artwork-alike things relevant only in our context (ie: alternative web start page for the browser, font packages, etc).
• To have a smooth end-user experience we need to provide stuff as installable debian packages, which goes a bit against the ditribution-agnostic GNOME approach.

Feel free to comment on that. In general, I think that first argument is the most important one. I really think we should only focus now on developer-oriented tasks. If we can move our whole hildon developer-experience to GNOME, that'll be a huge accomplishement already.