Without further ado, here are the episodes so far:

• Arjen Van de Ven – MeeGo Technical Overview
• Quim Gil – A Working Day in MeeGo project
• Greg Kroah-Hartman – MeeGo netbooks
• Henrik Hartz – Qt Quick

<3 <3

First of all Dawn Foster, the MeeGo co-Community Manager from Intel (Quim Gil of Nokia being the other) introduced herself and asked us to introduce ourselves too, with three words. That proved to be a funny experience and it was even funnier looking at my attempted recording of the introductory round (though I succeeded in pointing the camera at the right person with surprisingly high percentage!). There were plenty of Nokians, Intelians (though I had to wonder how many of them know Walter) and even a person from Adobe developing Flash. Of course Bergie was there too, after all, he was the first person I met on previous day, Wednesday arriving to the venue. Ericsson had people attending the workgroup, as did Igalia and Collabora, and, of course, Canonical as well. In my hazy (feverish) state I forgot to discuss with Robert McQueen of Collabora more, it would have been fun to discuss the state of affairs of Linux, open source and Maemo in Cambridgeshire area.

After the roll-call Arjan Van de Ven, Senior Staff Engineer of Intel gave us an overview on the technical aspects of MeeGo. MeeGo is a personal OS for personal devices, and as Imad mentioned the day before, MeeGo plans to integrate upstream projects to be released every six months to nice bundles that manufacturers can use as a basis for the software stacks of their products. The grand plan is to make MeeGo a standard that can be used with standard Linux applications with least effort of porting effort, and Nokia will make efforts in synchronizing MeeGo with Qt releases.

Qt and C++ will be the languages of choice for development for MeeGo. Compliance testing may assume the applications are done on Qt. Judging from this, GTK will be phased out from the stack, which I think is a shame. Python can be used for programming too with Pyside, but it might not be available on every platform MeeGo will be released on. Browser hasn’t been decided on yet, it could be Fennec or Chromium, as it’s just an application. Webkit will be offered as the embeddable HTML viewer.

On the hardware side both ARM and Intel will be supported:

We as MeeGo don’t want to have one-time hardware-specific forks like Android has had.

Hardware patches, as other patches, should be submitted upstream because of this policy. Only devices that agree on the rules set by MeeGo can use the MeeGo logo and trademark: Devices need to ship with the full MeeGo stack and the application-level API must not be broken, so patches should be applied to the stack. There are plans for MeeGo application store as with Maemo has the community repositories, but proprietary stuff will be centralised either on Ovi Store or manufacturer-specific stores. There might be restrictions imposed to what can be installed to the devices by the manufacturers and the operators. [slides]

Next Greg Kroah-Hartman from Novell told us about the netbook UI. There was some video from Beijing that apparently presented the leaked UI. Novell is contributing to the Netbook quite a lot, so there’s a lot of Novell stuff going to the Netbook version: Banshee, Evolution, MobileMe, Tracker. As such, C# is included with the Netbook version and that can be used for development as well. The browser is going to be Chrome, and the aim is to have similar power/battery usage as Windows XP.

Decision making is important in every project. Quim told us about it in his presentation after lunch (Mexican menu in a Japanese restaurant was somewhat… disturbing is the best way to describe it) – by scribbling on the flip board (checking the notes from his N900 now and then). In hindsight someone should’ve taken pictures of all the scribblies Quim drew, but oh well… The basic idea of the decision-making is that there’ll be working groups for specific areas of development that make the big decisions – such as for handheld UX, netbook UX etc – but that for most of the stuff, it will decided as on every other distro out there.

Marcel Holtmann of Intel continued by offering us an overview of the connectivity framework used in MeeGo. It is built mainly on oFono, connman and Bluez with tight interaction: similar user interfaces and functionality overlap in the projects. connman controls all the radio on the device, it handles setting the device to flight mode, and on the todo list for it are for example statistics and counter interfaces, portal and location detection (I really wish this would come to Linux in general, hotel wifi authentication http catchalls are such a pain!) Wimax is a whole separate stack, controlled by connman, but LTE will be controlled by oFono. Currently there is nobody doing the mmsd and there is no open source mmsd implementation. VPN implementation isn’t ready yet, so far it supports Cisco VPN’s but OpenVPN support is coming up soon, too (WOHOO!). [slides]

Later, we were given a treat of hearing a presentation of Qt Quick (QML) by Henrik Hartz, Qt Product Manager. The UI is defined with a combination of “CSS” (even I, a non-coder understood some of that part) and JavaScript, and all the hard byte crunching happens underneath the bonnet with the logic done with C++. To me that sounds like a brilliant idea that allows the design of the UI and the actual programmatic logic be separated better, giving both aspects a fair amount of focus instead of concentrating only to the non-UI parts.

The last officially formed session was the MeeGo Technical panel with Sakari Poussa, Dawn Foster, Arjan Van de Ven and Andy Wilson. It shed some light on why MeeGo was formed: the goals and perceived methods to achieve them were considered so similar be the two companies that they figured the benefits of combining the efforts would outweigh the bad, but of course some negotiations were needed to make the most important platform decisions.

The panelists didn’t think working groups would cause a lot of decision making overhead as they are not meant to micromanage everything. Most decisions should be done by upstream developers on mailing lists, bug reports and team meetings in any case.

Although future MeeGo devices willh have the possibility for the operators to lock the phones to their network, Quim did reminds the audience that if a Nokia device is bought directly from Nokia store or online shop, there will be Methos of unlocking it, if it’s not outright unlocked by default.

Finally we had a quite uninformal discussion about translations for MeeGo, led by Intel’s Margie Foster. The discussion was about the translation tool, Transifex, quality control, best practices and teams.

I’ve got some experience on translating software to my native language, Finnish. At one point I was an active member of the translation community of Finland due to personal interest and my job. My line manager at Nomovok, Timo Jyrinki is the team leader of the Finnish translations in Ubuntu and GNOME, and during my more active years in the Finnish translation community some of the knowledge rubbed on me too.

Out of interest I found my way to MeeGo’s current translations and checked out the Finnish translations. Some of the translations were in an abysmally bad they literally made my eyes water. I was horrified when I was told that someone had been paid to do those translations (getting paid for translating open source stuff is good, doing a bad job at it is not). I couldn’t keep my mouth shut but asked what kind of quality control is there for the translations, and how is MeeGo as a project going to make sure that translations pulled from upstream aren’t written over or edited to be worse than they originally were – since I know cases of this happening too. The best way I know to make sure the quality of the translations are consistent is to make the amount of contributors consistent and big enough. If you have done translations for Ubuntu, perhaps you could have a look at doing translations for MeeGo as well?

The evening party was organized by MeeGo and it consisted of drinks and tapas at Dosa on Filmore/Post. I had lengthy discussions with Ryan Abel, Randall Arnold, Quim Gil and Ronan MacLaverty, and couple of other people whose names I’ve probably managed to forget.

Unfortunately I had a flu at the same time so some of my memories of the sessions are a bit hazy, but not to worry! Before the summit we attended WhereCamp, an unconference about geoinformation, maps and everything related to that. (I’m not too much into location information, but my partner is, and I tagged along.) The organizers gave out five Flip UltraHD camcorders, and we got one! So I naturally used mine to record the sessions, which turned out to be a good thing, since the MeeGo Workshop on Thursday was not recorded by anyone else. I’m still in process of editing the video files into uploadable format – my laptop and Linux applications for video editing seem to be incompatible combination – but I promise I’ll upload the stuff soon! (Keep tuned to this channel!)

The Linux Foundation Collaboration Summit was held in San Francisco on the 14th to 16th of April, 2010. Because of the flu I attended only the two first days, but that was plenty of action! Our hotel is down south at Sunnyvale so I had to find a way to travel to downtown San Francisco. I don’t have a car or drivers licence, so Caltrain was the only viable option, and that was plenty of adventure! I did plan to use the public transport in San Francisco, but it was too much for my hazy brain and I ended up using the taxi from the train station to Hotel Kabuki, where the conference was held. Being afraid of heights traveling on Caltrain was an experience, as the carriages were double-decker (see picture).

We visited Japantown on the Sunday previous to the conference so I’d know a bit about my surroundings, and it was a good decision. The hotel the conference was held is very pretty, and it’s next to a shopping centre full of Japanese shops and restaurants. It helped a lot with my navigation later!

Arriving to the venue on Wednesday we got breakfast and while eating my croissant and drinking my coffee, Elizabeth introduced me to couple of people, including Landon Jurgens from GE. I also had a little touch with fame as Bradley M. Kuhn joined our group and we talked, among other things, about Star Wars memorabilia. Geek, me?

First keynote was held by Jim Zemlin, Executive Director at The Linux Foundation, justifiably. He welcomed us, and talked about the State of the Linux Union. He told us about the reasons why Linux is so successful, but reminded us about the challenges the ecosystem faces too. As a funny sideline he showed us a video comparison of Steve Jobs describing the iPad: “wonderful, amazing, magical, easy” and beloved RMS describing GNU/Linux: free, freedom, freedoms, be a good neighbour…

I think one of the biggest reasons Linux is becoming more and more successful is the omnipresence of electrical and information technology related equipment. Even if personal computers might be running Windows or OS X or other non-Linux operating systems, there’s plenty of appliances, mobile phones, networking hardware, cars and DVR’s around.

The biggest problem with the heterogeneity of the open source community and projects – especially those who are responsible to the paradigm shift of computing infrastructure from locally owned and operated hardware/software combinations to computing as a service industry – is that there has to be extra vigilance to fit and finish what has been started and not lull into complacency with releases of half-baked services. This problem can be addressed with proper management of the project, setting targets, tasks, having testing at the heart of things and making quality assurance a top priority. [video]

Following Jim’s presentation, Daniel Frye with his IBM keynote discussed the lessons the company has learned through their decades of commitment to Linux and open source development. I found this presentation probably the most interesting of the morning sessions and enjoyed the view to the history of the IBM participation. One of the most important points that can be seen in retrospect are that it’s a lot easier to join an existing community than to create a totally new one, and that code drops are a difficult and dangerous way of participation; incremental edits for delivering change is usually better! [video]

The last presentation before lunch break was a panel about cloud computing. To my great disappointment Mark Shuttleworth wasn’t at the conference and didn’t take part in the discussion (although there were plenty of Canonical employees, including Pete Graner). I’m not a great connoisseur of cloud computing, but there were couple of points I managed to catch up: There’s vendor lock-in with the different cloud providers! I hadn’t really thought of that before, and it surprised me a bit. This makes it a bit risky business to trust your stuff to cloud services, but an idea of smaller vendors to create a standard by sharing code and infrastructure sounds mighty good to me. I’ll definitely need to add cloud computing to one of the subjects I need to read more about! [video]

After lunch Ari walked on the podium wearing a Maemo shirt to give his keynote about MeeGo, the free and standard Linux for the mobile industry. As we know, MeeGo is the result of the recent co-operation incentive of Nokia’s Maemo and Intel’s Moblin. There’s great hopes for this one, but I have been more or less out of touch of the real ideas behind MeeGo since I happened to be very, very sick on the week the new project was announced.

Having been watching the Maemo development from close range for quite some many years, the fact that MeeGo is aimed at not only smartphones but also TVs, tablets, car systems (and trains, planes etc) and netbooks requires some mental adjustment. MeeGo will be using Qt, Telepathy, WebKit, Fennec, RPM and GNOME, so there are some changes to Maemo. I’ve looked at the community response and the change to RPM has been the hardest to digest so far by the people.

Linux Foundation hosts the some work under MeeGo workgroup and there’s already considerable amount of collaboration going on with the platform, as Acer, Asus, BMW, Cisco, Careland, CS2C, Ericsson, DeviceVM, Gameloft, EA, Kingsoft, Linpus, Mandriva, Metasys, MontaSys, Neusoft, Novell, PixArt, Red Flag and others have already joined the MeeGo community. In the meantime first release of MeeGo has already been done in form of a code dump. It’s not really usable yet as it doesn’t have a GUI yet. N900 is the first reference device for MeeGo though, so there’s some hopes for the “older” devices :-P [slides, video]

The kernel panel was mainly uneventful. The new kernel will have better SSD support and some other new features such as a Linux equivalent of DTrace. Even if there are new features in kernel, the kernel developers keep getting older and there might not be as many new contributors to it as there has been in the past. Part of the problem is that the it’s not regarded as cool to be a kernel developer as it used to be. The code the old developers are writing into the kernel is so specialized and done by long time experts that it might be hard to understand and get used to by newer contributors. Long time contributors are well motivated and dedicated to their work on the kernel though – partly because most of them are employed to develop the kernel – so perhaps all isn’t lost after all. [video]

Imad Sousou of Intel and MeeGo technical steering group spoke after the kernel panel. He started off by mentioning his wish that since Ari had talked earlier and covered most of the topics he had in his presentation, perhaps he wouldn’t be asked the hard questions since Ari had already answered them. (This wish the audience later broke, by asking hard questions about proprietary blobs Maemo has had in the past. Ari answered them as diplomatically as possible, telling that while the project itself aims to be 100% open source, there might be proprietary components, such as device drivers, Skype etc. distributed by the vendors of the devices. Nokia will be one of the vendors, so, there will be proprietary components in the devices Nokia ships. This didn’t come as a surprise to me.)

What Imad stressed in his talk is that MeeGo plans to work very closely to the upstream.

If you want a kernel patch into MeeGo, send it to kernel upstream instead of MeeGo. If you want a Qt patch into MeeGo, send it to Qt.

MeeGo will also have a six month release cycle. First one is going to be released really soon (hopefully) as the schedule is aiming to release every May and November. [slides, video]

Why Your Life Might Depend on Your Code from the DFS Deutsche Flugsicherung (that’s the German Air Traffic Control) was mind-boggling. I’ve not watched the video yet, but I know it includes the video they showed us, and instead of yapping about too much about what the presentation was about, I suggest that you watch the video of the presentation. I can’t make justice to it by trying to condensate the points. [slides, video]

The presentation about how to prevent communities and co-operation was hilarious. Josh Berkus engaged the audience with his Over The Wall presentation. He had condensed how to stop global warming in a few easy steps that make sure you’ve built a wall between your developers and the community and stop contributions. The first premise you need to apply to the rest is that your developers do not take part in the community and all the releases are done in code drops, as thrown over the wall.

Ingredients include: difficult tools, preferably proprietary, homegrown, outdated or non-gui stuff, going all the way from CVS to CMS, via buildsystems and bugtrackers. The team needs to be overworked, and you need to make sure it’s kept that way: otherwise they’ll be babbling with the community! To make sure no communication happens, meetings need to be closed too – teleconferences make things hard, but make stuff impossible by having closed meetings. If you have a means of communication, obscure it as much as you can, and feed the trolls to make the community work against itself. Leave everything to be managed by one person, one person for webpages, mailing lists, etc. Use legalese everywhere where possible, but if you really want to tick people off, just be silent. [slides, video]

Chris diBona used Josh’s slides backwards to tell how Google does Open Source. Basically everything is in reverse! But in the end, Chris started using his own slides. Mootpoint was, that Google has released so far 915 projects as open source, and that more than 200 Google employees are patching and contributing to upstream projects. The message that also was included was that looking for enemies within the Linux and open source community isn’t beneficial. For Android to succeed MeeGo doesn’t have to fail, and indeed, in Android there’s plenty of stuff that has been originally contributed by Nokia employees. At the end of his presentation Chris won over the hearts and souls of the audience by giving every attendee a free Nexus One! [slides, video]

The first day of the event was brilliant, and we moved to a Japanese restaurant to an afterparty. I was getting tired after waking up at five o’clock and left the party around eight o’clock, to recuperate from the day to be ready for the next day. That’s up in my next blog post, coming up soon on this same bat channel! If you want to read a more accurate description of both the first and second day of Linux Collaboration Summit 2010, I highly recommend reading this Qaiku thread, written by Henri Bergius.

• a better audiobook player for Linux than the existing ones. Features that I want include m3u playlists, resume from where left on start, adjustable sleep timer, support for librivox feeds, coverfinder from Amazon, and portability to Maemo 5. I wouldn’t mind if the interface would look like Sharp GF-777, or would have a option to look like it, too!
• a counter app, you know, software equivalent of this. Shouldn’t be too hard to do, but I have no experience on GTK or any other graphical tool kit programming, or any language that uses any nice toolkit for Linux, since Java doesn’t count. If possible, I’d love a Maemo 5 widget too! Need it to keep track of knitted rows.
• feature to Xournal to make closed freeform shapes with fill colour. Would help greatly in creating knitting patterns.
• Peace and Goodwill for everyone in Ubuntu/Maemo communities,and for me personally more patience to handle people that haven’t gotten any, especially on IRC. If this is too hard to implement, O’Reilly books would also do.

KTHX. I’ll be waiting for you. I might knit you a pair of socks, if you tell me your shoesize.

But why is that? Why is it that something that has filled my free time almost totally for almost fifteen past years is now a source of anxiety and anger?

My use of IRC has evolved from being fun way of passing time and communicating with friends to source of information, connecting with people interested in similar issues and surprisingly, keeping in touch with the professionals, enthusiasts and issues I consider vital to my work and learning new skills. This comes with a downside: I expect a level of professionalism from people I discuss with.

I’m not saying being casual is bad. God knows my jokes are sometimes horrible, punchlines somewhat questionable and sometimes I’m just irrational. But I still expect a certain level of professionalism, not only on IRC, but in conference speeches, blog entries I see in various places, like Planet Ubuntu and Planet Gnome and all the rest I follow, in discussion forums and IRL meets. What I’m looking for is a atmosphere you’d expect to find in a pub on a weekday, after 5pm, but before 8pm. I call it The After Work Beer -atmosphere.

What is it? Lets do a thought experiment. Imagine going to a pub for a drink (be it alcoholic or just your favourite fruit juice) with your colleagues. While you might still talk shop, the atmosphere is notably more casual than at the office or on the shop floor. There’s still most of the social norms of the work place in effect – social faux pas that should be honoured in most cases, right?

This includes how you interact with your colleagues of different gender, sexuality, race, nationality, religion and so on.
A) Think of how you’d behave?

Consider then another group coming in the bar for an AWB just like your group has. They might be all female, all Indians, all Finns, all LGBT, all Somali, all Russians, all Muslim (or Jewish or Bahá’i), all English, all Mexicans.
B) How would you behave towards them?

here’s some hints:
A) You treat them respectfully as you’d treat them at workplace. You don’t hit on them, make racial slurs, tell them they’re going to hell because of their religion or sexual preference, you don’t aggressively pick them out from the group, but you don’t also ignore them.
B) You treat them respectfully as you’d treat them at workplace, being guests, customers or subcontractors. You don’t gang up on them to hit on them, make racial slurs, tell them they’re going to hell because of their religion or sexual preference, you don’t make a scene by calling them out by names from across the pub. If you’re interested in them, you go and ask them all to join your group, but you don’t single out just a few or feel insulted if the request is declined.

And this is what I expect of the FLOSS community, as we are trying to produce a professional level software and services that are on par or better than proprietary ones. We may not be working in the same company, not in the same country or share opinions on political, religious, sexual or whatever levels. But we are interested in reaching the same goal, and we need to work together to achieve it.

So here we are then :-)

myrtti.wav (Wave audio, 113K)
myrtti.ogg (Ogg/Speex, 24K)
myrtti.mp3 (MP3, 55K)

I couldn’t help myself ;-) :-P

But then I was told that TheSixtyOne has something that none of the earlier services have: a gaming element. Yes. A Gaming Element. While you can listen to whatever music you find in the service – and they do have lots of CreativeCommons licenced stuff! – the service also guides you on how to find new, intresting music and how to enhance your experience by having Quests that you can do, Achievements you can reach and Reputation you can collect to Level up. Bloody brilliant.

Only thing I’m missing is an API and new ecosystem of applications for this. Listening to the music only with the browser is a bit tiresome, as browsers tend to be, atleast in my use, the most unstable part of my system. Proper applications would also help bypass Flash, which is all nice and fun on a proper browser, but on n800 or on my mobile I’m not even bothering.

In any case, ROCK ON!

1. Pick a song of your favorite artist. It has to be a song with lyrics.
2. Pick a passage you remember by heart, even when drunk, feverish, sleepy
   

   I don’t wanna be your friend
   I just wanna be your lover

3. Mangle it with any means you can think of, using a pattern you’ve decided, for example:
   • shorthand words, “love” = <3
   • randomly capitalize words that you think should be emphasised, like Your and Friend
   • pick n-th letter of each word, “IdwbyF,IjwbY<3″ (a password generated from the passage picked above)
   • use maths to break repetition, “Your ears should be burning” = Yes2b or quoting The Who – Our love was is: (Our love was famine, frustration We only acted out an imitation) “O<3wf,fW2(oa)i”
   • remember to use punctuation, “Denial, denial” = D,d
4. check the resulting password can be typed with all hardware you use and to all applications (for example, if you use mobile phone, use an application that saves your password in xml etc)

Use and enjoy :-)

I was fortunate enough to have seen her talk before she vanished from the radar scope, and have referred to her blog entries later in my life for inspiration. I’ve never been a gamer and not really a coder either, but her input to my thinking about user experience, marketing and blogosphere has been profound.

There are a few names I’d like to mention in addition to Kathy; many of the women of Ubuntu Women and the Finnish IRC collective of female geeks, who have been empowering and supportive in my daily quest to keep my sanity as one of the Invisible Pink Unicorns of the Internet, women who use/do Linux (and even might get paid for it!). I’d like to thank, in no special order, Mackenzie Morgan, Emma Jane Hogbin, Melissa Draper, Elizabeth Krumbach, Jonna Pesonen and Johanna Toikkanen. Some of the names you might or might not know, some probably are not that active in the development scene of Linux and Ubuntu but are “only end-users”, but all of them deserve a thank you from me. Thank you for being you.

• Ubuntu Fridge Events
• Facebook friends birthdays
• Facebook event invitations
• Finnish Open source events
• Finnish public holidays and events
• My friends travel schedule

I also hate Evolution, and have a dislike for Sunbird after using both for several years. Currently my desktop calendar system is mainly Google calendar, my phone and for quick looks while offline, orage. Orage doesn’t currently come with an option of subscribing to online calendars, but that can be easily solved.

What I don’t like is synchronizing these by hand. Things should be automatic, easy and happen without me noticing a thing. Here in picture comes my home server, bluetooth dongle, crontab, msynctool and wget.

Most important part of this setup is msynctool. I use it to synchronize my phone with Google cal automatically with cronjobs.
53 */8 * * * msynctool --conflict n --sync google-phone 2>/dev/null 1>/dev/null
msynctool needs configuration:

1. first of all, you need multisync-tools and some plugins for opensync, and of course software for bluetooth. My pesky Dell Optiplex GX50 running as my homeserver runs with Ubuntu Hardy 8.04.1 LTS, to which I’ve installed multisync-tools from a PPA:
   deb http://ppa.launchpad.net/debian-opensync/ubuntu hardy main
   and have installed atleast opensync-plugin-file opensyncutils opensync-plugin-google-calendar opensync-plugin-irmc opensync-plugin-syncml multisync-tools
   In Intrepid the needed tools are available from the normal intrepid repositories.
2. figure out your phone settings. Make sure your phones bluetooth is visible to outside queries, and do a scan to acquire the bluetooth MAC address:
   myrtti@kengu:~$ hcitool scan
Scanning ...
00:1C:D4:4C:93:AA Nasu
   and check the channel for SyncML:
   myrtti@kengu:~$ sdptool search --bdaddr 00:1C:D4:4C:93:AA SYNCML
Searching for SYNCML on 00:1C:D4:4C:93:AA ...
Service Name: SyncMLClient
Service RecHandle: 0x1000b
Service Class ID List:
UUID 128: 00000002-0000-1000-8000-0002ee000002
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 10
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x454e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"" (0x00000002-0000-1000-8000-0002ee000002)
Version: 0x0100

   In this case the channel is 10.

3. Try if the connection to your phone works with:
   syncml-obex-client -b 00:1C:D4:4C:93:AA 10 --slow-sync text/x-vcalendar Calendar --identifier "PC Suite" --wbxml
4. you need to configure the synchronization group. As stated in man msynctool, this is done by:
   msynctool --addgroup <groupname>
   in this case, let’s do two groups, google-phone and file-backup.

   After creating the groups, you need to add members to them:
   msynctool --addmember google-phone google-calendar
msynctool --addmember google-phone syncml-obex-client

   msynctool --addmember file-backup syncml-obex-client
msynctool --addmember file-backup file-sync

5. Now that you have members added, you need to configure them. For the first group we added, google-phone, the configuring happens with commands
   1. msynctool --configure google-phone 1
      which will open up a file in your favorite editor that looks roughly like this:
      <config>
<url>http://www.google.com/calendar/feeds/USER@gmail.com/private/full</url>
<username>USER@gmail.com</username>
<password>PASSWORD</password>
</config>

      Replace the USER and PASSWORD with your own.
   2. msynctool --configure google-phone 2
      which will open up a file in your favorite editor that looks roughly like this:
      <?xml version="1.0"?>
