@alice_i_cecile@mastodon.gamedev.place avatar

alice_i_cecile

@alice_i_cecile@mastodon.gamedev.place

🍁 Complex systems ecology meets open source meets game design 🌈
Helping build the Bevy game engine in Rust, one RFC at a time 🕊️

Professional game designer and programmer.

Este perfil es de un servidor federado y podría estar incompleto. Explorar más contenido en la instancia original.

alice_i_cecile, a random en
@alice_i_cecile@mastodon.gamedev.place avatar

Hi! I'm back from RustNL! Taking it light today (definitely still exhausted) but I'm feeling ready for another . Let's take a look at the PRs that our community has made and reviewed for us this week :) There was a request to check the website repo, so let's start there! 9 PRs are ready, so that's a great call: https://github.com/bevyengine/bevy-website/pulls?q=is%3Aopen+is%3Apr+label%3AS-Ready-For-Final-Review

alice_i_cecile, a random en
@alice_i_cecile@mastodon.gamedev.place avatar

@bevy now has working groups! These are bottom-up initiatives that provide a space for contributors to collaborate and plan complex but scoped initiatives. To make one, you need 1) at least two other enthusiastic collaborators 2) the blessing of project leadership for the direction of your work.

Make a proposal, write-up a design doc (however you want), run it by the experts in the space and you're off to the races! I'm really keen to see these play out. We have five to start...

alice_i_cecile, a random en
@alice_i_cecile@mastodon.gamedev.place avatar

I just started my first day as a professional (well, engine dev) for @bevy.

Super exciting to have the bandwidth to start putting my plans into motion. I decided that I want to do a daily status update in engine-dev, and let folks track my current areas of focus using a GitHub project board.

https://github.com/orgs/bevyengine/projects/17/views/1

Today was focused on laying out my priorities and tasks, then diving straight into the thorniest project management challenges we have (see below).

alice_i_cecile, a random en
@alice_i_cecile@mastodon.gamedev.place avatar

is regularly the #1 barrier to contributions IME: very easy to get yourself into trouble, hard to help with remotely, merge conflicts are baffling for beginners and recovering from mistakes is endlessly painful. It's often easier just to start fresh on a new branch!

In related news, I have a new contributor struggling with Git: https://github.com/bevyengine/bevy/pull/12640#issuecomment-2019243271

Anyone have better advice than "I would just redo the changes" for them? Because that's what I would do at this stage.

alice_i_cecile, a random en
@alice_i_cecile@mastodon.gamedev.place avatar

Another Monday, another . Let's take a look at the twice-approved (by anyone!), non-controversial PRs that are ready for this week.

https://github.com/bevyengine/bevy/pulls?q=is%3Aopen+is%3Apr+label%3AS-Ready-For-Final-Review+-label%3AS-Controversial+-label%3AS-Blocked+-label%3AS-Adopt-Me+

Looks like we're at 6 at the moment: I should do more reviews! Follow along for an explanation of what each PR does, and how I evaluate its merge-readiness.

  • Todo
  • Suscrito
  • Moderado
  • Favoritos
  • random
  • noticiascr
  • CostaRica
  • Todos las revistas