@@ -4,20 +4,25 @@ date = 2024-05-02
44transparent = true
55+++
66
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
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 a while. The reason was mostly maintainer burnout, which is
11+ also why the newsletter of August 2023 was not published [ until a few days
1012ago] [ august-news ] .
1113
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.
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+ You can read more about the changes being made in [ this blog
20+ post] [ newsletter-changes-blog ] .
1621
1722### Schedule Changes
1823
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:
24+ Thierry Berger ([ @Vrixyz ] ), has come up with a new [ monthly
25+ schedule] [ monthly_schedule ] that we will try out:
2126
2227- 3rd of the month: Newsletter starts. A call for submissions is made on social
2328media and community Discord servers interested in receiving it. At the same
@@ -37,26 +42,26 @@ schedule.
3742### Community Survey
3843
3944This 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** .
45+ We've got some community feedback on the [ Rust GameDev Discord] [ Discord ] already
46+ and would like to hear more from you. It would be great if you could fill out
47+ [ this survey] [ survey ] to let us know how we can improve the newsletter going
48+ forward. The survey closes on the ** 28th of May 2024** . We will be evaluating
49+ the [ survey] results in an upcoming blog post, so stay tuned for that.
4450
4551### Future Steps
4652
4753Based on feedback we've already gotten, the steps for next months are:
54+
4855- Add an email subscription option to the newsletter
4956- Setup a system for how to edit entries that are not ready before the
5057newsletter ships. We are currently looking into either hiring a part-time
5158editor, using generative AI to add a few sentences where needed, or simply
5259removing these entries.
5360
54- Additionally, we will be evaluating the [ survey] results in the next newsletter,
55- so stay tuned for that.
56-
5761That's all for now. Have fun reading!
5862
5963[ august-news ] : https://gamedev.rs/news/049/
64+ [ newsletter-changes-blog ] : https://gamedev.rs/blog/newsletter-changes/
6065[ @janhohenheim ] : https://github.com/janhohenheim
6166[ @Vrixyz ] : https://github.com/Vrixyz
6267[ monthly_schedule ] : https://github.com/rust-gamedev/rust-gamedev.github.io/issues/1417#issuecomment-1764534286
0 commit comments