-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Update 2022-02-16-this-week-in-rust.md (#1) #2941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
* Update 2022-02-16-this-week-in-rust.md * Update 2022-02-16-this-week-in-rust.md
There are TWiR editors who already monitor most of the popular Rust sites (HN, Reddit, etc.) so there's no need for you to submit PRs for every link you come across. These add to the editor workload because we need to merge commits that contain things we're already adding. If you come across a good link that's not already widely distributed, great! But most of these were already being tracked by the community editors. |
Hi @ericseppanen. If you could provide documented guidance for which URLs are being monitored it would be helpful otherwise I don't see how I can distinguish what is contribution worthy content without potentially missing at least some relevant articles each week... Alternatively, if the prior PRs editing the weekly draft could be merged at a cadence faster than weekly at least the draft might then be used as a point in time reference to what has already been widely distributed. Thanks! |
The things editors monitor is a moving target (and not every link from upstream sources is accepted), but it's safe to assume that if it's from a current or former Rust team member or gets posted to Reddit or HN, we'll see it. |
Hello all - The responsibility for the weekly cadence of merging pull requests (rather than reviewing and merging them as I come in) is on me. I'm realizing now that, with the volume that we receive, I've been making myself a bottleneck and it's been adding additional work to others. This is something that will be changing in the near future - my fellow editors will also be able to review and merge PRs. This should cut down on the review time and the merge conflicts. |
That said, @kw-fn, could you resolve the merge conflicts in this pull request? And it looks like this may be re-adding some links that were also added in just merged pull requests and those will need to be cleaned up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After rebasing with master and removing the duplicates, it looks like the only two new articles are:
While the Performance Tools link is fine, the Glean one, as noted in the in line comments, does not have enough Rust content in it to include. Please remove the Glean one, and then I would be happy to merge this with the Performance tools link in it.
* [rsadsb: v0.5.0 Release](https://rsadsb.github.io/v0.5.0.html) | ||
* [SixtyFPS becomes Slint](https://slint-ui.com/blog/sixtyfps-becomes-slint.html) | ||
* [This week in Fluvio #22: the programmable streaming platform](https://www.fluvio.io/news/this-week-in-fluvio-0022/) | ||
* [This week in Glean](https://blog.mozilla.org/data/2022/02/09/this-week-in-glean-migrating-legacy-telemetry-collections-to-glean/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I recognize this project may have parts written in Rust, there's not enough Rust content in the newsletter to include this link.
No description provided.