Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Newsletter 23 #677

Copy link
Copy link
Closed
Closed
Copy link
@ozkriff

Description

@ozkriff
Issue body actions

Newsletter 26: September 2021

Editors: @ozkriff, @AngelOnFira, and @17cupsofcoffee

Another month has gone by, so it's time to put together the Rust Gamedev newsletter with September news!

If you want to help writing the newsletter:

  • Read CONTRIBUTING.md.
  • Grab some of the "🆓 free" sections by leaving a comment like "I'd like to work on {section_name_1} and {section_name_2}".
    • The links in brackets (like "1, 2, 3") are suggestions of links to include in the section. Feel free to add more!
    • Mentions in brackets (like "🆓 free (@ozkriff?)") are just a suggestion of who could pick the work up - it's not an obligation, and other people are welcome to take those sections.
    • Extra sections not listed in the plan are welcomed - just leave a comment and open a PR!
  • 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 (lint errors will fail the CI build).
    • Insert line breaks (softbreak) at 80 chars, please.
    • Leave a comment or DM me on Discord if you have any issues.
  • 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.

As with the last few newsletters, we're trying to delegate the writing workload where we can - to quote @AngelOnFira from a few months ago:

We're also 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 💯 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. 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 😄


Current Schedule

The soft deadline for all section PRs is the 5th of October. PRs will usually be accepted as long as they are ready before the newsletter's release, but the earlier the better :)


⚠️ The most important formatting/style rules from CONTRIBUTING.md:

  • Only one image (<300kb) or GIF (<2.5mb) before the text, with an optional caption and mandatory alt text for accessibility.
  • 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 characters per line and no other markdownlint warnings on CI.

Please use these templates as a starting point:

Games/apps/libraries:

### [Game name]

![alt text](img)
_optional image label_

[Game name] ([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), [Twitter](link), [etc](link)_

[Game name]: http://example.com

Articles/blog posts/videos/etc:

### [Article name]

![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)_

[Article name]: http://example.com

Current Structure & Status

Below is a list of our current planned structure for the newsletter, and the status of each PR (which we'll try to keep updated).

This is not an exhastive list - if you have your own project that you want to write about, just make a comment on this issue and open a PR!

Final steps:

  • Final review - by everyone
  • Publish - by @ozkriff
  • Post on /r/rust, /r/rust_gamedev, /r/gamedev, URLO, twitter.com/rust_gamedev - by @ozkriff
  • Add comment links - by @ozkriff
  • Add a draft of the 27th newsletter - by @ozkriff

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.