LinuxMCE Forums

General => Feature requests & roadmap => Topic started by: tschak909 on June 03, 2010, 09:39:14 pm

Title: Meego (was: Attitude of COOPERATION.)
Post by: tschak909 on June 03, 2010, 09:39:14 pm
We intend to move to 1004 for the immediate future. I am doing research to move the stack to MeeGo.

-Thom
Title: Meego (was: Attitude of COOPERATION.)
Post by: Enigmus on June 04, 2010, 01:34:26 pm
I took a quick look at MeeGo.  It looks exciting, but it seems like it would be a lot of work to convert to a new foundation.  However, I trust you would know better then I.
Title: Meego (was: Attitude of COOPERATION.)
Post by: B34N on June 04, 2010, 03:25:02 pm
I am doing research to move the stack to MeeGo.

Is it the consensus of LMCE developers that MeeGo will be the open source OS of choice for portable devices in the future? It looks very promising to me but I'm not qualified to make that judgment. I installed 1.0 it on my netbook and it looked ok.
Title: Meego (was: Attitude of COOPERATION.)
Post by: tschak909 on June 04, 2010, 03:27:19 pm
Let me make this very clear,

at this point, there is no indication of where MeeGo will Go.

I am doing this, as a systems analysis and feasibility research project.

My intention is to present a working system as a proof of concept, and ask for developers to test, review, and to make a decision.

-Thom
Title: Meego (was: Attitude of COOPERATION.)
Post by: philtrick on August 10, 2010, 12:55:34 am
Let me make this very clear,

at this point, there is no indication of where MeeGo will Go.

I am doing this, as a systems analysis and feasibility research project.

My intention is to present a working system as a proof of concept, and ask for developers to test, review, and to make a decision.

-Thom

This is very interesting from a couple of directions:

I think a base like meego will provide a solid platform to build on
The screens and layouts for the handset versions of meego will be invaluable to the project
I have an O2joggler and I am going to try to get meego running on it as a device, but I was thinking that booting gPXE from the Efi and using that to load the joggler as an MD for the bedside table or similar.

(Mind you, that will happen when I get linuxmce working which at the moment is proving to be a bit of a nightmare, but that is the subject of another post....)


Right, that is my 2cents worth, off to sleep!
Phil
Title: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 10, 2010, 07:00:13 pm
Let me make this very clear,

at this point, there is no indication of where MeeGo will Go.

I am doing this, as a systems analysis and feasibility research project.

My intention is to present a working system as a proof of concept, and ask for developers to test, review, and to make a decision.

-Thom

This is very interesting from a couple of directions:

I think a base like meego will provide a solid platform to build on
The screens and layouts for the handset versions of meego will be invaluable to the project
I have an O2joggler and I am going to try to get meego running on it as a device, but I was thinking that booting gPXE from the Efi and using that to load the joggler as an MD for the bedside table or similar.

(Mind you, that will happen when I get linuxmce working which at the moment is proving to be a bit of a nightmare, but that is the subject of another post....)


Right, that is my 2cents worth, off to sleep!
Phil

Why not look at porting Touch Orbiter to the 02joggler? See here for info http://wiki.linuxmce.org/index.php/Touch_Orbiter_-_for_the_CUWIN3500_in-wall_Touch_Panel (http://wiki.linuxmce.org/index.php/Touch_Orbiter_-_for_the_CUWIN3500_in-wall_Touch_Panel)

This will get you today's Orbiter functionality on the Joggler and in the future we plan to enhance Touch Orbiter so that local UI capabilities of the host device/OS can be integrated eg if the host device/OS support dynamic scrollable lists or any other UI widget these will be part of the UI experience on that device...on other simpler device the Ui experience might be much more spartan & basic.

Anyway getting Touch Orbiter ported to any OS/Dev environment only requires limited knowledge of developing for the target device/OS and no requirement to understand the internals of the Orbiter sources themselves...and we provide full source code for the WinCE 5.0 reference implementation to use as your base.

All the best


Andrew
Title: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 15, 2010, 04:04:31 am
Let me make this very clear,
at this point, there is no indication of where MeeGo will Go.

Hi all,
This is my first post: let me breefly introduce myself:
I live in Brussels (hence my poor english), I'm an economist and have been a Linux fan for years.

back to the discussion:
The MeeGo option looks very good to me:

* backed by the biggest CPU players: Intel and ARM (I hope AMD will join the party)
* backed by Linaro, a big budget Linux tools player (ARM, IBM, Samsung, ST-Erisson, TI)
http://www.linaro.org/why-linaro/
* MeeGo is Linux, 100% open source
http://www.linuxfoundation.org/lp/page/meego
* for developers: Qt, a cross-platform application and UI framework to target desktops, notebooks, netbooks, tablets and phones
http://qt.nokia.com/

* MeeGo for Netbooks 1.1 will be available in october and deployed in the Intel-ecosytem:
 Asus, Acer, MSI, etc. will have MeeGo netbooks and tablets.
http://www.youtube.com/watch?v=m4vv7yFaqxw&feature=player_embedded
* MeeGo for Handsets 1.1 (Nokia high-end phones) will be available in november-december.
 Nokia is by far the biggest mobile phone manufacturer in the world, but the US market and the high-end segment are Nokia's weak points at the moment. MeeGo phones based on the latest and greatest Qualcomm CPUs and playing nice with the US carriers will remedy this anomaly.

MeeGo's website explains it probably better than me: http://meego.com/
One last thing: Windows dominates the desktop, but Linux will rule the mobile world !  ;)


Hope this helps,
Olivier
Title: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 15, 2010, 01:21:46 pm
Let me make this very clear,
at this point, there is no indication of where MeeGo will Go.

Hi all,
This is my first post: let me breefly introduce myself:
I live in Brussels (hence my poor english), I'm an economist and have been a Linux fan for years.

back to the discussion:
The MeeGo option looks very good to me:

* backed by the biggest CPU players: Intel and ARM (I hope AMD will join the party)
* backed by Linaro, a big budget Linux tools player (ARM, IBM, Samsung, ST-Erisson, TI)
http://www.linaro.org/why-linaro/
* MeeGo is Linux, 100% open source
http://www.linuxfoundation.org/lp/page/meego
* for developers: Qt, a cross-platform application and UI framework to target desktops, notebooks, netbooks, tablets and phones
http://qt.nokia.com/

* MeeGo for Netbooks 1.1 will be available in october and deployed in the Intel-ecosytem:
 Asus, Acer, MSI, etc. will have MeeGo netbooks and tablets.
http://www.youtube.com/watch?v=m4vv7yFaqxw&feature=player_embedded
* MeeGo for Handsets 1.1 (Nokia high-end phones) will be available in november-december.
 Nokia is by far the biggest mobile phone manufacturer in the world, but the US market and the high-end segment are Nokia's weak points at the moment. MeeGo phones based on the latest and greatest Qualcomm CPUs and playing nice with the US carriers will remedy this anomaly.

MeeGo's website explains it probably better than me: http://meego.com/
One last thing: Windows dominates the desktop, but Linux will rule the mobile world !  ;)


Hope this helps,
Olivier

Touch Orbiter will run under Meego too. So I would see this as the best development path to take.

Andrew
Title: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 16, 2010, 05:21:57 am
It would be beneficial to LinuxMCE to have a presence on MeeGo, a high-profile project, to attract new developers.
An example: a small-scale project like "MeeGo Home" (Home automation) on a tablet would be very attractive !  ;)

It could be even hosted here, to keep it simple for a newcomer:  :)
https://projects.forum.nokia.com/home

If we don't do it, someone else will, it's almost a certainty.
It's one of the biggest problems in open source: people reinventing the wheel ...

