[Meego-handset] Plasma Active on Mer
Lists Hi, I've been doing some work to get Plasma Active from your Trunk:Testing project to build against Mer on COBS which I though may be of interest to people on the lists My Plasma branch is at https://build.pub.meego.com/project/show?project=home%3Avgrade%3Abranches%3AProject%3AKDE%3ATrunk%3ATesting You can find an image for Exopc, kickstart, and various log files here http://bug10738.openaos.org/images/exopc/mer-plasma/ http://bug10738.openaos.org/images/exopc/mer-plasma/xsession-errors http://bug10738.openaos.org/images/exopc/mer-plasma/messages http://bug10738.openaos.org/images/exopc/mer-plasma/Xorg.0.log The first run animated application runs with the swirling segments but as you will see from the logs the plasma-device seg faults. If you leave the device the screen saver shows up and you can unlock normally. Remember when analysing the logs Mer comprises of packages which were pulled up from MeeGo.com:Trunk:Testing (I don't think Plasm Active is building against that on OBS at the moment) and that we have Qt 4.8 Beta in Mer. I would welcome a discussion on where we go from this point with regards to getting plasma-active up. Regards vgrade ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] Naming of Community Edition - community, discussion
I propose these two names for the Community Edition: 1. MerGo makes you think of Mer & MeeGo 2. MerSet makes you think of Mer & (hand)Set Vim ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] CommunityEdition renaming bikeshed poll is now OPEN!
I agree that it's not a good way and as you noticed it's not the intention. Part of the motivation was to slow the endless stream of bikeshed suggestions (we're well over 100 by now) and make people have a look what already was proposed. Also the poll might give the SG some ideas if it e.g. yields support for viable names. Ultimately the CE SG will call the shots and if they chose something completely different, that's fine by me. :) Cheers Thomas -- Sent from my Nokia N950, thus top post and full quote... On 13.10.2011 17:57 Dave Neary wrote: Hi, thomas.ruc...@tieto.com wrote: > To aid the CE SG in their decision making process I've dusted off an > LimeSurvey instance I have around and set up a survey. > > Sivan helped to compile all proposals made so far and well here it is > in all its bikeshed glory: > > http://survey.bfst.de/95275/ > > The survey will run till Monday 23:59:59 UTC so that the results can be made > available to the SG for their meeting on Tuesday. For the record, I think polls are a terrible way to pick names. I would much prefer the main stakeholders get together & pick their favourite. > PS: We took everything and didn't filter in any way (even MerDE is there). Works well in France - as I'm sure you know already. > It will be up to the SG to decide what they want to do and the survey > should not be understood as to be binding them in any way. Oh, good. Cheers, Dave. -- Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] CommunityEdition renaming bikeshed poll is now OPEN!
Hi, thomas.ruc...@tieto.com wrote: > To aid the CE SG in their decision making process I've dusted off an > LimeSurvey instance I have around and set up a survey. > > Sivan helped to compile all proposals made so far and well here it is > in all its bikeshed glory: > > http://survey.bfst.de/95275/ > > The survey will run till Monday 23:59:59 UTC so that the results can be made > available to the SG for their meeting on Tuesday. For the record, I think polls are a terrible way to pick names. I would much prefer the main stakeholders get together & pick their favourite. > PS: We took everything and didn't filter in any way (even MerDE is there). Works well in France - as I'm sure you know already. > It will be up to the SG to decide what they want to do and the survey > should not be understood as to be binding them in any way. Oh, good. Cheers, Dave. -- Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] Mer breadth (Was Naming of Community Edition)
2011/10/12 Andrew Flegg : > On Wed, Oct 12, 2011 at 20:55, Carsten Munk wrote: >> >> "Initially the project will be developing a Core for basing products on >> and will split UX and hardware adaptations out into seperate projects >> within the community surrounding the Core." -- hence the "there's no >> "the" Mer Handset UX". >> >> There's some reasons why this split. [...] > > Thanks makes sense and is well explained. Having said that, I'd be > concerned that a small Core with a few hackers won't be possible to > gain enough momentum to capture a new middle-tier-or-above vendor. Honestly, I think where success lies is with small to medium vendors instead. That's who will have the most strength from this. Of course, the solutions that we intend to provide will be usable for bigger organisations too. > >> 2) We want to move much of the politics out of the Mer project and >> motivate people to create and build their own projects, though basing >> on Mer, much in the same way site projects are based upon Apache >> httpd. - we can't and don't want to govern projects utilizing the >> core, let them innovate on their own terms. > > Apache's an interesting choice of example given there *is* an > overarching "Apache" project and brand under which projects like JCL, > Tomcat, HTTPD, Commons Lang, Commons Collections and so on all > operate. Agreed, perhaps "Linux" would be a better comparison > >> There was a discussion about same topic some days back on IRC and the >> conclusion we reached was: [...] > > It's a little disappointing that so much is happening in realtime on > IRC, preventing those who can't participate 24x7 from contributing. > It's still a massive step-up on private conference calls within MeeGo, > but it is still a barrier to openness when ad-hoc discussions result > in decisions without any pre-prepared agenda. Even post-communication > to the mailing lists would be sufficent. Agreed - we had a hiccup with DNS so that's blocking Mer mailing lists for a little bit. > Well put. But what is the success criteria? My suggestion would be > that a vendor is looking for an ecosystem-in-a-box whilst providing > the differentiation capabilities they feel they need to succeed in > their market. That means a good core; points where they can integrate > either an off-the-shelf OSS UI or build their own differentiating one; > good tools (both for app developers and their own developers looking > to adapt to their hardware) and an assurance that some things (e.g. > security updates for some packages) will be got "for free". Let's face it - if giant companies have difficulties making ecosystems, we'll have even more difficulties. What I think really has value is the fact that you can avoid hiring a lot of Linux people to maintain a simple stack. That it's easy to get things made - want an alarm clock? here, take a beagleboard and an LCD and some speakers, write some QML, there you go. > > A bootstrapping project which delivers a tight Linux userland with Qt > might not provide sufficient leg up for it to appear on a list of > options compared with the perceived "weight" of Ubuntu/Debian/... (or > even, heaven forbid, Tizen). The problem is, again that if those solutions are really so great and easy, why aren't people having an easy time building products using these things? With Tizen, it's vaporware right now. But we intend on utilizing Tizen in the core where possible - our angle is just ease through Qt instead and a open innovative process. > > So, I suppose my question is: what's the perceived problem? How does > Mer address it? How is success measured? And is Core the focus because > it's the right answer for the perceived problem or because it's > pragmatically the thing which can be delivered now? Success for Mer is measured in people using it to innovate and for people to make prototypes and products using it. The Core is the focus as this is the simple thing many really lust for is a simple, easy-to-port working Linux platform, openly developed and governed that doesn't rely on the whims of corporate choices and roadmaps, that you can build your business on without risking bankruptcy at every new keynote opportunity. Success for myself is if I have a stable foundation for my business to make products in a world like in http://www.youtube.com/watch?v=6Cf7IL_eZ38 - and having fun developing the core at same time. BR Carsten Munk > > Cheers, > > Andrew > > -- > Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ > ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
[Meego-handset] CommunityEdition renaming bikeshed poll is now OPEN!
As David just put it aptly: >PS. This thread has now gone on long enough that I'm wondering what >process is in place for going from where we are to a decision. Perhaps >the CE team leaders need to narrow down all of the proposals & chatter >to a list of suggestions, and then get together and pick one? To aid the CE SG in their decision making process I've dusted off an LimeSurvey instance I have around and set up a survey. Sivan helped to compile all proposals made so far and well here it is in all its bikeshed glory: http://survey.bfst.de/95275/ The survey will run till Monday 23:59:59 UTC so that the results can be made available to the SG for their meeting on Tuesday. Cheers Thomas PS: We took everything and didn't filter in any way (even MerDE is there). It will be up to the SG to decide what they want to do and the survey should not be understood as to be binding them in any way. The hope is though that it will help them to understand what the community would like to see though. ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
Re: [Meego-handset] Naming of Community Edition - community discussion
Hi, On 10/12/2011 06:51 PM, Tim Samoff wrote: I agree. If code names are required, I suggest types of storms: http://en.wikipedia.org/wiki/Storm#Types Or perhaps clouds? Nimbus, Cumulus, Nimbus, Stratus, and Cirrus are all pretty cool codenames. Presumably all taken,, also, but if none of them are used in the realm of mobile software, we should be OK on the TM front. It references the old naming structure while remaining obtuse enough to be different. And, names like Cyclone, Typhoon, Firestorm, etc. are just cool. ;) I agree :) Cheers, Dave. PS. This thread has now gone on long enough that I'm wondering what process is in place for going from where we are to a decision. Perhaps the CE team leaders need to narrow down all of the proposals & chatter to a list of suggestions, and then get together and pick one? -- Email: dne...@maemo.org Jabber: nea...@gmail.com ___ MeeGo-handset mailing list MeeGo-handset@lists.meego.com http://lists.meego.com/listinfo/meego-handset
