Mirko Lindner vegyraupe at
Mon Aug 31 15:57:01 CEST 2009


just wanted to add another 2-cents to the bucket, which by now should  
contain a lot of small change ...

Reading some of the mails in this thread I think we need to get the  
definitions straight:

- fso - phoning middleware
- shr - a distro which comes with fso preinstalled
- om2009 - another distro that comes with fso and paroli preinstalled
- paroli - a python daemon that comes with 4 phoning apps and a  
settings app by default

The question here was: should om2009 be continued.

Never having tried SHR i can't go down that path deciding by  
comparison. I heard many good things about SHR, I liked the guys I  
met at the dev meeting in Braunschweig so I would recommend active  
devs to go for SHR.

As for Om2009 it has always been a one-man show or at least mainly.  
And that man was Angus. He did the cleanup, made the builds etc etc.  
Seen that he has limited resources now I would think Om2009 has a  
dark future ;) So probably best to say good bye while we still have  
good memories :)

I heard there would be efforts to bring paroli to SHR and maybe  
integrate it better or make it smoother, if anyone wants to do so,  
just let me know if you need commit access to the paroli git and  
we'll try to get you into the loop (which can be very chaotic at  
times ;) )

As for me, due to heavy engagements with Qi Hardware I don't have  
much time left for paroli right now, every now and again there is a  
burst of commits but nothing too stable so any help is welcome.


On 29 Aug 2009, at 19:10, Bernhard Reiter wrote:

> Am Freitag, den 28.08.2009, 21:09 +0200 schrieb Sebastian  
> Krzyszkowiak:
>> Oh guys... I'm SHR developer (once I tried Om2009), but... regarding
>> stablity, SHR and FSO is mainly the same! We both use FSO and we both
>> are affected by FSO bugs. And most of bugs regarding phone
>> functionality came from FSO on both distros (ok, in early stage SHR
>> ophonekitd wasn't perfect, but now it should be rock solid). That's
>> just matter of used versions. Saying "om2009 is unstable cause i  
>> can't
>> answer call" means that this bug probably is (was or even will be)
>> also in SHR, and vice versa.
>> Om2009 was much stabler than SHR-unstable. That's why I liked SHR  
>> more
>> ;) Now shr-unstable has bugfixes to most of om2009 issues. That's why
>> shr-unstable is now stabler than om2009.
>> And don't get me wrong - i'm SHR developer, and I love SHR, and I
>> "fight" with Om2009 (regarding "i with SHR want to be better than  
>> guys
>> with om2009" ;)), but I really don't like criticizing anything  
>> without
>> knowing anything about mentioned issues and causes! Paroli is great
>> work, I just don't like approach "everything in one big daemon", but
>> my opinion doesn't make Paroli worse... I'll just use SHR without
>> saying bad words on Paroli.
> well, so maybe it's because i was using om2009t5 (not unstable),  
> but it
> having being promoted as stable enough for daily use, i was pretty
> disappointed to find it was not. and with shr-u (from around 07/31, i
> think), things worked pretty good. so maybe i really don't know enough
> about internals and organization, but trust me: with om2009t5, i
> couldn't pick up about every other incoming call -- or more -- which
> made it practically useless. with shr-u, i can pick up calls. that's
> about all i wanted to say about om2009 vs. shr.
> bernhard
>> Well, probably reality isn't as simple as i presented in this post.
>> But i'm sure it's at least close to ;) And I hope you'll understand
>> what I said. This post can be noisy cause i'm excited with listening
>> to really great concert of polish rock group (Perfect) from 1981
>> (great time of rock in Poland) which I just got ;)
> :-)
> _______________________________________________
> Openmoko community mailing list
> community at

More information about the community mailing list