Todo lists are used by the developers when a software development is needed. This is common when there is a software development plan, such as the inclusion of new code or port code to the HyperbolaBSD kernel or userspace, new features, etc. The progress can be tracked here, and completed todo lists can be browsed as well.

• Add further packages within context of missing protocols (Gopher, Gemini), additions for free and libre gaming and applications for digital book-publication → DONE (Responsible: throgh)

• Fix and update packages reported being malfunctional or missing features → IN PROGRESS (Responsible: rachad, throgh)
• Add further packages within context of backup-software and supporting libraries, additions for free and libre video- and audio-production → DONE (Responsible: throgh)
• Testing and fixing runit-integration → DONE (Responsible: throgh)

• Rebranding BSD kernel → DONE (Responsible: Emulatorman)
• Rebranding BSD userspace → DONE (Responsible: Emulatorman)
• Rebranding Xenocara → DONE (Responsible: Emulatorman)
• Build and test the rebranded system → IN PROGRESS (Responsible: coadde)
• Check all files with licenses issues ¹⁾ and GPL incompatibility → IN PROGRESS (Responsible: Emulatorman)
• See if some of those unlicensed files are copyrightable → IN PROGRESS (Responsible: Emulatorman)
• Remove nonfree firmware blobs → DONE (Responsible: Emulatorman)
• Write compatible code to replace the nonfree files

• Modularise BSD kernel → DONE (Responsible: coadde)
• Modularise BSD userspace
• Port and test hyperman ²⁾ → IN PROGRESS (Responsible: Gaming4JC)
• Port and test hypertools ³⁾
• Port and test HyperDB ⁴⁾
• Port and test HyperBLibC ⁵⁾
• Port and test HyperRC ⁶⁾
• Package the entire modularised BSD system and some core packages with hyperman ⁷⁾

• Index incompatible packages
• Upgrade and maintain packages
• EOL of GNU/Linux-libre support ⁸⁾
• Restructuring of entire Hyperbola Project with HyperbolaBSD

• Review of codebase and additions from OpenBSD
• Review of codebase and additions from DragonFlyBSD (Hammer, Hammer2, cryptsetup, dm-crypt)
• Review of codebase and additions from NetBSD (GNU/Linux compat layer, architectures, and Nouveau driver, LVM and Xen)
• Review of codebase and additions from HardenedBSD (Address Space Layout Randomization on userspace, libarchive has support for lz, port Pax and grsecurity patchset)
• Maintain, add and upgrade packages to new base under HyperBK
• Removal of Hyperbola GNU/Linux-libre from Hyperbola Project

• Contact original authors and request removal of the advertising clause in Original BSD license (BSD-4)
• Replace code under Original BSD license with new one under GPLv3 in HyperBK
• Replace code under Original BSD license with new one under LGPLv3 in HyperBLibC
• Port ReactOS btrfs kernel driver, instead of Linux kernel, given this one is GPLv2-only (not GPLv3-compatible)
• Maintain, add and upgrade packages to new base under HyperBK and HyperBLibC

• Implement new features and technologies in kernel under GPLv3.
• Write new firmware code and implement new drivers.
• Replace blobs with new code under GPLv3.
• Implement new features and maintain the base system.
• Maintain, add and upgrade packages