Skip to content

Newsletter 30 - January 2022 #912

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
30 of 59 tasks
17cupsofcoffee opened this issue Feb 1, 2022 · 26 comments
Closed
30 of 59 tasks

Newsletter 30 - January 2022 #912

17cupsofcoffee opened this issue Feb 1, 2022 · 26 comments
Assignees

Comments

@17cupsofcoffee
Copy link
Collaborator

17cupsofcoffee commented Feb 1, 2022

Newsletter 30: January 2022

tags: newsletter

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

Another month has gone by, so it's time to put together the Rust Gamedev newsletter with January 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 8th of Feb. 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:

@Friz64
Copy link
Contributor

Friz64 commented Feb 1, 2022

I'd like to write about my erupt-bootstrap Vulkan init library.

@Bombfuse
Copy link
Contributor

Bombfuse commented Feb 1, 2022

Missed last month, but I can do an update on the release of Harvest Hero Origins! 👍

@CleanCut
Copy link
Contributor

CleanCut commented Feb 1, 2022

I'll do the section for Rusty Engine 4.0.

One observation about the top comment: The soft deadline for all section PRs is the 8th of Jan. -> a deadline in the future would probably be more effective. 😉

@17cupsofcoffee
Copy link
Collaborator Author

One observation about the top comment: The soft deadline for all section PRs is the 8th of Jan. -> a deadline in the future would probably be more effective. 😉

you saw nothing 🥷

(thanks for the heads up!)

@kunos
Copy link
Contributor

kunos commented Feb 1, 2022

Will do Hydrofoil Generation.

@Bromeon Bromeon mentioned this issue Feb 1, 2022
@JustinRyanH
Copy link
Contributor

Will do Refactoring from Legion to Bevy

@Bromeon
Copy link
Contributor

Bromeon commented Feb 1, 2022

Wrote godot-rust 🤖🦀
#913

@cart
Copy link
Contributor

cart commented Feb 1, 2022

I'll take bevy!

@james7132
Copy link
Contributor

I'll take bevy_backroll!

@r4gus
Copy link
Contributor

r4gus commented Feb 1, 2022

I'll take nodus

@CleanCut
Copy link
Contributor

CleanCut commented Feb 1, 2022

Rusty Engine 4.0 done in #914

@r4gus r4gus mentioned this issue Feb 1, 2022
@ramirezmike
Copy link
Contributor

I'll write about Not Snake!

@Im-Oab Im-Oab mentioned this issue Feb 2, 2022
@Im-Oab
Copy link
Contributor

Im-Oab commented Feb 2, 2022

I added the current development status of Flesh. #916

@alice-i-cecile
Copy link
Contributor

I'm not sure petitset is worth including right now; it's extremely specialized and only incidentally related to gamedev. I'll do a write-up for leafwing-input-manager though.

@ghost
Copy link

ghost commented Feb 2, 2022

I'd like to write about about my ezinput lib.

@zakarumych
Copy link
Contributor

I'll cover Edict

@zakarumych zakarumych mentioned this issue Feb 3, 2022
@cart cart mentioned this issue Feb 3, 2022
@17cupsofcoffee
Copy link
Collaborator Author

Reminder: the soft deadline for this month's newsletter is tomorrow!

If you'd like to write a section, please try to get the PR submitted in the next 24 hours if you can (or let us know if you need more time).

@johanhelsing
Copy link
Contributor

@17cupsofcoffee I'll be able to write short entries for bevy_smud and extreme_bevy in a couple of hours if it's not too late.

johanhelsing added a commit to johanhelsing/rust-gamedev.github.io that referenced this issue Feb 8, 2022
johanhelsing added a commit to johanhelsing/rust-gamedev.github.io that referenced this issue Feb 8, 2022
johanhelsing added a commit to johanhelsing/rust-gamedev.github.io that referenced this issue Feb 8, 2022
@17cupsofcoffee
Copy link
Collaborator Author

The release PR is now up for everyone to review: #941

@Keavon
Copy link
Contributor

Keavon commented Feb 8, 2022

Planning to submit the PR tonight announcing Graphite's imminent alpha release.

@17cupsofcoffee
Copy link
Collaborator Author

@Keavon Sorry, I hit merge on the release PR before seeing this 😩

How soon do you think you'll be able to submit your PR? I can hold off on the announcements if it's coming soon, but I'd really like to get stuff done before it gets too late in my timezone.

@17cupsofcoffee
Copy link
Collaborator Author

I've reverted the release for now.

@Keavon
Copy link
Contributor

Keavon commented Feb 8, 2022

Ah, sorry to hold you up, didn't mean to cause you trouble. These time zones are hard to think through (it's only 3 PM here in the US-Pacific, on the 8th).

I am working on writing it now so I expect it will take an hour or two (the length limit makes it kinda slow to write). I'll do my best to be quick with it!

@17cupsofcoffee
Copy link
Collaborator Author

@Keavon: No problem - I may have to leave the release till tomorrow in that case, as it's nearly midnight where I am and it'll take me a bit of time to do the social media posts that go with it.

@17cupsofcoffee
Copy link
Collaborator Author

Right, let's try that again 😄

The release PR is back up for review: #944

Planning to get this merged at around 9PM GMT (three and a half hours from now), assuming no issues found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests