Re: [MeeGo-dev] MeeGo.com Outage and general maintenance - 10/20/2012 16:00 UTC for 8 hours.
Hello Nnaemeka. MeeGo is alive and continues currently under the Mer project: http://www.merproject.org/ and is used by companies like Jolla: https://twitter.com/JollaMobile Also, the infrastructure at MeeGo.com is in good use for example in the form of the public OBS: https://build.pub.meego.com/ -Timo 2012/10/25 Nnaemeka David nnaemeka.da...@gmail.com: Hello. Please, forgive me if I transgress. But i heard the meego development has been discontinued so i decided to look elsewhere. is this true? thaks On 10/18/12, adam.gretzin...@linux.intel.com adam.gretzin...@linux.intel.com wrote: MeeGo General Backend Maintenance Announcement for 10/20/2012 at 16:00 UTC Some general maintenance activities will be taking place on the MeeGo.com and MeeGo related sites on Saturday, October 20, 2012 at 16:00 UTC. (Saturday October, 20, 2012 09:00 PDT) for a duration of 8 hours. During this time multiple Patching, Firmware updates, Virtual Machine Migrations will be in progress. While the window is 8 hours long most services will be interrupted once or twice. --- Adam Gretzinger adam.r.gretzin...@intel.com adam.gretzin...@linux.intel.com Intel Open Source Technology Center ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines -- Writer, Translator and Web designer. nnaemeka david +234 08024287480, +234 07042029927 http://emekadavid-solvingit.blogspot.com/ (mon blog) http://www.facebook.com/people/Nnaemeka-David/11963356636 (facebook page) http://twitter.com/#!/emeka_david (twitter profile) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo Reconstructed - a plan of action and direction for MeeGo
2011/10/5 Jeremiah Foster jeremiah.fos...@pelagicore.com: Distrowatch are server and dektop disties. The special thing in MeeGo was that the focus was on emerging devices. And how exactly did it do that? By using Connman? By using an embedded Linux kernel? Btrfs? By being small? What exactly makes MeeGo different from other desktop distros? Or was it just a little bit of marketing? I agree with Jeremiah here. MeeGo really was a lot more pain to get slimmed down with its actually desktop distro legacy and for example package dependencies than with Debian. Maemo was the actual embedded OS, but MeeGo never got to reach it. That said, I do believe there is a lot of room and need for Mer, and potentially Tizen (hopefully fully usable by Mer and others) when it actually materializes, simply because it tries to continue MeeGo as is but fixing the problems mostly everyone agrees with - MeeGo was not lean core at any point, and the community, decision and communication aspects sucked in many ways. Doing so gets the existing MeeGo community people to continue, while any other one choice like Debian (advertised by me among else), openSUSE (advertised by Jon among else), Yocto or other would not get all the same people on-board. With individuals it can be about simple things like familiriaty with tools, and OBS does rock. The important thing is to do something that matters (to you), and if possible do it in a way that everyone can benefit. The lesson with MeeGo here should be not to put all eggs into one basket. I'm a multi-distro person myself, and see strong value in distro-previously-called-MeeGo, Ubuntu, Yocto etc. in addition to Debian which I think rules the most broadly in its operation and scope. -Timo ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] MeeGo Reconstructed - a plan of action and direction for MeeGo
ma, 2011-10-03 kello 19:09 +0100, Si Howard kirjoitti: I'm for that! Wasn't the Mer project part of the Maemo 5.0 porting to the Nokia N8X0 platform? That's one way of putting it, but it was indeed about reconstructing Maemo so that it worked as a whole distribution. That then made possible to try to get newer Maemo components working on older tablets purely as a community effort. So more like Maemo 5.0 porting to the Nokia N8X0 platform was a part of the Mer project, not the other way around :) -Timo ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [MeeGo-community] invitation... and a second one
(cc:ing to meego-dev as well since Jos originally wanted to post there, too) to, 2011-09-29 kello 21:40 +0200, Jos Poortvliet kirjoitti: Dear MeeGo friends! Many people in your community wonder where to go since the Tizen announcement. At a MeeGo meet in Tampere, many expressed concerns: can we contribute to Tizen? How long will it last *this time*? How will Samsung behave? I know many of you are concerned about loosing the great community you've build. Thanks Jos for the invitation! I have now written another invitation from Debian perspective and an overview of the situation from my point of view at: http://losca.blogspot.com/2011/10/from-meego-to-tizen-debian.html In brief: do not fall in agony, there is a wide range of communities out there. Just answer the Aaron Seigo's question about thinking about evaluating own motives in contributing to for example MeeGo. Then choose the communities (plural) you want to work in! Obviously it could be the future Tizen community as well. But it could be openSUSE, Debian, Qt project, KDE project, Mer, or any number of other possibilities. All of them have some similarities with what MeeGo was. -Timo ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] cross-armv7l-gcc, cross-armv5tel-gcc are not installable
2010/6/28 Jan-Simon Möller jsmoel...@linuxfoundation.org: me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -c test.c as: unrecognized option '-meabi=5' me...@[meego-netbook-sdk]::~$ /opt/cross/bin/armv7l-meego-linux-gnueabi-gcc -print-prog-name=as as ok, what happens if you do AS=/opt/cross/bin/armv7l-meego-linux-gnueabi-as LD=/opt/cross/bin/armv7l-meego-linux-gnueabi-ld gcc .. I have identical output for both commands also when using those extra variables. And tested both when using cross-armv7-* packages from 1.0 and trunk in Ubuntu 10.04 i386 chroot (helped with alien) and when installing those packages inside MeeGo SDK chroot with zypper and trying to compile after that. Just trying hello world. The host system itself is 64-bit Ubuntu. This one is worth a bugreport. Please assign it to me - jsmoel...@linuxfoundation.org. Was this filed? Cannot find in bugs.meego.com but maybe I just don't what to search for. -Timo ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] how to start developing on MeeGo?
2010/4/29 David Greaves da...@dgreaves.com: http://wiki.meego.com/Packaging/Deb_conversion_example More to follow - we'd appreciate constructive feedback both from those knowledgeable about rpms and those trying to gain that knowledge. Yes, feedback and changes welcome. Like I noted on the discussion page, I learned rpm:s myself during the writing of the page, so definitely there is room for improvement and expansion. -Timo ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
