-
Notifications
You must be signed in to change notification settings - Fork 343
Newsletter 42: Jan 2023 #1267
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
Comments
Hi, I'm the author of rustysynth. I found out about this newsletter through a GitHub notification that my name was included in this issue. Would it be possible for me to write a description of rustysynth? |
@sinshu of course, we would appreciate a PR! Here are our contributing guidelines but don't worry about them too much, we'll fix all the style/formatting issues during the PRs review. :) |
I'll comment on |
I'll take Idu |
Yeah I'll write something up on tween. I'm also working on a library called |
hope its not too late, I'll take miniquad update! |
I'll take Cargo Space and Matchbox. Cargo space is nearly done, matchbox hopefully within a day. |
Is the newsletter a good place for this article I wrote? https://indiedevcasts.com/posts/ecs-introduction . If yes, should I put it in other news? |
@theredfish yes! I've added to the "Learning Material Updates" group - feel free to send a PR with a full section! |
Thanks @ozkriff I will send it soon ! |
Hi! I'm the developer for Petrichor64. I'm not sure how you figured out my github when the repo is currently private, good sleuthing! I would like to write an article but I'm slammed with dayjob/parent stuff this month. The rust side of project is also unfortunately closed source at this time, so the coding/api layer is entirely in lua. For this reason Im not sure the project belongs here or not, but I'd love to give some insight or tips with wgpu or something next time! |
@Auxnon sorry, I've just googled your Twitter nickname, nothing sketchy :D As for Petrichor64, it definitely belongs to the newsletter - feel free to submit your updates and articles when you're ready |
Newsletter 42: Jan 2023
tags:
newsletter
Editors: @AngelOnFira, @ozkriff
Another month has gone by, so it's time to put together the Rust Gamedev newsletter with TODO's news!
Current Schedule
The soft deadline for all section PRs is 10 Feb 2023.
We may still accept PRs that are submitted later than this, as long as they're ready before the newsletter's release, but this isn't guaranteed. If you want your section to be included, don't leave it till the last minute!
How to Contribute
If you want to help writing the newsletter:
source
branch (example: N15: A/B Street #336).Style Guidelines
The full style guide is in CONTRIBUTING.md, but here are the most important rules:
Please use these templates as a starting point:
Games/apps/libraries:
Articles/blog posts/videos/etc:
Current Structure & Status
Below is our current planned structure for the newsletter, and the status of each PR (which we'll try to keep updated).
This is not an exhaustive list - if you have your own project that you want to write about, just make a comment on this issue and open a PR!
Rust Gamedev Meetup
Game Updates
Learning Material Updates
Engine Updates
Tooling Updates
Library Updates
Other News
Discussions
Publishing Steps
The text was updated successfully, but these errors were encountered: