Skip to content

Commit aaa90cd

Browse files
committed
Add newsletter changes blog post
1 parent d65056b commit aaa90cd

File tree

1 file changed

+64
-0
lines changed

1 file changed

+64
-0
lines changed

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

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

0 commit comments

Comments
 (0)