http://forum.meego.com/showthread.php?t=715
http://forum.meego.com/showthread.php?t=1010
Title: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 16, 2010, 08:10:08 am
It would be beneficial to LinuxMCE to have a presence on MeeGo, a high-profile project, to attract new developers.
An example: a small-scale project like "MeeGo Home" (Home automation) on a tablet would be very attractive !  ;)
But the problem is it would not be s 'small' project at all...it would be a very substantial undertaking and one requiring an enormous amount of effort from a team of devs who have a detailed understanding of LinuxMCE.
Quote

It could be even hosted here, to keep it simple for a newcomer:  :)
https://projects.forum.nokia.com/home
Believe me this would not be 'simple' and would certainly not be good newcomer territory.
Quote

If we don't do it, someone else will, it's almost a certainty.
It's one of the biggest problems in open source: people reinventing the wheel ...

http://forum.meego.com/showthread.php?t=715
http://forum.meego.com/showthread.php?t=1010
If your up for it why not kick the effort off yourself? No one here would be against it...or hold you back from trying. What I am pointing out is the scale of the task...LinuxMCE is not a single monolithic piece of software...its a very large rambling codebase that has truck loads of dependencies and therefore high complexity. But having said that if you can gather some like minded people alongside you then you can as a group get your heads into the code and create a new branch in svn and get started.

All the best

Andrew
Title: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 16, 2010, 09:44:11 am
The basic idea would be to engage a dialogue with developers interested in Home Automation in the MeeGo Forum.
I certainly couldn't do this: I'm not a programmer and my english is not good enough.  :)

Like you said, LinuxMCE is a "very large rambling codebase that has truck loads of dependencies and therefore high complexity."
So even if a young developer wants to do "his own thing", that's not a problem, just keep in touch.  ;)

Regards,
Olivier
Title: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 16, 2010, 12:38:01 pm
The basic idea would be to engage a dialogue with developers interested in Home Automation in the MeeGo Forum.
I certainly couldn't do this: I'm not a programmer and my english is not good enough.  :)

Like you said, LinuxMCE is a "very large rambling codebase that has truck loads of dependencies and therefore high complexity."
So even if a young developer wants to do "his own thing", that's not a problem, just keep in touch.  ;)

Regards,
Olivier

Hi Olivier,

I'd love to see some Meego devs build a version of our Touch Orbiter for Meego portable devices... this could be done really very easily indeed (you dont need any detailed understanding of LinuxMCE to implement Touch Orbiter) and would provide the starting point for bringing Meego handheld devices to a point where they could be used as touch based Orbiters (ie the user interface to the system).

See here for info & source code; http://wiki.linuxmce.org/index.php/Touch_Orbiter_-_for_the_CUWIN3500_in-wall_Touch_Panel (http://wiki.linuxmce.org/index.php/Touch_Orbiter_-_for_the_CUWIN3500_in-wall_Touch_Panel)

All the best


Andrew
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 17, 2010, 06:27:37 am
yep, excellent idea !  :)

But I read in the wiki that the Orbiter software already works for Maemo (= +- MeeGo) and the Nokia N800/N900
http://wiki.linuxmce.org/index.php/Nokia_N800

Maybe the best option is to wait for MeeGo 1.1 in october: we'll have loads of netbooks, tablets and phones and a mature OS !  ;)
All these devices (even Symbian phones) will be compatible with Qt.
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 17, 2010, 09:38:58 am
yep, excellent idea !  :)

But I read in the wiki that the Orbiter software already works for Maemo (= +- MeeGo) and the Nokia N800/N900
http://wiki.linuxmce.org/index.php/Nokia_N800

Maybe the best option is to wait for MeeGo 1.1 in october: we'll have loads of netbooks, tablets and phones and a mature OS !  ;)
All these devices (even Symbian phones) will be compatible with Qt.

Yes there is an Nokia N800/N810 Orbiter - and there has been for a long time too. The problem is that the N800/Maemo Orbiter uses the full Orbiter codebase (ie whats running on an MD) but really makes no use of about 85-90% of that code. This makes it way too complex for the task it performs and also makes it a very big job porting it to new platforms or keeping it working on existing ones.

