You're right, I don't speak for anyone but myself. Regardless of that, I don't see anything contradictory in those statements, the first one I said that end-user readiness wasn't an explicit goal, our goals are clear, basic functionality that makes the MeeGo N900 Community Edition day-to-day usable for developers and power users.

As the project increased in momentum, what was originally a hardware adaptation project and a few enthusiastic users that tweaked the higher layers, gained resources from Nokia and we had this Developer Edition project. That project injected a lot of energy and progress into MeeGo on the N900. And today, it is day-to-day usable in-my-opinion. But I don't think it's user ready, and there are clearly issues, issues that are being actively worked on.

My second statement was just; sure, I'd love to see MeeGo on the N900 end-user ready, mainly because I think our efforts with MeeGo "N900" Community Edition will last a lot longer than the N900s life. Now, what's the point? How many end-users are actually going to be interested in upgrading to a capable MeeGo? But the next devices will have a huge headstart with what we've started with on the N900.

This project, doesn't have a life expectancy, the Community Edition, hopefully, will be around for a long time, a lot longer than the N900, and hopefully a lot longer than the Harmattan device after that. And like all projects you'd hope the goals are to make it better. So, end-user ready is really just a matter of when, but what matters here is, when is it acceptable from the N900s perspective. If it takes another year? Is that acceptable to the users here. And we can't progress completely without valuable feed back from users, obviously we want to start with the more experienced users. Mainly because we don't what the type of people that'll try to boot it, and fail, or if they succeed be like "This is bull ****, why do you bother and why is it so crap after _all_ of this time" like some people tend to do.

I would guess that a lot more users will be interested in MeeGo than were interested in Nitdroid. As for the"this is crap" commenters, I think the community at large already deals with them fairly well. Developers need to live with a certain amount of unfair commentary. Politicians do. Artists do. Parents do.

Sure, I'm just saying why I'm not personally, actively, inviting them to the party. The fact is MeeGo works on the N900, it's a bit rough around the edges, but it works, and I think it works well. Especially now we're utilising the hardware more to it's potential, and that will only continue as we migrate to Wayland and Qt5 for the 1.3 track, which I'm very excited about

Also, if you are a developer, and you want to play around with the sort of things Harmattan will have, MeeGo N900 Community Edition is a good head start in that area.

see this is another illustration of this problem

ppl and ts talk about developer edition for n900 and coupled with ts comments of course they dont care about meego n900

now tex seems to be sayoing otherwise ?

so confusing

at least with maemo its simple - bug fixes that make this platform better - thats what cssu is

no need to guess about developer edition or intent or whatever - just plain old bug fixes that can be applied as they roll the line

u can spin all these statemjents all u want but at the end of the day the normal users just get confused and switched of

@Frap, well, mission accomplished then :P there is no spin, if they don't understand what's going on then it's probably best to stay away.

Agreed with Tom, there is no spin from the MeeGo side, but certainly a clear naysaying agenda from some here.

FYI, I am not part of MeeGo project management, either, and just calling it as I see it.

Who's competing for that? You maybe, but I've NEVER said Maemo is "more open" than MeeGo, ever. In fact I said many times that it's pointless to argue about which is "more open", since either way you still have binary blobs that will probably not transition from one version to the next. That's been my main point in several posts in this thread!

My argument is that Maemo is more functional than MeeGo, and by far more mature. You are the one that started making claims that because it was "more open" it was "better". I've consistently said that regardless of how much more open it is, unless it's 100% open it has the same flaw as Maemo, making the argument of which is "more open" a moot point.

As for "attitude"... I'm not the one saying "this isn't for users" and imply that end users can essentially go stuff themselves.

Bravo. And you only had to go back 200 years to find one example. To be fair though, that was signed more as a way to cut loose a major expense (a war) than it was to grant governance. I doubt the US being a free nation hinged on the king of England "granting" it. I'm pretty sure it was already well under way when that was signed.

Having your cake and eating it too? MeeGo for the N900 is not GPL. It has binary blobs of closed source that are required for it to deliver something even comparable to the existing system already available for the N900. And really, if you're arguing MeeGo is a non-installable stand alone, then based on the semantic discussion we had before, does it still qualify as being an OS?

I'm quite happy that MeeGo as a base (apparently not as an OS) is open source. But that's not really what we're talking about here is it? I thought we were talking about MeeGo for the N900. If we're talking about weather to talk about MeeGo here as the generic, non-installable base that is GPL, then I'm changing my vote to a firm NO. They have their own forums for that.

Please show me where I've ever said Google/Android is open source? I haven't. And yes, if their API is public, you can continue to use that API with other servers.

