Closed ozkriff closed 4 years ago
Really like this format 😄 Hopefully it gets more people helping out.
I'll pick up writing the section for Lonely Star, if that's okay?
I'll be doing Veloren, and I'll take some others,
Antorum finished
Taking Akigi
I'd like to add a section about everpuzzle https://github.com/Skytrias/everpuzzle even though i probably won't be able to release version 0.2 till the newsletter comes out i'd like to show the project of
As discussed on Discord, I'll also pick up the section about the AWGY updates 🙂
Heya, I'll write something for the specs
update, and add a link to my game's "Designing Network Play" blog post.
edit: PR #73.
I'd like to work on the Scale
and Ultimate Scale
updates.
Edit: Done!
Hi! I can take on the savefile crate!
Taking "Noodle Cat"
Taking "Robo Instructus"
I've got some free time, so I'll grab:
@ozkriff I came across this while looking at crow. Might be worth adding?
@AngelOnFira yeah. I think it's better to add this as a subsection of the "crow v0.3" section.
Moved the planned release day:
I'm hoping to publish the newsletter on 2019.03.03.The newsletter will be published on 2019.03.04.
UPD: ugh, the newsletter will be published on 2019.03.05.
I can pick up 'Fix Your Time Step in Rust and GGEZ' in a few hours, if no-one else wants it? Then all the items will be accounted for :)
The final content PR is ready - #85 ("Newsletter 7") - everyone is invited to review!
:timer_clock: Hope to merge this in a few hours if there're no objections!
The newsletter is out! :tada:
https://rust-gamedev.github.io/posts/newsletter-007 (twitter, /r/rust)
Many thanks to all contributors and reviewers! 🦀
Well done on the newsletter, everyone. I think the tracking issue worked really well, @ozkriff. A good idea! 👏
yea good job, everyone.
will every project always have to reintroduce itself each newsletter? takes a few paragraphs per project
i think we could make it somethink like this: if project got introduced in previous newsletter, one could add a link to that project note.
Good idea?
will every project always have to reintroduce itself each newsletter? takes a few paragraphs per project
@Skytrias I've been trying to use big introductions only for projects that weren't mentioned in the newsletter before, otherwise use only a quick one-sentence reminder.
Next! #89 ("Newsletter 8: Coordination/Tracking")
I'm hoping to publish the newsletter on 2019.03.03.The newsletter will be published on 2019.03.04.The newsletter will be published on 2019.03.05 for sure.If you want to help writing the newsletter:
source
branch (example: #49)Current status/structure (I'll try to keep this updated):
TODOs: