24
edits
Community:SummerOfCode17: Difference between revisions
Jump to navigation
Jump to search
No more rust candidates please
(Remove Tor Experiment) |
(No more rust candidates please) |
||
| Line 269: | Line 269: | ||
|- | |- | ||
! Rust + WebAssembly showcase | ! Rust + WebAssembly showcase | ||
! Rust and WebAssembly are going to be a great pair. Design and implement a simple and attractive web application, in Rust, that demonstrates the power of Rust on the web. Make fixes to upstream projects as necessary. Write a blog post about it. | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust and WebAssembly are going to be a great pair. Design and implement a simple and attractive web application, in Rust, that demonstrates the power of Rust on the web. Make fixes to upstream projects as necessary. Write a blog post about it. | ||
! Rust, web development | ! Rust, web development | ||
! [https://github.com/brson/ brson] | ! [https://github.com/brson/ brson] | ||
| Line 276: | Line 276: | ||
|- | |- | ||
! Rust dashboard updates | ! Rust dashboard updates | ||
! Update rusty-dash.com to include additional metrics important to the project. This tool is vital to the day-to-day management of Rust, but it needs some dedicated attention to fulfill its promise. | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Update rusty-dash.com to include additional metrics important to the project. This tool is vital to the day-to-day management of Rust, but it needs some dedicated attention to fulfill its promise. | ||
! Rust | ! Rust | ||
! [https://github.com/brson/ brson] | ! [https://github.com/brson/ brson] | ||
| Line 283: | Line 283: | ||
|- | |- | ||
! Rust reproducible builds | ! Rust reproducible builds | ||
! Make the Rust build process produce the identical binaries when run with identical configurations. This improves the security of the Rust ecosystem by allowing others to | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Make the Rust build process produce the identical binaries when run with identical configurations. This improves the security of the Rust ecosystem by allowing others to | ||
double-check the official Rust builds | double-check the official Rust builds | ||
! Rust, compilers, systems programming | ! Rust, compilers, systems programming | ||
| Line 291: | Line 291: | ||
|- | |- | ||
! Abstract the Rust standard library | ! Abstract the Rust standard library | ||
! The Rust standard library is very portable, but can be very, very portable. Refactor the | ! (this project has many applicants and is not considering new candidates. please look elsewhere) The Rust standard library is very portable, but can be very, very portable. Refactor the | ||
standard library to pull out a platform abstraction layer. | standard library to pull out a platform abstraction layer. | ||
! Moderate Rust experience | ! Moderate Rust experience | ||
| Line 299: | Line 299: | ||
|- | |- | ||
! Rust cross-platform showcase project | ! Rust cross-platform showcase project | ||
! Rust is very portable. Create a single showcase demo project that compiles for Windows, OS X, Linux, Android, iOS, wasm, and microcontrollers. Use real crates to accomplish some real task. Set up CI for all platforms on Travis. To be used as a teaching tool and for regression testing. Write a blog post. | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust is very portable. Create a single showcase demo project that compiles for Windows, OS X, Linux, Android, iOS, wasm, and microcontrollers. Use real crates to accomplish some real task. Set up CI for all platforms on Travis. To be used as a teaching tool and for regression testing. Write a blog post. | ||
! Moderate Rust experience | ! Moderate Rust experience | ||
! [https://github.com/brson/ brson] | ! [https://github.com/brson/ brson] | ||
| Line 306: | Line 306: | ||
|- | |- | ||
! rustc micro-optimization bonanza | ! rustc micro-optimization bonanza | ||
! Just go hog wild finding microoptimizations in rustc. Write a blog post bragging about it. | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Just go hog wild finding microoptimizations in rustc. Write a blog post bragging about it. | ||
! Performance optimization | ! Performance optimization | ||
! [https://github.com/brson/ brson] | ! [https://github.com/brson/ brson] | ||
| Line 313: | Line 313: | ||
|- | |- | ||
! Rust-specific benchmark suite | ! Rust-specific benchmark suite | ||
! Today Rust uses perf.rust-lang.org to track _compile time_ performance, but nothing to track _runtime_ performance. Work with the Rust developers to create a benchmark suite specific to Rust. | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Today Rust uses perf.rust-lang.org to track _compile time_ performance, but nothing to track _runtime_ performance. Work with the Rust developers to create a benchmark suite specific to Rust. | ||
! Programming | ! Programming | ||
! [https://github.com/brson/ brson] | ! [https://github.com/brson/ brson] | ||
| Line 320: | Line 320: | ||
|- | |- | ||
! Rust crate semver compatibility tool | ! Rust crate semver compatibility tool | ||
! Rust libraries follow the semver spec for indicating API compatibility, but conformance to semver is not enforced in any way - it is up to crate authors to guarantee their crates can be upgraded correctly. With Rust's strong type system it should be possible to mechanically check whether crates | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust libraries follow the semver spec for indicating API compatibility, but conformance to semver is not enforced in any way - it is up to crate authors to guarantee their crates can be upgraded correctly. With Rust's strong type system it should be possible to mechanically check whether crates | ||
are obeying semver. This would be a huge boon to the stability of the Rust ecosystem. | are obeying semver. This would be a huge boon to the stability of the Rust ecosystem. | ||
! Static analysis | ! Static analysis | ||
| Line 328: | Line 328: | ||
|- | |- | ||
! Reconstruct the Rust bootstrap chain | ! Reconstruct the Rust bootstrap chain | ||
! Rust is a self-hosted compiler, originally bootstrapped from OCaml, then self-bootstrapped several hundred times over the years. Today there is only one Rust 'lineage' of any note, the official compiler, but with compilers diversity of implementation is a security issue. If another party could replicate the | ! (this project has many applicants and is not considering new candidates. please look elsewhere) Rust is a self-hosted compiler, originally bootstrapped from OCaml, then self-bootstrapped several hundred times over the years. Today there is only one Rust 'lineage' of any note, the official compiler, but with compilers diversity of implementation is a security issue. If another party could replicate the | ||
Rust compiler it would provide assurance that the official isn't compromised by, or can recover from, a "trusting trust" attack. Although the historical information needed to rebootstrap Rust is mostly complete, it is not trivial to do. Construct a script that can reconstruct the modern Rust compiler from the original OCaml implementation, run it to completion, write a blog post. | Rust compiler it would provide assurance that the official isn't compromised by, or can recover from, a "trusting trust" attack. Although the historical information needed to rebootstrap Rust is mostly complete, it is not trivial to do. Construct a script that can reconstruct the modern Rust compiler from the original OCaml implementation, run it to completion, write a blog post. | ||
! Scripting, build systems | ! Scripting, build systems | ||