Welcome to MeeGo
Hi Everyone
I'm sure you've heard the news: Moblin and maemo are merging! We are taking the best pieces from these two open source projects and are creating the MeeGo software platform. Both teams have worked for a long time to support the needs of the mobile user experience - and MeeGo will make this even better. We want it to be fun, focused, flexible, technically challenging and ultimately, something that can change the world.
We all use mobile devices every day. The power and capability of handhelds has reached astounding levels - netbooks have been a runaway success - and connected TVs, tablets, in-vehicle infotainment, and media phones are fast growing new markets for devices with unheard of performance. Our goal is to develop the best software to go with those devices. The teams behind maemo and Moblin have plenty of experience and even more ideas on how to make things better - and together we will create something special.
The MeeGo website is still evolving - you'll run into a few "coming soon" pages as we pull all the content together and get things ready for our first project release in the second quarter. But there's already a lot to see - and a community to join! Please take a look - and come back often as we approach that first release.
We really want to hear from you. Be in on IRC, on our developer mailing list, or through bugzilla. MeeGo is an open project and it will be successful through its developer community. It's my personal goal to make sure that we can all together be successful. And have fun.
Imad Sousou
Director of Intel’s Open Source Technology Center
(and now also co-chair of the MeeGo steering group)
- imad's blog
- Login or register to post comments
Comments
Will MeeGo run on my N900?
Will MeeGo run on my N900?
already answered
Please see the reply to this question on this page: http://meego.com/community/blogs/valhalla/2010/towards-day-one. In summary, a developer version is being planned.
Wishing the best
As long as MeeGo is as dedicated and serious towards the open source community (you guys on this site ;-) as they have been so far with Maemo, the future of MeeGo is very promising, indeed.
Already Android is drifting away, and, at the same time, together with iPhone, shows signs of fatigue ---- N900 and Maemo came like a wake-up call to all dull companies with short term strategies. Well done, Nokia Maemo and N900 team !
And well done to all the contributors of software to Maemo - the number of applications might not be so large, but the quality is very high --- NMap on my mobile ? Siiiiick ;-)
Yay!
This is great news! Will MeeGo run on my 5800?
will soon!
will soon!
It is true meego will support AMD processors?
I want to create a meego installer for AMD processor. Please, help me.
MEEGO???? Jeez!!!
Repost from Moblin Site:
Clearly Intel & Nokia need some marketing people. They could have picked a better name than Meego. Something that accentuates the power of Linux. Something that sounds like power and high tech. Meego sounds like me wanna go to the bathroom, or meego somewhere. Are you sure they didn't hire the same gang of people that came up with iPad for Apple?
I am no marketing guy, but clearly I think some of the names I have thought of below sound way better and can "draw" people , consumers and devs alike to the platform just by the name alone.
1. Mobile-X
2. AMP (Advanced Mobile Platform)
3. NXM (Next X for Mobiles)
4. M2 (M Squared..... Maemo x Moblin)
I could go on and on , but the 4 I have listed above ring better to the ear than Meego. If it's not too late, I wish you guys would reconsider. Perhaps next time have a poll or something, but Meego!!!! Honestly folks... Let's hope the sum of its parts is better than its name.
My 2 cents.
I agree, but...
I'm hoping WE can help overcome the cynical perceptions of this less-than-ideal name. In the end, it's about the product.
Why not Cyborg as a C/C++ alternative to Andriod!
Why not Cyborg as a C/C++ alternative to Andriod! There could be a really cool logo designed for this one!
I second the motion
MeeGo was not a smart name to choose, and i'm sure that the majority of consumers will agree on that (surveys pending). Decisions for things like this don't often get much objective, consultative input inside companies, for a lot of reasons. It's like Nokia deciding back in the day to have double touch and single touch jumbled up in the 5800, etc. They'll recognise their wary ways soon enough. Whether or not they'll do something about it, though...
KDE coop—one FOSS ecosystem from the desktop to the smartphone
I would like to say, I was totally surprised by this announcement. But if you (Nokia and intel) do a great job—put a lot of developer resources and money into it, work closely on and with the upstream projects, treat the community well, use as much open standards as you can (Telepathy, Avahi, etc.)—I think MeGoo can get something really beautiful. Although I have to say I do not like RPM. ;-)
I really do like the idea of having one distro from the smartphone to the netbook. That is a point Apple is imho right at with the iPad: If there is such a third device category, it can't have yet another whole isolated operating system / software stack.
What I love most about maemo (in contrast to Android) and why I bought an N900: it uses a lot of standardized stuff from the GNU/Linux and free software world. I hope you will keep your promise that MeGoo will do this as well—or even intensify it. But why let this paradigm be limited to system level services like DBus/Telepathy, …? You already mentioned, Qt will be an important part of MeGoo—that sounds great, I love Qt! Okay, but why not expand this principle to the desktop and build MeGoo on top of KDE and Plasma technology—and while doing that also strongly boost the cooperation between KDE and Gnome and their work on common free software desktop standards‽
Please help us to create one great FOSS ecosystem, which is usable from the desktop to the smartphone, and build on top of it MeeGoo: a great GNU/Linux distro for mobiles, handhalds, smartphones, netbooks and tablets.
PS: Why not merge with WebOS as well? ;-)
Cyborg
> PS: Why not merge with WebOS as well? ;-)
and, of course, with some Openmoko stuff
(http://wiki.openmoko.org/wiki/Distributions)
So take the best out of WebOS, moblin, maemo and Openmoko and create ›Cyborg‹ ;-)
"Moblin and maemo are
"Moblin and maemo are merging! "
Does the "merging" mean no more moblin and no more maemo? Or new MeeGo and still have moblin and maemo?
I hope after the merge, all the developers and the users merge too. Other wise, it is another break.
MeeGo-mania!
Dear Imad,
Thanks for your hard work! This is a great opportunity for everyone to be involved in a project that is great for the community and great for each of us as individuals. I'm really looking forward to the soon-to-be-released MeeGo devices; especially the "pocketables," which will be the next cycle after the breakthrough success of the N900.
Regarding the upcoming pocketable devices to run on MeeGo: I have read conflicting reports as to a tentative release time, specifically that the icebreaker MeeGo instances will be available Q2 2010. Could you offer any clarification on this pressing question?
And finally, welcome to all our fellow aMeeGos!
Mobile C++ API Yes!!!!!
Mobile C++ API Yes! After looking at Android, I thought wouldn't it be nice to have a faster (running and development cycle) C/C++ mobile API.
Also Intel and Nokia should look at product visualization by integrating with design tools such as SolidWorks wich would allow for mobile products to be designed, coded and tested as a virtual device.
distribution and vm support
As a developer, one of the gaps in Moblin was iso distribution and support for VMs. There were numerous work arounds posted to navigate this gap, but it would have been simpler to load the ISO in a vm.
My dev platform of choice is a VM on my workstation - even if the app target is netbook or smart phone. Directly supporting this model would be great.
debian or more specifically
debian or more specifically deb and its tools(ipkg is similar too) is the de facto standard for embedded system, the rpm choice is a huge turn off at least for me. plus moblin has never really had an active community (too bloated, rpm not deb,etc). I would like to see deb support from meego, seriously.
Strongly Agreed
While moblin doesn't have any real active community, this choice simply drops maemo community out and meego will lose community people. Unless meego can provide seamless transition tools for developers to move previous works on maemo into meego, I can't understand this decision which has no benefits for meego.
Full of hope
Dear MeeGo team,
I think there are many who are filled with hope for this new initiative, and you can count me in :-)
First and foremost I am hopeful that porting from existing linux applications will be simple -
would love to run the same applications on my desktop and on my phone/device - or am I being too naïve ? :-)
For instance, VNC on Maemo is a very useful option.
And, I love to see Google and Apple get some fair competition.
Thank you.
What kind of community approach?
As Maemo community member I would be very interested to hear about what kind of vision Intel has for MeeGo community.
Great thing about Maemo.org is it's acceptance of endusers and amateur enthusiasts, and providing means to these members to have input in the community. My Moblin knowledge is basically limited to checking Moblin.org today, but it seems that Moblin community was only for corporate people involved and 3rd party developers. It would be great to hear what kind of plans, if any, Intel has for MeeGo community beyond developers.
Who Is The Community?
The community will be who joins it.
I am an end user who last wrote code in the 1980s for the Commodore 64. Here I am.
What can I contribute? I hope to contribute an end user point of view.
What do I gain? I hope to gain a better understanding of how the parts fit together so I am not using a "black box" but a device I understand and therefore can better appreciate it's strengths and weaknesses.
I may never write a line of code but I will learn to appreciate the struggles, the limits and the successes of those who do.
Without end user's
Without end user's experience, MeeGo will just be a baby toy in tiny group.
How to improve end user's experience as microsoft and apple do, I think, is a major job for MeeGo community.
Community mailing list created
I wanted to let everyone know that a community mailing list was created for discussions around the community building and infrastructure for MeeGo. I know a lot of discussion has already begun on talk.maemo.org, which is great. Feel free to subscribe to the meego list and begin talking about what is needed to make MeeGo equally as compelling of a community as maemo.org!
You can subscribe to the list from your account page on this site, or by heading over to the mailman interface:
http://lists.meego.com/listinfo/meego-community
A few wiki pages have already been started to look at building out the community:
http://wiki.meego.com/Maemo_and_Moblin_community_assets
http://wiki.meego.com/Proposal_for_a_Community_working_group
Thanks
Agreed
Thanks for bringing this up Rauha, it's a very important question to be sure!
I'm of course very interested in finding out how the maemo.org community, all of it, can fit in here...
bringing the values from maemo community
Hi, are there any drafted plans for utilizing all the advantages from the two parent initatives?
E.g. maemo has quite an active community, which recently (N900 release) started to learn that not everybody is a power user/community champion/developer in one person.
There are different interests for different people and if meego wants to benefit from the previous userbase and the values built during the 2 and 5 years of history from the two, it would be good to cater for all needs at one place (to avoid user and developer sites spawning in different places etc.).
It would also help platform acceptance - imagine if all users and community members could be smoothly channeled here? The power of 40000 community members, thousands of Qt developers all contributing at one place would create tremendous momentum within weeks.
One example here: http://talk.maemo.org/showthread.php?t=44581
Dear Mr Sousou, are you considering a discussion forum on here?
I'm a member over at maemo.org as well. Part of the great appeal of Maemo has been its user community where both developers and users meet, not only to develop but also to discuss, share ideas, suggestions, solutions etc. It makes the community vibrant. So my question to you is, are you planning on opening that up on meego.com, or are you planning on keeping this strictly OS development focused, where only official bloggers can start new subject threads?
Thank you.
discussion forum
Is in the works. Start here: http://wiki.meego.com/Forum_/_Talk
Existing devices
i'm a moblin user and a n900 owner, and even though i like the concept and i think it's neccesary to build around the community, my question is... where do we stand, users of existing devices like the n900, is maemo 6 going to come out?, it's gonna be scrapped in favor of meego?, am i going to lose my money because it wont run on the n900?... this is a message specialy for nokia... they put out these devices and now are kinda improvising with their os strategy, if you see the symbian development and future deployment you would see that too, i'm a huge nokia fan and i'm really happy that intel has joined in to make the best devices available, love moblin interface, but i don't want lose my money if i'm going to invest time on these kinda projects and to not wonder if in the next quearter they're going to say "we just got google involved so we're gonna scrap everything we told you 4 months ago", that's something that really worries me
I'm in your boat... but i
I'm in your boat... but i just got here 2 days ago.
Did Nokia just kill the OS for my phone just a few months after it was released?
Seriously if we don't get an upgrade path there will be rage-a-plenty.
The N900 is a damn nice phone and i'm having a ball with the thing, but this announcement has me a bit worried.
Nokia please clarity :\
cool
A very cool idea, working together like this will make the impact of both larger. And Qt seems like the perfect choice for something like this, high-level and crossplatform as it is. Moreover, the KDE community can provide a large number of excellent applications already, and you guys might be able to take advantage of Plasma to provide scalable, network share-able, easy-to-develop and powerfull widget technology.
Question
Hi,
Maybe this is wrong place to ask...
Will this new platform support .DEB? Or RPM maybe?
Thank you,
Stefan.
RPM
RPM will be used. Personally I prefer Debian, but...
.Deb or RPM
Why RPM, .Deb is so much more used in the community.
Kristoffel
.RPM is being used because of
.RPM is being used because of the Linux Standard Base (LSB), which is a project started by the Linux Foundation in order to reduce the differences between individual Linux distributions to make it easier and cheaper for developers to port their apps to different distributions.
Which is not surprising at all, as it is the Linux Foundation that is hosting this project as well.
Another Vote For DPKG
I would definitely prefer deb/apt over rpm/yum any day of the week. Why not do what Debian does and make alien available if people really want to use rpm?
I do actually deal with both on a daily basis, and I've seen rpm/yum royally screw with dependencies a lot more than deb/apt.
apt also tends to be a lot faster and more efficient that yum which is surely a consideration when dealing with mobile devices.
LSB might be a great idea, but it does have flaws such as recommending rpm as the package format of choice.
Linux standard base nonscence
I always tried to avoid all linuxdistro's that use RPM.
It makes the packagemanager disolve the dependancies way to slow in comparison to apt or emerge.
This really is the biggest turnoff in this otherwise positive news.
Linux is about choice and not about some whackejobs desiding RPM is the way to go because most commercial software supports it. Deb is superior if I wouldn't use a source based distro myself I would be using a debian based distro.
The Linux Standard Base is a joke and has never served any purpose. I severaly doubt that could ever be a primary reason.
PLEASE Reconsider and use deb.
Policy might be more significant than package file format
Stability and safety require strict policy of what packages may contain and touch. Isn't that the Debian way?
That challenge becomes pretty hard if it's made possible for mainstream users to install packages from other sources than rigorously controlled central repositories. Ad-hoc installation scripts would be out of question. Only new files or ones installed by earlier version of same package maintainer should be accepted. Configuration management should go through a proxy that would require the user to accept access to targeted services.
Even then, malware would flourish. Unless each binary is restricted from seeing any parts of the system foreign to it. Capability-based encapsulation, then?
I'll now shut up in a late attempt to hide my amateurishness.