Commit 01117c5c authored by Ticki's avatar Ticki
Browse files

Update the side-projects

parent 1dc2684e
......@@ -9,21 +9,25 @@ Our [BDFL](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life) is [Jackp
- [RedoxFS](https://github.com/redox-os/redoxfs)
- [Newlib and C ports](https://github.com/redox-os/libc)
- [Orbclient](https://github.com/redox-os/orbclient)
- [OrbTK](https://github.com/redox-os/orbtk)
- [OrbTK](https://github.com/redox-os/orbtk) (with assistance from [stratact](https://github.com/stratact))
- [Orbutils](https://github.com/redox-os/orbutils)
- The overall direction of the project.
The other side projects have different maintainers:
[Ticki](https://github.com/ticki) maintains:
- [Ion](https://github.com/redox-os/ion): [Skyler Berg](https://github.com/skylerberg).
- [Sodium](https://github.com/redox-os/sodium): [Ticki](https://github.com/Ticki).
- [The implementation of ZFS](https://github.com/redox-os/zfs): Formerly Tedsta, now Ticki.
- [Magnet](https://github.com/redox-os/): Ticki
- [Coreutils](https://github.com/redox-os/coreutils): Ticki.
- [Extrautils](https://github.com/redox-os/extrautils): Ticki.
- [Binutils](https://github.com/redox-os/binutils): Ticki.
- [libmalloc](https://github.com/redox-os/libmalloc): The advanced userspace memory allocator.
- [Coreutils](https://github.com/redox-os/coreutils): The core utilities of Redox.
- [Magnet](https://github.com/redox-os/magnet): The package manager.
- [Sodium](https://github.com/redox-os/sodium): The text editor of Redox.
- [The implementation of ZFS](https://github.com/redox-os/zfs): ZFS for Redox (originally written by [Tedsta](https://github.com/tedsta))
- [libextra](https://github.com/redox-os/libextra): Stuff libstd lacks of.
- [Binutils](https://github.com/redox-os/binutils): Utilities for manipulating binary files.
- [Extrautils](https://github.com/redox-os/extrautils): Extra utilities for Redox.
- [games-for-redox](https://github.com/redox-os/games-for-redox): Funsies.
The "core team" (people who are regularly contributing to Redox) is currently:
[Ion](https://github.com/redox-os/ion) (shell) is maintained by [Skyler Berg](https://github.com/skylerberg).
The "core team" (people who are members of the GitHub organization) is currently:
(alphabetically sorted)
......@@ -36,6 +40,7 @@ The "core team" (people who are regularly contributing to Redox) is currently:
- mgattozzi
- mmstick
- nounoursheureux
- polymetric1
- roxxik
- skylerberg
- stratact
......
......@@ -8,16 +8,30 @@ In addition to the kernel, we are developing several side projects, including:
- Ion: The Redox shell.
- Orbital: The display server of Redox.
- OrbTK: A widget toolkit.
- Oxide: Redox's package manager.
- Magnet: Redox's package manager.
- Sodium: A Vi-like editor.
- libmalloc: A memory allocator.
- libextra: Supplement for libstd, used throughout the Redox code base.
- games-for-redox: A collection of mini-games for Redox (alike BSD-games).
We also have three utility distributions, which are collections of small, useful command-line programs:
- Coreutils: A minimal set of utilities essential for a usable system.
- Extrautils: Extra utilities such as reminders, calendars, spellcheck, and so on.
- Binutils: Utilities for working with binary files.
We chose to implement these programs ourselves because we feel that there is room for innovation in many core operating system tools.
By creating our own implementations we can ensure that they work on Redox as both the kernel and the tools evolve.
Furthermore, since all of these programs are written in Rust we get all of the benefits discussed in [Why Rust].
What tools for fitting in the Redox distribution?
-------------------------------------------------
Some of these tools will in the future be moved out of the default distribution, into seperate optional magnet packages. Example of these are Orbital, OrbTK, Sodium, and so on.
The listed tools fall into three categories:
1. Tools, which are needed for a full functioning and usable system.
2. Tools, which are "nice" to have and are inherently simple.
3. Tools, which are there for establishing consistency within the ecosystem.
The first category should be obvious: an OS without certain core tools is an useless OS. The second category contains the tools which are likely to be non-default in the future, but nonetheless are in the official distribution right now, for the charm. The third category is there for convenience: namely for making sure that the Redox infrastructure is consistent and integrated (e.g., Magnet, OrbTK, and libextra).
It is important to note we seek to avoid non-Rust tools, for safety and consistency (see [Why Rust]).
[Why Rust]: introduction/why_rust.html
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment