The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Main Page
m |
(→Introduction to Mer) |
||
| Line 3: | Line 3: | ||
We have some clear goals: | We have some clear goals: | ||
| − | * To be openly developed and governed as a meritocracy | + | * To be openly developed and governed as a meritocracy -- see [[Governance]] for details |
* That the primary customers of the platform are device vendors – not end-users. [http://lists.meego.com/pipermail/meego-dev/2011-October/484281.html info] | * That the primary customers of the platform are device vendors – not end-users. [http://lists.meego.com/pipermail/meego-dev/2011-October/484281.html info] | ||
* To have a device manufacturer oriented structure, processes and tools: make life easy for them | * To have a device manufacturer oriented structure, processes and tools: make life easy for them | ||
| Line 13: | Line 13: | ||
If you want to install and use Mer on a device then you probably need a product built on Mer. There are actually a few to choose from already: | If you want to install and use Mer on a device then you probably need a product built on Mer. There are actually a few to choose from already: | ||
* [[Nemo#Nemo_Mobile | Nemo Mobile]] | * [[Nemo#Nemo_Mobile | Nemo Mobile]] | ||
| − | * Plasma Active | + | * [http://plasma-active.org/ Plasma Active] |
| − | * Cordia | + | * [http://cordiahd.org/ Cordia] |
== Vendors == | == Vendors == | ||
Revision as of 22:49, 31 January 2012
Contents |
Introduction to Mer
Mer aims to be a FOSS, inclusive, meritocratically governed and openly developed Core optimised for HTML5/QML/JS, providing a mobile-optimised base distribution for use by device manufacturers. Mer is based upon the work from the Core section of the MeeGo project and aims to share effort and code together with the Tizen project once Tizen tools and code are publicly available.
We have some clear goals:
- To be openly developed and governed as a meritocracy -- see Governance for details
- That the primary customers of the platform are device vendors – not end-users. info
- To have a device manufacturer oriented structure, processes and tools: make life easy for them
- To provide a device oriented architecture
- To be inclusive of technologies (such as MeeGo/Tizen/Qt/EFL/HTML5)
- To innovate in the mobile OS space
End Users
If you want to install and use Mer on a device then you probably need a product built on Mer. There are actually a few to choose from already:
Vendors
If you're interested in why Mer is right for you then please approach Carsten Munk or David Greaves. We'll be putting some material up that should focus on the benefits that Mer offers.
Developers
The resources below should help. In particular we have Contribution and Contribution in detail pages.
Resources
- Mailing lists
- Building against Mer in COBS
- Contribution
- FAQ
- IRC Chat @ irc.freenode.net ~ #mer
- Community Workspace
- Test process
- Website Ideas
- Trying it out in a virtual machine
- Some [Images] are here
- News items and Blogs
- Platform SDK work in progress
- OBS projects setup work in progress
