Open-source project
rust-lang/this-week-in-rust avatar
rust-lang/this-week-in-rust

This Week in Rust's biggest section now comes from a forum instead of pull requests

Data for this-week-in-rust.org

2,661 stars1,726 forksPythonLicense varies

At a glance

What is it?
rust-lang/this-week-in-rust is the content and the publishing pipeline for a weekly Rust newsletter: a draft folder per issue that contributors edit through pull requests, a static site generator with themes and plugins, and feeds. Three things on the page are more interesting than the roundup itself. The project and tooling updates section has closed to pull requests and is now sourced from posts on a named forum, with contributors asked to follow that forum's rules. The project has a written policy on articles written with a language model, which argues about authorship rather than tooling. And the link rules are specific enough to ban tracking parameters by name.
Who is it for?
Submit to this newsletter if you have written something about Rust that teaches rather than announces, because that is the filter the criteria describe, and it is stricter than it first looks. Three things to know before you open a pull request.
Can I use it commercially?
Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly Python, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • rust-lang/this-week-in-rust2,661 ★ · +17
Star history
Repository2026-10-042026-11-15
rust-lang/this-week-in-rust2.6k2.7k

17 Stars in the last 42 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two licences in a single sentence

The second line of the readme splits the project in half. The written content is made available under a creative commons share alike licence, and all code is under the MIT licence, with the code attributed to a named person and a 2014 copyright. Two licences in one project is common for a site with its own content, but the split here is drawn explicitly and in one sentence, which is more than most projects manage. What is missing is any of this reaching the repository metadata, which records no licence at all. So a tool scanning the repository for terms finds nothing, and a person reading the readme finds two. Anyone vendoring the site generator or the plugins needs to know which half they are taking, and the readme is the only place that says.

The project updates section now comes from a forum

One section has changed shape. The page states that pull request submissions for the project and tooling updates section are no longer accepted, links to an issue for the detail, and then explains the replacement: editors monitor a named forum and will consider links posted there. Contributors are asked to follow that forum's own community rules when they post. The practical effect is that the largest and most contested section of a weekly roundup has moved its intake from the newsletter's own review to a public forum's feed, which means the newsletter's judgement about what counts as more informative than a changelog is now applied second hand, to posts somebody else approved. It also means a project announcement can reach the newsletter without anybody here ever reading a pull request about it.

The language model policy argues about authorship, not tooling

There is a section headed with the subject rather than tucked into the rejection list, and it starts by saying the project takes no position on whether you use these tools. Then it says what it does care about, which is whether the article was written by people. The reasons given are worth quoting in order, because none of them is about quality of output in the abstract. Truthfulness may be compromised. More importantly there is no community growth: no author to learn from feedback, and no peer for the reader to connect with. The ask is correspondingly narrow: if you submit something written this way, disclose it in the article. For a newsletter whose value is a human reading a human, that is a defensible line, and it is a more interesting position than either a blanket ban or silence.

Four of the five rejection rules are about other people

The rejection list is short and one entry dominates it. Anything violating the community code of conduct is out. So is anything degrading to any part or member of the community, and the sentence that follows is the whole editorial philosophy in one line: rather than an article about what is wrong with something, they would much rather you wrote something explaining how you would make it better. The remaining three are procedural: no duplicates of recent posts even with reworded wording, nothing behind a paywall, and nothing that requires an email address or similar to be shared in order to read it. Two of those three exist to protect readers from a link, which is the same instinct as the anti-tracking rule below.

Link rules ban tracking parameters by name

There is a short style guide that goes further than most editorial guidelines go. The link text should be the title of the page, and if the title needs context added, you should ask in the pull request comments rather than adding it silently. Links should use the most canonical form, with the rule that a site which redirects to another host should be linked by the host it redirects to. And links should not carry unnecessary tracking parameters, with two named as examples. Then there is a prefix convention: a tag for videos, one for audio, one for a series, and a two letter language code for anything not in English. So a link is expected to be clean, canonical and annotated, which is a small amount of work per link and a large amount of work across an issue.

