Mirrors/rust
1
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2026-04-27 18:57:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated Note getting started developing Rust (markdown)

Brian Anderson
2013-06-23 15:53:42 -07:00
parent 753c154716
commit 870548b81f
1 changed files with 0 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Note-getting-started-developing-Rust.md
-19
@@ -152,25 +152,6 @@ Syntax highlighting for vim is included in the Rust repository, under `src/etc/v
We use the [GitHub issue tracker](https://github.com/mozilla/rust/issues) to track bugs and feature requests in Rust. If you prefer not to use the standard GitHub issue tracker, there's a [secondary front-end that is quite a bit more responsive](http://githubissues.heroku.com/#mozilla/rust).
## Picking something interesting to do
The way most people seem to get involved is by simply trying to write Rust code. Inevitably you will hit a bug or missing feature, at which point you may feel compelled to write a patch.
Another way to get involved is to look through the issue tracker for issues labeled with "[E-easy]", "[I-enhancement]", "[I-wishlist]", and/or "[A-an-interesting-project]". Unassigned bugs are always fair game. Assigned bugs that don't seem to be getting worked on actively can be fair game, but always check with the bug owner first in that case. Also see the [[development policy|Note development policy]].
[E-easy]: https://github.com/mozilla/rust/issues?labels=E-easy&page=1&state=open
[I-enhancement]: https://github.com/mozilla/rust/issues?labels=I-enhancement&page=1&state=open
[I-wishlist]: https://github.com/mozilla/rust/issues?labels=I-wishlist&page=1&state=open
[A-an-interesting-project]: https://github.com/mozilla/rust/issues?labels=A-an-interesting-project&page=1&state=open
Outstanding bugs or feature requests in Rust often have a corresponding test in the test suite that doesn't yet pass. One good way to jump into Rust development is to look for files in the test/run-pass directory containing the string `xfail-test`. Those tests all correspond to bugs that need to be fixed or features that someone needs to finish.
The source is also littered with hundreds of comments marked with 'FIXME' and 'TODO'. In Rust, FIXME comments come with an issue number; sometimes these refer to issues that may be resolved easily.
For inspiration, read about [how cmr started hacking the compiler][cmr]. If in doubt, ask on IRC. Somebody will surely have a task that needs doing.
[cmr]: http://cmr.github.io/blog/2013/06/23/how-i-got-started-with-rust/
## Communicating
Join irc.mozilla.org #rust for real-time discussion of Rust development. We try to remain on that channel during working hours in UTC-7 (US Pacific).