View Single Post
Posts: 52 | Thanked: 593 times | Joined on Dec 2016
EDIT: The work can now be followed here:


TL;DR: Let's see if we can organise the maemo porting efforts a bit more to make
it easier for others to join and test/help-out/develop.

For some time I've been wanting to get Gentoo running on my phone, with a
mainline kernel. Now that I managed to make that work, mostly thanks to the
great work done by Pali, freemangorden and others, I realised that while a fun
target, it doesn't really help maemo a whole lot.

Others on IRC seems to think the same -- it's much better if we try to unify our
efforts move maemo forward. To make maemo live on -- after the last n900 finally
breaks (likely 20 years from now ;-).

This post aims to do just that - while there has been a lot of development
happening already recently ([1], [2]), it does seem like a good idea to
organise it a bit more, and make participation easier -- as many have indicated
that they wanted to help.

The goals right now are to take useful things from fremantle (hildon-desktop,
for example) and port them to a modern distribution, while also using the
modern/new libraries. In the current form, we're aiming for devuan (and thus
also debian, mostly), with gtk-related code being ported to gtk3.

The goal is also to get everything to work on other devices as well, so that
testing can be done on other devices than the N900:
  • QEMU virtual image (perhaps we can offer a updateable devuan qcow2 image)
  • Intel laptops/desktops/devices
  • Cheap ARM Linux (allwinner a33?) tablets
  • Development boards (like Olimex LIME boards)
  • Neo900 and/or Pyra

There are a LOT of things that need to be done, and I personally also do not (by far)
oversee all that needs to be done (please reply to get things added):
  • Automated builds of ported packages
  • Automated deb repository where built packages go to
  • Porting applications from maemo-cssu and stock repositories. (We need to
    keep a list of applications that are ported, and applications that we require
    to be ported, with some priority)
  • Reverse engineering of components/packages (What ones? Link to the list or make it)
  • Documentation:
    • How to join in the development(!)
    • What components do we not want to keep or port
    • What devices are known to have some sort working state, how do you set a
      device up with the ported software
    • Common porting things/problems that one might run in to
  • Status: We need to keep the current status clear to prevent double work

Concluding, I think it is good if:

1) People who are interested to help out, post on this threads (perhaps also
share what you'd like to work on, or what you can work on)
2) We shape/form ideas on how we will document the process and make sure it's
doable for interested developers to join the efforts. Let's do this for a few
days and see who is interested, and then with the interested parties make some
important decisions, like where to host the documentation, and so on.
3) We figure out what our common first goals are

For now, I haven't done much programming work for this porting at all, but do
hope to do more work in the future, but we'll also need people who can do status
updates, organise lists, tasks and write documentation and keep it documentation
up to date, as well people trying to get it to work on their device.

Finally, I realise some documentation may already be out there -- please link it here, so I/we can attempt to organise it in a central place - makes it easier for others to start out.


Last edited by Wizzup_; 2018-02-04 at 10:53.

The Following 19 Users Say Thank You to Wizzup_ For This Useful Post: