Milestones

From postmarketOS
Jump to: navigation, search

postmarketOS aims to be like a typical Linux distribution - with lots of possibilities to choose from. And with a default selection of components, that are most useful to casual users.
This means, that there is no concrete plan, that everyone must follow for it to succeed. Instead, everyone is encouraged to work on what they enjoy most!

In consequence, pmOS does not use a regular milestone plan with versions (at least right now). Here is a list with what individuals are working on. Feel free to add yourself here and what you are interested in (optionally with priorities and estimated finish date), but you don't have to! If you do, please keep your section of this list updated.

These are all estimations and the community is expected to understand when something does not work out as planned here. This is a free time project after all, so be grateful, that the individuals step up and share their plans at all.

ollieparanoid

Basically all points listed below are done together with other community members. In fact, when I do postmarketOS work today, it is most of the time not running/porting pmOS on a device, but doing something else from below.

Make development enjoyable for everybody:

  • fix all pmbootstrap bugs
  • test / review / integrate pull-requests
  • help whenever someone is stuck with development
  • work on features, that make development easier (e.g. #688 new kernel porting workflow, #383 split aports into its own git repository)
  • assist with implementation ideas in GitHub issues
  • improve documentation in the wiki
  • improve continuous integration (e.g. #110 more automatic shell checking, #760 run fast tests in Travis)
  • write about what we do in blog posts
  • help with infrastructure (homepage, wiki, ...)
  • work together with upstream

Get postmarketOS ready for daily usage:

  • research on how we could implement "daily driver" stuff (e.g. #161 plasma-mobile, #598 cellular modem, #592 firmware patching)
  • binary package repository

MartijnBraam

  1. Try to post as much different devices as portable to find edgecases in the build process
  2. Maintaining some of the pmos infra (wiki, binary package mirrors, website)

AndrewMcSwain

  1. Evangelization
    • project-specific (devs)
    • Means: current: word of mouth in Sao Paulo ; future: meetups, talks, panels, presentations
    • philosophy and anthropology of tool-making (gateway for layperson to the hacking community)
    • Means: writings and discussions with intellectuals, the urban youth, the homeless, and the elite of Sao Paulo society
  2. On-boarding and new dev integration
  3. Documentation

-(more details to come)-

ata2001

  • [x] 1. Implement a feature in pmbootstrap, what will allow users to create recovery flashable zips for android devices. (#109)
  1. Make postmarketOS work on the following devices:
    • [x] Sony Xperia Z1 Compact (amami)
    • [ ] Motorola Moto G 3rd gen. (osprey)
    • [ ] Motorola Defy+ (jordanplus)

Pablo Castellano

  1. Add support for new devices (actually focused on Moto G 2014). If you want, you can send me your device by mail and I will try to add pmOS support to it. After that I will return the device back to you.
  2. Make pmOS debugging easier for new developers
  3. Improve documentation & usability of pmboostrap/pmOS

craftyguy

  1. Develop osk-sdl, an sdl/directfb on-screen keyboard for use during initramfs execution
  2. Make the greatest device ever, the Nokia N900, the best device to use with postmarketOS.
    • telephony
    • audio
    • UI (plasma?)
  3. Assist with documentation & on IRC/matrix where I can.

drebrez

  • ☑ Optimizing the pmOS system image size by creating the partitions as small as possible and resize them during the first boot (#127)
  • ☑ Add possibility to export an Odin flashable file for samsung devices (pmbootstrap flasher export --odin)
  • ☐ Add support for MTD devices (generate yaffs2 image, adapt initramfs script)
  • ☐ Porting PostmarketOS to a BlackBerry
  • ☐ Use LVM over system and userdata partitions (#60)
  • ☐ Add versioning in initramfs scripts (check initramfs and initramfs-extra versions)
  • ☐ Integrate alternative flashing method using netcat (#456)
  • ☐ Add support for new devices

PureTryOut

In general, get postmarketOS to a ready for daily usage state, in my case getting packages and UI packaged for the end user to install. Right now focus is on:

  1. Packaging Phone UI: Plasma Mobile
  2. Packaging Phone UI: UBports/Yunit

bshah

  1. Getting postmarketOS working on my device locally
  2. Helping to make Plasma Mobile working on postmarketOS

McBitter

  1. Get bootloader for Coolpad Modena 2 opensourced and unlocked. Requires lots of reverse engineering work.
  2. Eventually start porting device to pmOS.
  3. Write open source replacement for SP flashtool (very low priority).

yuvadm

  1. Expand support for the Mozilla Flame
  2. Work on pmOS documentation and website
  3. Help develop the pmOS architecture

opendata

  1. Get audio and BT working to overtake the n900 in supported features
  2. Get mainline working for castor

wfranken

  • [x] Basic support for yuga
  • [ ] Getting mainline working for yuga.
  • [ ] Getting more features working on yuga.
  • Adding more device support
  • Work on wiki
  • In general: make pmos usable as a daily driver

pave1 -- Pavel Machek

  • kernel work on Nokia N900
  • would like to use N900 as daily phone
  • some interest in Nokia N9, N950, LG Optimus Chic E720
  • mild interest in OpenMoko gt01, Nokia N770, N800, N810

steamport

✔ Basic Kindle Fire HDX (2013) support

✖ Get X11/xorg working on the HDX

✖ Get wifi working on the HDX...