Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

And by"this" you mean posting several lies, saying I've said things that I never said, dozens of times, and then never addressing it when called on it?

The same way I did the first time. Both have blobs that will eventually fail. If you can sleep easier at night because one is 5% closed and one is "40%" closed, then so be it. If the closed blobs get frozen (and/or CE doesn't catch up to Maemo in functionality) then the whole argument is pointless.

Then why did you lie and say I said something when I didn't? Why would you say that I claimed "Meego's goals were not to make an usable OS"? Why would you lie like that, not just once, but several times over this thread?

As for the rest... Squabble about semantics. Is it a tablet, or a computer, and AMD is the same as x86, but three processors in the same OMAP family are all different, but anything that compiles for ARM is all the same... That's all off topic. A smoke screen of semantics and crap you're using to avoid admitting that you were wrong.

I want to address one real key issue here though: Your habitual use of lies, repeatedly claiming I said things that I never said.

Until you man up about it, I really don't see a point in talking with you any more. If you're just going to lie, why would I want to talk with you?

And because you've lied so much in this thread, what makes you think for an instant that I'm going to accept anything you say as truth? Why would I accept that you know more about MeeGo (and it's history), when everything else I've read, including material from the MeeGo project site itself, says something different? Why should I trust someone I know to be a habitual liar over a community based-factual source?

Spread your FUD and lies elsewhere. I'm done feeding you, troll.

P.s. @Gerbick: Smaller post. Happy? :)

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

You did it again! Back to square one.

Less number of closed blobs -> less maintainership overhead, less number of requests to be to Nokia, more easiness to actually replace the blobs if the need arises -> non-marginal increased chances of the platform being actually useful in the future.

And sorry, but it's been you the one that has had to start deviating from the main topic with totally unrelated and non-verifiable stuff like ARM not being a initial target of MeeGo --despite the FAQ he has clearly partially read has an entry about ARM _exactly_ to avoid him saying that ARM is a secondary target of MeeGo--, then got his ego hurt when pointed out numerous times about his multiple factual errors, and eventually started doing "goodbye" posts in increasing number of colors only to come back later.

My main point has been clear since day one, I still don't see how you can objectively argue against it and you'd be lucky to find one open source developer that does not objectively find it true.

The only thing that is keeping me here is watching yourself dig your own manhole by spewing more and more opinions about things you don't know about (technically, I'm also digging mine by burning my posts-karma ratio).

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

What none of you are doing is getting MEEGO working as an OS for the N900.

So is this to and fro is going to gain a meego os FULLY WORKING with ALL components? then stop arguing and talk to the so called development team that are working on this so called N900 Meego adaption.

If they cannot even get the BME component to work after ALL this development time when they have been given access to all closed source components then there is something wrong with this development team.

"Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)? "

is the title of this thread and they do not report simply because there is nothing to report as the so called adaption has not only failed but is no further forward than it was 3 month ago.

So carry on with your pathetic off topic debate.

This community very much wants a COMPLETE Meego OS for the N900.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

That's just plain wrong - please stop spreading misinformation.

They've had BME working since forever in the 1.2 images - wall charger and USB charging. Even with a battery meter in UI and charging indication.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

"architectual choices" is probaly the best thing you have said on this thread because no way they have started even on the right track with this so called meego adaption.

I am probably the only one brave enough on this forum to say the work on this adpation is absolute crap, all wrong from start to finnish (pardon the pun) and if one person can "chase them away" then they are not worthy in the first place.

Please note that this is in fact a Maemo community and nothing to do with Meego..... THEY MADE IT THAT WAY !.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

http://forum.meego.com/showthread.php?t=3733&page=7

Go read THAT ok.

The last post made by cckwes MeeGo Greeter.......


"We have new image available that is based on MeeGo 1.3 and has some of the CE packages already included. Compared to the previous image this image boots to the Handset UX. It is however still far from ready and has many bugs.

=== WARNING ===
Battery management doesn't work yet so make sure you have fully loaded battery before booting this image.
=== WARNING ===

NOTES:
- systemui crashes often
- battery management isn't working so be careful with that your battery doesn't run out (investigation ongoing)
- zypper has problems with package installation (patch already submitted)
- ssh doesn't start during boot (investigation ongoing)"

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

woody, I'll just pitch in with what I know of historical facts and not really to join whatever fight is here. Some of this is more along lines of what was experienced and not really documented, but here goes:

MeeGo's base was Moblin 2.0, severely modified architectually to become MeeGo. Moblin 2.0 was built for Atom, yes. During this big modification time (what led to 1.0), the ARM port was done by both the hardware adaptation team that currently does MeeGo CE and some Linux Foundation contractors.

This practically meant, build all the source packages with ARM compiler and set up a target. Nowadays the ports are pretty equal. Initially the port was built for ARMv5 instruction set, then changed to build for ARMv7-A instruction set as this is where the most devices are based on nowadays.

Now, this portable core doesn't include hardware adaptations - like, adding in graphics drivers and other specific things, so they had to be made. Which is why we have seen the MeeGo core and UX'es on different ARMv7 devices - the core isn't specifically made for a certain device

It does actually work. The problem was that the stupid aegis security system blocked people being able to flash custom kernels in the firmware revision given out to N950 developer program people. This is fixed in a later version that N950 developer program will hopefully soon get, and N9 owners will have in sales release.

The process of this hardware adaptation for N950/N9 was similar to that of N900 - take the hardware agnostic MeeGo core, add in hardware adaptation such as GLESv2 drivers (actually shared with N900), kernel, wifi firmware/bt fimware, etc.

Just a minor comment - you state that a dialer for one device using ofono won't work on the other - that's not really true. The MeeGo dialer was made by a person from Intel who has no N900, developing it on Intel hardware + Infineon modems and we were able to use it directly on N900 + ISI modems, using same Ofono API with no source modifications.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Ah-ha, you do go outside this forum :) Please note that I said 1.2, you were exaggrating that they couldn't get it working after "after ALL this development time"

They're rebasing all components on to a new core on top of MeeGo 1.3 and well, since you see the whole open development, you also see what things aren't done yet :) The images exist so people can do their work and get things working without having to wait on one person that does the battery part. The 1.3 work practically just started.

The issue here, technically is that a open source component, DSME does not yet have the needed service description files to boot on startup - we were looking to replace DSME with something else. And well, BME depends on DSME (or a variant of this), so BME doesn't work in 1.3 images. Yet.

Not the blob's fault.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

I am quoting what you just said in your previous reply to me yet again...... it speaks for itself now.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Tekki i actually do not want to argue with you, all i want to see happen is a FULLY working flashable image to take over the Maemo OS.

Please at least try to understand my goal here ok.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Right, abill_uk - you have succesfully made me believe in those people that think this place should be shut down.

Kind of like nuking an island to kill the alien monster, despite all the unfortunate collateral.

If any of you would like to have real information and to have productive discussions of MeeGo, MeeGo on N900 and other devices, I have posted several avenues on where you can do so (I do somewhat agree with gerbick's opinion that forum.meego.com seems a little too clinical from layout etc, but I'd actually like to chat with gerbick at times and hear his views on IRC, for instance)

Any and all of you are welcome to come chat and discuss. Like many others who has come by. I've even seen ysss on IRC. People hang out in multiple places, cross-talking between CSSU, Cordia, Harmattan, MeeGo CE, etc.

http://talk.maemo.org/showpost.php?p...&postcount=262 - IRC chat information

http://talk.maemo.org/showpost.php?p...&postcount=269 - Mailing list and forum information

This is tekki signing off forever, disillusioned by this place by now.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

@abill, are you happy now, man?

Do you wake up everyday thinking, how do i degrade TMO today?
What nonsense do I spout today? How can I make the world a worse place?

I cant start to imagine how the people around you in real life suffer you. My hearts go out to them.

</rant>

Sorry, I just had to do it. I have seen too many people leaving TMO beacuse of him and too many discussions getting offtracked due to his FUD and uninformed BS. Maybe TMO should have abill_uk ignored by default?

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

If asking for a meego image is too much for someone then so be it but i tell you this community is desperate for something, anything, and now we see cssu dis-regarded by the meego team, all thay have done is distant everythng AWAY from Maemo and eventually they will all feel so guilty leaving this community in the lurch they would leave anyhow.

You need to get a grip of reality instead of making such un-educated posts.... really.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

@Tekki: well I was already idling on irc nearly 20 years ago, so it's not that alien to me (or maybe it was, to see that it hasn't changed all that much through the years).

At the core, I think we do need to represent the openness (libre) that we are fighting for here by letting people like abill say their piece... to a certain extent, at least... But looking at his warpath and the actual societal damage that he has done to what little is left of the maemo community is also disheartening and screams for tighter control and moderation.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

And the reason there is little left in the way of developers on the Maemo community is because stskeeps came in here with his fantastic explanation of why every developer working on Maemo should leave that behind and transfer there skills to meego.

The rest is elementary watson, so there you have my reasoning behind my ambiguous posting on this thread.

And when tekki tried to tell everyone the BME component was working

"They've had BME working since forever in the 1.2 images - wall charger and USB charging. Even with a battery meter in UI and charging indication."

and having followed the meego development for some time silently i just had to copy the last post regarding BME.

Then he obviously felt such a twit by telling me i talk FUD, he felt he had to leave, his doing not mine as i have never asked nor wanted anyone to leave Maemo.org especially to do with Maemo development.

It is all going down the pan slowly but surely, something i predicted a good few months ago on here and it all began with the dev's leaving for other projects such as meego.

I would very much like meego to make the grade as an OS for the N900 but i also would have liked further development going on by that team, and on here for Maemo.

Maemo progression has been slowly destructed without any explanations, all in the dark, and still everyone want's and hopes Maemo to be further developed because after all this is Maemo.org.

So yes i am bit sad that it is all going from here slowly but surely and please remember the meego developers put the gap between the 2, that was the beggining of the end as far as i could see it and has proved me right yet again, something i did never want to happen but it has.

The arguments going on here between a few are nothing actually to do with meego or Maemo development and you should really be directing your critisism in that direction not at me, work it out for yourself.

I am done with this thread now unless a miracle happens as it is of no use whatsoever to either meego or Maemo.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

@abill_uk: you mean when you asked stskeeps to break his legal contract and leak the codes under his care and he basically told you to f off? you two were already in a wicked downward spiral by that time anyway.

We'll see how 'done' you are this time, as according to google you've declared that you're 'done' with some part of TMO more than 30 times already by now, yet you seem to be immortal here.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Then silently let something happen. Angrily requesting stuff that cannot be released is not the way to go.

It'll happen. Or it won't. Until then, silence is a necessary virtue.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

I appreciate that. I was hoping someone from MeeGo would chime in, but didn't want to call out specifically for someone to speak if they didn't want to.

Exactly as the FAQ indicated, and everything I'd read. MeeGo = Moblin + ARM + Nokia driver merge-in.

I would suspect that, post MeeGo 1.0. Usually the 1.0 mark means you met your initial internal goals, which I'm sure included ARM integration. Once done (especially at the kernel/driver level), it's commonly pretty stable from there on. Very little in user-land should be platform dependent, since that's really the goal/task of the OS layer: To abstract out hardware dependencies so programs don't need to know/care about that. (As you indicated.)

I appreciate the update and detailed info. I was (probably ignorantly) basing my knowledge of the N9/N950 status on something Javispedro said:
Which he then criticized me for talking about the next day saying:
In retrospect, I should have known better to accept such information from a known habitual liar.

I'll accept the correction... Instead I'll say: The dialer for one device using ofono may not always work on other devices. I know from the past via the OpenMoko projects that the dialer apps for some releases (both using ofono) didn't cross over to other projects or architectures cleanly. It may be that the dialer he used was already aware of several groupings or types of devices, which allowed it to work without adding a new set of instructions.

Still, ofono, while nice, is more like SNMP than a direct library. There's no "DialNumber()" call... It's done instead through a more complex interface that can change based on underlying chipsets. That means either the dialer app has evolved to know more possibilities, or the industry has started to standardize a bit more since I looked at it last (which was admittedly nearly 3 years ago).

Either way, that's a good thing. :)

Thanks again for the update and clarification. It's always appreciated to hear actual facts from someone who knows what they're talking about.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Is this the right room for an argument?

http://www.youtube.com/watch?v=kQFKtI6gn9Y&t=1m15s

:D

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

I guess you yourself should know there's no black and white -- the existence of an image doesn't mean a release (and in fact as you quoted I did mention there would be a release soon...).

