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)

• 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)

• Fix and update packages reported being malfunctional or missing features → IN PROGRESS (Responsible: throgh)
• Fix generic reports for major applications like UXP-based for example → IN PROGRESS (Responsible: throgh)
• Optimize desktop-experience for Hyperbola → IN PROGRESS (Responsible: throgh)
• Migrate build server to new VPS instance → DONE (Responsible: coadde)
• Create CI infrastructure with Laminar to build, sign and release packages to repos → DONE (Responsible: coadde)
• Create VPN and SSH infrastructure in build server with hardened security → DONE (Responsible: coadde)
• Create job scripts in Laminar to build and release packages to repos → DONE (Responsible: coadde)
• Test new build server → DONE (Responsible: throgh)

• Removal of defined packages from [extra]-repository for transition towards HyperbolaBSD → IN PROGRESS (Responsible: throgh, Emulatorman)

• Rebrand BSD kernel → DONE (Responsible: Emulatorman)
• Rebrand BSD userspace → DONE (Responsible: Emulatorman)
• Rebranding Xenocara → DONE (Responsible: Emulatorman)
• Port BSD kernel to our custom GCC/LLVM versions → DONE (Responsible: coadde)
• Build and test the ported BSD kernel → DONE (Responsible: coadde)
• Port BSD userspace to our custom GCC/LLVM versions → IN PROGRESS (Responsible: coadde)
• Build and test the ported BSD userspace
• Test pre-alpha HyperbolaBSD version running in a virtual machine (without Xenocara)
• Port Xenocara to our custom GCC/LLVM versions
• Build and test the ported Xenocara
• Test pre-alpha HyperbolaBSD version running in a virtual machine (with Xenocara)
• Check all files with licenses issues ¹⁾ (x86 architectures) → DONE (Responsible: Emulatorman)
• See if some of those unlicensed files are copyrightable (x86 architectures) → DONE (Responsible: Emulatorman)
• Check all files with licenses issues ²⁾ (non-x86 architectures) → DONE (Responsible: bUst4gr0)
• See if some of those unlicensed files are copyrightable (non-x86 architectures) → DONE (Responsible: bUst4gr0)
• Remove nonfree firmware blobs → DONE (Responsible: Emulatorman)
• Remove all non-x86 specific source code in kernel
• Write compatible code under Simplified BSD License ³⁾ to replace the nonfree files in kernel
• Replace nonfree tools/applications with fully free third-party ones in userspace

• Modularise BSD kernel → DONE (Responsible: coadde)
• Modularise BSD userspace
• Port and test hyperman ⁴⁾
• Build libretools and add patches to make it working in HyperbolaBSD → IN PROGRESS (Responsible: coadde)
• Build runit and add patches to make it working in HyperbolaBSD
• 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