Now that the release of ggez 0.4 is nigh, we dearly would like people to just run the examples on different platforms and make sure they work properly, as well as making sure the build documents for every platform are correct. Problems can be reported on the issue tracker!
I’d suggest to create an issue to which we can link to (and where discussions may take place by interested to-be contributors). This could even be a meta-issue which may link to other issues specific to each platform.
Here are some simple and (I think) interesting issues in https://github.com/gluon-lang/gluon
Here’s another one from
mdbook. It’s a bit more complex than the previous batch but I’m planning on mentoring anyone who wants to have a go at it.
Myself and the rest of my dev team could really use a hand with quite a LOT of things on the Aardwolf project. But I just created a new issue that might be good for a beginner. Basically I haven’t had enough time to fully understand the way that Rocket routes to web templates, and I would LOVE to have a proper UI to demo
Something more advanced would be the related repo for ActivityStreams implementation in Rust (https://github.com/jfmcbrayer/activitystreams) but to be polite I will have to ask my dev if I can create a “help wanted” issue first hahah
Looking for some more eyes on miniz_oxide as it’s starting to see some use as a back-end for flate2.
This may be a nice starting point for new contributors, but other help is welcome as well:
This is specially for beginners or people wanting to create their first PR:
A really easy PR:
Hey we have a few issues here:
The new and upcoming mutagen project needs your help! I (at the moment it’s just me) have a few issues to work on, so come and help
break a lot of Rust code shape the future of mutation testing for Rust!
Here’s a little task for someone with a Windows machine:
I am still learning cargo internals, but I would be willing to help someone who wanted to take one of these on:
They are simpler than they appear, each of them 5-10 lines of new code, but have room for extra credit / additional work if desired.
Something not too hard I believe:
It would be great to have this included in another issue! I went around trying to label issues that might be better for beginners:
The rustc guide is more of a writing project than a programming project, but there are a bunch of things that need doing. There are
- easier issues: https://github.com/rust-lang-nursery/rustc-guide/issues?q=is%3Aissue+is%3Aopen+label%3AEasy
- issues which might require a bit of investigation/code reading: https://github.com/rust-lang-nursery/rustc-guide/issues?q=is%3Aissue+is%3Aopen+label%3AMedium
- issues which probably require some advanced knowledge or a lot of time: https://github.com/rust-lang-nursery/rustc-guide/issues?q=is%3Aissue+is%3Aopen+label%3AMedium+label%3AHard
(sorry, discourse is not letting me post more than 2 links for some reason )
Would like have this again this week please
Perhaps with a quick intro like “rustc-guide is a project to write a short guide about how the rust compiler works”. Plus what was written last week.