Look at XMPP. It's an open standard, and several people have jumped on to it, including Facebook and Google. Suppose either decided tomorrow to drop XMPP support and start using it's own API. How many customers would it lose? How many would hop to other open platforms for their chatting needs?

How many servers speak XMPP? How many speak other open protocols (like IRC)? How many speak CompuServeChat? See the difference? That's the power of open source. You can continue to use it, improve on it, etc, even if the original provider goes away. IRC, for example, started on a BBS/server that has long since gone away. But it's open, so it survived. If Yahoo were to go away tomorrow, how long do you think the chat client/protocol would last once the servers a Yahoo shut off? A month? A week? A day?

Thus my point. When (not if) Nokia pulls back on MeeGo for N900, the game's over. Done. What's out there is out there, and nothing more (if you're lucky, and they don't build in timeout bombs into the blobs). We already have a static "last image" blob with Maemo, just a matter of time before it happens to MeeGo too.

At that point, a real comparison can be done. Which is more stable? Which is more usable? Which is more supported? Which has a longer shelf life?

Based on the state MeeGo is in right now, assuming Nokia pulls that trigger in the next week, Meego is the loser in all 4 questions. That may all change in a day, a month or two, or in a year. But I'm not willing to toss out a perfectly good and working system for one that may be good in a month or a year. I live based on where I am now, and where the past has shown me things are likely to wind up. In this case, the present tells me MeeGo for the N900 isn't going to do anything I can't already do with Maemo. And the past tells me that's unlikely to change.

Because I use wifi a lot. Enough that it being unstable is a big reason for me to not move to it right this second, as many here (yourself include) have been advocating for, in an odd "no users" type of way. I still don't get that. With one breath you're saying it's wonderful, the future, fully functional, and the best thing since sliced bread. Then with the next you're saying it will never be ready for "users", it's unpolished, and non-developers can essentially go stuff themselves. Which is it?

Btw: I assume having several viable bugs logged against it in the bug tracker, all showing random disconnect problems implies there's an issue. The fact that it's being worked on is great. You saying it's not an issue because you've "never had problems with it" just reminds me of replies from Nokia's bug tracker. They never had issues with key broken items that lots of users had. Just another yellow flag against Meego from where I'm standing.

Again, newest doesn't mean better. Remember my example of which is better (Win98 vs WinME driver)? You could have the best binary blob driver in the world for the N900 GSM in MeeGo. If I can't make a phone call by tapping on the UI, it's useless. Even if I can make a call, but can't use the device the way I use it now because of an issue with some other closed component that's borked in some way, that "newer/better" GSM driver is still equally useless. I have a desk full of gadgets that half work. I don't need another one. Especially when I can have it work fully with the existing system.

Good luck forward porting them to MeeGo 2.0 when it comes out. See my point? And what exactly is it that you have in MeeGo N900 CE that we don't have in Maemo? Instability? Lots of apps? Didn't you say just a few posts ago that the reason you're here is to siphon off app developers, and/or get them to compile apps for MeeGo? What does MeeGo have? A future? How so, if it's not going to ever be ready for users?

I was using it as an example. I was noting that "governance" isn't needed for purely open products, like Mozilla. The fact that MeeGo needs it implies there are non-open components, and/or that someone is granting that in a rescindable way.



Again, bravo for trying, and I do wish you luck in getting it all worked out. But please stop touting it here like it's already finished, or "better" than Maemo until it's at least on par.

That's all I've been asking of people with their competing OSes (with ALL the alternatives, NitDroid, MeeGo, Baad, or whatever it's called...). Every time I ask that people stop claiming their system is "better", or comparable when it's not, they get their panties in a bunch and start ranting about how it's "more" open, or how it's "governed", or how it's "faster" or has a better UI. That's great. Call me when it can perform solidly for a week without rebooting, while taking calls, browsing the web, syncing with my calendar and running home made scripts and apps in the background. Until then, you're not competing against Maemo.

Present it for what it can do, great. But talking it up and calling it better does nothing but get people all riled up and trying to install a half-ready system. Most often they either screw up their device trying, or will get it installed only to find major issues unresolved. Either way, it hurts your project when you misrepresent it, since doing so drives people away from it and gives it a bad name.

Most often, you get one shot to impress people with a new system. MeeGo already has a bad reputation because it blew it's own welcome horn way to early. Repeating that mistake again and again is the best way to kill it before it even has a chance.

But! - it's actively hostile to GPLv3 and friends, to the point of forking old obsolete versions of several components, contradicting both its own compliance spec and "upstream first" policy in the process.

You deserve a medal for this post woody !.

You even quoted some of my words .