The exact cause is that the images are not bootable on the current bootloaders, as said above.

Sadly, one of the developers that was driven away after a ~8 page discussion here was one of the authors of the dialer app... otherwise you could have asked him how he did it (oops! turns out there's a "dialnumber" call, despite your assertions to the contrary...).

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

I see... so that justifies lies? To say in one post that it's not running on them, and then the next to say it is, and criticize me for repeating that you said it wasn't?

Btw: I noticed your silence when someone authoritative confirmed what I said (that MeeGo was based from Moblin, which did not have an ARM target, something you claimed I was ignorant and incorrect in saying). What's the matter? Cat got your liar tongue? But then why would I expect you to address this lie you told, when you haven't been man enough to address the other lies?

Probably by someone that lied, or claimed he said something when he didn't. Or, someone that claimed they knew all about something, and it's history, when they knew jack about it. Know anyone like that? Someone you've seen in a mirror lately? (Or do trolls not have reflections? Or was that vampires? Both maybe? OMG! He's a vampire troll! That explains so much!)

LOL... Now who's ignorant? Yes, in the MeeGo library you pointed to, someone did indeed implement such a call. (And they call it several times too!) You'll note in the source you pointed to that the class in question isn't part of ofono. It's a MeeGo library, using a base class (org:: ofono:: VoiceCallManager)., not part of ofono itself.

What you don't get is that there's a lot more to do than call one function, which is why he implemented said call in his own class. You'll note he does lots of other setup in that function, like starting a watcher, connecting a callback function, and...

Wait... Why am I bothering? You won't read any of this, or reply to it but to nit-pick it. Damn vampire troll! Luring me into conversations! You seem to do nothing but lie and nit-pick, and frankly are a waste of my time (and the time of others). But it's so hard to resist the siren song... OMG! A Siren vampire troll! The trifecta! Where's a deaf vampire hunter with a flaming stake when you need one?!

Congratulations: You're now officially the first person I've added to my ignore/block list here. In fact, you're the first person I've ever added in block/ignore list in a non-IM environment, ever. You've proven your self to be such a nuisance, and so full of lies, misinformation, and reasonless spite that I honestly believe you have nothing valid to share, nor will you likely ever say anything vaguely useful in the near future. Further, if you did have something to useful to share, I couldn't believe it without separate validation, since you lie (or "omit the truth") so readily it would be impossible to tell what's real and what's been freshly plucked from your backside.

It takes a lot for me to get here, even abill at his craziest didn't make the cut to get ignored. You though, you just made it, by [__] that much. Now excuse me while I don a garlic necklace and go tie myself to a mast, in the center of a moated ring of fire. :p

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

