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.
To propose content for inclusion in the next newsletter (found in the
folder), create a new Pull Request updating the relevant section in the
Alternately, tweet us @thisweekinrust.
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:
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.
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.
Some prefixes are used, and should be placed to the left of the link.
[audio]for podcasts or other audio.
[series]for articles that are one of a series.
[FR]) for content in a language other than English.
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.
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:
Use the included
Ensure you have SASS installed. The easiest way to get it is via
Ruby package manager.
env SASS_BIN=$HOME/.gem/ruby/*/bin/sass pelican content -s pelicanconf.py
TWIR_NEWSLETTER_THEME=1 pelican --delete-output-directory content