Mer: A year after
0 likes632 views
Mer began as an effort to reconstruct the Maemo platform to be more open, hackable, and aligned with standard Linux distributions. The project transformed the Maemo platform code to separate it from device code, making the platform more open for development while keeping device differentiation closed. Over time, Mer has been ported to various hardware and its desktop environments have evolved from basic X11 to more polished graphical experiences. The project aims to establish Mer as the leading open platform for tablet devices.
Mer: A year after
- 1. Mer:ayearafter By Carsten Valdemar Munk (Stskeeps), Mer lead developer 1
- 5. Whatdidwefindout? There's a reason why Maemo is like it is: Power saving Memory saving Performance 5
- 6. October2008:AcalltoreconstructMaemo Tablets are not under-powered embedded systems, they are powerful, power-efficient, economical handheld computers. Make Maemo a general platform for tablet devices. Make it more developer-friendly. More hackable. Align with standard Linux distributions. 6
- 7. October2008:AcalltoreconstructMaemo Separate device and platform code Open development of the Maemo platform - the device-specific and vendor-specific differentiation development can be closed. It should be easy to port existing desktop applications - platform peculiarities should be kept to the absolute minimum required for the mobile use-case. 7
- 8. Buildingourprojectinourbasement.. Creating Maemo 'from scratch' initially building all of Maemo by hand. On top of mojo.handhelds.org Ubuntu port Getting hildon-desktop running and going from there Hacked up autobuilder. Adding support for Mer to Scratchbox. Trauma that will never heal. 8
- 10. Andthennewsbroke.. December 2008: Maemo 5.0 (Fremantle) pre-alpha This early release comes with an invitation to build variants based on Maemo 5 compatible with existing hardware like the N800 and N810. Maemo SW can't promise commercial quality for such configurations but through maemo.org we are able to collaborate at a community level with technical support, license changes and code. 10
- 11. 意姻温稼壊韓看姻馨庄稼乙油庄稼岳看油珂艶姻.. Namechange from M-R to Mer Moving into #mer allowing us to create a community of our own Establishing wiki.maemo.org/Mer Why maemo.org? 11
- 13. 珂艶艶岳庄稼乙油温油岳温鉛艶稼岳艶糸油姻顎壊壊庄温稼 13
- 14. Where has Mer been ported to? 14
- 15. Dealingwithhardwarevendors A social contract for the vendors wanting to adapt Mer on their hardware. Principles for the interaction between the Mer project and hardware vendors. Modelled on the open attitude by Nokia with regards to the Internet Tablets. wiki.maemo.org/Mer/Documentation/Vendor_Social_Contract 15
- 16. VSC No tivoization Open source kernel modules Vendors are encouraged to work with maemo.org to provide repositories containing closed firmware and bits, intended only for specific device types 16
- 17. Thesecondyear:Threedesktops Plain(X11) Polished(SWGL) Shiny(GLES) 17
- 18. Plain 18
- 19. Polished 19
- 20. Shiny? 20
- 21. Somethingsfromtheroadmap Week 42-43; Integrate Fremantle sources. Hildon Input Method Thumb kbd first version of Polished. Improving the status area (backlight, battery, NetworkManager, volume, bluetooth). Cross-compiler in OBS. Initial versions of Plain. Week 44: Full localization en_US, multi-layout HIM Week 45: 0.17 release. N8x0 Vendor Repository. Sound, GPS, etc. Week 49: 0.18 release (1.0?) 21
- 22. Merin2010 Maemo Platform as the no. 1 platform for open* devices Mer 1.0 & 'Shiny' (GL enabled) on N900, N8x0(W) with proper hardware support Mer 2.0: Harmattan based Platform wars are won in the reference implementations. Mer being a standalone OS that is usable from the moment you have it ported. (* open as in conforming to our Vendor Social Contract) 22
- 23. TohearmoreaboutMerandourmethods Friday 15:30 N800 room: Mer: How the community innovates Saturday 16:15 770 room: Git hands-on workshop Sunday 11:00 -N800 room: Building for Mer Sunday 14:30 Lightning talks: Mer from a user's perspective http://wiki.maemo.org/Mer #mer on irc.freenode.net 23