"They can't develop Meego because they lack hardware" -> I tell you there are images of Meego for the N950 around (post #300). In fact, I got notified of one three days ago.
"What are the future developments for Meego" -> I tell you : the N900, the N950 and the N9. (post #246).
I do not think either is a lie. I do not think they are contradictory either. Take your own conclusions...

Where have I claimed that Moblin had an ARM target? I've claimed that:
- ARM was a target for Meego since day 1, and specifically for MeegoCE since day -1 (post #246)
- Nokia had already started merging their stuff with upstream even before Meego, plus Moblin had a policy of using upstream stuff (post #251)
- That the Meego 1.0 release including ARM support was done within three months of the announcement (post #279), confirming that most of the work had already been done.

You have claimed that:
- That there was no ARM support at all during the Meego announcement (post #247)

Make your own conclusions.

Yeah, he was discussing with _you_. I sadly arrived late to that party.


Why it does not surprise me that you're not even capable of basic C++ understanding.

It's the Meego QML dialer application. That functions call the Dial(QString number) function which is implemented in its base class -- org::ofono::VoiceCallManager -- which is part of... you guessed it, ofono.

Sadly, I guess giving C++ samples is too much for you. Maybe you prefer a link to the official ofono documentation; look for the Dial function.

The only thing extra done by that "ultra super class with lots of extra functions" is keeping a handle to the call so that you can, among other things, end it. Ah, if you only knew how QDBus worked...

So, will you post a retraction this time?
I'm still waiting for the one where you said the number of closed packages between Maemo and Meego was only marginally different. That's not something you can explain with your baseless "it does not matter" argument. It's false. And you've avoided the issue twice.

Also, I would rather enjoy you make a list of the supposed "lies" instead of more and more colorful posts. I've posted several retractions -- unlike you, who still doesn't want to accept the truth about ofono even when presented with the raw source code in front of his eyes.


Now that he is technically not listening: what's up with him?
Someone should point that link to him before he goes out spewing more FUD?

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Well that's disappointing. Ignoring someone still tells you when they post? What good is that? :p It's so tempting to unban them to read what they said. :rolleyes: I think I'll avoid that temptation for now. I'm sure it's just another set of lies, personal insults and something misdirecting the conversation into yet another side channel to avoid the obvious fallacies of the lies (s)he tells.

Btw: Did you all see the big announcement about how Intel is going to "temporarily discontinue development of its MeeGo OS". Interesting... How long do you give Nokia before they stop funding the MeeGo CE team and/or MeeGo in general?

I'm betting Meego CE doesn't see an update after Jan 1 2012. Maybe then I can unban javispedro and see his "words of wisdom" on this topic again. (Plus it will be mid winter, and I'll have nothing better to do than engage siren vampire tolls, assuming this forum is still running then. :rolleyes: )

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Now he's reporting on a week old "rumor" (from the same people who brought you "Samsung plans to buy Meego") that has been discussed to death already and has even been denied by Intel's own CEO. Despite that, woody14619 calls it "a big announcement". What a tool.

And _even_ if Intel were to drop Meego today, and Nokia were to send black helicopters to kidnap all Meego CE developers, I do not know what that has to do with my point: that it is more open, and has thus better changes of actually going forward.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

And another post from javispedro? Doesn't give up does he? I have to say, I kind of like the ignore feature. Should have started using it ages ago.

"Have you stopped beating dead horses?" :rolleyes:

Just a couple of other bits if info I found, that unlike the Intel news has not been highly discussed... Looks like Nokia is confirming a bit that my speculation on where MeeGo (& MeeGoCE in particular) is headed was right. From the last Maemo Community Meeting:
Sounds like the MeeGo CE team is not going to be around much longer... Sad in a way, but not a surprise. Guess those blobs won't see much in the way of updates after all.

Also, it looks like MeeGo in general is seeing less activity these days, via another report about paid developers going away (due to priority shifts by corps funding it, one would assume). In particular the stats on the MeeGo-dev list and the MeeGo-commits list are painful. The spike in the commits, followed by relatively low traffic would indicate to me a last-effort dump before a stabilization period, or a spin-down. This could be the 1.3 release? But previous releases didn't see this pattern, so I'm not sure it makes sense in that context.

http://blog.ossoil.com/wp-content/up.../09/ml-dev.png

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

@woody14619 - AFAIK it will be 1.3 release. Which will be great news.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

I agree. A new release should be celebrated, and the commit cycle makes sense for that. But the drop-off in devel chatter? It could just be vacations? The author of the blog thinks otherwise, but... Let's hope. :)

Tizen != MeeGo
 

Huh.... Calendar reminders are really persistent little buggers.

I had a reminder set to come unban Javispedro and see how my initial "prediction" of MeeGo CE not seeing an update after 1-1-2012 was going. Looks like I guessed a little late. Better to be safe than sorry I suppose.

How's that open governance working out now? I've seen quite a few complaints about how fragmented the N9 information is, including in the last MWKN. That and how the apps garage on meego.com never came to be.

Really is sad, especially for those on the N9/Harmattan. I'm sure eventually they'll be folded back into Maemo.com, since there's not a lot of other places to go as a community. Perhapse it will even help breath a little more life into the forum, or at least keep Nokia funding it a while longer.

Sad to be so right on this one...

Re: Tizen != MeeGo
 

With the last release being less than a month ago and a new release coming this week (http://lists.meego.com/pipermail/mee...er/000875.html), I say you did indeed misguessed.

Actually, I'm going to go farther and use this as a living example for my initial point: as Meego is more open, its development has survived abandonment by its two larger backing companies.

No need to enter on this infrastructure debate because I fully agree and it is being worked on. (I personally do not feel the need for a garage any longer seeing that everyone else uses github either way, but on the other hand apps.formeego.org is slowly coming).

Btw, it's maemo.org .

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Nemo Mobile is well and alive (new name for MeeGo CE, old name was well, tainted) and we rebased on the Mer effort instead

http://wiki.merproject.org/wiki/Nemo

IRC at irc.freenode.net #nemomobile

We announce on mer-general@ mailing list right now, http://www.mail-archive.com/mer-gene...erproject.org/ with latest release on 22 December 2011, http://www.mail-archive.com/mer-gene.../msg00060.html

Nsuffy's youtube channel is a good way to track UI progress, http://www.youtube.com/user/nsuffys

Re: Tizen != MeeGo
 

Thanks for the links, it's really appreciated. It's also good to know where to go to catch up on things and see where things stand when one hasn't looked at it in a while. The video is nice, but shows there's still a good way to go toward base functionality on the N900. But it's clearly much farther along than it was before. I assume it can make/take calls & do SMS? DE got that semi-working just before the conference as I recall, but it wasn't the most solid thing in the world. Is there a nice chart somewhere with functionality level boxes for Nemo on the N900? There is one for MeeGo CE on the wiki, but some claimed those were "out of date" the last time we talked, and they've not been updated since then according to the wiki history.

Interesting that Mer is looking to expand to N9. But I have to wonder: if that happens, how long will it be before Mer no longer works on the N900? It's bound to happen eventually, as old hardware support gets dropped from any project eventually. I just foresee the same happening in Nemo which happened to many of the OM projects when FreeRunner came out (and is semi-happening again with GTA04).

My bad... I wasn't tracking it through the plethora of splits and the very recent name changes. (Tizen, Mer, Nemo?). And I pretty much figured that the dropping of MeeGo by virtually everyone meant it was pretty much dead. Even the N9 isn't really running MeeGo per se, but a hybrid MeeGo/Harmattan core. Doesn't much matter now, unless someone (LG, etc) decides to pick up the MeeGo banner and make new hardware for it.

That said, I still don't see many N900 users moving to it. That was the main assertion being made when the thread started, that within a year most of those with N900s still would have moved off of Maemo and on to MeeGo because it was so "future proof". I have a calendar reminder setup for that too, about 8 months away now.

The N9 (if Nemo supports it eventually) may find some converts, since it sounds like Nokia has pretty much gone out of it's way to kill any possible 3rd party support, announcing it dead before it even shipped. Sad, because the hardware looks nice. But when you throw in the step 1 of n cycle again (new-ish OS), Aegis, the limited distribution, clear lack of ongoing support, etc... Just not worth the price, figuratively or literally.

I do see the CSSU, which was labeled a "wasted effort" by a few MeeGo commenters here, taking off pretty well though. Lots of people integrating into that now, to the point that they lack testers for checking things without CSSU installed. It even has a "stable" branch, not that the testing branch is unstable...

Generally, a project changing it's name, splitting, and merging a couple times a year isn't a good sign. Recamping with Mer (which earlier was somewhat poo-poo'ed as the "wrong way to go") may be classified as survival, but not the best in the way of an example. What you really mean is the people that were working on MeeGo (in an unpaid way) have renamed themselves Nemo, and become a hardware shoot-off of Mer in the process. I'm not 100% sure I call that survival.

As for MeeGo itself, that sounds pretty dead to me. Indicators from people in the loop seem to think MeeGo.com may go dark before years end; well before Maemo.org (thanks for catching that btw...) I'm not making bets on that one either way, too many variables.

But my prediction of funded development on MeeGo CE being gone by the end of the year was pretty much dead on. And I'm pretty sure my bet that there will be far more N900 users on CSSU than MeeGo/Nemo/Mer/Tizen by next August is pretty set to come true as well. Not bad for someone that "doesn't know what he's talking about".

Anyway, been nice reminiscing. See you all in a few months!

Re: Tizen != MeeGo
 

Mer's a core (the typical linux/qt stack), not tied to a certain hardware, doesn't contain UIs or hardware adaptations, so it even works on N8x0 still, so that danger isn't terribly high.. It even does MIPS.. :P

N9 adaptation is within the Nemo project

Re: Tizen != MeeGo
 

I think the more prevalent concern is that the N9 has been/will be prematurely and artificially limited as Nokia begins focus on WM7 phones and will be a smaller sub-community compared to the N900. So the jury is still out whether the N9 will be a progression in the development of maemo. Of course, there's always the Qt "cross-platform" thing.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Yes they should!!!

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

What we really need is to have Nemo working on far more devices than just Nokia's. It won't be a perfect rock solid OS, but that will give it more momentum.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Works on ExoPC as well, just grease up and get the hardware adaptations done.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Whoa! its a "myfirtsrant"!
Despite the fact that i find it incredibly amusing and funny to read, how is the discussion between members like (but certainly not limited to) Woody14619 and Javispedro helping anything here?
Can we please quit acting like a bunch of ffing children here?
These discussions are tearing this forum apart, whilst we should just be working together here. nokia is'nt gonna be much of a help anymore, so all we really have is each other. But I guess thats not important, just that you can spam this forum with "who is right" and "he started it!".

end of rant.

Sorry had to get this of my chest.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Had you actually read the thread, and not just the last page of posts, you may have noticed this was a discussion involving a lot more that just the two of us. As for "tearing this community apart", you clearly missed the entire point of the discussion, since that exactly what was being discussed. One group was trying to pull the "community" one way (toward MeeGo) while the rest were trying to keep us all in one house (under Maemo).

As a recap: This thread started as a group of developers working on MeeGo's N900 port asking if they should continue to post info about that effort here. It was pretty clear to most that they had a side-agenda of urging developers here to stop developing for Maemo (and CSSU by name at least once) and join them in project MeeGo instead, as it was going to be "the future" of N900. An agenda that I saw early on, and which at least one person (the one that started the thread I believe) confirmed.

I took objection to them urging people to cease work on Maemo/CSSU, and along with others noted that after a year or work, MeeGo couldn't even answer or place a call on a single device, including the N900. Which side would you be on in that discussion? Which side was tearing the community apart? Which side was being childish?

Now we're 1.5 years out (closing on 2?) and MeeGo/CE has "morphed" into Mer/Nemo. They're still not even on par with what Maemo5 delivered in PR1.0 two plus years ago. And with MeeGo dropped by everyone outside of this little group, it seems a bit off the rocker to suggest that it's still the "future" of anything, yet alone the N900. Yet that's been the constant assertion here, even now.

Was there a point to coming back and mentioning it? Yes... Because those that forget their history repeat it. Which is exactly why I (remembering the OpenMoko fiasco) stood against leaping to MeeGo. That, and it shows a little bit of whom among the group had some foresight when it came to "predicting" where things are going.

That may sound "childish" to you, but I ask you this: If you were looking at who's going to take a lead role (say as a council member here), would you prefer someone who's predicted what was going to happen accurately, or someone arguing for what turned out to be a dead end? How would you know where anyone stood without discussing it? How would you even know it happened without it being archived here to read?

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

Well, afaiu Mer/Nemo (similar to MeeGo CE) aims at providing a full Open Source smartphone/cellphone OS. This includes not only the "standard" Linux kernel + user land stuff but also Open Source implementations of vital cellphone functions such as making calls, 3G, or SMS functionality.
While Maemo 5 (Fremantle) as well as Harmattan are to some degree Open Source, the vital cellphone functions such as calls, 3G, SMS etc. are closed source bits. iirc with Maemo5 it's even worse as there are quite a number of closed source parts that are very important to the entire system (bme, e.g., was some keyword iirc).

So in this sense, yes, Mer/Nemo are a pretty big improvement over what we have with Fremantle or Harmattan nowadays Open Source wise. As far as I could follow this whole topic, having Open Source implementations of this cellphone specific stuff is really challenging. And while it may seem quite "trivial" to have such functionality like making calls or sending SMS it may actually be pretty hard work to have these bits implemented as Open Source.

Re: Should MeeGo developers continue to publish info on this forum for maemo users (wrt Nokia device support)?
 

No, it is better to scare of potential devs calling them dead-end guys and hope nokia will save us. Seriously, why some guys here get god-like followship I cannot understand. It is so against the whole idea. This just makes them 'saviours' that lockdown the community into their own bits that cannot be uninstalled, are incompatible, but shhh. Why did we scare of meego/openpandora devs? Do those responsible now feel superior, or do they now sign all their posts: sent from my uber android phone loosers!!! ???