The mission and goals of Mer is amongst others:

Mer is an open, mobile-optimised, core distribution aimed at device
manufacturers; powered by Qt/QML and HTML5 - openly developed,
inclusive, and meritocratically governed.

Provide a mobile device oriented architecture
Primary customers are device vendors - not end-users.

Over time, the traditional mobile device focus has been done mostly as
part of the Nemo Middleware project, with Mer focusing on base system,
with a large overlap in contributor, vendor participation, use and
contributions, even infrastructure.

The barrier between Mer and Nemo Middleware and what goes where has
often been confusing and let to big architectural challenges and
difficulty in contributing to Mer and especially Nemo MW based
projects, with differing methods, bugtrackers, requirements, etc -
despite the overlap of people, bugtrackers, even if they were on the
same infrastructure.

In that sense, it makes sense that we try to remove the artifical gap
between Mer and Nemo Middleware to ensure a productized and working,
tested mobile core distribution.

This is a RFC for Mer vendors, remaining advisory board members and
maintainers, with idea of implementation happening after 1st of May

We have already begun (a long time ago goal) to try and make Mer
contribution easier, through setting up GitLab and migrating the core
repositories from Gerrit to GitLab, hosted in Mer infrastructure,
authenticated with Mer bugtracker accounts.

In addition to that, we have set up a OBS _service based Mer build in

This uses the tar_git web service with option 'dumb' to utilize old
Mer repository formats.

Due to previous inability for Mer to accept contributions and release
sufficiently fast for Mer-based products, a method was devised to make
sure contribution could happen faster, by overlaying Mer with a
faster-moving set of packages, based on git repositories where actual
development happened. The lessons from that has been learnt and were
part of the reason for the GitLab move and _service based mentioned in
the previous three paragraphs. It led to bad situations before that
the factual bleeding edge Mer was not in Mer Gerrit, but in Mer GitHub

It is also worth noting that it is easy, and possible to only use a
subset of Mer source packages in vendor builds for specific purposes.
The original thought that Mer vendors would typically use full binary
releases of Mer has been disproven and most uses are using their own
Mer builds, done on own OBSes, and hence it makes more sense to see
Mer as a set of software components that can be combined in different
ways and built in a couple of different configurations for QA.

The intended components to be updated and replacing current versions
in Mer (currently Qt 5.0 based):

* Mobile-productized Qt5.1 packaging and modifications from Nemo's Qt fork:

(Primary maintainer, Robin Burchell/w00t)
[some may be missing]

With updated 5.2 packages in a staging project while it gets

* Updated ConnMan 1.23

(Primary maintainer, Lorn Potter/lpotter/ljp) (APN list) (new) (new needed for UI
enablement of ConnMan)

* Updated PulseAudio 4.0

(Primary maintainer, Juho Hammilinen/jusa) (new) (new)

* Updated Systemd to 208

(Primary maintainer, Pekka Lundstroem) (new)

* Updated versions of Qt5 ports of Mer middleware such as KCalcore,
Resource framework enablers, Accounts framework, Sensor framework (new)

* BlueZ 4.101,
- includes patches to successfully pass Bluetooth certifications (new) (new) (new)

(Primary maintainer: Hannu Mallat)

Wayland related updates and fixes:

* Project config enablers to make X11-less builds in Mer, which will
be default off (i.e. X11 enabled) in Mer QA builds and general package
updates/build system adjustments:

The intended additional components to be merged into Mer:

* Ruby (minimal)
-- needed for QtWebKit for Qt5 builds.

(Primary maintainer: Islam Amer)

* libsystrace  (for doing easier tracing of Mer/Qt5-based systems)

(Primary maintainer: Robin Burchell/w00t)

Location framework: GeoClue:

(Primary maintainer: Aaron MacCarthy/amccarthy)

Improvement for image creation and package updates:

(Primary maintainer: Bernd Wachter/Aard)

Replacement for unmaintained ContextKit, statefs

(Primary maintainer: Denis Zalevski/dez)

Utilizing a FUSE based file system for context information:

Audio resource policy system independent bindings and completeness of
Resource Policy implementation before partially in Mer:

(Primary maintainer: Juha Hammalinen/jusa)

Package Management daemon and bindings:

(Primary maintainer: Thomas Perl)

Synchronization framework: (not obligatory)

BTRFS related support: (like e2fsprogs)

oFono with ability to connect with Android RILD stack and bindings: (update) (new) (new)

Telepathy framework + oFono telepathy plugin:

Device state management:

Primary maintainer: Simi Piironen/spiironen

Communication logging and contacts framework:

SDL2 framework (not obligatory)

(Primary maintainer: Thomas Perl)

Application booster - a method to start up Qt (and others)
applications much faster:

(Primary Maintainer: John Brooks)

Maliit Input Framework:

(Primary Maintainer: Pekka Vuorela)

Time daemon (also for synchronization, alarms, timezone changes):

(Primary Maintainer: Petri M. Gerdt)

QML Bindings for common middleware tasks:

Non-graphical feedback (vibrations, sound, etc) framework: [for

Seamless Software Updates:
- a way to authenticate access to repositories, easier do upgrades
between updates, etc.

Primary maintainer: Bernd Wachter/Aard

Python3 + TheOtherSide bindings for Qt5:

Primary maintainer: Thomas Perl (thp)

Media indexing framework (optional):
[and likely a boatload of the dependencies below]

Qt-based script framework and backup framework:

Primary maintainer: Denis Zalevski (dez)

Wayland compositor framework/lipstick:

Primary maintainer: Robin Burchell (w00t)

Transfer management engine:

Media playback and playlist management framework:

Social media framework:

User management framework:

Framework for building telephony dialers with telepathy(-ring) and oFono:

Gecko-based browser engine with Qt5 bindings:

USB mode management framework:

Primary maintainer: Phillipe De Swert

Additional packages for discussion if they're alive or not and if
other packages above depend on them and if they are not more part of

If you claim meritocratic maintainership to any of these packages,
please let me know and we'll set up access rights for merging and
review rights accordingily after 1st of May 2014 if proposal holds.
Protesting to the architectural and location move of your component is
perfectly valid to do, as well.

I believe from an architectural and project point of view that this
move will strengthen Mer and related Nemo middleware components as a
open source mobile platform in it's own right and make contribution
and participation easier to understand, explain and do.

With best regards,
Carsten Munk
Mer project architect

Reply via email to