Skip to content
linux-phone-ocoPublic

About

The project's memory: which phone does what, how we know, why we decided, what is next.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

linux-phone-oco/docs

The memory of linux-phone-oco, whose goal is Linux phones as good as Android for everyday use, and better - one device and one piece of hardware at a time, everything upstream. Here: which phone supports which hardware, how we know, why decisions were made, and what is next. The data behind it is plain, versioned, and queryable - see AGENTS.md.

Read it as a site: https://linux-phone-oco.github.io/docs/. Style follows software-engineering-canon's RFC-like minimal theme (deliberately: structure by indentation and whitespace, not font-size jumps, bold, or color).

What is here

  • devices.md - one phone each.
  • components.md - a fixed vocabulary of hardware features (audio, display, connectivity, ...).
  • support_status.md - the matrix: which device supports which component, and how we know. unknown means nobody has checked; it is not a softer broken.
  • session_log.md - the development log for this org: what was done, why, and what was considered and rejected.
  • sources.md, backlog.md - citations, and the open plan.

Process

Built on creation-guidelines/text-as-data-template; the engineering process this org follows is ideal-project-playbook.

About

The project's memory: which phone does what, how we know, why we decided, what is next.

Topics

Resources

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages