|
|
| (39 intermediate revisions not shown) |
| Line 1: |
Line 1: |
| - | = Mer Project Blueprint =
| + | #REDIRECT [[Mer]] |
| - | | + | |
| - | == General Purpose ==
| + | |
| - | | + | |
| - | The Mer platform is a Linux distribution for mobile devices based on the
| + | |
| - | Maemo platform from Nokia but developed solely by community effort. The
| + | |
| - | goals of Mer include:
| + | |
| - | | + | |
| - | *Developing parts of Maemo that has the interest of the community to improve upon.
| + | |
| - | *Making it easier to port existing desktop applications by hildonizing and adjusting them to the tablet form factor.
| + | |
| - | *Encouraging third party experimentation and development.
| + | |
| - | *Supporting outdated tablet hardware no longer supported by Nokia.
| + | |
| - | *Making Maemo a generic platform for all tablet devices, including non-Nokia ones.
| + | |
| - | | + | |
| - | Mer platform development will be done in the open, with public SCM
| + | |
| - | repository, bugtrackers, and Wiki-based blueprint discussion.
| + | |
| - | | + | |
| - | We should stop seeing the tablets as strictly under-powered embedded systems, and see them for what they really are: powerful, power-efficient,
| + | |
| - | economical handheld computers.
| + | |
| - | | + | |
| - | | + | |
| - | == Collaboration infrastructure and requirements ==
| + | |
| - | | + | |
| - | *Using garage.maemo.org. We have a strong connection to maemo.org, so, and many users and potential contributors are already registered with the services.
| + | |
| - | *Advantages of garage: mailing lists per project, bug tracking, news, file releases, forums, svn, git (upcoming)
| + | |
| - | *Each team and sub-team should have a garage project. Each garage project should be able to make git.maemo.org/projectname/<whatever>.git - where they host their master/release tags/etc of the areas they are responsible for.
| + | |
| - | *Each user should be able to have their own personal git repositories, for example, git.maemo.org/~username/<whatever>.git. This will make it possible to branch existing git trees, and host them on garage, and lower the entry level for contributing to Mer. Similar possibilites can be seen on launchpad. Also has the advantage of making each team able to merge the changes from the user, even if he/she vanishes, and encourage development in the open.
| + | |
| - | *Using bugzilla.maemo.org for easy upstream notification of found bugs?
| + | |
| - | *Wiki: wiki.maemo.org
| + | |
| - | | + | |
| - | == Development method ==
| + | |
| - | | + | |
| - | Each team should work through SCRUM [[Maemo.org_Sprints]], - since the teams are spread over several timezones, daily reporting should consist of microblogging?, - maybe a way to automatize the reporting in % through scripts and established form of the microblogging items. Meeting-less cos of several timezones?
| + | |
| - | | + | |
| - | Each team should have a team master which is responsible for the area, and selects gatekeepers for the git repositories, who in turn selects commits to be merged from (if in development). Everyone should be able to join the team, and commit to items in the sprint, but not everyone has commit rights for the git repositories at first, and should push their updates from their personal repos/branches to the gatekeepers.
| + | |
| - | | + | |
| - | == Bootstrapping ==
| + | |
| - | | + | |
| - | In the beginning bootstrapping will be done by the initial interested participants.
| + | |
| - | | + | |
| - | == Teams ==
| + | |
| - | | + | |
| - | === maemo.org council role ===
| + | |
| - | | + | |
| - | Responsibilities: General directions of Mer, upstream relations (Nokia, Ubuntu), community relations, decisions on what infrastructure to provide, maemo.org
| + | |
| - | | + | |
| - | === Mer taskmasters/bridge/steering committee ===
| + | |
| - | | + | |
| - | Responsibilities: Establishes specific short and long term goals of Mer based on the general directions of Mer from council. They meet regularly and decide on the high level goals of each team and release planning
| + | |
| - | | + | |
| - | Participants: Consists of the team leaders from each team. Bootstrap participants are the initial steering committee, and select initial team leaders amongst interested parties, and they manifest in the first steering committee.
| + | |
| - | | + | |
| - | Bootstrap tasks:
| + | |
| - | | + | |
| - | * Establish Garage project and mailing lists
| + | |
| - | * Establish short and long technical term goals of Mer.
| + | |
| - | * Select initial team leaders amongst interested parties.
| + | |
| - | | + | |
| - | === Mer Architecture ===
| + | |
| - | | + | |
| - | Responsibilities:
| + | |
| - | | + | |
| - | * Kernel, initfs
| + | |
| - | * porting to new architectures/platforms/devices
| + | |
| - | * Rescue capabilities for devices
| + | |