Thats why Touch Orbiter is so exciting - it light 7 simple because it uses proxy_orbiter (running on the Core) and this makes the code running on the target device very simple and easy to support/port. This brings the added advantage that someone coming into LinuxMCE from outside the community can get into Touch Orbiter without having to study the whole LinuxMCE codebase for a year first before writing a line of code! With Touch Orbiter the only skills you need are ones relating to the device/OS you are porting Touch Orbiter too.

Because of this simplicity we believe that Touch Orbiter is a perfect way to encourage development not only lots of new control devices but importantly a way to get more Devs to try LinuxMCE for the first time

All the best



Andrew
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 17, 2010, 12:48:37 pm
Thanks, I think I'm getting it !   ;)

Just a last noob question: do you think it makes sense to put Touch Orbiter on a basic netbook, without a touch UI ?
I'm asking this because MeeGo for Netbooks:
* has a huge potential market, right now: http://wiki.meego.com/Devices
* is an easy target

Real touch devices like MeeGo tablets and phones will be important, but much later
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 17, 2010, 02:39:17 pm
Thanks, I think I'm getting it !   ;)

Just a last noob question: do you think it makes sense to put Touch Orbiter on a basic netbook, without a touch UI ?
I'm asking this because MeeGo for Netbooks:
* has a huge potential market, right now: http://wiki.meego.com/Devices
* is an easy target

Real touch devices like MeeGo tablets and phones will be important, but much later


Well yes I think it does. Touch Orbiter is in effect the functionality of Web Orbiter 2.0 wrapped up in C++ so that  it can run without the need for a Web Browser to act as a 'container'. We use Web Orbiter's from desktop & laptops a lot in our installations.

Go for it :-)

Andrew
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 17, 2010, 04:44:22 pm
OK, I'll try to find a MeeGo dev;
I'll send him to your Touch Orbiter thread:
http://forum.linuxmce.org/index.php?topic=10583.0

Another solution would be to include Touch Orbiter in the MeeGo Architecture:
http://meego.com/developers/meego-architecture
do you think this would be an acceptable option for these guys ?

Regards,
Olivier
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 18, 2010, 09:17:47 am
OK, I'll try to find a MeeGo dev;
I'll send him to your Touch Orbiter thread:
http://forum.linuxmce.org/index.php?topic=10583.0

Another solution would be to include Touch Orbiter in the MeeGo Architecture:
http://meego.com/developers/meego-architecture
do you think this would be an acceptable option for these guys ?

Regards,
Olivier

Well re including the Touch Orbiter in the Meego UX layer...that sounds like a big hill to climb as i guess that layer is sanctioned at some level. But making a compatible UX layer App is more like where we should start and finding someone in the Meego world to put that in place would seem possible. The Touch Orbiter is not a complex app to create.

All the best

Andrew
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 18, 2010, 10:06:09 am
including the Touch Orbiter in the Meego UX layer...that sounds like a big hill to climb as i guess that layer is sanctioned at some level.

It would be a very attractive proposition for the MeeGo team if:
* the code is small , effective and maintained.
* the UI is "MeeGo-like"

Every MeeGo device would be a ready-to-use Orbiter:
this would be a killer-app for the MeeGo project and the LinuxMCE project, of course !  ;)

But if we want Touch Orbiter to be included in MeeGo for Netbooks 1.1 (= commercial launch in october), we should start now !  :)

Regards,
Olivier
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 18, 2010, 10:58:35 am
including the Touch Orbiter in the Meego UX layer...that sounds like a big hill to climb as i guess that layer is sanctioned at some level.

It would be a very attractive proposition for the MeeGo team if the code is small , effective and maintained.
Every MeeGo device would be a ready-to-use Orbiter:
this would be a killer-app for the MeeGo project and the LinuxMCE project, of course !  ;)

But if we want Touch Orbiter to be included in MeeGo for Netbooks 1.1 (= commercial launch in october), we should start now !  :)

Regards,
Olivier

