Home

Awesome

This Week in Rust

Content for this-week-in-rust.org. Made available under CC-BY-SA.

All code Copyright 2014 Ember Arlynx, made available under the MIT license.

TWiR Editors

Language Reviewers

PRs for next issue are now being accepted

To propose content for inclusion in the next newsletter (found in the drafts/ folder), create a new Pull Request updating the relevant section in the draft.

Alternately, tweet us @thisweekinrust.

What do we look for when considering whether to include something in This Week in Rust?

This Week in Rust is intended to highlight the incredible work of the Rust Community.

What we are generally looking for includes:

What we are generally NOT looking for includes:

Projects/Tooling Updates

There are further guidelines for the Projects/Tooling Updates Section

We include:

We do not include:

Notes:

These are meant to be guidelines, if you are ever not sure about whether something should be included please feel free to open a pull request anyway and we can discuss it!

The editors of This Week in Rust do reserve the right to make the decision about whether to include something or not, but we intend to do so in a way that is as transparent as possible.

Link style guidelines:

The link text should be the same as the page's title. If the title seems to need additional context (for example, if the title is "What's New" and should have the project name added), please ask in the PR comments.

Links should use the most canonical form. For example, if example.tech redirects to www.example.com, then the latter is preferred.

Links should not contain unnecessary tracking parameters, e.g. utm_source, utm_campaign.

Some prefixes are used, and should be placed to the left of the link.

Community sub-categories

Editors will sort community links into sub-categories. The following sub-categories are currently used:

Most blog posts about Rust belong in Rust Walkthroughs if they show how something is done (including source code), otherwise Observations/Thoughts. Articles that don't contain much Rust content, or news articles that mention Rust, won't always be accepted, but when they are they can be placed in the Miscellaneous sub-category.

If a set of related links is published (e.g. from a large Rust conference), the editors may choose to invent a new category just for that issue.

Call for Participation guidelines

The Call for Participation section covers both projects looking for contributors and events recruiting speakers.

CFP - Projects

The project section will include good issues for someone looking to get into Rust, or for someone who wants to find a new project to contribute to. Guidelines:

CFP - Events

The CFP events section will include CFP links for events that either heavily feature Rust content, or have a specific Rust track. It's not appropriate for general tech conferences, unless there is a large enough coding or Rust section to appeal to the TWiR audience.

Generally speaking (excepting the rolling 30 day window), if it would be listed in the Events section of TWiR, it will be right for this section as well.

Publishing

The editors have a detailed guide for publishing that is stored elsewhere, but this content is retained here as well.

How I get PR lists:

git log --author=bors --since='MM/DD/YYYY 12:00PM' --until='MM/DD/YYYY 12:00PM' --pretty=oneline > ~/entropy/twir.txt

edit in vim to get rid of everything but PR number, copy into clipboard

for pr in $(xsel -ob); do firefox https://github.com/mozilla/rust/pull/$pr; sleep 0.07; done

wait a long time... write TWIR

Alternatively use GitHub search:

https://github.com/rust-lang/rust/pulls?q=is%3Apr+is%3Amerged+updated%3A2014-11-03..2014-11-10

How I get new contributors:

Use the included new_contribs.sh script:

new_contribs.sh 6/21/2014

Building

To ensure consistency across development setups, we use a Docker container-based workflow for building the website and email newsletter. Similarly, we use a makefile to Ensure you have Docker installed on your system if you intend to build the website or email newsletter.

Building the website

Before attempting to build the website, ensure Docker is in a running state on your system.

Note: If looking to test the website's search functionality locally, you will need to adjust the TESTING_LOCALLY variable to True.

Building the newsletter

Before attempting to build the email newsletter, ensure Docker is in a running state on your system.