diff --git a/README.md b/README.md
index bc2e3f2c6..2e900e85e 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ This repository generates the user and dev documentations of https://github.com/
## User documentation
It is available on:
-https://uutils.github.io/coreutils/docs/
+https://uutils.org/coreutils/docs/
Can be generated with:
```bash
@@ -17,23 +17,24 @@ mdbook build
## Playground
An in-browser playground runs the uutils coreutils WASM build directly in your browser:
-https://uutils.github.io/playground/
+https://uutils.org/playground/
-See also how it works: https://uutils.github.io/playground-how-it-works/
+See also how it works: https://uutils.org/playground-how-it-works/
## Developer documentation:
It is available on:
-https://uutils.github.io/dev/coreutils/
+https://uutils.org/dev/coreutils/
Can be generated with:
```bash
cargo doc --no-deps --all-features --workspace
```
-The pages are committed daily into the gh-pages branch.
+The website CI builds this on each `main`/scheduled run and publishes it
+under `/dev/coreutils/` (and `/dev/findutils/`) as part of the deploy.
## Build timing
Generated by cargo, the build timings can be seen on:
-https://uutils.github.io/cargo-timings/cargo-timing.html
+https://uutils.org/cargo-timings/cargo-timing.html
diff --git a/config.toml b/config.toml
index 156734cf3..3ed6d8901 100644
--- a/config.toml
+++ b/config.toml
@@ -1,5 +1,5 @@
# The URL the site will be built for
-base_url = "https://uutils.github.io"
+base_url = "https://uutils.org"
title = "uutils"
diff --git a/content/_index.md b/content/_index.md
index e7d9145cf..a349b9b11 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -3,12 +3,25 @@ title = "Home"
template = "index.html"
+++
-
-
-
-
-
-
uutils
+
+
+ uutils --about
+
+
+
+
+
+
+
+
user@machine:~$ uutils --about
+
uutils_
+
Cross-platform Rust reimplementations of the command-line tools you use every day, with full GNU compatibility.
The uutils project reimplements ubiquitous command line utilities in
@@ -29,83 +42,36 @@ C has served us well for decades, but it is time to move on. For new generations
This is not about fighting the GNU project. It is not primarily about security (GNU coreutils only had 17 CVEs since 2003) or about license debates. It is about **modernizing foundational software** so it can be maintained and improved by the next generation of contributors.
-Ubuntu is already [carefully but purposefully adopting](https://discourse.ubuntu.com/t/carefully-but-purposefully-oxidising-ubuntu/56995) uutils coreutils, and Debian is following the same path.
+Ubuntu is already [carefully but purposefully adopting](https://discourse.ubuntu.com/t/carefully-but-purposefully-oxidising-ubuntu/56995) uutils coreutils, Debian is following the same path, and Microsoft offers it as well.
# Projects
-
# Crates
@@ -119,10 +85,19 @@ which are published on [crates.io](https://crates.io/).
- [`platform-info`](https://github.com/uutils/platform-info)
- [`uutils-term-grid`](https://github.com/uutils/uutils-term-grid)
+# Who we are
+
+uutils is a community-driven, open-source effort maintained by volunteers around the world. There is no company behind it, just contributors who care about the future of foundational command-line tools.
+
+Everything happens in the open on [GitHub](https://github.com/uutils), and newcomers are genuinely welcome. Many of our contributors landed their first-ever open-source patch on a uutils project, and we are happy to help you do the same.
+
+[Meet the team](/team) behind uutils.
+
# Contributing
You can help us out by:
+- [Tackling a good first issue](https://github.com/search?q=org%3Auutils+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22&type=issues&s=created&o=desc) across any of our projects (the easiest way to get started)
- Contributing code
- Contributing documentation
- Reporting bugs (e.g. incompatibilities with GNU utilities)
diff --git a/content/awk.md b/content/awk.md
new file mode 100644
index 000000000..5f7c0be06
--- /dev/null
+++ b/content/awk.md
@@ -0,0 +1,25 @@
++++
+
+title = "awk"
+template = "project.html"
+
+[extra]
+wip = true
+
++++
+
+Rust implementation of `awk`, the pattern scanning and text-processing language.
+
+This project aims to be a drop-in replacement of the original command.
+
+# Goals
+
+This project aims to be a drop-in replacement for GNU awk (gawk). Differences with the original are treated as bugs.
+
+# Contributing
+
+To contribute to uutils awk, please see [CONTRIBUTING](https://github.com/uutils/awk/blob/main/CONTRIBUTING.md).
+
+# License
+
+uutils awk is licensed under the MIT License - see the [LICENSE](https://github.com/uutils/awk/blob/main/LICENSE) file for details.
diff --git a/content/coreutils.md b/content/coreutils.md
index e77608a62..72480cb0c 100644
--- a/content/coreutils.md
+++ b/content/coreutils.md
@@ -3,6 +3,9 @@
title = "coreutils"
template = "project.html"
+[extra]
+status = "ready"
+
+++
uutils coreutils is a cross-platform reimplementation of the GNU coreutils in Rust. While all programs have been implemented, some options might be missing or different behavior might be experienced.
diff --git a/content/diffutils.md b/content/diffutils.md
index 90a0b88de..58d1434bc 100644
--- a/content/diffutils.md
+++ b/content/diffutils.md
@@ -3,6 +3,9 @@
title = "diffutils"
template = "project.html"
+[extra]
+status = "beta"
+
+++
Rust implementation of GNU diffutils: `diff`, `cmp`, `diff3` and `sdiff`.
diff --git a/content/findutils.md b/content/findutils.md
index d801f9f5c..0760aff58 100644
--- a/content/findutils.md
+++ b/content/findutils.md
@@ -3,6 +3,9 @@
title = "findutils"
template = "project.html"
+[extra]
+status = "beta"
+
+++
Rust implementation of GNU findutils: `xargs`, `find`, `locate` and `updatedb`.
diff --git a/content/grep.md b/content/grep.md
new file mode 100644
index 000000000..603d4e226
--- /dev/null
+++ b/content/grep.md
@@ -0,0 +1,27 @@
++++
+
+title = "grep"
+template = "project.html"
+
+[extra]
+status = "beta"
+
++++
+
+Rust implementation of GNU grep: `grep`, `egrep` and `fgrep`.
+
+This project aims to be a drop-in replacement of the original commands.
+
+# Goals
+
+This project aims to be a drop-in replacement for GNU grep. Differences with GNU are treated as bugs.
+
+# Contributing
+
+To contribute to uutils grep, please see [CONTRIBUTING](https://github.com/uutils/grep/blob/main/CONTRIBUTING.md).
+
+# License
+
+uutils grep is licensed under the MIT License - see the [LICENSE](https://github.com/uutils/grep/blob/main/LICENSE) file for details.
+
+GNU grep is licensed under the GPL 3.0 or later.
diff --git a/content/gsoc.md b/content/gsoc.md
index f7820cc72..b6f26ff62 100644
--- a/content/gsoc.md
+++ b/content/gsoc.md
@@ -2,12 +2,18 @@
title = "Uutils at GSOC"
+++
-Google summer of code is:
-
-> Google Summer of Code is a global, online program focused on bringing
-> new contributors into open source software development. GSoC
-> Contributors work with an open source organization on a 12+ week
-> programming project under the guidance of mentors.
+
+
+ uutils gsoc --help
+
+
+
+
+
+
$ uutils gsoc --help
+
Google Summer of Code is a global, online program focused on bringing new contributors into open source software development. GSoC contributors work with an open source organization on a 12+ week programming project under the guidance of mentors.
+
+
If you want to know more about how it works, check out the links below.
@@ -18,7 +24,7 @@ If you want to know more about how it works, check out the links below.
# What is it about?
-The [uutils project](https://github.com/uutils/) is aiming at rewriting key Linux utilities in Rust, targeting [coreutils](https://github.com/uutils/coreutils), [findutils](https://github.com/uutils/findutils), [diffutils](https://github.com/uutils/diffutils), [procps](https://github.com/uutils/procps), [util-linux](https://github.com/uutils/util-linux), and [bsdutils](https://github.com/uutils/bsdutils). Their goal is to create fully compatible, high-performance drop-in replacements, ensuring reliability through upstream test suites. Significant progress has been made with coreutils, diffutils, and findutils, while the other utilities are in the early stages of development.
+The [uutils project](https://github.com/uutils/) is aiming at rewriting key Linux utilities in Rust, targeting [coreutils](https://github.com/uutils/coreutils), [findutils](https://github.com/uutils/findutils), [diffutils](https://github.com/uutils/diffutils), [sed](https://github.com/uutils/sed), [grep](https://github.com/uutils/grep), [awk](https://github.com/uutils/awk), [procps](https://github.com/uutils/procps), [util-linux](https://github.com/uutils/util-linux), and [bsdutils](https://github.com/uutils/bsdutils). Their goal is to create fully compatible, high-performance drop-in replacements, ensuring reliability through upstream test suites. coreutils is already production-ready and shipping in distributions; findutils, diffutils and grep are well advanced; while sed, awk and the system utilities (procps, util-linux, bsdutils) are at earlier stages of development.
# How to get started
@@ -32,7 +38,7 @@ with uutils.
1. **Reach out to us!** We are happy to discuss potential projects and help you find a meaningful project for uutils. Tell us what interests you about the project and what experience you have and we can find a suitable project together. You can talk to the uutils maintainers on the [Discord server](https://discord.gg/wQVJbvJ). In particular, you can contact:
* Sylvestre Ledru (@sylvestre on GitHub and Discord)
-2. **Get comfortable with uutils.** To find a good project you need to understand the codebase. We recommend that you take a look at the code, the issue tracker and maybe try to tackle some [good-first-issues](https://github.com/uutils/coreutils/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). Also take a look at our [contributor guidelines](https://github.com/uutils/coreutils/blob/main/CONTRIBUTING.md).
+2. **Get comfortable with uutils.** To find a good project you need to understand the codebase. We recommend that you take a look at the code, the issue tracker and maybe try to tackle some [good-first-issues](https://github.com/search?q=org%3Auutils+is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22&type=issues&s=created&o=desc) across any of our projects. Also take a look at our [contributor guidelines](https://github.com/uutils/coreutils/blob/main/CONTRIBUTING.md).
3. **Find a project and a mentor.** We have a [list of potential projects](https://github.com/uutils/coreutils/wiki/GSOC-Project-Ideas) you can adapt or use as inspiration. Make sure discuss your ideas with the maintainers! Some project ideas below have suggested mentors you could contact.
4. **Write the application.** You can do this with your mentor. The application has to go through Google, so make sure to follow all the advice in Google's [Contributor Guide](https://google.github.io/gsocguides/student/writing-a-proposal). Please make sure you include your prior contributions to uutils in your application.
@@ -44,448 +50,273 @@ with uutils.
# Project Ideas
-This page contains project ideas for the Google Summer of Code for
-uutils. Feel free to suggest project ideas of your own.
-
-[Guidelines for the project list](https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list)
-
-Summarizing that page, each project should include:
-- Title
-- Description
-- Expected outputs
-- Skills required/preferred
-- Possible mentors
-- Size (either ~175 or ~350 hours)
-- Difficulty (easy, medium or hard)
-
-## Performance optimization for coreutils
-
-While [uutils/coreutils](https://github.com/uutils/coreutils) has achieved strong GNU compatibility, some utilities can still benefit from performance improvements to match or exceed GNU coreutils speed. This project focuses on identifying performance bottlenecks and implementing optimizations across key utilities.
-
-The goal is to systematically profile, benchmark, and optimize coreutils to ensure they are production-ready for performance-critical environments.
-
-Key areas of work include:
-* Profiling utilities to identify performance bottlenecks (using perf, flamegraph, criterion)
-* Creating comprehensive benchmark suite comparing against GNU coreutils
-* Optimizing hot paths in frequently-used utilities (cat, cut, sort, uniq, wc, etc.)
-* Implementing algorithmic improvements and efficient data structures
-* Reducing allocations and improving memory usage patterns
-* Leveraging SIMD instructions where applicable for data processing
-* Optimizing I/O operations with proper buffering strategies
-* Benchmarking across different file sizes and input patterns
-* Setting up continuous performance monitoring in CI
-* Documenting performance characteristics and optimization techniques
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Performance profiling and optimization techniques
- - Understanding of systems programming and I/O optimization
- - Benchmarking methodologies
- - Knowledge of SIMD and parallel processing is a plus
- - Familiarity with coreutils behavior
-
-## Expand differential fuzzing for coreutils
-
-The [uutils/coreutils](https://github.com/uutils/coreutils) project has [some fuzzing infrastructure](https://github.com/uutils/coreutils/tree/main/fuzz/fuzz_targets) in place, but many utilities still lack comprehensive fuzz testing. This project focuses on expanding differential fuzzing coverage across coreutils to identify edge cases, improve robustness, and ensure compatibility with GNU coreutils.
-
-Differential fuzzing compares the behavior of uutils implementations against GNU coreutils to automatically detect discrepancies and bugs that might be missed by traditional testing.
-
-Key areas of work include:
-* Creating new fuzz targets for utilities that currently lack them
-* Implementing differential fuzzing harnesses that compare uutils vs GNU outputs
-* Expanding existing fuzz targets to cover more code paths and options
-* Setting up structured fuzzing campaigns with AFL++ and libFuzzer
-* Integrating continuous fuzzing into CI/CD workflows
-* Triaging and fixing bugs discovered through fuzzing
-* Creating a corpus of interesting test inputs for regression testing
-* Documenting fuzzing infrastructure and best practices
-* Performance profiling of fuzz targets to maximize coverage
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Experience with fuzzing tools (AFL++, libFuzzer, cargo-fuzz)
- - Understanding of differential testing methodologies
- - Debugging and bug triage skills
- - Familiarity with coreutils behavior
-
-## Complete `findutils` GNU compatibility
-
-The [uutils/findutils](https://github.com/uutils/findutils) project has made significant progress with [more than half](https://github.com/uutils/findutils-tracking/) of the GNU findutils and BFS tests passing. This project focuses on completing the remaining work to achieve full GNU compatibility and production readiness.
-
-The goal is to finish implementing missing features, fix failing test cases, and ensure the utilities (`find`, `xargs`, `locate`, etc.) are fully compatible with their GNU counterparts.
-
-Key areas of work include:
-* Implementing missing command-line options and predicates for `find`
-* Fixing edge cases in file system traversal and symlink handling
-* Completing `xargs` implementation with proper argument handling
-* Improving performance and memory efficiency
-* Setting up fuzzing infrastructure for differential testing
-* Implementing fuzz targets similar to the [coreutils fuzzing approach](https://github.com/uutils/coreutils/tree/main/fuzz/fuzz_targets)
-* Running and passing remaining GNU test suite cases
-* Conducting differential fuzzing against GNU findutils and BFS
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: Sylvestre
-- **Required skills**:
- - Rust
- - Understanding of file system operations
- - Familiarity with `find` and `xargs` usage
- - Experience with fuzzing tools is a plus
-
-## Complete `diffutils` GNU compatibility
-
-The [uutils/diffutils](https://github.com/uutils/diffutils) project provides Rust implementations of `diff`, `diff3`, `cmp`, and `sdiff`. Significant progress has been made, but additional work is needed to achieve full GNU compatibility and handle all edge cases.
-
-This project focuses on completing the remaining features, fixing compatibility issues, and ensuring all utilities pass the GNU test suite.
-
-Key areas of work include:
-* Implementing missing options and output formats for `diff`
-* Improving algorithm efficiency for large file comparisons
-* Completing `diff3` three-way merge functionality
-* Fixing edge cases in binary file detection and handling
-* Supporting all unified and context diff formats
-* Running and passing the GNU diffutils test suite
-* Performance benchmarking and optimization
-* Adding fuzzing infrastructure for differential testing against GNU diffutils
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Understanding of diff algorithms (Myers, Patience, etc.)
- - Familiarity with `diff` and patch workflows
- - Text processing and parsing
-
-## Complete the Rust implementation of `sed`
-
-The `sed` (stream editor) utility is a fundamental Unix tool for parsing and transforming text. A Rust implementation has been started but requires significant work to achieve full compatibility with GNU `sed` and POSIX standards.
-
-This project focuses on completing the existing Rust `sed` implementation to make it production-ready. The work involves implementing missing commands and flags, fixing edge cases, improving regular expression support, and ensuring the implementation passes the GNU test suite.
-
-Key areas of work include:
-* Implementing missing `sed` commands and addressing flags
-* Handling complex regular expressions and backreferences
-* Supporting multi-line pattern space operations
-* Implementing hold space operations correctly
-* Adding support for GNU `sed` extensions
-* Fixing edge cases and improving error handling
-* Running and passing the GNU `sed` test suite
-* Performance optimization and benchmarking against GNU `sed`
-* Setting up fuzzing infrastructure for differential testing
-* Implementing fuzz targets similar to the [coreutils fuzzing approach](https://github.com/uutils/coreutils/tree/main/fuzz/fuzz_targets)
-* Conducting differential fuzzing against GNU `sed` to identify edge cases and bugs
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Understanding of regular expressions
- - Familiarity with `sed` usage and scripting
- - Text processing and parsing concepts
- - Experience with fuzzing tools (AFL++, cargo-fuzz) is a plus
-
-## Rust implementation of `grep`
-
-The goal of this project is to create a high-performance, feature-complete Rust implementation of `grep` (GNU grep) as part of the uutils ecosystem. While tools like `ripgrep` exist, this project aims to provide a drop-in replacement for GNU `grep` with full compatibility, including all command-line options, output formats, and edge case behaviors.
-
-The `grep` utility is one of the most widely-used Unix tools for searching text using patterns. A uutils implementation would need to balance GNU compatibility with the performance advantages that Rust can provide.
-
-Key aspects of the project include:
-* Implementing full POSIX and GNU `grep` command-line interface
-* Supporting basic regular expressions (BRE), extended regular expressions (ERE), and Perl-compatible regular expressions (PCRE)
-* Implementing all output modes (normal, inverted match, count, files-with-matches, etc.)
-* Supporting context lines (-A, -B, -C options) and various formatting options
-* Handling binary files, compressed files, and recursive directory search
-* Optimizing performance for common use cases while maintaining correctness
-* Implementing color output and various line-buffering modes
-* Running and passing the GNU `grep` test suite
-* Setting up fuzzing infrastructure and differential testing against GNU `grep`
-* Performance benchmarking against GNU `grep` and other implementations
-
-- **Difficulty**: Hard
-- **Size**: ~350 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Deep understanding of regular expression engines
- - Familiarity with `grep` usage and advanced features
- - Performance optimization and profiling
- - Text processing and I/O optimization techniques
-
-## Rust implementation of `awk`
-
-The goal of this project is to create a Rust-based implementation of `awk`, one of the most powerful and widely-used text processing utilities in Unix/Linux systems. The `awk` utility provides a complete programming language for pattern scanning and processing, making it essential for data extraction, report generation, and text transformation tasks.
-
-This implementation would be a standalone project within the uutils ecosystem, similar to how `findutils` and `diffutils` are organized. The primary objectives are to achieve compatibility with POSIX `awk` specification and GNU `awk` (gawk) extensions, while leveraging Rust's performance and safety guarantees.
-
-Key aspects of the project include:
-* Implementing the `awk` lexer and parser for the AWK programming language
-* Building the pattern-action execution engine
-* Supporting built-in variables (`NR`, `NF`, `FS`, `RS`, etc.) and functions
-* Implementing regular expression matching and field splitting
-* Adding support for arrays, user-defined functions, and control flow
-* Ensuring compatibility with the POSIX `awk` standard
-* Gradually implementing GNU `awk` extensions where feasible
-* Setting up GNU test suite execution for validation
-
-- **Difficulty**: Hard
-- **Size**: ~350 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Understanding of lexers, parsers, and interpreters
- - Familiarity with `awk` usage and programming
- - Knowledge of regular expressions
- - Experience with programming language implementation is a plus
-
-## Complete `procps` implementation and GNU compatibility
-
-The [uutils/procps](https://github.com/uutils/procps) project aims to reimplement process and system monitoring utilities in Rust. While initial implementations have been started for various tools, this project focuses on completing the core utilities and achieving production readiness with full GNU compatibility.
-
-This project focuses on completing the most essential procps utilities (`ps`, `top`, `pgrep`, `pkill`, `free`, `uptime`) and ensuring they are ready for real-world usage.
-
-Key areas of work include:
-* Completing core functionality for essential procps utilities
-* Implementing missing command-line options and output formats
-* Fixing edge cases in /proc filesystem parsing across different kernel versions
-* Ensuring accurate process information gathering and display
-* Implementing performance optimizations for tools like `top` and `ps`
-* Setting up and running GNU procps test suite
-* Adding comprehensive error handling and validation
-* Creating fuzzing infrastructure for robust /proc parsing
-* Performance benchmarking against GNU procps
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Understanding of Linux /proc filesystem
- - Familiarity with process management and system monitoring
- - Knowledge of procps tools usage
-
-## Complete `util-linux` implementation and GNU compatibility
-
-The [uutils/util-linux](https://github.com/uutils/util-linux) project aims to reimplement essential system utilities in Rust. This project focuses on completing the most commonly-used util-linux utilities and achieving production-ready status with full GNU compatibility.
-
-This project prioritizes completing utilities that are frequently used in scripts and system administration (`dmesg`, `lscpu`, `mount`, `umount`, `kill`, `logger`).
-
-Key areas of work include:
-* Completing implementation of high-priority util-linux utilities
-* Implementing missing options and edge case handling
-* Ensuring proper interaction with kernel interfaces and system calls
-* Supporting various Linux distributions and kernel versions
-* Setting up and running GNU util-linux test suite
-* Adding comprehensive error handling for system operations
-* Performance optimization and resource efficiency
-* Creating fuzzing infrastructure for system call interactions
-* Documentation and man page compatibility
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Understanding of Linux system calls and kernel interfaces
- - Familiarity with util-linux utilities
- - System administration knowledge
-
-## Complete `bsdutils` implementation
-
-The [uutils/bsdutils](https://github.com/uutils/bsdutils) project focuses on reimplementing BSD-origin utilities commonly found on Linux systems. This project aims to complete the core utilities and achieve compatibility with both BSD and GNU/Linux variants.
-
-This project focuses on completing essential bsdutils tools like `logger`, `script`, `column`, `hexdump`, and `look`, ensuring they work correctly across different Unix-like systems.
-
-Key areas of work include:
-* Completing implementation of core bsdutils utilities
-* Ensuring compatibility with both BSD and GNU/Linux behavior
-* Implementing missing command-line options and output formats
-* Handling cross-platform differences and portability
-* Setting up test suites for both BSD and GNU variants
-* Adding comprehensive error handling
-* Performance optimization and memory efficiency
-* Creating fuzzing infrastructure for robust input handling
-* Documentation and compatibility notes
-
-- **Difficulty**: Medium
-- **Size**: ~175 hours
-- **Mentors**: TBD
-- **Required skills**:
- - Rust
- - Familiarity with both BSD and Linux environments
- - Understanding of bsdutils tools
- - Cross-platform development experience
-
-## Localization
-Support for localization for formatting, quoting & sorting in various utilities, like `date`, `ls` and `sort`. For this project, we need to figure out how to deal with locale data. The first option is to use the all-Rust `icu4x` library, which has a different format than what distributions usually provide. In this case a solution _could_ be to write a custom `localedef`-like command. The second option is to use a wrapper around the C `icu` library, which comes with the downside of being a C dependency.
-
-This is described in detail in [issue #3997](https://github.com/uutils/coreutils/issues/3997).
-
-And was also discussed in [#1919](https://github.com/uutils/coreutils/issues/1919#issuecomment-846471073), [#3584](https://github.com/uutils/coreutils/issues/3584).
-
-- Difficulty: Hard
-- Size: TBD
-- Mentors: TBD
-- Required skills:
- - Rust
-
-## `procps`: Development of Process Management and Information Tools in Rust
-
-This project focuses on creating Rust-based implementations of process management and information tools: `ps`, `pgrep`, `pidwait`, `pkill`, `skill`, and `snice`. The goal is to ensure full compatibility with all options and successful passing of GNU tests, maintaining the functionality and reliability of these essential tools.
-
-- **Description:** Develop Rust-based versions of key process management and information tools, ensuring compatibility with all options and GNU tests.
-- **Expected Outputs:** Efficient, reliable tools with full option compatibility and passing GNU tests.
-- **Skills Required/Preferred:** Proficiency in Rust, understanding of Linux process management, experience with GNU testing methodologies.
-- **Possible Mentors:** [To be determined]
-- **Size:** ~350 hours.
-- **Difficulty:** Medium.
-
-## `procps`: Development of System Monitoring and Statistics Tools in Rust
-
-This project involves the Rust-based development of system monitoring and statistics tools: `top`, `vmstat`, `tload`, `w`, and `watch`. The objective is to achieve full compatibility with all options and to pass GNU tests, ensuring these tools provide accurate and reliable system insights.
-
-- **Description:**: Create Rust versions of system monitoring and statistics tools, with a focus on full option compatibility and passing GNU tests.
-- **Expected Outputs:**: Robust tools for system monitoring and statistics, fully compatible with existing options and verified by GNU tests.
-- **Skills Required/Preferred:**: Rust expertise, knowledge of system performance metrics, familiarity with GNU testing frameworks.
-- **Possible Mentors:**: [To be determined]
-- **Size:**: ~350 hours.
-- **Difficulty:**: Medium.
-
-## `procps`: Development of Memory and Resource Analysis Tools in Rust
-
-The aim of this project is to develop Rust-based versions of memory and resource analysis tools: `pmap` and `slabtop`. The project will focus on ensuring full compatibility with all options and passing GNU tests, providing in-depth and reliable analysis of memory usage and kernel resources.
-
-- **Description:**: Implement Rust versions of memory and resource analysis tools, with emphasis on option compatibility and passing GNU tests.
-- **Expected Outputs:**: Advanced tools for memory and resource analysis, fully compatible with existing options and validated by GNU tests.
-- **Skills Required/Preferred:**: Proficiency in Rust, deep understanding of memory management and kernel resources, experience with GNU testing methodologies.
-- **Possible Mentors:**: [To be determined]
-- **Size:**: ~175 hours.
-- **Difficulty:**: Medium.
-
-## `util-linux`: Reimplementation of essential system utilities in Rust
-
-The objective of this project is to reimplement essential system utilities from the util-linux package in Rust. This initiative will include the development of Rust-based versions of various utilities, such as `dmesg`, `lscpu`, `lsipc`, `lslocks`, `lsmem`, and `lsns`. The primary focus will be on ensuring that these Rust implementations provide full compatibility with existing options and pass GNU tests, delivering reliable and efficient system utilities for Linux users.
-
-- **Description:**: Reimplement essential system utilities, including `dmesg`, `lscpu`, `lsipc`, `lslocks`, `lsmem`, and `lsns`, using Rust while emphasizing compatibility with existing options and GNU test validation.
-- **Expected Outputs:**: Rust-based system utilities that mirror the functionality of their counterparts, ensuring full compatibility and reliability, validated by GNU tests.
-- **Skills Required/Preferred:**: Proficiency in Rust programming, knowledge of system utilities and their functionality, experience with GNU testing methodologies.
-- **Possible Mentors:**: [To be determined]
-- **Size:**: ~175 hours.
-- **Difficulty:**: Medium.
-
-## `util-linux`: Process and Resource Management: Reimplementation in Rust
-
-This project focuses on the reimplementations of crucial Linux utilities related to process and resource management in the Rust programming language. The target utilities include `runuser`, `sulogin`, `chrt`, `ionice`, `kill`, `renice`, `prlimit`, `taskset`, and `uclampset`. The primary goal is to create Rust-based versions of these utilities, ensuring compatibility with their original counterparts, and validating their functionality with GNU tests.
-
-- **Description:**: Reimplement key Linux utilities for process and resource management, such as `runuser`, `sulogin`, `chrt`, `ionice`, `kill`, `renice`, `prlimit`, `taskset`, and `uclampset`, in the Rust programming language. The emphasis is on maintaining compatibility with the original utilities and validating their functionality using GNU tests.
-- **Expected Outputs:**: Rust-based versions of the specified utilities that seamlessly integrate into Linux systems, providing the same functionality and passing GNU tests for reliability.
-- **Skills Required/Preferred:**: Proficiency in Rust programming, understanding of process and resource management on Linux, experience with GNU testing methodologies.
-- **Possible Mentors:**: [To be determined]
-- **Size:**: ~175 hours.
-- **Difficulty:**: Medium.
-
-## `util-linux`: User and Session Management: Reimplementation in Rust
-
-This project focuses on the reimplementations of essential Linux utilities related to user and session management in the Rust programming language. The target utilities include `su`, `agetty`, `ctrlaltdel`, `pivot_root`, `switch_root`, `last`, `lslogins`, `mesg`, `setsid`, and `setterm`. The primary goal is to create Rust-based versions of these utilities, ensuring compatibility with their original counterparts, and validating their functionality with GNU tests.
-
-- **Description:**: Reimplement essential Linux utilities for user and session management, such as `su`, `agetty`, `ctrlaltdel`, `pivot_root`, `switch_root`, `last`, `lslogins`, `mesg`, `setsid`, and `setterm`, in the Rust programming language. The emphasis is on maintaining compatibility with the original utilities and validating their functionality using GNU tests.
-- **Expected Outputs:**: Rust-based versions of the specified utilities that seamlessly integrate into Linux systems, providing the same functionality and passing GNU tests for reliability.
-- **Skills Required/Preferred:**: Proficiency in Rust programming, understanding of user and session management on Linux, experience with GNU testing methodologies.
-- **Possible Mentors:**: [To be determined]
-- **Size:**: ~175 hours.
-- **Difficulty:**: Medium.
-
-This project aims to modernize and enhance critical Linux utilities related to user and session management, ensuring they remain efficient, reliable, and fully compatible with existing systems.
-
-## Code refactoring for `procps`, `util-linux`, and `bsdutils`
-
-Refactoring the Rust-based versions of procps, util-linux, and bsdutils to reduce code duplication.
-
-- **Title:**: Code Optimization and Refactoring for procps, util-linux, and bsdutils in Rust
-- **Description:**: This project involves optimizing and refactoring the Rust-based versions of procps, util-linux, and bsdutils. The focus will be on eliminating duplicated code across these utilities, particularly in areas like uudoc, the test framework, and support for single/multicall binaries.
-- **Expected outputs:**: A streamlined codebase with reduced duplication, improved maintainability for procps, util-linux, and bsdutils.
-- **Skills required/preferred:**: Proficiency in Rust programming, understanding of Linux utilities, experience with code optimization and refactoring.
-- **Possible mentors:**: Sylvestre
-- **Size:**: 175 hours
-- **Difficulty:**: Medium
-
-## A multicall binary and core library for `findutils`
-
-`findutils` currently exists of a few unconnected binaries. It would be nice to have a multicall binary (like
-`coreutils`) and a library of shared functions (like `uucore`).
-
-This also might require thinking about sharing code between coreutils and findutils.
-
-- **Difficulty**: Medium
-- **Size**: 175 hours
-- **Mentors**: TBD
-- Required skills:
- - Rust
-
-## Implementation of GNU Test Execution for `procps`, `util-linux`, `diffutils`, and `bsdutils`
-
-The project aims at integrating the GNU test suite execution using the Rust-based versions of `procps`, `util-linux`, `diffutils`, and `bsdutils`, ensuring compatibility, crucial for seamless drop-in replacement integration. We have been doing such operation successfully for the Coreutils using [GitHub Actions](https://github.com/uutils/coreutils/blob/main/.github/workflows/GnuTests.yml), a [build script](https://github.com/uutils/coreutils/blob/main/util/build-gnu.sh) and a [run script](https://github.com/uutils/coreutils/blob/main/util/run-gnu-test.sh).
-
-- **Description:**: Run the GNU test suite on the Rust-based versions of procps, util-linux, diffutils, and bsdutils
-- **Expected Outputs:**: The GNU test suite execution for each utility, ensuring functionality meets expected standards
-- **Skills Required/Preferred:**: GitHub action understanding, Proficiency in Rust, experience with GNU testing methodologies, familiarity with Linux system utilities, and understanding of software testing principles.
-- **Possible Mentors:**: Sylvestre
-- **Size:**: ~175 hours
-- **Difficulty:**: Medium
-
-## Symbolic/Fuzz Testing and Formal Verification of Tool Grammars
-
-See [Using Lightweight Formal Methods to Validate a Key Value Storage Node In Amazon S3](https://www.amazon.science/publications/using-lightweight-formal-methods-to-validate-a-key-value-storage-node-in-amazon-s3).
-
-Most KLEE scaffolding was done for [KLEE 2021](https://project-oak.github.io/rust-verification-tools/2021/07/14/coreutils.html).
-
-Start with `wc`, formalize the command line grammar. Get it working under AFL++ and Klee. Add several proofs of resource use and correctness - especially proofs about operating system calls and memory/cache usage. Generalize to other tools. Try to unify the seeds for the fuzzer and KLEE so they can help each other find new paths. Use QEMU to test several operating systems and architectures. Automate detection of performance regressions - try to hunt for [accidentally quadratic](https://accidentallyquadratic.tumblr.com) behavior.
-
-Specific to `wc` - formalize the inner loop over a UTF-8 buffer into a finite state automata with counters that can generalize into SIMD width operations like [simdjson](https://simdjson.org). Further generalize into a monoid so K processors can combine results.
-
-- Difficulty: Mixed
-- Size: Mixed
-- Mentors: TBD - informally @chadbrewbaker
-- Required skills:
- - Rust
- - KLEE
- - Fuzzers like AFL++
- - Grammar testing frameworks like [LARK](https://github.com/ligurio/lark-grammars/tree/master/lark_grammars/grammars)
- - /usr/bin/time -v (and similar tools for Widows/OSX).
- - Alloy, TLA+, [P](https://github.com/p-org/P)
- - System call tracing with [strace](https://jvns.ca/blog/2014/02/17/spying-on-ssh-with-strace/), [uftrace](https://github.com/namhyung/uftrace) etc.
- - SMT solvers like [Z3](https://www.philipzucker.com/programming-and-interactive-proving-with-z3py/) and CVC5 for superoptimization and proofs of automata equivalence.
- - [SOUPER](https://github.com/google/souper) and [CompilerExplorer](https://godbolt.org)
- - Basic statistics on quantiles (histograms) for outlier detection. The math is simple as generalizing from one to k medians but the formal notation is [complex](https://aakinshin.net/posts/thdqe-hdi/).
- - [MPI-IO](https://wgropp.cs.illinois.edu/courses/cs598-s16/lectures/lecture32.pdf), just enough to read a file into k parts and combine "wc" outputs to understand multicore scaling.
-
-## Development of advanced terminal session recording and replay tools in Rust
-
-This project involves creating Rust-based implementations of `/usr/bin/script`, `/usr/bin/scriptlive`, and `/usr/bin/scriptreplay`. The `/usr/bin/script` command will record terminal sessions, `/usr/bin/scriptlive` will offer real-time recording features, and `/usr/bin/scriptreplay` will be used to replay recorded sessions.
-
-The work will happen in https://github.com/uutils/bsdutils.
-
-- **Description:**: Develop Rust-based versions of `/usr/bin/script`, `/usr/bin/scriptlive`, and `/usr/bin/scriptreplay` for terminal session recording and replaying.
-- **Expected Outputs:**: Robust and cross-platform terminal session recording and replay tools, with real-time features in `scriptlive`.
-- **Skills Required/Preferred:**: Proficiency in Rust, understanding of terminal emulation, experience with cross-platform development.
-- **Possible Mentors:**: [To be determined]
-- **Size:**: ~175 hours
-- **Difficulty:**: Medium
-
-## Official Redox support
-We want to support the Redox operating system, but are not actively testing against it. Since the last round of fixes in [#2550](https://github.com/uutils/coreutils/pull/2550), many changes have probably been introduced that break Redox support. This project would involve setting up Redox in the CI and fixing any issues that arise and porting features over.
-
-- Difficulty: Medium
-- Size: 175 hours
-- Mentors: TBD
-- Required skills:
- - Rust
+These are starting points for a Google Summer of Code project with uutils. Feel free to adapt one or propose your own, and see the [guidelines for the project list](https://google.github.io/gsocguides/mentor/defining-a-project-ideas-list). Each idea lists its difficulty, an estimated size (~175 or ~350 hours) and a suggested mentor where one is available.
+
+
+
+
+
Performance optimization for coreutils
+
+ Medium
+ ~175h
+ Mentor: TBD
+
+
uutils/coreutils has strong GNU compatibility, but some utilities can still be made faster. Systematically profile, benchmark and optimize the hot paths so they match or beat GNU coreutils.
+
+
Profile utilities with perf, flamegraph and criterion
+
Build a benchmark suite comparing against GNU coreutils
+
Optimize hot paths in cat, cut, sort, uniq, wc, etc.
+
Reduce allocations, improve buffering, use SIMD where it helps
+
+
Skills: Rust, performance profiling, systems/I/O optimization; SIMD a plus.
+
+
+
+
Expand differential fuzzing for coreutils
+
+ Medium
+ ~175h
+ Mentor: TBD
+
+
coreutils has some fuzzing infrastructure, but many utilities lack coverage. Expand differential fuzzing that compares uutils against GNU to catch discrepancies automatically.
+
+
Add fuzz targets for utilities that currently lack them
+
Build differential harnesses comparing uutils vs GNU output
+
Run campaigns with AFL++ and libFuzzer, wire them into CI
uutils/findutils already passes more than half of the GNU findutils and BFS tests. Finish the remaining work to reach full compatibility and production readiness.
+
+
Implement missing options and predicates for find
+
Fix edge cases in traversal and symlink handling
+
Complete xargs argument handling
+
Pass the remaining GNU tests; add differential fuzzing
+
+
Skills: Rust, filesystem operations, find/xargs usage; fuzzing a plus.
+
+
+
+
Complete diffutils GNU compatibility
+
+ Medium
+ ~175h
+ Mentor: TBD
+
+
uutils/diffutils implements diff, diff3, cmp and sdiff. Complete the remaining features and edge cases so it passes the GNU test suite.
+
+
Implement missing options and output formats for diff
+
Improve algorithm efficiency for large files
+
Complete diff3 three-way merges
+
Pass the GNU diffutils tests; add differential fuzzing
+
+
Skills: Rust, diff algorithms (Myers, Patience), text processing.
+
+
+
+
Complete the Rust implementation of sed
+
+ Medium
+ ~175h
+ Mentor: TBD
+
+
uutils/sed has been started but needs significant work to fully match GNU sed and POSIX. Implement the missing commands and edge cases and make it pass the GNU test suite.
+
+
Implement missing commands and addressing flags
+
Handle complex regex, backreferences and multi-line pattern space
+
Implement hold-space operations correctly
+
Pass the GNU sed tests; add differential fuzzing
+
+
Skills: Rust, regular expressions, sed scripting, text processing.
+
+
+
+
Rust implementation of grep
+
+ Hard
+ ~350h
+ Mentor: TBD
+
+
Build a high-performance, feature-complete drop-in replacement for GNU grep - full command-line interface, output modes and edge-case behavior, with the performance Rust can provide.
+
+
Implement the full POSIX/GNU grep CLI
+
Support BRE, ERE and PCRE patterns
+
Handle context lines, recursive search, binary and compressed files
+
Pass the GNU grep tests; benchmark against GNU grep
Implement awk, a complete programming language for pattern scanning and text processing, targeting POSIX awk and GNU awk (gawk) extensions.
+
+
Build the lexer, parser and pattern-action execution engine
+
Support built-in variables (NR, NF, FS, RS) and functions
+
Implement field splitting, arrays, user functions and control flow
+
Set up GNU test suite execution for validation
+
+
Skills: Rust, lexers/parsers/interpreters, regex; language implementation a plus.
+
+
+
+
Complete procps implementation
+
+ Medium
+ ~350h
+ Mentor: TBD
+
+
uutils/procps reimplements the process and system monitoring tools. Complete the core utilities and reach production readiness with full GNU compatibility. Scope can be focused on one of the groups below.
+
+
Process management & info: ps, pgrep, pidwait, pkill, skill, snice
+
System monitoring & statistics: top, vmstat, tload, w, watch
Robust /proc parsing across kernels; run the GNU procps tests
+
+
Skills: Rust, Linux /proc filesystem, process management and monitoring.
+
+
+
+
Complete util-linux implementation
+
+ Medium
+ ~350h
+ Mentor: TBD
+
+
uutils/util-linux reimplements essential system utilities. Complete the most commonly used tools and reach production-ready status with full compatibility. Scope can be focused on one of the groups below.
Skills: Rust, BSD and Linux environments, terminal emulation, cross-platform development.
+
+
+
+
Localization
+
+ Hard
+ Size: TBD
+ Mentor: TBD
+
+
Support localization for formatting, quoting and sorting in utilities like date, ls and sort. The core question is how to deal with locale data: the all-Rust icu4x library (possibly with a custom localedef-like command) versus a wrapper around the C icu library.
Code refactoring for procps, util-linux & bsdutils
+
+ Medium
+ ~175h
+ Mentor: Sylvestre
+
+
Refactor the Rust versions of procps, util-linux and bsdutils to reduce duplication, particularly around uudoc, the test framework, and single/multicall binary support.
+
+
Eliminate duplicated code across the three projects
+
Unify the documentation and test scaffolding
+
Improve maintainability and shared infrastructure
+
+
Skills: Rust, Linux utilities, code optimization and refactoring.
+
+
+
+
A multicall binary and core library for findutils
+
+ Medium
+ ~175h
+ Mentor: TBD
+
+
findutils currently consists of a few unconnected binaries. Build a multicall binary (like coreutils) and a library of shared functions (like uucore).
+
+
Design a unified multicall entry point
+
Extract shared functionality into a core library
+
Consider sharing code between coreutils and findutils
+
+
Skills: Rust, library and CLI design.
+
+
+
+
GNU test execution for procps, util-linux, diffutils & bsdutils
+
+ Medium
+ ~175h
+ Mentor: Sylvestre
+
+
Integrate the upstream test suites against the Rust versions of procps, util-linux, diffutils and bsdutils - crucial for proving drop-in compatibility. We already do this for coreutils via GitHub Actions, a build script and a run script.
+
+
Adapt the coreutils CI approach to each project
+
Wire the test suites into GitHub Actions
+
Track and report compatibility over time
+
+
Skills: GitHub Actions, Rust, GNU testing methodologies, Linux utilities.
+
+
+
+
Symbolic/fuzz testing and formal verification of tool grammars
Inspired by lightweight formal methods at AWS; most KLEE scaffolding was done for KLEE 2021. Start with wc, formalize its command-line grammar, run it under AFL++ and KLEE, then generalize.
+
+
Add proofs of resource use and correctness, especially around syscalls and memory
+
Unify fuzzer and KLEE seeds so they help each other find paths
+
Formalize the wc UTF-8 inner loop into a SIMD-friendly automaton / monoid
We want to support the Redox operating system but are not actively testing against it. Since the last round of fixes in #2550, regressions have likely crept in.
+
+
Set up Redox in CI
+
Fix the issues that arise and port missing features
+
+
Skills: Rust, cross-platform/OS development.
+
+
+
diff --git a/content/playground.md b/content/playground.md
index aa14e87a3..73f9575dc 100644
--- a/content/playground.md
+++ b/content/playground.md
@@ -17,7 +17,20 @@ template = "page.html"
Extra programs:
-
+
+
+ user@uutils: ~
+
+
+
+
+
+
+
+
+
+ Run a command, then copy a link that reruns it for anyone you share it with.
+
@@ -25,118 +38,7 @@ template = "page.html"
-
+
-
-
## Sharing commands via URL
-You can pre-fill the terminal with a command using the `?cmd=` URL parameter. The command runs automatically when the page loads - great for sharing examples or linking from documentation.
+After running a command, click **🔗 Copy share link** below the terminal to copy a link that reruns it. You can also build one by hand with the `?cmd=` URL parameter. The command runs automatically when the page loads - great for sharing examples or linking from documentation.
**Examples:**
diff --git a/content/sed.md b/content/sed.md
index c2ba7dafb..9267e4cac 100644
--- a/content/sed.md
+++ b/content/sed.md
@@ -5,6 +5,7 @@ template = "project.html"
[extra]
wip = true
+status = "alpha"
+++
diff --git a/content/shadow-rs.md b/content/shadow-rs.md
deleted file mode 100644
index 3f365e34f..000000000
--- a/content/shadow-rs.md
+++ /dev/null
@@ -1,32 +0,0 @@
-+++
-
-title = "shadow-rs"
-template = "project.html"
-
-[extra]
-wip = true
-
-+++
-
-Memory-safe Rust reimplementation of Linux shadow-utils: `useradd`, `userdel`, `usermod`, `passwd`, `pwck`, `chpasswd`, `chage`, `groupadd`, `groupdel`, `groupmod`, `grpck`, `chfn`, `chsh`, and `newgrp`.
-
-This project aims to be a drop-in replacement for the original commands, with the same flags, exit codes, and output format as GNU shadow-utils.
-
-# Goals
-
-This project aims to be a drop-in replacement for the GNU shadow-utils, with a focus on:
-
-- **Drop-in compatibility** — same flags, same exit codes, same output format as GNU shadow-utils.
-- **Memory safety** — eliminating buffer overflows and use-after-free vulnerabilities through Rust's type system.
-- **Security hardening** — Landlock sandboxing and privilege dropping.
-- **Comprehensive testing** — unit tests, property-based tests, integration tests, and fuzz targets.
-
-# Contributing
-
-To contribute to uutils shadow-rs, please see [CONTRIBUTING](https://github.com/uutils/shadow-rs/blob/main/CONTRIBUTING.md).
-
-# License
-
-uutils shadow-rs is licensed under the MIT License - see the [LICENSE](https://github.com/uutils/shadow-rs/blob/main/LICENSE) file for details.
-
-GNU shadow-utils is licensed under the BSD 3-Clause License.
diff --git a/content/shadow.md b/content/shadow.md
new file mode 100644
index 000000000..1235bfc9b
--- /dev/null
+++ b/content/shadow.md
@@ -0,0 +1,33 @@
++++
+
+title = "shadow"
+template = "project.html"
+aliases = ["/shadow-rs"]
+
+[extra]
+wip = true
+
++++
+
+Memory-safe Rust reimplementation of Linux shadow-utils: `useradd`, `userdel`, `usermod`, `passwd`, `pwck`, `chpasswd`, `chage`, `groupadd`, `groupdel`, `groupmod`, `grpck`, `chfn`, `chsh`, and `newgrp`.
+
+This project aims to be a drop-in replacement for the original commands, with the same flags, exit codes, and output format as GNU shadow-utils.
+
+# Goals
+
+This project aims to be a drop-in replacement for the GNU shadow-utils, with a focus on:
+
+- **Drop-in compatibility** - same flags, same exit codes, same output format as GNU shadow-utils.
+- **Memory safety** - eliminating buffer overflows and use-after-free vulnerabilities through Rust's type system.
+- **Security hardening** - Landlock sandboxing and privilege dropping.
+- **Comprehensive testing** - unit tests, property-based tests, integration tests, and fuzz targets.
+
+# Contributing
+
+To contribute to uutils shadow, please see [CONTRIBUTING](https://github.com/uutils/shadow/blob/main/CONTRIBUTING.md).
+
+# License
+
+uutils shadow is licensed under the MIT License - see the [LICENSE](https://github.com/uutils/shadow/blob/main/LICENSE) file for details.
+
+GNU shadow-utils is licensed under the BSD 3-Clause License.
diff --git a/content/team.md b/content/team.md
new file mode 100644
index 000000000..9d0dceaa7
--- /dev/null
+++ b/content/team.md
@@ -0,0 +1,34 @@
++++
+
+title = "Who we are"
+template = "page.html"
+
++++
+
+uutils is a community-driven, open-source effort maintained by volunteers around the world. There is no company behind it, just contributors who care about the future of foundational command-line tools.
+
+Everything happens in the open on [GitHub](https://github.com/uutils), and newcomers are genuinely welcome. Many of our contributors landed their first-ever open-source patch on a uutils project, and we are happy to help you do the same.
+
+
-