Skip to content

Commit a6f2749

Browse files
aturonaturon
committed
impl Future for Rust
1 parent 63eb932 commit a6f2749

File tree

1 file changed

+312
-0
lines changed

1 file changed

+312
-0
lines changed

‎_posts/2017-09-18-impl-future-for-rust.md

Lines changed: 312 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,312 @@
1+
---
2+
layout: post
3+
title: "impl Future for Rust"
4+
author: Aaron Turon
5+
description: "The Rust community is going to finish out its 2017 roadmap with a bang—and we want your help!"
6+
---
7+
8+
The Rust community has been hard at work on our [2017 roadmap], but as we come
9+
up on the final quarter of the year, we're going to kick it into high gear—and
10+
we want you to join us!
11+
12+
[2017 roadmap]: https://github.com/rust-lang/rfcs/pull/1774
13+
14+
Our goals for the year are ambitious:
15+
16+
* [Rust should have a lower learning curve](https://github.com/rust-lang/rust-roadmap/issues/3).
17+
* [Rust should have a pleasant edit-compile-debug cycle](https://github.com/rust-lang/rust-roadmap/issues/1).
18+
* [Rust should provide a solid, but basic IDE experience](https://github.com/rust-lang/rust-roadmap/issues/2).
19+
* [Rust should provide easy access to high quality crates](https://github.com/rust-lang/rust-roadmap/issues/9).
20+
* [Rust should be well-equipped for writing robust, high-scale servers](https://github.com/rust-lang/rust-roadmap/issues/10).
21+
* [Rust should have 1.0-level crates for essential tasks](https://github.com/rust-lang/rust-roadmap/issues/11).
22+
* [Rust should integrate easily into large build systems](https://github.com/rust-lang/rust-roadmap/issues/12).
23+
* [Rust's community should provide mentoring at all levels](https://github.com/rust-lang/rust-roadmap/issues/13)
24+
25+
**To finish off these goals, we intend to spend the rest of the year focused
26+
purely on "implementation" work—which doesn't just mean code!** In particular, we
27+
are effectively spinning down the [RFC process] for 2017, after having merged
28+
[almost 90] RFCs this year!
29+
30+
[RFC process]: https://github.com/rust-lang/rfcs#rust-rfcs
31+
[almost 90]: https://github.com/rust-lang/rfcs/pulls?utf8=%E2%9C%93&q=is%3Apr%20merged%3A%3E2017-01-01
32+
33+
So here's the plan. Each Rust team has put together several *working groups*
34+
focused on a specific sub-area. Each WG has a leader who is responsible for
35+
carving out and coordinating work, and a dedicated chat channel for getting
36+
involved. We are working hard to divvy up work items into many shapes and sizes,
37+
and to couple them with mentoring instructions and hands-on mentors. **So if
38+
you've always wanted to contribute to Rust but weren't sure how, this is the
39+
perfect opportunity for you.** Don't be shy—we want and need your help, and, as
40+
per our roadmap, our aim is mentoring at *all* levels of experience.
41+
42+
## A few points of order
43+
44+
There are a few online venues for keeping in the loop with working group activity:
45+
46+
- There is a [dedicated Gitter community](https://gitter.im/rust-impl-period/)
47+
with channels for each working group, as well as
48+
a [global channel](https://gitter.im/rust-impl-period/Lobby) for talking about
49+
the process as a whole, or getting help finding your way to a working group.
50+
51+
- The brand-new [findwork](https://www.rustaceans.org/findwork) site, which
52+
provides an entry point to a number of open issues across the Rust project,
53+
including those managed by working groups (see the "impl period" tab). Thanks,
54+
@nrc, for putting this together!
55+
56+
We also plan two in-person events, paired with upcoming Rust conferences. Each
57+
of them is a two-day event populated in part by Rust core developers; come hang
58+
out and work together!
59+
60+
- [October 2-3 at RustFest](http://blog.rustfest.eu/this-week-in-rustfest-9-impl-days).
61+
- [October 24-25 at Rust Belt Rust](https://goo.gl/forms/e9hmmsFw4owhhDf62).
62+
63+
As usual, all of these venues abide by the [Rust code of conduct]. But more than
64+
that: this "impl period" is a chance for us all to have fun *collaborating* and
65+
*helping* each other, and those participating in the official venues are
66+
expected to meet the highest standards of behavior.
67+
68+
[Rust code of conduct]: https://www.rust-lang.org/conduct.html
69+
70+
## The working groups
71+
72+
Without further ado, here's the initial lineup! (A few more working groups are
73+
expected to arise over time.)
74+
75+
### Compiler team
76+
77+
<table>
78+
<tr>
79+
<td><b>WG-compiler-errors</b></td>
80+
<td>Make Rust's error messages even friendlier.</td>
81+
<td><a href="">Learn more</a></td>
82+
<td><a href="">Chat</a></td>
83+
</tr>
84+
<tr>
85+
<td><b>WG-compiler-front</b></td>
86+
<td>Dip your toes in with parsing and syntax sugar.</td>
87+
<td><a href="">Learn more</a></td>
88+
<td><a href="">Chat</a></td>
89+
</tr>
90+
<tr>
91+
<td><b>WG-compiler-middle</b></td>
92+
<td>Implement features that involve typechecking.</td>
93+
<td><a href="">Learn more</a></td>
94+
<td><a href="">Chat</a></td>
95+
</tr>
96+
<tr>
97+
<td><b>WG-compiler-traits</b></td>
98+
<td>Want generic associated types? You know what to do.</td>
99+
<td><a href="">Learn more</a></td>
100+
<td><a href="">Chat</a></td>
101+
</tr>
102+
<tr>
103+
<td><b>WG-compiler-incr</b></td>
104+
<td>Finish incremental compilation; receive undying love.</td>
105+
<td><a href="">Learn more</a></td>
106+
<td><a href="">Chat</a></td>
107+
</tr>
108+
<tr>
109+
<td><b>WG-compiler-nll</b></td>
110+
<td>Delve into the bowels of borrowck to slay the beast: NLL!</td>
111+
<td><a href="">Learn more</a></td>
112+
<td><a href="">Chat</a></td>
113+
</tr>
114+
<tr>
115+
<td><b>WG-compiler-const</b></td>
116+
<td>Const generics. Enough said.</td>
117+
<td><a href="">Learn more</a></td>
118+
<td><a href="">Chat</a></td>
119+
</tr>
120+
</table>
121+
122+
### Libs team
123+
124+
<table>
125+
<tr>
126+
<td><b>WG-libs-blitz</b></td>
127+
<td>Help finish off the Blitz before all the issues are gone!</td>
128+
<td><a href="">Learn more</a></td>
129+
<td><a href="">Chat</a></td>
130+
</tr>
131+
<tr>
132+
<td><b>WG-libs-cookbook</b></td>
133+
<td>Work on bite-sized examples to get folks cooking with Rust.</td>
134+
<td><a href="">Learn more</a></td>
135+
<td><a href="">Chat</a></td>
136+
</tr>
137+
<tr>
138+
<td><b>WG-libs-guidelines</b></td>
139+
<td>Take the wisdom from the Blitz and pass it on.</td>
140+
<td><a href="">Learn more</a></td>
141+
<td><a href="">Chat</a></td>
142+
</tr>
143+
<tr>
144+
<td><b>WG-libs-simd</b></td>
145+
<td>We want stable SIMD, and we need your help.</td>
146+
<td><a href="">Learn more</a></td>
147+
<td><a href="">Chat</a></td>
148+
</tr>
149+
<tr>
150+
<td><b>WG-libs-openssl</b></td>
151+
<td>Want better docs for openssl? So do we.</td>
152+
<td><a href="">Learn more</a></td>
153+
<td><a href="">Chat</a></td>
154+
</tr>
155+
<tr>
156+
<td><b>WG-libs-rand</b></td>
157+
<td></td>
158+
<td><a href="">Learn more</a></td>
159+
<td><a href="">Chat</a></td>
160+
</tr>
161+
</table>
162+
163+
### Docs team
164+
165+
<table>
166+
<tr>
167+
<td><b>WG-docs-rustdoc</b></td>
168+
<td></td>
169+
<td><a href="">Learn more</a></td>
170+
<td><a href="">Chat</a></td>
171+
</tr>
172+
<tr>
173+
<td><b>WG-docs-rustdoc2</b></td>
174+
<td>Get in on a bottom-up revamp of rustdoc!</td>
175+
<td><a href="">Learn more</a></td>
176+
<td><a href="">Chat</a></td>
177+
</tr>
178+
<tr>
179+
<td><b>WG-docs-rbe</b></td>
180+
<td></td>
181+
<td><a href="">Learn more</a></td>
182+
<td><a href="">Chat</a></td>
183+
</tr>
184+
</table>
185+
186+
### Dev tools team
187+
188+
<table>
189+
<tr>
190+
<td><b>WG-dev-tools-rls</b></td>
191+
<td></td>
192+
<td><a href="">Learn more</a></td>
193+
<td><a href="">Chat</a></td>
194+
</tr>
195+
<tr>
196+
<td><b>WG-dev-tools-vscode</b></td>
197+
<td></td>
198+
<td><a href="">Learn more</a></td>
199+
<td><a href="">Chat</a></td>
200+
</tr>
201+
<tr>
202+
<td><b>WG-dev-tools-rustfmt</b></td>
203+
<td></td>
204+
<td><a href="">Learn more</a></td>
205+
<td><a href="">Chat</a></td>
206+
</tr>
207+
<tr>
208+
<td><b>WG-dev-tools-IntelliJ</b></td>
209+
<td></td>
210+
<td><a href="">Learn more</a></td>
211+
<td><a href="">Chat</a></td>
212+
</tr>
213+
<tr>
214+
<td><b>WG-dev-tools-rustup</b></td>
215+
<td></td>
216+
<td><a href="">Learn more</a></td>
217+
<td><a href="">Chat</a></td>
218+
</tr>
219+
<tr>
220+
<td><b>WG-dev-tools-clippy</b></td>
221+
<td></td>
222+
<td><a href="">Learn more</a></td>
223+
<td><a href="">Chat</a></td>
224+
</tr>
225+
<tr>
226+
<td><b>WG-dev-tools-bindgen</b></td>
227+
<td></td>
228+
<td><a href="">Learn more</a></td>
229+
<td><a href="">Chat</a></td>
230+
</tr>
231+
</table>
232+
233+
### Cargo team
234+
235+
<table>
236+
<tr>
237+
<td><b>WG-cargo-native</b></td>
238+
<td>Let's make native dependencies as painless as we can.</td>
239+
<td><a href="">Learn more</a></td>
240+
<td><a href="">Chat</a></td>
241+
</tr>
242+
<tr>
243+
<td><b>WG-cargo-registries</b></td>
244+
<td>Going beyond crates.io to support custom registries.</td>
245+
<td><a href="">Learn more</a></td>
246+
<td><a href="">Chat</a></td>
247+
</tr>
248+
<tr>
249+
<td><b>WG-cargo-pub-deps</b></td>
250+
<td></td>
251+
<td><a href="">Learn more</a></td>
252+
<td><a href="">Chat</a></td>
253+
</tr>
254+
<tr>
255+
<td><b>WG-cargo-integration</b></td>
256+
<td>How easy can we make it to use Cargo with your build system?</td>
257+
<td><a href="">Learn more</a></td>
258+
<td><a href="">Chat</a></td>
259+
</tr>
260+
</table>
261+
262+
### Infrastructure team
263+
264+
<table>
265+
<tr>
266+
<td><b>WG-infra-crates.io</b></td>
267+
<td></td>
268+
<td><a href="">Learn more</a></td>
269+
<td><a href="">Chat</a></td>
270+
</tr>
271+
<tr>
272+
<td><b>WG-infra-perf</b></td>
273+
<td></td>
274+
<td><a href="">Learn more</a></td>
275+
<td><a href="">Chat</a></td>
276+
</tr>
277+
<tr>
278+
<td><b>WG-infra-crater2</b></td>
279+
<td></td>
280+
<td><a href="">Learn more</a></td>
281+
<td><a href="">Chat</a></td>
282+
</tr>
283+
<tr>
284+
<td><b>WG-infra-secure</b></td>
285+
<td></td>
286+
<td><a href="">Learn more</a></td>
287+
<td><a href="">Chat</a></td>
288+
</tr>
289+
<tr>
290+
<td><b>WG-infra-host</b></td>
291+
<td></td>
292+
<td><a href="">Learn more</a></td>
293+
<td><a href="">Chat</a></td>
294+
</tr>
295+
<tr>
296+
<td><b>WG-infra-rustbuild</b></td>
297+
<td></td>
298+
<td><a href="">Learn more</a></td>
299+
<td><a href="">Chat</a></td>
300+
</tr>
301+
</table>
302+
303+
### Core team
304+
305+
<table>
306+
<tr>
307+
<td><b>WG-core-site</b></td>
308+
<td>The web site is getting overhauled; help shape the new content!</td>
309+
<td><a href="">Learn more</a></td>
310+
<td><a href="">Chat</a></td>
311+
</tr>
312+
</table>

0 commit comments

Comments
 (0)