<config>
<!-- (Only for bluetooth) The bluetooth address if the bluetooth mode is selected -->
<bluetooth_address>00:1C:D4:4C:93:AA</bluetooth_address>
<!-- (Only for bluetooth) The bluetooth channel to use. `sdptool browse $MAC` to search for the correct channel -->
<bluetooth_channel>10</bluetooth_channel>
<!-- (Only for USB) The usb interface number of the SYNCML-SYNC target. use syncml-obex-client -u (you will need access to the USB raw device) to find it. -->
<interface>0</interface>
<!-- The string that the plugin will use to identify itself. Some devices need a special string here. -->
<identifier>Google Calendar</identifier>
<!-- The syncml version to use: 0 for 1.0, 1 for 1.1 and 2 for 1.2 -->
<version>1</version>
<!-- if the plugin should use wbxml -->
<wbxml>1</wbxml>
<!-- The username to use. Leave empty to not require a username -->
<username></username>
<!-- the password for the username -->
<password></password>
<!-- sets the connection type to use. 5 means obex over usb, 2 means obex over bluetooth -->
<type>2</type>
<!-- If wbxml is enabled, defines wether the wbxml should use string tables -->
<usestringtable>0</usestringtable>
<!-- Never send ADD command, but send REPLACE (not needed normally) -->
<onlyreplace>0</onlyreplace>
<!-- Workaround around for mobile phones which only use local timestamps and _no_ UTC timestamps! -->
<onlyLocaltime>0</onlyLocaltime>
<!-- Sets the maximum allowed size in bytes of incoming messages (some device need this option set). Example: 10000 -->
<recvLimit>0</recvLimit>
<maxObjSize>0</maxObjSize>
<!-- The name of the contacts db. Must be the same as the phones sends -->
<contact_db>Contacts </contact_db>
<!-- The name of the calendar db. Must be the same as the phones sends -->
<calendar_db>Calendar </calendar_db>
<!-- The name of the note db. Must be the same as the phones sends -->
<note_db>Notes </note_db>
</config>

      Save this file to your home directory or somewhere else accessible, because we’ll need this for configuring the file-backup group!

   and for the second group, file-backup, with

   1. msynctool --configure file-backup 1
      which will require the exact same configurations as google-phone member 2 did, so now just replace the dummy file with the one you saved in the previous step WITH ONE EXCEPTION:
      <identifier>File Backup</identifier>
   2. msynctool --configure file-backup 2
      which will be a XML file a bit like this:
      <?xml version="1.0"?>
<config>
<!-- directory path for file-sync -->
<path>/home/myrtti/.phonebackup</path>
<!-- should care of subdirectories (TRUE or FALSE) -->
<recursive>FALSE</recursive>
</config>

      Note that you need to create a directory for the filesync, in this case it would be /home/myrtti/.phonebackup
6. To configure your phone, go to Menu – Tools – Sync and add:
   1. Synchronization profile for File Backup
      1. 
      2. 
      3. 
      4. 
   2. Synchronization profile for Google Calendar
      1. 
      2. 
      3. 
      4. 
      5. 
7. now you should be able to synchronize your phone using the commands
   
msynctool --conflict n --sync google-phone
msynctool --conflict n --sync file-backup

   and add it them to your cronjobs as in the example in the beginning of this entry.
8. As the final touch for those of you who use Orage, do a cronjob:
   10 * * * * wget -O ~/.personal.ics http://www.google.com/calendar/ical/USER%40gmail.com/private-eaq193204802357106916067/basic.ics
   where the URL fetched is the private iCal URL that you can get from your Google Calendar sharing settings. Similar procedure can be done with other iCal’s you find on the web, after which you can import them to your Orage with the foreign file import:
   

   those of you who use Gnome and have evolution-data-server installed, but don’t use Evolution itself for your calendar events (and use Sunbird/Lightning or some other calendar application instead) and still want to make the events to show up in the Gnome clock when you click it, try and enter on your terminal prompt:
   /usr/lib/evolution-webcal/evolution-webcal http://www.google.com/calendar/ical/USER%40gmail.com/private-eaq193204802357106916067/basic.ics
   where the URL is again the one acquired from the Google Calendar settings (thanks to topyli for this one!)

BWUH! I’m fairly sure this HOWTO contains more than one mistake, so you might need to fiddle around with your phone and computer more than this lets you assume. I’ve managed to make mine work though with this. A word of warning, though! Keep a good copy of your stuff elsewhere too, and study the meaning of the
[--conflict 1-9/d/i/n] Resolve all conflicts as side [1-9] wins, [d]uplicate, [i]gnore, or keep [n]ewer

The theme I currently use on my phone is Glamurv3