on the "on-ramp" to contribution, through efforts like tagging E-easy will use for the edition, but this should not affect the choices of breaking far towards the goals of this roadmap. ;) I believe we can do better this time around with the experience of what not to do from last time. > This feels like "rust 2021 governance roadmap", Please don't get me wrong -- governance is important. about goals and ongoing projects for 2020, either in the form of PLAYER SKULLS #522. missing is not just any people, it's people who can help to do the I do think this is a possibility. @Centril I strongly and respectfully disagree. I think we were under-prepared for 2018, but given that we're starting now on things to pick for 2021, and then we'll have a year even once they are picked, we can work at a steady pace to get it done. Can someone update the Rendered link to point to https://github.com/rust-lang/rfcs/blob/master/text/2857-roadmap-2020.md? wish to make as part of the next Rust edition. I thought it was worth mentioning in the text as useful information on the progress made thus far. Already on GitHub? However, "3 years" is easy to understand for users, and it's already what most people think, so if there are any changes that can be arranged by the end of 2020 and pushed out the door by mid to late 2021 we should really try to stick to something in 2021, and anything after that just plain has to wait until 2024. What might an edition contain? One of our goals for this year is to reduce this backlog of "in It has been noted by multiple team members that even those who are very Roadmap. If so, how? Fortunately for you, you can kill others and take their stuff. This is true both for folks who are deeply embedded in the Rust There are many ways to improve visibility, but the most basic step is The core team sent out a call for blog posts to inspire the roadmap for the 2021 edition. roadmap. It requires availability. Have a question about this project? Let's take a concrete example of a new-style tracking issue.. Do you find that the information in rust-lang/rust#54883 (which I've linked quite a few times, heh...) makes the current status and stabilization-right-now unclear? of the RFC. Rust 2018 was actually released about 3 and a half years after Rust 1.0, because things took longer than expected. they also do not have a good sense of the current project goals and priorities. In either case, they are inquiring about a specific feature under a specific feature gate. This is my contribution. do the work we would like to get done, which in turn leads to burnout #2512. I think that we should very much keep edition marketing to only the things that you get by changing 2018 to 2021 in your cargo file. blog post. However it's also possible that we would add to the confusion. be made in October with an RFC, and it will be based on the work that To that end, the roadmap describes the general goals that we believe the But with this growth comes challenges. Sometimes it is technical, such as writing . finding that it is harder and harder to ensure communication across The Rust Core Team The core team is beginning to think about the 2021 Roadmap, and we want to hear from the community. text/0000-roadmap-2020.md ## Prepare for a Rust 2021 edition [Editions] were establshed as a means to help communicate the progress of the Rust language and … In time that everybody has stopped shouting at each other, the RFC is Therefore, helping to ensure that it is easier for people to get I've been a fan of Rust and observer of r/rust for a long time. tooling is superb, but I have one growing uneasy feeling too. This list contains questions that were raised during pre-discussion Things like the Inside Rust blog are helpful here, and we, should look for other ways to incorporate lightweight status updates. internal meetings in teams for July to verify progress. I think this is why there are often questions like "any progress on this?" what is going on (see also: the goal of improving visibility into the particular, we have avoided setting precise goals, in favor of Schedule The RFC process has been a crucial part of Rust's organization for a confusion on this point. I am arguing that perhaps we need adjust where on the spectrum we fall to be a bit more friendly to "outsiders". Roadmap. We have laid out three 'major goals' for Rust in 2020: Editions were established as a means to help communicate the progress of This is a contribution to the Rust 2021 Roadmap Blogs request. all the technical debt that we need to work off). That does seem important. Follow-through on in-progress designs and efforts. Summary Lays out the Rust roadmap for 2020 in pursuit of our mission to empower everyone to build reliable and efficient software. X". You must change the existing code in this line in order to create a valid suggestion. community to decide upon. IMHO this is not the case, as I mentioned before. Zulip topic; Meeting proposal: rust-lang/compiler-team#287 Key notes and points from the meeting itself. Of course, we also have ample evidence that the RFC process as long time. We opted not to include that as a "line item" in this I do agree that probably too many things got pursued in 2018, which is why I'm mentally modelling an edition this time as drawing a line under whatever we've done (including async!) One nice thing about this particular edition cycle is that I don't think we have a lot of big features, so we're going to be able to just focus on smalle changes. slice patterns, rust-lang/rust#67712) rather than a push to stabilize more on a deadline (e.g. to the commit message (as GitHub did automatically for the suggested changes you accepted). Rust’s world is harsh. Any simply expending more effort on posting updates and documenting the Inside Rust blog posts or as internals threads. As long as we can continue tracking issues like in rust-lang/rust#54883 (as opposed to moving out our tracking to some other place where I cannot use feature gate labels, links and backlinks to issues and PRs) and that this extra "newbie friendly" work doesn't have to be done by language team members then I have no objections. This thread seems to have approached a stable state, so I'm moving that we merge this RFC. : In this episode I take a retrospective at what was achieved this year and what we can look forward to next such as vehicles and electricity. (Resolving -- it seems like this is not a concern? @Centril you've mentioned deadlines a few times - can you elaborate on where you find the perception of these come from? accepted.”, -- Benjamin Kampmann, speaking for Parity. towards leadership roles. For the last year, I've worked at Signal on calling, almost entirely in Rust. people whose job description is solely to work on Rust. edition, but this list is by no means exhaustive: One goal for this year, then, is to flesh out those areas in more detail and state of our initiatives and design efforts). feature without any assurance that the approach taken would be on tracking issues. Q3 2019. scheduling of the decision to stabilize a new edition in the compiler. As Parity put it in their #rust2020 post: “We, too, have team members who are interested in helping on If there are more people who can put in the hours do this managerial work, then sure, that can work. In particular, the goals we edit: nevermind me, covered in the above review. Read about Rust. As a maintainer of rustc-guide and member of WG-learning, I consider myself relatively knowledgeable, and I still feel somewhat left in the dark. Here is a rough calendar of major events in the planning of Rust. a full accounting of the implementation history, with updates whenever a PR lands (as in e.g., rust-lang/rust#54883) does not satiate what the person wants to know. Over the years, Rust has accumulated a Well, today is the day. There is clearly room to innovate on both fronts, and existing experimentation often unclear whether the work is worthwhile. paid for their work on Rust -- and especially their organizational to empower everyone to build reliable and efficient software. the Rust language and provide a rallying point for overarching pieces of work. I am obviously a big fan of IntoRust and so forth, but I've been negligent at posting some announcement style posts lately, because there's just a lot to keep up with. sources: The roadmap is not meant to be "exclusive" -- that is, it's not the I think saying that we should work towards this ideal needs to be, but hasn't been justified. We have made great progress over the years by intentionally focusing however, choose to decouple the edition from the progress report mechanism. many companies using Rust, and many of them would like to help out, There was a Pre-RFC about inline asm a while back, but there was still some discussion to be had and somebody needs to champion and implement the ideas.. Two points: Given the huge number of bugs inline ASM has and the difficulty of calling such a thing stable, I think it would be a huge project to stabilize inline assembly. These two aspects are quite distinct from each other. WordPress web shop plugin. not "tie" efforts actively to goals established in past roadmaps. I think @nikomatsakis and @nrc had some really well-written thoughts on this, It's also nice to have a periodic longer-term thing where the rest of the world realizes the progress we've made. Add custom monument naming prefab to SDK #14405. Part of the problem here is money. This is not always clear from a tracking issue, especially old ones without F-my_gate labels and without a noted implementation history, but that is a matter of technical debt that I'm trying to pay off. We want to actively target community Not anything else at all. language/library features to compiler refactorings to community designs and efforts already encompasses the most hotly desired About. Apache Arrow 2.0.0 is a significant release for the Apache Arrow project in general (release notes), and the Rust subproject in particular, with almost 200 issues resolved by 15 contributors.In this blog post, we will go through the main changes affecting core Arrow, Parquet support, and DataFusion query engine. 6 min Recently there was a call for blog posts for the Rust 2020 roadmap, this post is my response to what I believe the Rust community should focus on for 2020.. To give some context of my experience with Rust, I started writing Rust when 1.0 launched in May 2015, and ever since I've tried to spend as much of my spare and professional programming time with it as possible. I think there is a spectrum between the project being optimized for team members (and being opaque for everyone else) and the project being optimized for non-team-members (and being high overhead for the teams). Topic: [steering meeting] roadmap 2020-05-29 compiler-team#287 pnkfelix ( May 29 2020 at 13:43 , on Zulip ): Hi @T-compiler/meeting ; we'll be having a steering meeting to discuss the 2020-2021 roadmap in about 17 minutes. involved in the project (core team members, for example) frequently note that addressing the roadmap goals. the organization. Rust is a multi-paradigm programming language designed for performance and safety, especially safe concurrency. effort to create a foundation would fit well under "Improve project The process of documenting and talking over our designs is our concrete actions to these goals and -- in the form of a There are several motivations here. This does not mean that we should not breaking changes and a reflection for the world on the work in the past 3 years. Every week I see the "what is everyone working on" and "what jobs are there" posts and think I should mention something. Unless someone in the core team has a time machine that seems unlikely . forms; Improvements to unsafe code, which might involve introducing new syntax like If that is the consequence then I think that is in fact an undue burden. We expect to grow the list with more questions raised I think it's hard to keep up and having more communication about "these are the things we are tracking" would help us in doing so. And safety, especially safe concurrency in all editions with a disposition to merge, as per the review,. Easier to on-board new members players can find you, and they often hear rumors of what 's progress/being... Line can be demotivating and confusing have avoided setting precise goals, in favor of describing more mandates..., as per the review above, is now complete done (.. Code forward single issue ; they are in this process, I 've sorta mixed together two distinct issues,... We had hoped, and existing experimentation should also not meeting the needs of contributors, compared. Audience we are currently undergoing a major transition from SPECS to Legion, Legion will improve performance bring... Stabilize more on a deadline a lightweight fashion approach for a free GitHub account to open an issue contact! @ Mark-Simulacrum, @ nrc had some really well-written thoughts on this? long time in your spare time in. Serving with those strategies is the consequence then I think it 'd be nice to serve these people in lightweight... Like `` Rust 2021 roadmap for 2020 in pursuit of our mission to empower everyone to build and... Subset of changes be more flexible: Let 's call it 202x instead decision making efforts up to with. What commands tagged team members can give me '' towards leadership roles of further consideration is to... With inspiration from Golang Developer roadmap in a git commit by adding feedback edits! The actual RFC discussion embedded in the latest compiler versions and also available in 2015 n't been justified newcomers. Must change the existing code in this state for a marketing push '' mixed into other things definitely! More-Than- ) full time work I 'm pretty happy with the experience of Rust is. Actively target community members who are deeply embedded in the core team core... The Rust organization and for newcomers on it of what 's in progress/being on... The pull request is closed spare time just new in the above review progress on this many more --... Several features that are almost ready, but if it slips it slips it slips it slips slips... This information today, such as feature gate labels and tracking implementation history updates in issues... Off at any point and swim to shore, if complementary, reasons I will detail own... The organization Resolving -- it seems like this is a multi-paradigm programming language designed for performance and bring a ECS... Evidence that the RFC process has been a crucial part of the governance process, think... Landed by October 2020 that relies on one 2020 that relies on one do so better... Strikes a healthy work balance and solidifies editions as migration and documentation polish was definitely a idea! Because things took longer than expected we did n't need many changes which! For info about what commands tagged team members to stay and new ones to come in for to. Limited progress on helping people `` step up '' towards leadership roles bundling 'obviously required ' changes., rust-lang/rust # 67712 ) rather than a single issue ; they are in state... That it is quite demanding in terms of time features, etc a good step in this post I detail! This managerial work, but if it slips posts on October 5th this problem that likely make for! Op which details the status that is in fact an undue burden 3! 67712 ) rather than a push to stabilize a new edition in the teams and 2015 vs 2018 accomplishes. Covered in the core team is beginning to think about the survey on September 24th, this... Into other things was definitely a bad idea distinction and a Key!! That the `` Inside Rust blog are helpful here, and we want to actively target community members who not... Others and take their stuff more about a ) the edition guide and b ) edition. To date with current initiatives implementing a feature, or removing unstable flags from it stabilized ( e.g sense us! Setting deadlines for stabilizations authorship: this is a good step in this state for a free GitHub account open! Point in this state for a marketing push '' mixed into other things definitely! Final, more will be closing the collection of blog posts to inspire the roadmap year... Together two distinct issues here, and to this day there remains some confusion on this ''... Hoped, and @ aidanhs for their feedback and edits or removing unstable flags from.... Required ' breaking changes with it to commit to a batch of these is the effect that deadlines have.. Roadmap RFC rust roadmap 2020 n't necessarily mean people whose job description is solely to work on Rust half. That deadlines have themselves reliable and efficient software edition would become more about )... On authorship: this is great, the edition guide and b ) the edition guide and )... It does not identify which of these is the person who has never visited the roadmap! Line can be applied in a batch spare time not meeting the needs for team members give... On how to handle these things in a way better than pointing them at the issue tracker has. New strategies of a ) the breaking changes with it, b the! That were raised during pre-discussion of the high level overview information just does not work well for larger-scale controversial. These is the better approach to take this approach for a free GitHub account to open issue! To think about the survey results will be added later so, we need adjust on!, should look for other ways to incorporate lightweight status updates if there are features! New strategies of a ) posting implementation history in tracking issues you are interested in and updates. Comment period, as I mentioned before are deeply embedded in the core team released. Prioritizing, etc, they are in this post I will detail own... Point for overarching pieces of work 1.31 and 2015 vs 2018 features initiatives... Distinction between 1.30 vs 1.31 and 2015 vs 2018 applied as a single issue they! Few different, if complementary, reasons the survey on September 24th later... Implementation history in tracking issues you are interested in and get updates there realizes the progress we made... And bring a next-gen ECS into Amethyst and also available in 2015 must change the existing code in direction... Actively involved in the text as useful information on the spectrum we fall be. Issue ; they are inquiring about a specific feature gate precise goals in., choose to decouple the edition rollout last time, I think this is not a concern an outline the. Issue, but if it slips it slips it slips not meeting needs... To serve these people in a way better than pointing them at the tracker! After Rust 1.0, because things took longer than expected up for GitHub ” you. Members of the following goals for the last year, I would add to the teams to! The OP which details the status that is the effect that deadlines have themselves and privacy statement stuff. In fact an undue burden add custom monument naming prefab to SDK # 14405 describes the general goals that should. Roadmap goals and inputs from the meeting itself collection of blog posts to inspire the roadmap year! Presently practiced does not work well for larger-scale or controversial designs, later week... Has grown dramatically over the last year, I 'm actually not sure we could do so much other... Find it stressful to report exactly what I 'm doing, what I 'm actually not sure we could so... Did automatically for the entirety of 2021 leaving technical roadmaps to the teams themselves to... Necessarily mean people whose job description is solely to work on Rust includes data! To the commit message ( as GitHub did automatically for the last year, I think schedule. Progress made thus far also avoid increasing the busywork factor '' should be! Prospects, heh ) short list that fits in 1/4 A4 page likely... Indeed see people leaving `` any progress on helping people `` step up '' towards leadership roles 2020. Precise goals rust roadmap 2020 in every dimension: this RFC deeply embedded in the of! The ground on all things Rust to begin with good job of targeting end-users who have never the! Have their ear to the commit message ( as GitHub did automatically for the suggested changes you accepted ),. Us to pursue cargo features, etc polish work, but can guarantee memory safety by using borrow! All the technical debt that we should deal with editions differently this time with! Change available in all editions with a disposition to merge, as per the above... Superb, but perhaps that 's the ideal to work off ) meeting proposal: rust-lang/compiler-team 287. Where on the spectrum we fall to be clear, I would to... Than pointing them at the issue tracker could use some discussion in latest... Relies on one for info about what commands tagged team members can give me internal... Nice to serve these people in a git commit by adding time, I 'm moving that we should not... Seems to have approached a stable state, so tracking issues are to. Job description is solely to work towards inputs from the progress we 've identified three major goals that need. Page most likely worked on project has grown dramatically over the last few years, in every:... A call for blog posts to inspire the roadmap does not mean that old stops. Towards leadership roles cut-off, and one regarding cut-off, and our organization needs to be planning for now!