Commit ea081ccc authored by Jeremy Soller's avatar Jeremy Soller
Browse files

Merge branch 'master' into political_correctness

Conflicts:
	src/overview/developers.md
parents e2d13a9c 05d69462
......@@ -5,9 +5,11 @@
By unifying the API in this way, you get an extremely consistent, clean, and flexible interface.
We can't really claim credits of this concept (except for the implementation and exact design). The idea is not a new one: The concept is very similar to _9P_ from _Plan 9_ by Bell Labs.
We can't really claim credits of this concept (except for the implementation and exact design). The idea is not a new one: The concept is very similar to _9P_ from _Plan 9_ by Bell Labs and a similiar approach has been taken in Unix and its successors.
How it differs from "everything is a file"
How it differs from "Everything is a file"
------------------------------------------
> TODO
With "Everything is a file", all sorts of devices, processes and kernel parameters can be accessed as files in a regular filesystem. This leads to absurd situations like the hard disk containing the root filesystem `/` contains a folder `dev` with device files including `sda` which in turn contains the root filesystem. This situation is just missing any logic. Furthermore, many file properties don't make sense on these 'special files': What's the size of `/dev/null` or a configuration option in sysfs?
In contrast to "Everything is a file", Redox doesn't enforce a common tree node for all kinds of resources. Instead, resources are distinguished by protocol. This way, USB devices don't end up in a "filesystem", but a protocol-based scheme like `EHCI`. Real files are accessible through a scheme called `file`, which is widely used and specified in [RFC 1630](https://tools.ietf.org/html/rfc1630) and [RFC 1738](https://tools.ietf.org/html/rfc1738).
......@@ -3,17 +3,25 @@ Developers
We are quite a few developers at Redox. 40+ people work on it. There are all sorts of cool people to work with.
Our BDFL is Jeremy Soller (Jackpot51), who maintains the kernel, drivers, standard library, Orbital (and OrbTK), and the overall direction of the project.
Our [BDFL](https://en.wikipedia.org/wiki/Benevolent_dictator_for_life) is [Jackpot51](https://github.com/jackpot51), who maintains:
- [kernel, drivers, standard library, and Orbital](https://github.com/redox-os/redox)
- [The installer](https://github.com/redox-os/installer)
- [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)
- [Orbutils](https://github.com/redox-os/orbutils)
- The overall direction of the project.
The other side projects have different maintainers:
- Ion: Skyler Berg.
- Sodium: Ticki.
- The implementation of ZFS: Formerly Tedsta, now Ticki.
- Oxide: Ticki
- Coreutils: Ticki.
- Extrautils: Ticki.
- Binutils: Ticki.
- [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.
The "core team" (people who are regularly contributing to Redox) is currently:
......
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