Eight buckets and a default rule for deciding between two of them

Editors sort the community links into sub-categories, and the list names eight of them, from official team communications and foundation news through project updates, newsletters, research, observations, walkthroughs and a miscellaneous bucket. Each has a definition, and the project updates entry is the strictest, requiring something more informative than a changelog. Then a default rule resolves the case that actually comes up: most blog posts about Rust belong in the walkthroughs bucket if they show how something is done, including source code, and in the observations bucket otherwise. Articles with little Rust content are not always accepted, but if they are they land in miscellaneous. And editors may create a new category for one issue when a large conference produces a batch of related links.

Eleven editors, five language reviewers, and a tweet as a second door

The masthead lists eleven current editors, five language reviewers covering Japanese, Spanish, Portuguese and Chinese, and eight alumni editors. That is a substantial volunteer structure for a weekly, and the language reviewers in particular are the part that explains how a roundup with non-English links in it gets produced. The submission process has two doors, and they do not match each other in tone. One section says pull requests for the next issue are being accepted, tells you to edit the relevant section of the draft in the folder named for it, and points at a pull request. Three lines later the page says you can alternatively send a tweet instead. The draft-and-pull-request route has the documentation behind it; the other one does not. The pipeline that turns a merged draft into an issue is pinned to nine exact versions, so a site rebuild is reproducible, and the components are recognisable: a static site generator, its asset pipeline and search plugins, a templating engine, a Markdown library, a Sass compiler, a feed generator, a minifier and a templating safety library. There is also a script whose name suggests adding contributors, and separate directories for the published site, the themes and the tools.

Editorial conclusion

Submit to this newsletter if you have written something about Rust that teaches rather than announces, because that is the filter the criteria describe, and it is stricter than it first looks. Three things to know before you open a pull request. One whole section no longer accepts submissions and is sourced from a forum, so a project announcement posted there may be picked up while the same link submitted here is not. Link hygiene is enforced, including a rule against carrying tracking parameters. And if a language model was involved in writing the piece, the page asks for that to be disclosed, which is a smaller ask than a ban and a larger one than silence. Read the rejection list before you write, because four of its five items are about how you treat other people rather than what you built.

Frequently asked questions

What is this-week-in-rust?

The content and the publishing pipeline for a weekly Rust community newsletter: a draft folder per issue that contributors edit through pull requests, plus the static site generator, themes, plugins and feeds that turn a draft into the site.

Can I submit a project update to This Week in Rust?

Not through pull requests any more. The page says submissions for the project and tooling updates section are closed, that editors now monitor a named forum and will consider links posted there, and that contributors must follow that forum's own community rules.

Does This Week in Rust accept articles written with a language model?

It takes no position on the tools and asks that the authorship be disclosed in the article. Its stated reasons are that truthfulness may be compromised, and that there is no author to learn from feedback and no peer for the reader to connect with.

What does This Week in Rust refuse to publish?

Content that breaks the community code of conduct, rants or anything degrading to the community, duplicates of recent posts, anything behind a paywall, and anything that requires an email address or similar to be given in order to read it.

What license is this-week-in-rust under?

Two, as stated at the top of the page: the written content under a creative commons share alike licence and the code under the MIT licence, with the code attributed to a named person and a 2014 copyright. The repository's own metadata records no licence.

How are community links sorted in This Week in Rust?

Editors sort them into eight sub-categories, from official announcements through foundation news, project updates, newsletters, research, observations, walkthroughs and a miscellaneous bucket, with a default rule that most blog posts go under walkthroughs when they show how something is done.

Official sources

  1. Issues
  2. Project website
  3. README
  4. rust-lang/this-week-in-rust on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/rust-lang-this-week-in-rust.svg)](https://hysenlabs.com/projects/rust-lang-this-week-in-rust)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/rust-lang-this-week-in-rust.svg)](https://hysenlabs.com/projects/rust-lang-this-week-in-rust)

Was this useful?