To get an App into the Meego release I imagine is quite a big hurdle to jump over. But the engineering involved in getting Touch Orbiter onto Meego is fairly trivial so I would suggest just getting a Meego Dev interested in getting involved as the first step. Then once we have Touch Orbiter on Meego we can look at the next steps beyond.

All the best

Andrew
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: nite_man on August 18, 2010, 01:36:45 pm
I confuse a bit. We're going to port Orbiter to MeeGo or next release of LinuxMCE will be on MeeGo platform?
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: posde on August 18, 2010, 01:45:36 pm
Michael,

atm it seems some people want to have the touch orbiter running under Meego. In the long term, TSCHAK evaluates moving the whole stack to Meego. imho, the whole stack should be re-engineered to be as platform independent as possible (sans the Orbiter probably)
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: nite_man on August 18, 2010, 02:19:29 pm
Thanks, Posde, for clarification. Personally I like solution with proxy orbiter suggested by Andrew. IMHO it looks more universal then MeeGo port.
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 18, 2010, 04:30:43 pm
We shouldn't move the entire stack to MeeGo: it's not a universal OS:
Intel targets its Atom CPUs, Nokia targets Qualcomm CPUs and AMD (+ATI) is completely out of the picture.
MeeGo is an OS for specific mobile devices.

But we should try to get the Orbiter code into the MeeGo Architecture.
http://meego.com/developers/meego-architecture

The best way to achieve that is to have a LinuxMCE dev:
1) to code a "MeeGo for Netbooks" Orbiter
2) to "sell" his code to the MeeGo team
3) to adapt his code to the MeeGo "look"
4) to adapt his code for the upcoming tablets and phones.

This is a long-term commitment, that can only be achieved by a motivated LinuxMCE dev.
But the rewards will be huge: to have every MeeGo device as a ready-to-use Orbiter is the best possible promotion for the LinuxMCE project !  :)

Regards,
Olivier
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: hari on August 18, 2010, 05:41:58 pm
We shouldn't move the entire stack to MeeGo: it's not a universal OS:

are *you* going to move anything?

br Hari
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: davegravy on August 18, 2010, 08:28:14 pm
We shouldn't move the entire stack to MeeGo: it's not a universal OS:

are *you* going to move anything?

br Hari

swift11... welcome to the Linuxmce community where you can have the best idea in the world but you won't be listened to until you make significant contributions. For better or for worse, it's very much a meritocracy.
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: tschak909 on August 18, 2010, 08:49:06 pm
davegravy, thanks as always for that snarky comment...

The simple fact is, the developers are overextended.

If someone wants something done, they have to do it themselves. This isn't about being listened to.

So please, your comment was superfluous and simply of no constructive use, dispense with it next time.

-Thom
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: totallymaxed on August 18, 2010, 09:01:03 pm
Michael,

atm it seems some people want to have the touch orbiter running under Meego. In the long term, TSCHAK evaluates moving the whole stack to Meego. imho, the whole stack should be re-engineered to be as platform independent as possible (sans the Orbiter probably)

I agree with that too.

Andrew
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: tschak909 on August 18, 2010, 09:05:55 pm
My reasoning with evaluating MeeGo as a platform is two fold:

(1) it is a platform intended precisely for the appliance domain.
(2) It wioluld allow us to construct a reference platform of known hardware that will be supported now and in the future, across two current processor architectures, X86 and ARM.

I have not backed down from this assesment, and I am saddened to see that so many see my thoughts as being narrow minded or short sighted. They're not. I am trying to mitigate as many of the flaws inherent in this stack as humanly possible, and I have spent almost two years thinking on this very subject so far,

how about the rest of you?

-Thom
Title: Here's a port of Touch Orbiter to the Mini-2440
Post by: totallymaxed on August 18, 2010, 09:14:52 pm
This port of Touch Orbiter was completed in about 5 days with just a little encouragement from me by mihajzm (who is a new Dev here on the Forum). He's done a great job and has not made a great deal of fuss about doing so... he just got on did it. In my opinion we need a few more like him here;

http://forum.linuxmce.org/index.php?topic=10583.msg73082#msg73082

