11. jan. 2012 08.52 skrev Christopher Stark <[email protected]>: > Dear Mer-Community/Developers, > > I'm new on this list and I am extremely happy that meego will live on in > this project. > I have some basic questions concerning Mer as I plan on buying a Tegra2 > Tablet (probably that Asus Tablet without Android Market). Hi Christopher,
Remember to look around if it already has been made possible to run own kernels and root file systems on it before buying :) > > I'm interested in the following: > > -Where is the difference between mer and meego? MeeGo is quite dead, Mer is quite alive. But seriously: Mer focuses on being a good Core - that is, all the needed software to run a full Linux/Qt stack. Unlike MeeGo, we don't contain hardware adaptations or user interfaces. That is added by vendors (our primary customers). Vendors are: companies using Mer, device hackers, user interfaces projects etc. but not typically end-users. MeeGo was 1200+ packages and Mer is 320 packages, that does the job of providing a great base for products. > What develepment > perspectives are there if no single big organization/company will take part > in the development? Okay, so, to explain this, try to look around at the small to medium businesses doing Linux based device products. All of them are doing the same thing essentially, maintaining their own little linux distributions for products. Mer is a project that allows them to work together and share effort on a common base, effectively being a cost saver, without the politics that usually come along with user interfaces and hardware. We'd much rather code and improve the core than spend time discussing what side of the dialog box the "Cancel" button goes on or if LG's new handset is better than our hardware adaptations can suppport. Mer's very technically driven. I did a statistic at some point: Even with a big organization/company, each MeeGo source package was only touched on average 2-3 times during the entire life of the project. With our small 320 package core (intentionally), we have a lot less area to cover, as well, so we can do quite well with a low number of people. On top of that, most of the development actually goes on in the upstream projects we package - we put them together as a working base/core. And as a community (or cooperative?) we work together to actively test and improve it. > -How many Applications are available for Mer by now? Are these the same > applications that can be used under regular Meego systems? Mer can run Qt, Qt QML applications, currently 4.8.0(-rc1) and eventually Qt5 based applications too. OpenGL ES apps as well. HTML5 can be used through QtWebKit > -Will it be possible in the future tho install programs from the debian > repository? Is a office application (e.g. koffice) available for mer? Koffice and such are more likely to be in user experiences, see below. Mer is RPM based and hence can't take applications from Debian repositories. On a mobile device, you have to consider that it might be better to provide Qt/QML based applications, though, instead of ones that depend on ancient toolkits :) > -Is plasma active the standard graphical environment for mer? Are more > graphical environments available? There's no standard or preferred graphical environment for Mer, there's even no standard or preferred hardware adaptations. Those are delivered by projects within the community. http://wiki.merproject.org/wiki/Community_Workspace is a good list of those > > > Best regards > Christopher Stark > BR Carsten Munk Mer project founder
