-
Notifications
You must be signed in to change notification settings - Fork 343
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
Newsletter 27 - October 2021 #818
Comments
We should be able to remove the section about the Rust Graphics Meetup, since although it happened in October, we already discussed it in the September newsletter (unless @kvark has any new plans 👍) |
I'll make an entry about https://github.com/Vrixyz/graph_nav |
@AngelOnFira Ah, I added it because I thought it was a monthly thing - if not, I'll remove it :) |
heya, I'd love to write about Blue Engine, however not much changed this month due to exams. next month and a half is expected to be spent towards exam too. Thanks! |
Will take the Hydrofoil Generation Sailing part. |
I'll pick up rend3 |
Picking LD49 LibraCity via #822, thanks! |
Since you asked me, I wrote a section on All is Cubes in #823. |
I'll introduce bevy_pen_tool.
Eliot
…On Sun, Oct 31, 2021 at 12:19 PM Joe Clay ***@***.***> wrote:
Newsletter 27: October 2021 tags: newsletter
*Editors*: @17cupsofcoffee <https://github.com/17cupsofcoffee>, @ozkriff
<https://github.com/ozkriff>, and @AngelOnFira
<https://github.com/AngelOnFira>
Another month has gone by, so it's time to put together the Rust Gamedev
newsletter for October!
If you want to help writing the newsletter:
- *Please read CONTRIBUTING.md
<https://github.com/rust-gamedev/rust-gamedev.github.io/blob/source/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* ***@***.***
<https://github.com/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
<https://spec.commonmark.org/0.29/#soft-line-breaks>) 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: #336
<#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
<https://github.com/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 *6th of November*. PRs will
usually be accepted as long as they are ready before the newsletter's
release, but the earlier the better :)
------------------------------
|
Picking Soldank and hecs_rapier |
I'll take The Process |
Hey I can write about Crunda :) |
Just sending out a ping in case you haven't seen this issue yet! (Sorry if you're already working on it 😅) This month's "soft" deadline is the 6th 📆 @darthdeus @thebracket @tom-leys @not-fl3 @Bombfuse @NiklasEi @yopox @xlambein @necauqua @TanTanDev @tomaskralcz @ManevilleF @JonahPlusPlus @LPGhatguy @LechintanTudor @emilk @Shfty |
I'll take Sparsey :) |
keep getting busy and forgetting, but I can throw a small snippet together for Berry Run tonight |
I'd like to add a section for the game I've been working on, PaddlePunks. |
ggez 0.6.1 and gwg 0.3.0 were already covered in last months issue, so they can be removed from the list |
Last call for sections! I will be posting the final PR later today. |
I will pick up Amethyst, the gamedev mini symposium, and the meeting minutes/discussions section. |
The release PR is now up at #846 - everyone is invited to review 🙂 Aiming to publish the newsletter later this evening all being well. |
Newsletter 27: October 2021
tags:
newsletter
Editors: @17cupsofcoffee, @ozkriff, and @AngelOnFira
Another month has gone by, so it's time to put together the Rust Gamedev newsletter for October!
If you want to help writing the newsletter:
source
branch (example: N15: A/B Street #336)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:
Current Schedule
The soft deadline for all section PRs is the 6th of November. PRs will usually be accepted as long as they are ready before the newsletter's release, but the earlier the better :)
Please use these templates as a starting point:
Games/apps/libraries:
Articles/blog posts/videos/etc:
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!
Rust Graphics Meetup(already covered last month)GGEZ 0.6.1 and good-web-game 0.3.0 (1)covered last monthFinal steps:
The text was updated successfully, but these errors were encountered: