Skip to content

Commit 661ee0b

Browse files
Add newsletter changes blog post (#1502)
Co-authored-by: Jan Hohenheim <[email protected]>
1 parent d65056b commit 661ee0b

File tree

1 file changed

+65
-0
lines changed

1 file changed

+65
-0
lines changed

Diff for: content/blog/newsletter-changes/index.md

+65
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
+++
2+
title = "Newsletter Changes"
3+
date = 2024-05-02
4+
transparent = true
5+
+++
6+
7+
*Please fill out [this survey][survey] before skipping this section! More info below!*
8+
9+
Hey everyone, it's been a while! As you've certainly noticed, the newsletter has
10+
been on hiatus for some months. The reason was mostly maintainer burnout, which is
11+
also why the newsletter of August 2023 was not published [until a few days
12+
ago][august-news].
13+
14+
We're back now though! A couple of community members, Jan Hohenheim
15+
([@janhohenheim]) and Thierry Berger ([@Vrixyz]), have led the revival of the
16+
newsletter. This includes making changes requested by the community, and
17+
improving sustainability for the long term.
18+
19+
### Schedule Changes
20+
21+
Thierry Berger ([@Vrixyz]), has come up with a new [monthly
22+
schedule][monthly_schedule] that we will try out:
23+
24+
- 3rd of the month: Newsletter starts. A call for submissions is made on social
25+
media and community Discord servers interested in receiving it. At the same
26+
time, last month's newsletter is published.
27+
- 3rd to 28th of the month: submissions are collected and the newsletter is
28+
written.
29+
- 28th of the month: Submissions are closed. New submissions go into the next
30+
month's newsletter.
31+
- 3rd of the next month: The newsletter is published. Any submissions not edited
32+
in time will be moved to the next month or removed entirely.
33+
34+
This more strict schedule should help with the issue of late entries and reduce
35+
the pressure of editing by having a dedicated time for it with no incoming
36+
submissions. The goal is to be more consistent and reliable in our publishing
37+
schedule.
38+
39+
### Community Survey
40+
41+
This restructuring is also a good time to improve the content of the newsletter.
42+
We've got some community feedback on the [Rust GameDev Discord][Discord] already
43+
and would like to hear more from you. It would be great if you could fill out
44+
[this survey][survey] to let us know how we can improve the newsletter going
45+
forward. The survey closes on the **28th of May 2024**. We will be evaluating
46+
the [survey] results in an upcoming blog post, so stay tuned for that.
47+
48+
### Future Steps
49+
50+
Based on feedback we've already gotten, the steps for next months are:
51+
52+
- Add an email subscription option to the newsletter
53+
- Setup a system for how to edit entries that are not ready before the
54+
newsletter ships. We are currently looking into either hiring a part-time
55+
editor, using generative AI to add a few sentences where needed, or simply
56+
removing these entries.
57+
58+
That's all for now. Have fun reading!
59+
60+
[august-news]: https://gamedev.rs/news/049/
61+
[@janhohenheim]: https://github.com/janhohenheim
62+
[@Vrixyz]: https://github.com/Vrixyz
63+
[monthly_schedule]: https://github.com/rust-gamedev/rust-gamedev.github.io/issues/1417#issuecomment-1764534286
64+
[survey]: https://forms.gle/oeSb46twWsxRKYJe7
65+
[Discord]: https://discord.gg/game-development-in-rust-676678179678715904

0 commit comments

Comments
 (0)