Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • redox redox
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 227
    • Issues 227
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • redox-os
  • redoxredox
  • Issues
  • #525

Closed
Open
Created Feb 28, 2016 by Jeremy Soller@jackpot51Owner14 of 22 tasks completed14/22 tasks

Documentation, transparency, and information

Created by: ticki

  • Contribute.md
  • Complete docs of everything in the kernel.
  • Complete design document.
  • Formal proof of the design (I'm working on this)
  • #![deny(missing_doc)] in all Redox-related crates.
  • A overview of the design principles.
  • "Everything is an URL" explanation (I'm working on this)
  • "What is done, and what is not done"
  • Complete list of goals and non-goals.
  • What is the rationale behind using Rust? What advantages does it carry? What disadvantages?
  • How and where is the userspace/kernelspace seperation enforced?
  • What general-purpose "means"
  • How we differ and not differ from Linux, BSD, Minix, and Plan9.
  • A complete, collected list of sources of information
  • The architecture of the ZFS implementation.
  • What Redox is and what it isn't.
  • How can I write programs for Redox? (I'm working on this)
  • A "book", see #403 (closed) (I'm working on this).
  • How POSIX-compatible is Redox?
  • Why?
  • Man pages.
  • Documentation for utils.

TODO: Add more

Assignee
Assign to
Time tracking