Hi, As a lurking, N900 owning user, I'd like to chip in here.
I bought an N900 (rather than any other phone on the same contract) because it was a Debian-based system. Initially I felt sad that Deb-based Maemo is being replaced by RPM-based MeeGo, but in the end I don't actually care since it is just a packaging method. What I care about as a user is that I don't need to know whether the packaging is Deb-based or RPM-based. As a developer I just need to know how to package my applications, and for that to be simple and easy -- i.e. for there to be good tools to do it, in my case a good SCons or Waf based mechanism. What I really, really care about is that there is a smooth and hassle free transition of the software running on my phone. I can happily handle doing a backup and restore of data. What I don't want is an unexpected total revolution in the UI of the applications I use, and I definitely don't want my phone to get "bricked". On Tue, 2010-04-27 at 09:00 +0300, Quim Gil wrote: > Hi, > > ext Matthieu Chaton wrote: > > Le 26 avr. 2010 à 10:10, Dave Neary a écrit : > >> As I understand it, to call yourself MeeGo, you have to have all the > >> core components of the platform & applications as defined by the MeeGo > >> project, and must use them all. RPM is part of the core platform > >> definition. > >> > >> Nothing is stopping someone from re-packaging all the MeeGo components > >> using deb, but you wouldn't be able to call it MeeGo. > > > > I'm not sure about that, Maemo 6 will be called MeeGo, and it will use deb > > packages > > Ibrahim [1] from The Linux Foundation is coordinating the work to define > and test MeeGo compliance. Please give them some time to come up with > their conclusions. > > Maemo 6 and Moblin 2.2 development plhases were caught in the middle of > the MeeGo announcement, with committed deliveries and deadlines. Both > are taking some compromises in order to fit within the MeeGo definition, > and both Nokia and Intel are doing the steps to deepen in one single and > common MeeGo stack. Hopefully everybody understands that this doesn't > happen overnight when you have to ship releases without delays. I for one am happy that this transition is being managed well, mostly because it is being talked about openly. OK there is some "behind closed doors" activity, but that is natural in the circumstance. As long as there is general openness, as indeed there seems to be, then confidence will be built up. > It is actually nobody's interest to focus in the differences of > Harmattan (the former Maemo 6) in order to tear it apart, as long as it > offers a MeeGo API and a simple tool for developers to deal with rpm/deb > and the Ovi Store. After the transition period MeeGo based devices from > Nokia will ship with a pure MeeGo stack, and problem solved. Even the transition is temporary and will go away. However, it is crucial: what matters is that the transition is smooth so that people stay with MeeGo and not shift to an Android-based phone. No matter what is said here and on other email lists, very few users actually care about the details of the platform, they care about the trendiness and zeitgeist. What matters for the N900 and its ilk is that people want to own one, and developers want to develop applications for it, contributing to people wanting to own one. Overall what has to happen is keep current N900 users informed about what is happening and what they will have to do. There are two main audiences, pure users and user/application developers (people actually developing MeeGo itself should already be in on the knowledge). The former group will need more hand-holding and less detail than the latter group -- who would undoubtedly want to hear much more technical detail. -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