Taking Touch Orbiter to Meego would be a simple task to be frank... and I would like to see someone who is new to this Forum get excited about doing it - and just do it like mihajzm did.

The exciting thing about Touch Orbiter is that we can get outside developers interested in the project quickly without the steep learning curve of developing other aspects of the system - this will hopefully not only generate a whole raft of new device running Touch Orbiter but will also encourage at least a significant number of these new Devs to dig deeper and do more complex contributions later.

All the best


Andrew
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: hari on August 19, 2010, 11:38:16 am
swift11... welcome to the Linuxmce community where you can have the best idea in the world but you won't be listened to until you make significant contributions. For better or for worse, it's very much a meritocracy.

you seem to misunderstand how open source works..

br Hari
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 19, 2010, 01:12:15 pm
Harri,

I've been working for more than 10 years on this stuff and it's available on the web for free:
http://sites.google.com/site/taoteking11/Home

I hope you will consider this also as "open source"  ;)

Regards,
Olivier

PS: translations of Lao-Tsu sell as hot cakes, and my translation is the first correct one !  ;D
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: hari on August 19, 2010, 01:18:53 pm
Hey swift11,

I meant davegravy not you :-)

br Hari
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 19, 2010, 01:21:24 pm
I know, but this was the starting point:  :)

We shouldn't move the entire stack to MeeGo: it's not a universal OS:

are *you* going to move anything?

br Hari
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: hari on August 19, 2010, 01:36:37 pm
sorry but i was a bit offended by "We should" instead of "one might want to consider..."

I've seen so many people here who think that developers should do this or do that.. I just wanted to point out that this is not how opensource works. Somebody needs code.. he writes it. He decides to make it open/free for others to be able to use and extend it, too. There is no democratic process or some kind of a voting system involved. Davegravy seems to also think it should be like that.

br Hari
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: swift11 on August 19, 2010, 01:51:02 pm
No problem at all  ;)

But like I said before, my english is far from perfect.
I speak french, dutch, german and english, but to be really polite is very difficult in any foreign language.  :)

Back to the topic: I consider a forum as a perfect brainstorming place, sort of a meeting place for developers, users, etc.

Regards,
Olivier
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: davegravy on August 19, 2010, 02:47:09 pm
Davegravy seems to also think it should be like that.
br Hari

Never said how I thought it should be, but merely how I have observed things to be.
Title: Re: Meego
Post by: swift11 on September 16, 2010, 04:34:53 am
For a MeeGo Netbook Orbiter: the new Intel AppUp developer program:   ;)

Million Dollar Development Fund :

What does the fund provide?
The Intel AppUp developer program Million Dollar Development Fund provides support to developers with the objective of reducing barrier to entry for new application development and accelerating time to market.

Who is eligible for the Intel AppUp developer program “Million Dollar Development Fund”?
The development fund is available to individual and student developers as well as small, medium and large software companies who submit applications.

What is Intel AppUp developer program Accelerator 2010?
Intel AppUp developer program Accelerator 2010 is a component of the Million Dollar Development Fund. Under this program, Intel will provide funding to software developers and companies looking to speed time to market for applications that bring new user experiences to netbook consumers.

Why is Intel launching Accelerator 2010?
The netbook has become one of the most popular consumer devices in the market today, but its true potential has been limited by applications that are not optimized for its mobility and smaller screen size. Through Intel AppUp developer program Accelerator 2010, we are looking for breakthrough applications that demonstrate new user experiences designed for Intel Atom processor-based netbooks, show potential for significant growth and broad consumer appeal.

http://appdeveloper.intel.com/en-us/article/frequently-asked-questions

Forum:
http://appdeveloper.intel.com/en-us/forum
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: Murdock on October 03, 2010, 05:02:25 am
In response to Thom's post here:

 
My reasoning with evaluating MeeGo as a platform is two fold:

(1) it is a platform intended precisely for the appliance domain.
(2) It wioluld allow us to construct a reference platform of known hardware that will be supported now and in the future, across two current processor architectures, X86 and ARM.

I have not backed down from this assesment, and I am saddened to see that so many see my thoughts as being narrow minded or short sighted. They're not. I am trying to mitigate as many of the flaws inherent in this stack as humanly possible, and I have spent almost two years thinking on this very subject so far,

how about the rest of you?

-Thom

  Watching the development over the last two years I think that having clearly defined supported hardware would help aide adoption as long as the hardware is as reasonably priced (if it isn't and people are forced to move to new hardware due to an architecture change current users will get frusterated and new users will be terrified by the price point). Much of the home automation items I've found are relatively expensive (zwave switches, existing home security alarm IP integration, etc). On the flip side, I know that over the last year alot of fantastic strides have been made by the project community to help show support interoperability in the wiki by adding the supportabiliy matrix to each article, and users post their current setup on the user section.

  As a relatively new person in the arena of programming, I don't fully grasp what would be required from a programming standpoint to migrate the LMCE code base from a Kubuntu OS to the Meego mobile OS though I do understand that developer time on this project is a very precious commodity and if a significant amount of effort is entailed with end user purchasing requirements the decision must be made carefully.

  Personally I've gone back and forth about the hardware issue: unless you know of someone (either personally or via the wiki) who has tried and tested whatever you happen to be looking at, you're rolling the dice on whether the hardware will integrate successfully with MCE. Though on the flip side I enjoy the spirit of challenge that's associated with the 'open-ness' of the platform and applications. I also enjoy that with a few stipulations (stick with nvidia graphics controllers and intel/amd cpus) you should be able to get most if not all hardware working if you're willing to step up to the challenge. I've had more than one evening of utter frustration banging my head against a piece of hardware not understanding where the issue was (the UIRT comes to mind, and a pesky NIC issue I had a while back) but these items helped grow my ability to troubleshoot and understand the architecture more.

  I believe it comes down to market - what is the goal or target audience of the project at this point in time? To gather developer interest, to gather as many (layman) users as possible or to gather more technical users who don't mind pushing themselves to jump in the code? I'm thinking all of those sound good, but there's always a priority, what's top priority? Whatever it ends up being, hopefully that helps to cast some light on an answer.
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: davegravy on October 03, 2010, 06:49:15 pm
  I believe it comes down to market - what is the goal or target audience of the project at this point in time? To gather developer interest, to gather as many (layman) users as possible or to gather more technical users who don't mind pushing themselves to jump in the code? I'm thinking all of those sound good, but there's always a priority, what's top priority? Whatever it ends up being, hopefully that helps to cast some light on an answer.

I'm happy to hear you speaking in terms of priorities.

If I were an interested developer, would I know where to focus my efforts (The Roadmap Wiki link above that I'm looking at is broken, for example)? Would I develop whatever aspect of Linuxmce seemed interesting to me, personally, instead of focusing on common goal(s)?

What do you end up with when you have a bunch of developers doing their own thing? Will the end product be disjointed?
Title: Re: Meego (was: Attitude of COOPERATION.)
Post by: posde on October 03, 2010, 07:20:40 pm
davegravy,

as long as there is no specific supporting business behind a project, I as an open source developer (poohh, what a statement, /me a dev, and OSS dev never the less...), work on the stuff, I like to work on. And I got the feeling, most people in the -devel channel do the same thing.

This does not mean, the project will be disjointed, on the contrary. We test each others stuff, we talk about each others stuff. That's how we get progress.

A very good example is los93sol's work on the asterisk problems. He started using the telecom part of the system, and could not stand the issues. So he learned about asterisk, the dialplan, and so on, talked in -devel about his findings, and about the way he would fix things, and everybody took turns in shooting down his ideas. But he prevailed :D  AND fixed a lot of bugs in doing so.

To go back in time, before the 710 release, I wanted to get the Maemo orbiter more easily installable. So I went ahead, and build deb packages (after spending a week or so trying to understand things (I am a very slow learner)), and in the end, we had a maemo Orbiter, people could install by selecting it from a web site.

That's how it works. That's how it will continue to work.