The content-security-policy spec is long. Implementing it and testing it takes all day just translating stuff from English to Rust; I figure many hands makes light work, if anyone’s interested in working on a small corner of Servo and Ammonia.
Tetra seems to run pretty well on Windows and Linux (or rather, there’s at least one person who’s got it working!), but Mac users are consistently getting black screens. I don’t have access to a Mac myself, so it’s not something I can debug easily…
If anyone with knowledge of OpenGL on Mac could have a poke around, their help would be much appreciated
As the library becomes more popular, does someones wanna to review the code and provide some feedbacks, improvements and best writing to maintain it.
It can be also a good start point to contribute to it too.
Crater needs this little feature to be implemented: it’s not difficult and there are mentoring instructions available.
I’ve created a number of issues for the Rust port of flamegraph, inferno, and am also happy to shepherd/mentor PRs (we’ve even had some already!). The initial code was also developed through a video series (part 1, part 2), which might be useful for people who want to contribute and really understand how it all fits together.
Tarpaulin/coveralls-api crates need help testing a new coveralls feature to create better reports using your CI environment variables. Looking for people who use things other than travis to help test https://github.com/xd009642/tarpaulin/issues/213
Should be pretty beginner-friendly. No knowledge of the compiler necessary. Semi-detailed instructions are available in the issue OP.
There’s an issue on pulldown-cmark to create a simple benchmark framework that guards against quadratic behaviour of the markdown parser. This should be feasible for someone with some Rust experience, yet still be interesting. There are already a number of test cases in the issue tracker and an outline of approaches in the issue description.
This requires adding two features to Cargo.toml and setting the appropriate
#[cfg(..)]s, perhaps putting things into a module to simplify things. I can mentor if required.
Three issues in ruma-client-api with difficulties from easy to hard:
I’ve created a tracking issue to discuss safety - if anyone could pitch in and save me from silly mistakes, it’d be helpful!
Wait… so what have we been using all this time?
Very beginner friendly. I need some test coverage for the futures-jsonrpc crate