Skip to content

Newsletter 20 #531

Closed
Closed
@ozkriff

Description

@ozkriff

Feel free to suggest sections about any March rust gamedev news and updates!

If you want to help writing the newsletter:

  • Grab some of the "🆓 free" sections by leaving a comment like "I'd like to work on {section_name_1} and {section_name_2}".
  • Mentions in brackets (like "🆓 free (@ozkriff?)") are just an invitation to write the corresponding section if you want, but anyone is free to take it.
  • Write a short overview:
    • Use provided links as a starting point.
    • Try to maintain a consistent style with the rest of the newsletter and run markdownlint, please.
    • Insert line breaks (softbreak) at 80 chars, please.
    • DM me on Discord or Telegram if there're any questions.
  • Send a PR to the source branch (example: N15: A/B Street #336)
    • Mention this issue in your PR's description to link it all together.

Quoting @AngelOnFira from the last month's coordination issue:

<...>
We're going to be transitioning to having authors or volunteers write about their own content, rather than the editing team doing it all at the end 100 This means if you want to see your work in the newsletter, you have to write it yourself! If you're not able to write about your work, feel free to comment and I can assign it free free. We're working on taking some of the load off the editing team where we can with this. Best to keep this sustainable!

Also, we want to make sure contributing to the newsletter feels open to anyone who wants to write a section about their project. If you have anything you can write about, just add a comment to this issue and I'll add it to the todo list smile


Current Schedule

The soft deadline for all section PRs is 2021.04.06.
Review and Release will take place on 2021.04~~.08~~ .09 .10.


⚠️ It was decided to try a shorter and more limited section format: ⚠️

  • Only one image (<300kb) or GIF (<2.5mb) before the text. With an optional caption and a mandatory alt text.

  • All the (rendered) text should be under 1000 characters (including spaces and punctuation) and under 6 paragraphs (without any subsections, etc).

  • No bold/italic/etc formatting - only links and one plain list without nesting per section (multiple lists are allowed if your project consists of multiple parts that aren't independent enough for their own sections).

  • Third-person perspective.

  • 80 chars per MD line and no other markdownlint warnings on CI.

  • Only the following simple templates are allowed:

    See the templates

    For games/apps/libs:

    ### [Gamename]
    
    ![alt text](img)
    _optional image label_
    
    [Gamename] ([GitHub], [Discord], [Twitter]) by [@nickname]
    is ... {short project description in one sentence}.
    
    {An overview of the recent updates with links to more details}.
    
    _Discussions: [/r/rust_gamedev](link), [Twiter](link), [etc](link)_
    
    {md links block}

    For articles/videos/etc:

    ### [Articlename]
    
    ![alt text](img)
    _optional image label_
    
    [@nickname] published an [article] about ...
    {overview what the resource is about}.
    
    _Discussions: [/r/rust_gamedev](link), [Twiter](link), [etc](link)_
    
    {md links block}

CONTRIBUTING.md isn't updated for this yet.

Current Structure & Status

If you have your own project that you want to write about, just make a comment on this issue!

(I'll try to keep this updated)

Final steps:

  • final review - by everyone
  • publish - by @ozkriff
  • post on /r/rust, /r/rust_gamedv, /r/gamedev, URLO, twitter.com/rust_gamedev - by @ozkriff
  • add comment links - by @ozkriff
  • add a draft of the 21th newsletter - by @ozkriff

Editors: @ozkriff @17cupsofcoffee @AngelOnFira

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions