Raise Alice's Pay

2025-03-30T00:00:00+00:00

</span>

</p>

Proposal:</strong> Francois Mockers proposes:</p>

increase Alice cost to the foundation to $6,324 USD (from $5,127 USD).</p> </blockquote>
Supporting information:</strong> Foundation donations and personal sponsors have changed since the last time (2024/08/07) we updated our budget.</p>
With today (2025/03/07) numbers:</p>
</th> amount (monthly USD)</th></tr></thead>

Foundation donations</td> 14880</td></tr>
Cart donations</td> 1300</td></tr>
Alice donations</td> 350</td></tr>
François donations</td> 65</td></tr>
total</td> 16595</td></tr> </tbody></table>
</th> cost (monthly USD)</th></tr></thead>

thera</td> 490</td></tr>
buffer (10% of Foundation donations</code>)</td> 1488</td></tr>
conference allowance</td> 167</td></tr>
hardware operation contract hosting costs</td> 100</td></tr>
total</td> 2245</td></tr> </tbody></table>
</th> amount (monthly USD)</th></tr></thead>

remaining (total donations - total costs</code>)</td> 14350</td></tr>
hour volume (2 full time + 1 part time: (40 + 40 + 6) * 4</code>)</td> 344</td></tr>
hourly rate (remaining / hour volume</code>)</td> 41.71</td></tr>
Cart payment (hourly rate * 40 * 4 - donations</code>)</td> 5374</td></tr>
Alice payment (hourly rate * 40 * 4 - donations</code>)</td> 6324</td></tr>
François payment (hourly rate * 6 * 4 + hosting costs - donations</code>)</td> 1036</td></tr> </tbody></table>
Spreadsheet with the current state and this proposal, with the calculations: https://docs.google.com/spreadsheets/d/1EXcwqWLO8yHHD1A_2msQXpGbNF2plvCy4kqdCeqxtzo/edit?gid=2076305514#gid=2076305514</p>
Votes:</strong> Yes by Rob Swain, Carter Anderson, Francois Mockers, James Liu. Alice Cecile abstains.</p>

Bevy at RustWeek 2025: come hack with us!

2025-01-07T00:00:00+00:00

Contributing to Bevy</a> is a blast, but what if you could meet each other in flesh?</p>
RustWeek 2025</a> has generously offered to let Bevy (among other Rust-affiliated groups!) nest into a room (plus a breakout room!) as part of their Unconf</a>. Three days of socializing, collaborating and working on Bevy, in whatever form we'd like!</p>

Bevy 0.15

2024-11-29T00:00:00+00:00

Thanks to 294</strong> contributors, 1217</strong> pull requests, community reviewers, and our generous donors</strong></a>, we're happy to announce the Bevy 0.15</strong> release on crates.io</a>!</p>
For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p>
To update an existing Bevy App or Plugin to Bevy 0.15</strong>, check out our 0.14 to 0.15 Migration Guide</a>.</p>
Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p>

Required Components</strong>: A rethink of how spawning entities works that significantly improves the Bevy user experience</li>
Entity Picking / Selection</strong>: A modular system for selecting entities across contexts</li>
Animation Improvements</strong>: generalized entity animation, animation masks, additive blending, and animation events</li>
Curves</strong>: a new Curve</code> trait, cyclic splines, common easing functions, color gradient curves</li>
Reflection Improvements</strong>: Function reflection, unique reflect, remote type reflection</li>
Bevy Remote Protocol (BRP)</strong>: A new protocol that allows external clients (such as editors) to interact with running Bevy games</li>
Visibility Bitmask Ambient Occlusion (VBAO)</strong>: An improved GTAO algorithm that improves ambient occlusion quality</li>
Chromatic Aberration</strong>: A new post processing effect that simulates lenses that fail to focus light to a single point</li>
Volumetric Fog Improvements</strong>: "Fog volumes" that define where volumetric fog is rendered (and what form it takes), along with Point Lights and Spotlight compatibility</li>
Order Independent Transparency</strong>: A new opt-in transparency algorithm that improves the stability / quality of transparent objects as their distance from the camera changes</li>
Improved Text Rendering</strong>: We've switched to Cosmic Text for our text rendering, which significantly improves our ability to render text, especially for non-Latin-based languages that require font shaping and bidirectional text</li>
Gamepads as Entities</strong>: Gamepads are now represented as entities, making them much easier to interact with</li>
UI Box Shadows</strong>: Bevy UI nodes can now render configurable box shadows</li> </ul>Bevy 0.15 was prepared using our new release candidate</strong> process to help ensure that you can upgrade right away with peace of mind. We worked closely with both plugin authors and ordinary users to catch critical bugs, polish new features, and refine the migration guide. For each release candidate, we prepared fixes, shipped a new release candidate on crates.io</a>, let core ecosystem crates update, and listened closely for show-stopping problems. A huge thanks to everyone who helped out</a>! These efforts are a vital step towards making Bevy something that teams large and small can trust to work reliably.</p>

Bevy Foundation is now a 501(c)(3) Public Charity

2024-09-25T00:00:00+00:00

In March we announced the Bevy Foundation</a>, our new non-profit dedicated to developing Bevy and teaching people how to use it. At that time, we applied for federal 501(c)(3) public charity status, which would give us tax-exempt status in the United States and make donations tax-deductible. It introduces stricter operational constraints that help protect the integrity of our mission and our community.</p>
I am excited to announce that the Bevy Foundation has been granted 501(c)(3) public charity status!</p>

Community Reflection on Bevy's Fourth Year

2024-09-11T00:00:00+00:00

@cart</a> here (Bevy's creator and Project Lead) with another update! A month ago was Bevy's Fourth Birthday! As is tradition, I took that as a chance to reflect on the past year and outline my hopes and dreams for the future. You can read that in my Bevy's Fourth Birthday</a> post.</p>
I also encouraged the Bevy community to write their own reflections on Bevy's fourth year in a similar style, and to post them here</a>.</p>

I landed my dream job making a Rust game engine. Now what?

2024-09-10T00:00:00+00:00

So I landed my dream job. Full-time open source building a game engine in Rust. Absolutely no meetings. What more could you ask for? With a very unconventional background (plant ecology, self-taught programming and years of disability), it's flatly astonishing to be supported</a> by such an awesome community: surrounded and empowered by experts and beginners alike making incredible things together.</p>
But now what? Bevy's fourth birthday</a> has rolled around, and @cart</code> has put out a call for others to reflect on the year behind us, and plan for the year ahead. How have my first few months of Serious Employment at the Bevy Foundation gone, and what am I cooking up?</p>
More relaxed voting rules 2024-09-09T00:00:00+00:00 </span> </p> Proposal:</strong> Carter Anderson proposes:</p> We should change "(b) an email transmission that is sent with sufficient information to determine the sender’s identity"" in section 5.16 of the Bevy Foundation Bylaws to "(b) an email transmission with sufficient information to determine the sender's identity or a Discord message or vote in an official Bevy channel or private chat where all maintainers are present." At the time of determining the results of a vote, "edits" to digital messages are considered invalid and the Secretary should take screenshots of the results to include in the meeting minutes.</p> </blockquote> Votes:</strong> Yes by Carter Anderson, Alice I. Cecile, Rob Swain and François Mockers. No vote by James Liu.</p> Recording who voted for which motions in the minutes 2024-09-09T00:00:00+00:00 </span> </p> Proposal:</strong> Carter Anderson proposes:</p> We should change "The names of the persons who were present for discussions and votes relating to the transaction or arrangement, the content of the discussion, including any alternatives to the proposed transaction or arrangement, and a record of any votes taken in connection with the proceedings." in section 8.5 of the Bevy Foundation Bylaws to "The names of the persons who were present for discussions and votes relating to the transaction or arrangement, the content of the discussion, including any alternatives to the proposed transaction or arrangement, and a record of any votes taken in connection with the proceedings. When a decision is not unanimous, the name of each voting board member and the content of their vote must be recorded in the minutes."</p> </blockquote> Votes:</strong> Yes by Carter Anderson, Alice I. Cecile, Rob Swain and François Mockers. No vote by James Liu.</p>
Bevy's Fourth Birthday

2024-08-10T00:00:00+00:00

Hey! @cart</a> here (Bevy's creator and Project Lead). Another year of Bevy development has finally passed, meaning that Bevy is officially four years old</em> now!</p>
As is tradition, I will take this as a chance to reflect on the past year and outline our hopes and dreams for the future. If you're curious, check out Bevy's First Birthday</a>, Second Birthday</a>, and Third Birthday</a> posts.</p>
I also highly encourage Bevy developers and community members to write their own "Bevy Birthday" reflection posts. Just publish your post somewhere (and to social media if you want) and link to it here</a>. One month from now, we will do a "Reflecting on Bevy's Fourth Year" rollup post that aggregates these in one place. This is our chance as a community to celebrate our wins, identify improvement areas, and calibrate our path for the next year.</p>
For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub. We have a Quick Start Guide</a>. You can also check out Bevy Assets</a> for a library of community-developed plugins, crates, games, and learning resources.</p>

Deprecating legacy sponsors

2024-07-16T00:00:00+00:00
</span>
</p>
Proposal:</strong> Carter Anderson proposes:</p>
Also: I think it is time to deprecate the "legacy sponsors" section. I've prepped a branch</a> but I won't create the PR until we agree</p> </blockquote>
Votes:</strong> Yes by Alice I. Cecile, Rob Swain and François Mockers. No vote from Carter Anderson or James Liu.</p>

Increasing Alice's salary

2024-07-08T00:00:00+00:00
</span>
</p>
Proposal:</strong> Cart proposes:</p>

So the proposal is: increase Alice's monthly payments to $6,417.67 CAD ($4,705.28 USD) as soon as Thera can make it possible. Vote on this comment with 👍 or 👎 to officially approve this proposal. Feel free to discuss first if you want to amend the proposal / notice any discrepancies.</p> </blockquote>
Context:</strong></p>

Cart: Alrighty it is definitely time to bump Alice's pay. Consider this a start of one of our "async chat-driven board meetings". Here is my proposal, given the current numbers.</p>
First, lets look at our current numbers: Our current net volume (aka what we take home after stripe fees, credit card fees, failed payments / disputes, etc) for a 4 week period on Stripe is 7,884 USD We have 15,932 USD in our account (with the next monthly Thera charge coming up on the 11th) Alice's current monthly "gross" income is 3,000 CAD We are charged 2,796 USD each month, which translates to about 3,813 CAD. The 813 CAD difference includes the 400 USD (545.65 CAD) Thera EOR fee, plus additional canadian employer taxes. Alice currently makes 675 USD from Github Sponsors I currently make 4245 USD from Github Sponsors. Given the current 7,884 USD, I think we should leave ~800 USD of wiggle room each month to account for fluctuations. That (in combination with our current 15,932 USD buffer) seems more than safe enough. That means we have 7,884 - 800 = 7,084 USD to distribute each month. Lets talk "auto-balance algorithm":</p>
On the topic of taxes: I think it is fair to say that taxes are a cost that is "paid" by the receiver of the funds, given that they pay into public benefits that the receiver benefits from. So when calculating auto-balance, it makes sense to do that pre-tax. On the topic of Thera fees: I think this cost should be split evenly across those getting paid, as the choice to incorporate in the United States was arbitrary and people outside of the united states should not be penalized for it. Put another way, this is a cost "paid by the Foundation prior to making payouts".</p>

So if we were to start auto-balancing now, this would be the calculation (in USD):</p> </blockquote>
$7,884 (currently monthly net income) - $800 (buffer) = $7,084 $7,084 - $400 (current Thera EOR) = $6,684 $6,684 / 2 = $3,342 $4,245 (current Cart Github Sponsors) + $3,342 = $7,587 (Cart's pre auto balance total) $675 (current Alice Github Sponsors) + $3,342 = $4,017 (Alice's pre auto balance total) $7,587 - $4,017 = $3,570 (pre-auto balance difference) $3,570 / 2 = $1,785 (amount to redistribute to Alice) $4,017 + $1,785 = $5,802 (Alice's post-auto-balance total) $7,587 - $1,785 = $5,802 (Cart's post-auto-balance total) $5,802 - $675 = $5,127 (Bevy Foundation payment to Alice) $5,802 - $4,245 = $1,557 (Bevy Foundation payment to Cart) $5,127 + $1,557 = $6,684 (proof that this adds up to the funds allocated for this by the foundation)</p>
From there, we need to sort out Alice's target "gross" income, based on all Canadian fees:</p>
Based on the current numbers: 3,000 CAD gross income 2,796.62 USD monthly cost to foundation 2,796.62 USD - 400 USD (EOR cost) = 2,396.62 USD (cost to foundation minus Thera EOR) 2,396.62 USD = 3,269.65 CAD at time of writing 3,269.65 CAD / 3,000 CAD = 1.089883333 (canadian overhead multiplier)</p>
5,127 USD ~= 6,994.51 CAD at the time of writing 6,994.51 CAD / 1.089883333 (canadian overhead multiplier) = 6,417.67 CAD (Alice monthly gross)</p>
Note that I am still not quite prepared on the "legal" side to take my cut, but I think we should set Alice's payment according to this rate, as I'm not certain how possible lowering monthly income arbitrarily is. We can sort out what to do with the extra funds later (ex: pay out as "fixup" bonuses, or we can discuss alternatives).</p> </blockquote>
Votes:</strong> Alice I. Cecile abstains. All others voted yes.</p>

Bevy 0.14

2024-07-04T00:00:00+00:00

Thanks to 256</strong> contributors, 993</strong> pull requests, community reviewers, and our generous donors</strong></a>, we're happy to announce the Bevy 0.14</strong> release on crates.io</a>!</p>
For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p>
To update an existing Bevy App or Plugin to Bevy 0.14</strong>, check out our 0.13 to 0.14 Migration Guide</a>.</p>
Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p>

Virtual Geometry</strong>: Preprocess meshes into "meshlets", enabling efficient rendering of huge amounts of geometry</li>
Sharp Screen Space Reflections</strong>: Approximate real time raymarched screen space reflections</li>
Depth of Field</strong>: Cause objects at specific depths to go "out of focus", mimicking the behavior of physical lenses</li>
Per-Object Motion Blur</strong>: Blur objects moving fast relative to the camera</li>
Volumetric Fog / Lighting</strong>: Simulates fog in 3d space, enabling lights to produce beautiful "god rays"</li>
Filmic Color Grading</strong>: Fine tune tonemapping in your game with a complete set of filmic color grading tools</li>
PBR Anisotropy</strong>: Improve rendering of surfaces whose roughness varies along the tangent and bitangent directions of a mesh, such as brushed metal and hair</li>
Auto Exposure</strong>: Configure cameras to dynamically adjust their exposure based on what they are looking at</li>
PCF for Point Lights</strong>: Smooth out point light shadows, improving their quality</li>
Animation blending:</strong> Our new low-level animation graph adds support for animation blending, and sets the stage for first- and third-party graphical, asset-driven animation tools.</li>
ECS Hooks and Observers:</strong> Automatically (and immediately) respond to arbitrary events, such as component addition and removal</li>
Better colors:</strong> type-safe colors make it clear which color space you're operating in, and offer an awesome array of useful methods.</li>
Computed states and substates:</strong> Modeling complex app state is a breeze with these type-safe extensions to our States</code> abstraction.</li>
Rounded corners:</strong> Rounding off one of bevy_ui</code>'s roughest edges, you can now procedurally set the corner radius on your UI elements.</li> </ul>For the first time, Bevy 0.14 was prepared using a release candidate</strong> process to help ensure that you can upgrade right away with peace of mind. We've worked closely with both plugin authors and ordinary users to catch critical bugs, round the rough corners off our new features, and refine the migration guide. As we prepared fixes, we've shipped new release candidates on crates.io</a>, letting core ecosystem crates update and listening closely for show-stopping problems. Thank you so much to everyone who helped out</a>: these efforts are a vital step towards making Bevy something that teams large and small can trust to work reliably.</p>
Repaying Cart for initial deposit into bank account 2024-06-16T00:00:00+00:00 </span> </p> Proposal:</strong> Carter Anderson proposes:</p> I do also think we're in a good enough spot reserves-wise (12k USD) for me to reclaim the 2k I added at the beginning. Are we ok with that?</p> </blockquote> Context:</strong> The Bevy bank account needed funds in it to be opened. Cart lent the Foundation $2000 USD from his personal account to cover this.</p> Votes:</strong> Yes by Alice I. Cecile, Rob Swain and François Mockers. No vote from James Liu. Carter Anderson abstained.</p> Sick leave documentation policy 2024-05-02T00:00:00+00:00 </span> </p> Proposal:</strong> Carter Anderson proposes:</p> Should Bevy Foundation employees require documentation for sick leave?</p> </blockquote> Votes:</strong> No from Rob Swain, Carter Anderson, Alice I. Cecile, James Liu. No vote from François Mockers.</p> Usage of the Bevy logo by the unofficial Bevy Playground 2024-04-18T00:00:00+00:00 </span> </p> Proposal:</strong> Alice Cecile proposes:</p> Thumbs up to this message to vote yes to approving use of the logo</a> for Bevy Playground</a>.</p> </blockquote> Votes:</strong> Yes by Carter Anderson, Alice I. Cecile, and Rob Swain. No vote from James Liu and Francois.</p> Initial job titles 2024-04-15T00:00:00+00:00 </span> </p> Proposal:</strong> Carter Anderson proposes:</p> All in favor of Project Lead (me once we hire me), Staff Engineer (soon to be Alice + future maintainer hires), and Principal for SME hires?</p> </blockquote> Votes:</strong> Unananimous yes</p> Using Thera as our Employer of Record 2024-04-15T00:00:00+00:00 </span> </p> Proposal:</strong> Carter Anderson proposes:</p> Are we good to move forward with onboarding [with thera], given that [the cost will be $400/month, $200 cheaper than that of Deel]?</p> </blockquote> Context:</strong> In order to readily employee folks from across the world, the Bevy Foundation uses an employer of record</a> to handle local compliance, taxation and benefits.</p> Votes:</strong> Yes from Rob Swain, Carter Anderson, Alice I. Cecile, François Mockers. No vote from James Liu.</p> Bevy Foundation 2024-03-11T00:00:00+00:00 It is with excitement that I unveil to the world ...</p> The Bevy Foundation</strong></a> is the next step in our journey to build a world class free and open source game engine. Bevy Foundation</strong> is a non-profit organization formed in Washington State, with a pending federal 501(c)(3) tax-exemption application (more on this later).</p> 2024 Budget 2024-03-08T00:00:00+00:00 It is hard to estimate how much money we'll have to work with this year, so for now our budget is pretty straightforward:</p> Spend ~90% of our income to bring Alice on as a full-time maintainer, until she is paid at our target salary of $150,000.</strong></li> Use the remaining ~10% to build up some buffer funds</strong></li> </ul> Hire Alice as a Full-Time Maintainer</h2> We have exactly one focus for the short term: bring Alice on full-time. For years, Alice has dedicated significant</em> time to the project as a Maintainer. She has been our primary project manager: wrangling issues, keeping the merge train running</a>, connecting developers to the right parts of the project, and doing the work that ensures we can harness and enable our ever increasing developer community. Not to mention her extensive technical contributions and documentation work!</p> If you have participated in Bevy's development, you are probably intimately aware of two things:</p> Project management is our bottleneck.</li> Alice is a world-class project manager.</li> </ol> In addition to performing the general "project management" role, Alice has the following specific priorities when she starts full-time:</p> The New Bevy Book</strong>: The new Bevy Book aims to be a complete, always up-to-date, and constantly improving guide to using Bevy. Alice has already contributed content and helped facilitate the book's production. If she joins full-time, she will work to finish it, in addition to helping others contribute.</li> Coordinating the Development of ECS Relations</strong>: Relations are an ECS feature that enable connecting entities to each other via special components called Relations. These are an often-requested feature that will make a number of scenarios (such as parent-child relationships) much nicer. Alice will work to coordinate this effort and fill in functionality gaps.</li> Building an Action System for Input Devices</strong>: Bevy sorely needs an official way to define "input actions", which are then mapped (and remapped) to inputs from one or more input devices (for example: a Jump</code> action that is mapped to the "A" button on controllers and "Spacebar" on keyboards). Alice built leafwing-input-manager</code></a>, which is a popular third-party Bevy plugin that does exactly that. Alice plans on taking the lessons learned there to build a proper first-party solution to this problem.</li> </ol> Alice deserves to be paid for her work, and Bevy needs her full-time. Our goal for the Bevy Foundation</strong> is to pay reasonably competitive, roughly market rate salaries. Therefore, our first goal is to pay Alice a salary of $150,000 a year.</p> We all believe Alice is worth at least that much, but given that funds will take time to build up, Alice has agreed to take a pay cut while things spin up.</p> Build Up Some Buffer</h2> To ensure we can respond to things as they come up, we'll want to build up some initial buffer funds. We'll eventually need to spend some money to help keep Bevy Foundation operational and compliant with state and federal regulations. We also anticipate minor hosting + infrastructure costs to start popping up soon. And once we start exploring other foundation programs, we'll likely need some funds to get those going. Best to be prepared!</p> Bevy 0.13 2024-02-17T00:00:00+00:00 Thanks to 198</strong> contributors, 672</strong> pull requests, community reviewers, and our generous sponsors</strong></a>, we're happy to announce the Bevy 0.13</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources. And to see what the engine has to offer hands-on, check out the entries in the latest Bevy Jam</a>, including the winner That's a LOT of beeeeees</a>.</p> To update an existing Bevy App or Plugin to Bevy 0.13</strong>, check out our 0.12 to 0.13 Migration Guide</a>.</p> Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p> Bevy Foundation Bylaws 2024-02-03T00:00:00+00:00 Article 1. Offices</h2> The principal office of Bevy Foundation (the “Corporation”) shall be located at its principal place of business or such other place as the Board of Directors (“Board”) may designate. The Corporation may have other such offices, either within or without the State of Washington, as the Board may designate or as the business of the Corporation may require from time to time.</p> Article 2. Purpose</h2> The Corporation is organized exclusively for charitable and educational purposes within the meaning of Section 501(c)(3) of the Internal Revenue Code of 1986, as amended, including but not limited to the following:</p> This corporation is formed to promote, protect, and advance the free and open source Bevy game engine and related open source projects. It educates and trains members of the general public in the usage of Bevy, helps coordinate and promote its continued maintenance and development, and advances the state of the art of game programming through scientific research and development. It offers Bevy for free to members of the general public through the use of open source software licensing, helping them create art, games, conduct scientific simulations, build computer-aided design tools, and more</p> Article 3. Shareholders</h2> The Corporation has no Shareholders.</p> Article 4. Membership</h2> The Corporation shall have no members as defined in Section 24.03A.010(45) of the Washington Nonprofit Corporation Act.</p> Article 5. Board of Directors</h2> 5.1 General Powers</h3> The affairs of the Corporation shall be managed by a Board of Directors.</p> 5.2 Number</h3> The Board shall consist of not less than three nor more than eleven Directors, the specific number to be set by resolution of the Board. The number of Directors may be changed from time to time by amendment to these Bylaws, provided that no decrease in the number shall have the effect of shortening the term of any incumbent Director.</p> 5.3 Qualifications</h3> Directors shall have such qualifications as the Board may prescribe by resolution or amendment to these Bylaws.</p> 5.4 Election of Directors</h3> 5.4.1 Initial Directors</h4> The initial Directors named in the Articles of Incorporation shall serve until the first annual meeting of the Board.</p> 5.4.2 Successor Directors</h4> Successor Directors shall be elected at the annual meeting of the Board. The terms of the Directors shall be set so that the terms shall be staggered to the extent possible.</p> 5.5 Term of Office</h3> Unless a Director dies, resigns or is removed, he or she shall hold office for a term of five years or until his or her successor is elected, whichever is later.</p> 5.6 Annual Meeting</h3> The annual meeting of the Board shall be held the month of January at a date and time established by the Board for the purposes of electing directors and officers and transacting such business as may properly come before the meeting. If the day fixed for the annual meeting is a legal holiday at the place of the meeting, the meeting shall be held on the next succeeding business day. If the annual meeting is not held on the date designated therefor, the Board shall cause the meeting to be held as soon thereafter as may be convenient.</p> 5.7 Regular Meetings</h3> By resolution, the Board may specify the date, time and place for the holding of regular meetings without other notice than such resolution.</p> 5.8 Special Meetings</h3> Special meetings of the Board or any committee designated and appointed by the Board may be called by or at the written request of the President or any two Directors, or, in the case of a committee meeting, by the chairman of the committee. The person or persons authorized to call special meetings may fix any place either within or without the State of Washington as the place for holding any special Board or committee meeting called by them.</p> 5.9 Remote Meetings</h3> Members of the Board or any committee designated by the Board may participate in a meeting of such Board or committee by or through the use of, one or more means of remote communication through which all of the directors may simultaneously participate with each other during the meeting. Participation by such means shall constitute presence in person at a meeting.</p> 5.10 Place of Meetings</h3> All meetings shall be held at the principal office of the Corporation or at such other place within or without the State of Washington designated by the Board, by any persons entitled to call a meeting or by a waiver of notice signed by all Directors.</p> 5.11 Notice of Special Meetings</h3> Notice of special Board or committee meetings shall be given to a Director in writing or by personal communication with the Director not less than two days before the meeting. Notices in writing may be delivered or mailed to the Director at his or her address shown on the records of the Corporation or given by facsimile or electronic transmission. Neither the business to be transacted at, nor the purpose of any special meeting need be specified in the notice of such meeting. If notice is delivered by mail, the notice shall be deemed effective when deposited in the official government mail properly addressed with postage thereon prepaid. Notice provided in an electronic transmission is effective when it is electronically transmitted to an address, location or system designated by the recipient for that purpose.</p> 5.12 Waiver of Notice</h3> 5.12.1 In Writing</h4> Whenever any notice is required to be given to any Director under the provisions of these Bylaws, the Articles of Incorporation or applicable Washington law, a waiver thereof in writing, signed by the person or persons entitled to such notice, whether before or after the time stated therein, shall be deemed equivalent to the giving of such notice. Neither the business to be transacted at, nor the purpose of, any regular or special meeting of the Board need be specified in the waiver of notice of such meeting.</p> 5.12.2 By Attendance</h4> The attendance of a Director at a meeting shall constitute a waiver of notice of such meeting, except where a Director attends a meeting for the express purpose of objecting to the transaction of any business because the meeting is not lawfully called or convened.</p> 5.13 Quorum</h3> A majority of the number of Directors in office shall constitute a quorum for the transaction of business at any Board meeting. If a quorum is not present at a meeting, a majority of the Directors present may adjourn the meeting from time to time without further notice.</p> 5.14 Manner of Acting</h3> The act of the majority of the Directors present at a meeting at which there is a quorum shall be the act of the Board, unless the vote of a greater number is required by these Bylaws, the Articles of Incorporation or applicable Washington law.</p> 5.15 Presumption of Assent</h3> A Director of the Corporation present at a Board meeting at which action on any corporate matter is taken shall be presumed to have assented to the action taken unless his or her dissent or abstention is entered in the minutes of the meeting, or unless such Director files a written dissent or abstention to such action with the person acting as secretary of the meeting before the adjournment thereof, or forwards such dissent or abstention by registered mail to the Secretary of the Corporation immediately after the adjournment of the meeting. Such right to dissent or abstain shall not apply to a Director who voted in favor of such action.</p> 5.16 Action by Board Without a Meeting</h3> Any action which could be taken at a meeting of the Board may be taken without a meeting if a written consent setting forth the action so taken is executed by each of the Directors entitled to vote. Such written consents may be executed in two or more counterparts, each of which shall be deemed an original and all of which, taken together, shall constitute one and the same document. Any such written consent shall be inserted in the minute book as if it were the minutes of a Board meeting. For purposes of these Bylaws, “executed” means: (a) writing that is signed; or (b) an email transmission with sufficient information to determine the sender's identity or a Discord message or vote in an official Bevy channel or private chat where all maintainers are present."</p> At the time of determining the results of a vote, "edits" to digital messages are considered invalid and the Secretary should take screenshots of the results to include in the meeting minutes.</p> For purposes of this Section 3.16 only, "each of the Directors entitled to vote" does not include an "interested director" who abstains in writing from providing consent, where:</p> The Board has determined that: The corporation is entering into the transaction for its own benefit; and</li> The transaction is fair and reasonable to the corporation when it enters into the transaction or the noninterested directors determine in good faith after reasonable investigation that the corporation cannot obtain a more advantageous arrangement with reasonable effort under the circumstances, at or before execution of the written consent; and</li> </ol> </li> Such determination is included in the written consent or in other records of the corporation.</li> </ol> 5.17 Resignation</h3> Any Director may resign at any time by delivering written notice to the President or the Secretary at the registered office of the Corporation, or by giving oral or written notice at any meeting of the Directors. Any such resignation shall take effect at the time specified therein, or if the time is not specified, upon delivery thereof and, unless otherwise specified therein, the acceptance of such resignation shall not be necessary to make it effective.</p> 5.18 Removal</h3> At a meeting of the Board, one or more Directors may be removed from office, with or without cause, by two-thirds of the votes cast by Directors then in office.</p> 5.19 Vacancies</h3> A vacancy in the position of Director may be filled by the affirmative vote of a majority of the remaining Directors though less than a quorum of the Board. A Director who fills a vacancy shall serve for the unexpired term of his or her predecessor in office.</p> 5.20 Compensation</h3> The Directors shall receive no compensation for their service as Directors but may receive reimbursement for expenditures incurred on behalf of the Corporation.</p> Article 6. Officers</h2> 6.1 Number and Qualifications</h3> The officers of the Corporation shall be a President, a Secretary, and a Treasurer, each of whom shall be elected by the Board. Other officers and assistant officers may be elected or appointed by the Board, such officers and assistant officers to hold office for such period, have such authority and perform such duties as are provided in these Bylaws or as may be provided by resolution of the Board. Any officer may be assigned by the Board any additional title that the Board deems appropriate. Any two or more offices may be held by the same person, except the offices of President and Secretary.</p> 6.2 Election and Term of Office</h3> The officers of the Corporation shall be elected each year by the Board at the annual meeting of the Board. Unless an officer dies, resigns, or is removed from office, he or she shall hold office until the next annual meeting of the Board or until his or her successor is elected.</p> 6.3 Resignation</h3> Any officer may resign at any time by delivering written notice to the President, the Vice President, the Secretary or the Board, or by giving oral or written notice at any meeting of the Board. Any such resignation shall take effect at the time specified therein, or if the time is not specified, upon delivery thereof and, unless otherwise specified therein, the acceptance of such resignation shall not be necessary to make it effective.</p> 6.4 Removal</h3> Any officer or agent elected or appointed by the Board may be removed from office by the Board whenever in its judgment the best interests of the Corporation would be served thereby, but such removal shall be without prejudice to the contract rights, if any, of the person so removed.</p> 6.5 Vacancies</h3> A vacancy in any office created by the death, resignation, removal, disqualification, creation of a new office or any other cause may be filled by the Board for the unexpired portion of the term or for a new term established by the Board.</p> 6.6 President</h3> The President shall, subject to the Board’s control, supervise and control all of the assets, business and affairs of the Corporation. The President shall preside over meetings of the Board. The President may sign deeds, mortgages, bonds, contracts, or other instruments, except when the signing and execution thereof have been expressly delegated by the Board or by these Bylaws to some other officer or agent of the Corporation or are required by law to be otherwise signed or executed by some other officer or in some other manner. In general, the President shall perform all duties incident to the office of President and such other duties as are assigned to the President by the Board from time to time.</p> 6.7 Secretary</h3> The Secretary shall: (a) keep or cause to be kept the minutes of meetings of the Board, and minutes which may be maintained by committees of the Board; (b) see that all notices are duly given in accordance with the provisions of these Bylaws or as required by law; (c) be custodian or ensure the safe custody of the corporate records of the Corporation; (d) keep records of the post office and email address of each Director and each officer; and (e) in general perform all duties incident to the office of Secretary and such other duties as from time to time may be assigned to the Secretary by the President or the Board.</p> 6.8 Treasurer</h3> If requested by the Board, the Treasurer shall give a bond for the faithful discharge of his or her duties in such amount and with such surety or sureties as the Board may determine. The Treasurer shall have charge and custody of and be responsible for oversight of all funds and securities of the Corporation; receive and give receipts for moneys due and payable to the Corporation from any source whatsoever, and ensure the deposit all such moneys in the name of the Corporation in banks, trust companies or other depositories selected in accordance with the provisions of these Bylaws; provide financial reports to the Board at its meetings and on request and in general perform all of the duties incident to the office of Treasurer and such other duties as from time to time may be assigned to him or her by the President or the Board.</p> Article 7. Administrative Provisions</h2> 7.1 Loans</h3> No loans shall be contracted on behalf of the Corporation and no evidences of indebtedness shall be issued in its name unless authorized by a resolution of the Board. Such authority may be general or confined to specific instances.</p> 7.2 Loans or Extensions of Credit to Officers and Directors</h3> No loans shall be made and no credit shall be extended by the Corporation to its officers or Directors.</p> 7.3 Checks, Drafts, Etc.</h3> All checks, drafts or other orders for the payment of money, notes or other evidences of indebtedness issued in the name of the corporation shall be signed by such officer or officers, or agent or agents, of the Corporation and in such manner as is from time to time determined by resolution of the Board.</p> 7.4 Books and Records</h3> The Corporation shall keep at its principal or registered office copies of its current Articles of Incorporation and Bylaws; correct and adequate records of accounts and finances; minutes of the proceedings of the Board, and any minutes which may be maintained by committees of the Board; records of the name and address of each Director, and each officer; and such other records as may be necessary or advisable.</p> 7.5 Accounting Year</h3> The accounting year of the Corporation shall be the twelve months ending December 31.</p> 7.6 Rules of Procedure</h3> The rules of procedure at meetings of the Board and committees of the Board shall be rules contained in Roberts’ Rules of Order on Parliamentary Procedure, newly revised, so far as applicable and when not inconsistent with these Bylaws, the Articles of Incorporation or any resolution of the Board.</p> Article 8. Conflict of Interest</h2> 8.1 Purpose</h3> Bevy Foundation encourages the active involvement of its directors and officers in the community. To be transparent and deal fairly with actual and potential conflicts of interest that may arise as a consequence of community involvement, Bevy Foundation adopts the following policy. The purpose of this conflict of interest policy is to protect the interests of Bevy Foundation as it fulfills its charitable purposes, and when it is contemplating entering into a transaction or arrangement that might benefit the private interest of an officer or director of Bevy Foundation or might result in a possible excess benefit transaction. This policy is intended to supplement but not replace any applicable state and federal laws governing conflict of interest applicable to nonprofit and charitable organizations.</p> 8.2 Policy</h3> Directors and officers are expected to use good judgment, to adhere to high ethical standards, and to conduct their affairs in such a manner as to avoid any actual or potential conflict between the personal interests of a director or officer and those of Bevy Foundation. A conflict of interest exists when a director or officer’s loyalties or actions are divided between the interests of Bevy Foundation and the director or officer’s interests. Both the fact and the appearance of a conflict of interest should be avoided.</p> 8.3 Definitions</h3> 8.3.1 Affiliation</h4> An affiliation includes any interests other than financial interests that may influence a director or officer’s judgment. An objective test determines whether an affiliation exists between the director or officer and the other person, entity, or organization: whether the involvement or relationship of the director or officer with the other person, entity, or organization is such that it reduces the likelihood that the director or officer can act in Bevy Foundation’s best interests.</p> 8.3.2 Interested Person</h4> Any director, principal officer, or member of a committee with governing board delegated powers, who has a direct or indirect financial interest, as defined below, or organizational affiliation, as defined above, is an interested person.</p> 8.3.3 Financial Interest</h4> A person has a financial interest if the person has, directly or indirectly, through business, investment, or family:</p> An ownership or investment interest in any entity with which Bevy Foundation has a transaction or arrangement,</li> A compensation arrangement with Bevy Foundation or with any entity or individual with which Bevy Foundation has a transaction or arrangement, or</li> A potential ownership or investment interest in, or compensation arrangement with, any entity or individual with which Bevy Foundation is negotiating a transaction or arrangement. Compensation includes direct and indirect remuneration as well as gifts or favors that are not insubstantial. A financial interest is not necessarily a conflict of interest. Under Article IV, Section 2, a person who has a financial interest may have a conflict of interest only if the appropriate governing board or committee decides that a conflict of interest exists.</li> </ol> 8.4 Procedures</h3> 8.4.1 Duty to Disclose</h4> In connection with any actual or possible conflict of interest, an interested person must disclose the existence of the financial interest or organizational affiliation and be given the opportunity to disclose all material facts to the directors and members of committees with governing board delegated powers considering the proposed transaction or arrangement</p> 8.4.2 Determining Whether a Conflict of Interest Exists</h4> After disclosure of the financial interest or organizational affiliation and all material facts, and after any discussion with the interested person, he/she shall leave the governing board or committee meeting while the determination of a conflict of interest is discussed and voted upon. The remaining board or committee members shall decide if a conflict of interest exists.</p> 8.4.3 Procedures for Addressing the Conflict of Interest</h4> An interested person may make a presentation at the governing board or committee meeting, but after the presentation, he/she shall leave the meeting during the discussion of, and the vote on, the transaction or arrangement involving the possible conflict of interest.</li> The chairperson of the governing board or committee shall, if appropriate, appoint a disinterested person or committee to investigate alternatives to the proposed transaction or arrangement.</li> After exercising due diligence, the governing board or committee shall determine whether Bevy Foundation can obtain with reasonable efforts a more advantageous transaction or arrangement from a person or entity that would not give rise to a conflict of interest.</li> The governing board or committee shall determine by a majority vote of the disinterested directors whether the transaction or arrangement is in Bevy Foundation's best interest, for its own benefit, and whether it is fair and reasonable. In conformity with the above determination, it shall make its decision as to whether to enter into the transaction or arrangement.</li> </ol> 8.4.4 Violations of the Conflict of Interest Policy</h4> If the governing board or committee has reasonable cause to believe a member has failed to disclose actual or possible conflict of interest, it shall inform the member of the basis for such belief and afford the member an opportunity to explain the alleged failure to disclose.</li> If, after hearing the member’s response and after making further investigation as warranted by the circumstances, the governing board or committee determines the member has failed to disclose an actual or possible conflict of interest, it shall take appropriate disciplinary and corrective action.</li> </ol> 8.5 Records of Proceedings</h3> The minutes of the governing board and all committees with board delegated powers shall contain:</p> The names of the persons who disclosed or otherwise were found to have a financial interest or organizational affiliation in connection with an actual or possible conflict of interest, the nature of the financial interest or organizational affiliation, any action taken to determine whether a conflict of interest was present, and the governing board’s or committee’s decision as to whether a conflict of interest in fact existed.</li> The names of the persons who were present for discussions and votes relating to the transaction or arrangement, the content of the discussion, including any alternatives to the proposed transaction or arrangement, and a record of any votes taken in connection with the proceedings. When a decision is not unanimous, the name of each voting board member and the content of their vote must be recorded in the minutes.</li> </ol> 8.6 Compensation</h3> A voting member of the governing board who receives compensation, directly or indirectly, from Bevy Foundation for services is precluded from voting on matters pertaining to that member’s compensation.</li> A voting member of any committee whose jurisdiction includes compensation matters and who receives compensation, directly or indirectly, from Bevy Foundation for services is precluded from voting on matters pertaining to that member’s compensation.</li> No voting member of the governing board or any committee whose jurisdiction includes compensation matters and who receives compensation, directly or indirectly, from Bevy Foundation, either individually or collectively, is prohibited from providing information to any committee regarding compensation.</li> </ol> 8.7 Periodic Statements</h3> Each director and officer shall periodically sign a statement that affirms such person:</p> Has received a copy of the conflict of interest policy,</li> Has read and understands the policy,</li> Has agreed to comply with the policy, and</li> Understands that Bevy Foundation is a charitable organization and in order to maintain its federal tax exemption it must engage primarily in activities which accomplish one or more of its tax-exempt purposes.</li> </ol> 8.8 The Bevy Sponsorship Pledge</h3> Each director that receives money for their work on Bevy must sign and adhere to the Bevy Sponsorship Pledge. A copy is available on the Bevy website: https://bevy.org/sponsorship-pledge</a>.</p> Article 9. Amendments</h2> These Bylaws may be altered, amended or repealed and new Bylaws may be adopted by the vote of a majority of the number of Directors in office.</p> The foregoing Bylaws were adopted by a majority of the Directors then in office at a meeting of the Board of Directors held on February 3rd, 2024 at which a quorum was present.</p> History</h2> Initial Bylaws adopted by the Bevy Foundation board on February 3rd, 2024.</li> </ul> Board meeting: 2024-02-03 2024-02-03T00:00:00+00:00 </span>Attendees #</a> </h2> Rob Swain</li> James Liu</li> Carter Anderson</li> Alice I. Cecile</li> François Mockers</li> </ul> Agenda #</a> </h2> Adopt bylaws</li> Elect officers</li> Approve Cart opening a bank account</li> Approve Cart transferring copyright of the Bevy logo</li> </ol> Adopt Bylaws #</a> </h2> Proposed by: Cart</p> As defined in Cart’s branch on 2024-02-03</a>.</p> Unanimously approved.</p> Officers #</a> </h2> Cart for President.</strong></p> Proposed by: Cart</p> Unanimously approved.</p> Alice for Secretary.</strong></p> Proposed by: Cart</p> Unanimously approved.</p> Board discussed who should be treasurer. Easier for US persons, due to the need to go in to the bank branch to validate ID.</p> Cart for Treasurer.</strong></p> Proposed by: Cart</p> Unanimously approved, with discussion of this as a temporary position.</p> Opening a bank account #</a> </h2> Cart shall open a bank account on behalf of the Foundation.</p> Proposed by: Cart</p> Unanimously approved.</p> Transferring of the Bevy logo copyright #</a> </h2> The Bevy Foundation should accept a copyright transfer of the Bevy logo from Carter Anderson.</p> Proposed by: Cart</p> Unanimously approved.</p> Making foundation board meeting minutes generally publicly available #</a> </h2> The board should make these meeting notes publicly available at the time of publication.</p> Proposed by: Alice</p> Unanimously approved.</p> Signing of meeting minutes #</a> </h2> Discussed how to validate meeting minutes.</p> Agreed on storing meeting minutes on GitHub on bevy-website repo</code>, and approved by board members via PR approval.</p> Transferring the ownership of the bevyengine.org domain to the Foundation #</a> </h2> Cart should transfer ownership of the bevyengine.org domain to the foundation.</p> Proposed by: James</p> Discussed how to pay for the bills associated. May need to delay until bank account is open and has funds.</p> Cart will cover hosting costs personally initially, and then will be reimbursed.</p> Unanimously approved.</p> Transferring ownership of the bevyengine GitHub account to the Foundation #</a> </h2> Unclear of how exactly we might do this. Broad agreement that this is Probably correct to do.</p> Might need to consider how/if to add more admin privileges to manage attack surface.</p> Motion to adjourn #</a> </h2> Proposed by: Cart</p> Unanimously approved.</p> SME Announcements 2023-12-12T00:00:00+00:00 @cart</a> here (Bevy's creator and Project Lead) with a quick update! We have some new SMEs (Subject Matter Experts) to announce.</p> Bevy 0.12 2023-11-04T00:00:00+00:00 Thanks to 185</strong> contributors, 567</strong> pull requests, community reviewers, and our generous sponsors</strong></a>, we're happy to announce the Bevy 0.12</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> To update an existing Bevy App or Plugin to Bevy 0.12</strong>, check out our 0.11 to 0.12 Migration Guide</a>.</p> Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p> Community Reflection on Bevy's Third Year 2023-09-21T00:00:00+00:00 @cart</a> here (Bevy's creator and Project Lead) with another update! A little over a month ago was Bevy's Third Birthday! As is tradition, I took that as a chance to reflect on the past year and outline my hopes and dreams for the future. You can read that in my Bevy's Third Birthday</a> post.</p> This year for the first time I also encouraged the Bevy community to write their own reflections on Bevy's third year in a similar style, and to post them here</a>.</p> Bevy's Third Birthday 2023-08-10T00:00:00+00:00 @cart</a> here (Bevy's creator and Project Lead) with an exciting announcement ... it has now been three years since the initial Bevy release!</p> As is tradition, I will take this as a chance to reflect on the past year and outline our hopes and dreams for the future. If you're curious, check out Bevy's First Birthday</a> and Second Birthday</a> posts.</p> This year, I am also highly encouraging everyone to write their own "Bevy Birthday" reflection posts. Just publish your post somewhere (and to social media if you want) and link to it here</a>. One month from now, we will do a followup "Reflecting on Bevy's Third Year" rollup post that aggregates these in one place. This is our chance as a community to celebrate our wins, identify improvement areas, and calibrate our path for the next year.</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub. We have a Quick Start Guide</a>. You can also check out Bevy Assets</a> for a library of community-developed plugins, crates, games, and learning resources.</p> Bevy 0.11 2023-07-09T00:00:00+00:00 Thanks to 166</strong> contributors, 522</strong> pull requests, community reviewers, and our generous sponsors</strong></a>, we're happy to announce the Bevy 0.11</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> To update an existing Bevy App or Plugin to Bevy 0.11</strong>, check out our 0.10 to 0.11 Migration Guide</a>.</p> Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p> Bevy + WebGPU 2023-05-17T00:00:00+00:00 I'm excited to announce that Bevy's main branch now supports WebGPU rendering on the web! This means you can play with it now by checking out our repo</a> provided you have a supported web browser</a> (WebGPU is still in the process of rolling out). You can also explore our live WebGPU examples</a>. The upcoming Bevy 0.11 release</a> will have WebGPU support built in, which is slated for release in about a month!</p> What is WebGPU? #</a> </h2> WebGPU is an exciting new web standard</a> for doing modern GPU graphics and compute. It takes inspiration from Vulkan, Direct3D 12, and Metal. In fact, it is generally implemented on top of these APIs under the hood. WebGPU gives us access to more GPU features than WebGL2 (such as compute shaders) and also has the potential to be much faster. It means that more of Bevy's native renderer features are now also available on the web. It also uses the new WGSL shader language</a>. We're very happy with how WGSL has evolved over time and Bevy uses it internally for our shaders. We also added usability features like imports! But with Bevy you still have the option to use GLSL if you prefer.</p> WebGPU has started making waves because Chrome just shipped WebGPU support in Chrome 113</a>, which means people with normal Chrome releases can start testing it. Firefox and Safari also have implementations in the works!</p> What is Bevy? #</a> </h2> </p> For those who don't know, Bevy is a refreshingly simple cross-platform data-driven game engine built in Rust. It has a modern and extensible 2D and 3D renderer, a best-in-class ECS (entity component system) that is delightful to use, plenty of features</a>, and a vibrant and open developer community</a>. It currently supports Windows, MacOS, Linux, iOS, and Web. We also have work in progress Android support ... and ambitions for even more platforms in the future!</p> You can check out our Quick Start Guide</a> to try it today. It is free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> Bevy 0.10 2023-03-06T00:00:00+00:00 Thanks to 173</strong> contributors, 689</strong> pull requests, community reviewers, and our generous sponsors</strong></a>, we're happy to announce the Bevy 0.10</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> To update an existing Bevy App or Plugin to Bevy 0.10</strong>, check out our 0.9 to 0.10 Migration Guide</a>.</p> Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p> Scaling Bevy Development 2023-01-14T00:00:00+00:00 The Bevy community has grown a lot over the past couple of years. We've had over 3,642 pull requests, 599 contributors, 357,917 downloads, and 21,200 github stars. Together we've built the most popular, most used Rust game engine on the market and the second most popular game engine on GitHub</a>. Up until now, in the interest of maintaining a consistent vision and quality bar, I've kept our decision making process as small and centralized as possible. And I scaled out our leadership roles as slowly as possible. I believe this was the right call for Bevy's early days, but we are overdue for changes that bias toward more trust and development agility.</p> Bevy 0.9 2022-11-12T00:00:00+00:00 Thanks to 159</strong> contributors, 430</strong> pull requests, community reviewers, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.9</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> To update an existing Bevy App or Plugin to Bevy 0.9</strong>, check out our 0.8 to 0.9 Migration Guide</a>.</p> Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p> Contingency Plans in Case of a Funding Cut 2022-11-06T00:00:00+00:00 </span> </p> Proposal:</strong> Carter Anderson proposes:</p> Open source funding can be unstable. The foundation needs a plan to handle drops in funding in a way that is best for the health of the organization. Salaries are already currently below our desired targets. We have already on occasion opportunistically increased salaries as the budget allows, and there is an understanding / agreement among employees that these will fluctuate based on the financials of the foundation. I propose formalizing the following plan:</p> Periodically (and opportunistically, as the need arises) raise or lower salaries based on our budget calculator (currently expressed in the Budget document on our google drive).</li> If this ever results in a drop below the "minimum viable yearly salary" (determined by the board), we will first cut non-critical programs and employees (as voted on by the board). If this is not enough to retain the remaining employees at the "minimum viable yearly salary", we will then enter a "part time" phase.</li> In the "part time phase", employees (that choose to stay) will scale back their hours by the amount required to balance the budget. By default this is done equally, unless an employee volunteers to give up their hours to the pool, or the board determines otherwise. If hours can be reduced no more (as determined by the board), employees will then be severed in an order determined by the board.</li> </ol> </blockquote> Votes:</strong> Yes from Rob Swain, Carter Anderson, Alice I. Cecile, François Mockers and James Liu.</p> Bevy's Second Birthday 2022-08-10T00:00:00+00:00 @cart</a> here (Bevy's creator, lead developer, and project manager) with another exciting announcement:</p> It has now been two years since the initial Bevy release! As is (now) tradition, I will take this as a chance to reflect on the past year and outline our plans for the future. If you're curious, check out last year's birthday post</a>.</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub. We have a Quick Start Guide</a>. You can also check out Bevy Assets</a> for a library of community-developed plugins, crates, games, and learning resources.</p> Bevy 0.8 2022-07-30T00:00:00+00:00 Thanks to 130</strong> contributors, 461</strong> pull requests, community reviewers, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.8</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide</a> to try it today. It's free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> To update an existing Bevy App or Plugin to Bevy 0.8</strong>, check out our 0.7 to 0.8 Migration Guide</a>.</p> Since our last release a few months ago we've added a ton</em> of new features, bug fixes, and quality of life tweaks, but here are some of the highlights:</p> New Material System</strong>: Custom shaders are now much</em> easier to define, thanks to the new Material trait and AsBindGroup derive.</li> Camera-driven Rendering</strong>: Each Camera now configures what it renders and how it renders it. Easily layer camera renders on top of each other, do split screen, or render to a texture in just a few lines of code.</li> Built-in Shader Modularization</strong>: Many built-in shader types and functions are now importable. Notably, custom shaders can now import the PBR shader logic</li> Spot Lights</strong>: A new light type that emits light in a cone shape from a fixed point.</li> Visibility Inheritance</strong>: Hiding an entity now also hides all of its descendants in the hierarchy.</li> Upgraded to wgpu 0.13</strong>: Uses a new, more ergonomic WGSL shader syntax.</li> Automatic Mesh Tangent Generation</strong>: If tangents are missing for a mesh, generate them with mikktspace.</li> Renderer Optimizations</strong>: Parallel frustum culling and unstable sorts for unbatched render phases yielded some big wins!</li> Scene Bundle</strong>: Easily spawn scenes using a normal Bevy bundle and extend them with new components and children.</li> Scripting and Modding Progress: Untyped ECS APIs</strong>: A step toward 3rd party scripting language support! Interact with Bevy ECS internals directly via pointers.</li> ECS Query Ergonomics and Usability</strong>: Queries now implement IntoIter</code> and mutable queries can be converted to immutable queries.</li> ECS Internals Refactors</strong>: Sweeping changes to Bevy ECS internals that make it simpler, safer, and easier to maintain.</li> Reflection Improvements</strong>: Support for reflecting more types, ECS resource reflection, untyped reflection, improved internals.</li> Hierarchy Commands</strong>: Hierarchy updates now use "transactional commands" to ensure hierarchy consistency at all times.</li> Bevy UI Now Uses Taffy</strong>: We've swapped to (and help maintain) a collaborative fork of the now abandoned Stretch UI layout library. Exponential blow-up bug begone!</li> </ul> Bevy 0.7 2022-04-15T00:00:00+00:00 Thanks to 123</strong> contributors, 349</strong> pull requests, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.7</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out The Quick Start Guide</a> to get started. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> To update an existing Bevy App or Plugin to Bevy 0.7</strong>, check out our 0.6 to 0.7 Migration Guide</a>.</p> As always, there are a ton</em> of new features, bug fixes, and quality of life tweaks in this release, but here are some of the highlights:</p> Skeletal animation and mesh skinning</li> GLTF animation importing</li> Unlimited* point lights in a scene</li> Improved clustered forward rendering: dynamic/adaptive clustering and faster, more accurate cluster assignment</li> Compressed texture support (KTX2 / DDS / .basis): load more textures in a scene, faster</li> Compute shader / pipeline specialization: Bevy's flexible shader system was ported to compute shaders, enabling hot reloading, shader defs, and shader imports</li> Render to texture: cameras can now be configured to render to a texture instead of a window</li> Flexible mesh vertex layouts in shaders</li> ECS improvements: Order systems using their names, Query::many_mut, use conflicting parameters in systems via ParamSets, WorldQuery derives</li> Documentation improvements: better examples, more doc tests and more coverage</li> More audio control: pause, volume, speed, and looping</li> Power usage options to enable only updating Bevy Apps when input occurs</li> </ul> Bevy 0.6 2022-01-08T00:00:00+00:00 Thanks to 170</strong> contributors, 623</strong> pull requests, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.6</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out The Quick Start Guide</a> to get started. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub. Check out Bevy Assets</a> for a collection of community-developed plugins, games, and learning resources.</p> To update an existing Bevy App or Plugin to Bevy 0.6</strong>, check out our 0.5 to 0.6 Migration Guide</a>.</p> There are a ton</em> of improvements, bug fixes and quality of life tweaks in this release. Here are some of the highlights:</p> A brand new modern renderer that is prettier, faster, and simpler to extend</li> Directional and point light shadows</li> Clustered forward rendering</li> Frustum culling</li> Significantly faster sprite rendering with less boilerplate</li> Native WebGL2 support. You can test this out by running the Bevy Examples in your browser!</a></li> High level custom Materials</li> More powerful shaders: preprocessors, imports, WGSL support</li> Bevy ECS ergonomics and performance improvements. No more .system()</code>!</li> </ul> Read on for details!</p> Bevy's First Birthday 2021-08-10T00:00:00+00:00 @cart</a> here (Bevy's creator, lead developer, and project manager) with some exciting news:</p> Today is Bevy's first birthday! And what a year it has been! Now seems like as good a time as any to look back on how far we've come, reflect a bit, and start thinking about what the next year of Bevy development will look like.</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub. We have a Quick Start Guide</a>. You can also check out Bevy Assets</a> for a library of community-developed plugins, crates, games, and learning resources.</p> Bevy 0.5 2021-04-06T00:00:00+00:00 Thanks to 88</strong> contributors, 283</strong> pull requests, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.5</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out The Quick Start Guide</a> to get started. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub. Check out Awesome Bevy</a> for a list of community-developed plugins, games, and learning resources.</p> Bevy 0.5</strong> is quite a bit bigger than our past few releases (and took a bit longer) as we have made a number of foundational changes. If you plan on updating your App or Plugin to Bevy 0.5</strong>, check out our 0.4 to 0.5 Migration Guide</a>.</p> Here are some of the highlights from this release:</p> Bevy 0.4 2020-12-19T00:00:00+00:00 A little over a month after releasing Bevy 0.3, and thanks to 66</strong> contributors, 178</strong> pull requests, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.4</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out The Quick Start Guide</a> to get started. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub.</p> Here are some of the highlights from this release:</p> Bevy 0.3 2020-11-03T00:00:00+00:00 A little over a month after releasing Bevy 0.2, and thanks to 59</strong> contributors, 122</strong> pull requests, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.3</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out The Quick Start Guide</a> to get started. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub.</p> Here are some of the highlights from this release:</p> Bevy 0.2 2020-09-19T00:00:00+00:00 A month after the initial Bevy release, and thanks to 87</strong> contributors, 174</strong> pull requests, and our generous sponsors</strong></a>, I'm happy to announce the Bevy 0.2</strong> release on crates.io</a>!</p> For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out The Quick Start Guide</a> to get started. Bevy is also free and open source forever! You can grab the full source code</a> on GitHub.</p> Here are some of the highlights from this release:</p> Scaling Bevy 2020-08-19T00:00:00+00:00 First, I want to take a moment to highlight just how wild the last week has been. Bevy was only released a week ago</strong></a> and we've already hit some pretty major milestones:</p> Introducing Bevy 0.1 2020-08-10T00:00:00+00:00 </video></p> After months of work, I am ecstatic to finally announce Bevy Engine</strong>!</p> Bevy is a refreshingly simple data-driven game engine and app framework built in Rust. It is free and open-source</a> forever!</p>

Bevy Engine

Bevy 0.18

Best Effort Salary Fixup Bonuses

Correctly account for cost to foundation of employees

Error in raises

Bevy 0.17

Community Reflection on Bevy's Fifth Year

Bevy's Fifth Birthday

Buying Bevy.org

Bevy 0.16

Allow use of Bevy in Pixel Eagle marketing

Conference Allowance

Hardware for Benchmarking

Hire Cart

Raise Alice's Pay

Bevy at RustWeek 2025: come hack with us!

Bevy 0.15

Bevy Foundation is now a 501(c)(3) Public Charity

Community Reflection on Bevy's Fourth Year

I landed my dream job making a Rust game engine. Now what?

More relaxed voting rules

Recording who voted for which motions in the minutes

Bevy's Fourth Birthday

Deprecating legacy sponsors

Increasing Alice's salary

Bevy 0.14

Repaying Cart for initial deposit into bank account

Sick leave documentation policy

Usage of the Bevy logo by the unofficial Bevy Playground

Initial job titles

Using Thera as our Employer of Record

Bevy Foundation

2024 Budget

Bevy 0.13

Bevy Foundation Bylaws

Article 3. Shareholders</h2> The Corporation has no Shareholders.</p>

Article 4. Membership</h2> The Corporation shall have no members as defined in Section 24.03A.010(45) of the Washington Nonprofit Corporation Act.</p>

Article 5. Board of Directors</h2>

5.1 General Powers</h3> The affairs of the Corporation shall be managed by a Board of Directors.</p>

5.3 Qualifications</h3> Directors shall have such qualifications as the Board may prescribe by resolution or amendment to these Bylaws.</p>

5.4 Election of Directors</h3>

5.4.1 Initial Directors</h4> The initial Directors named in the Articles of Incorporation shall serve until the first annual meeting of the Board.</p>

5.4.2 Successor Directors</h4> Successor Directors shall be elected at the annual meeting of the Board. The terms of the Directors shall be set so that the terms shall be staggered to the extent possible.</p>

5.5 Term of Office</h3> Unless a Director dies, resigns or is removed, he or she shall hold office for a term of five years or until his or her successor is elected, whichever is later.</p>

5.7 Regular Meetings</h3> By resolution, the Board may specify the date, time and place for the holding of regular meetings without other notice than such resolution.</p>

5.10 Place of Meetings</h3> All meetings shall be held at the principal office of the Corporation or at such other place within or without the State of Washington designated by the Board, by any persons entitled to call a meeting or by a waiver of notice signed by all Directors.</p>

5.12 Waiver of Notice</h3>

5.12.2 By Attendance</h4> The attendance of a Director at a meeting shall constitute a waiver of notice of such meeting, except where a Director attends a meeting for the express purpose of objecting to the transaction of any business because the meeting is not lawfully called or convened.</p>

5.13 Quorum</h3> A majority of the number of Directors in office shall constitute a quorum for the transaction of business at any Board meeting. If a quorum is not present at a meeting, a majority of the Directors present may adjourn the meeting from time to time without further notice.</p>

5.14 Manner of Acting</h3> The act of the majority of the Directors present at a meeting at which there is a quorum shall be the act of the Board, unless the vote of a greater number is required by these Bylaws, the Articles of Incorporation or applicable Washington law.</p>

5.18 Removal</h3> At a meeting of the Board, one or more Directors may be removed from office, with or without cause, by two-thirds of the votes cast by Directors then in office.</p>

5.19 Vacancies</h3> A vacancy in the position of Director may be filled by the affirmative vote of a majority of the remaining Directors though less than a quorum of the Board. A Director who fills a vacancy shall serve for the unexpired term of his or her predecessor in office.</p>

5.20 Compensation</h3> The Directors shall receive no compensation for their service as Directors but may receive reimbursement for expenditures incurred on behalf of the Corporation.</p>

Article 6. Officers</h2>

6.5 Vacancies</h3> A vacancy in any office created by the death, resignation, removal, disqualification, creation of a new office or any other cause may be filled by the Board for the unexpired portion of the term or for a new term established by the Board.</p>

Article 7. Administrative Provisions</h2>

7.1 Loans</h3> No loans shall be contracted on behalf of the Corporation and no evidences of indebtedness shall be issued in its name unless authorized by a resolution of the Board. Such authority may be general or confined to specific instances.</p>

7.2 Loans or Extensions of Credit to Officers and Directors</h3> No loans shall be made and no credit shall be extended by the Corporation to its officers or Directors.</p>

7.5 Accounting Year</h3> The accounting year of the Corporation shall be the twelve months ending December 31.</p>

Article 8. Conflict of Interest</h2>

8.3 Definitions</h3>

8.3.2 Interested Person</h4> Any director, principal officer, or member of a committee with governing board delegated powers, who has a direct or indirect financial interest, as defined below, or organizational affiliation, as defined above, is an interested person.</p>

8.3.3 Financial Interest</h4> A person has a financial interest if the person has, directly or indirectly, through business, investment, or family:</p>

8.4 Procedures</h3>

8.8 The Bevy Sponsorship Pledge</h3> Each director that receives money for their work on Bevy must sign and adhere to the Bevy Sponsorship Pledge. A copy is available on the Bevy website: https://bevy.org/sponsorship-pledge</a>.</p>

History</h2> Initial Bylaws adopted by the Bevy Foundation board on February 3rd, 2024.</li> </ul>

Board meeting: 2024-02-03

Attendees #</a> </h2> Rob Swain</li> James Liu</li> Carter Anderson</li> Alice I. Cecile</li>

Agenda #</a> </h2> Adopt bylaws</li> Elect officers</li> Approve Cart opening a bank account</li>

SME Announcements

Bevy 0.12

Community Reflection on Bevy's Third Year

Bevy's Third Birthday

Bevy 0.11

Bevy + WebGPU

Bevy 0.10

Scaling Bevy Development

Bevy 0.9

Contingency Plans in Case of a Funding Cut

Bevy's Second Birthday

Article 3. Shareholders</h2>
The Corporation has no Shareholders.</p>

Article 4. Membership</h2>
The Corporation shall have no members as defined in Section 24.03A.010(45) of the Washington Nonprofit Corporation Act.</p>

5.1 General Powers</h3>
The affairs of the Corporation shall be managed by a Board of Directors.</p>

5.3 Qualifications</h3>
Directors shall have such qualifications as the Board may prescribe by resolution or amendment to these Bylaws.</p>

5.4.1 Initial Directors</h4>
The initial Directors named in the Articles of Incorporation shall serve until the first annual meeting of the Board.</p>

5.4.2 Successor Directors</h4>
Successor Directors shall be elected at the annual meeting of the Board. The terms of the Directors shall be set so that the terms shall be staggered to the extent possible.</p>

5.5 Term of Office</h3>
Unless a Director dies, resigns or is removed, he or she shall hold office for a term of five years or until his or her successor is elected, whichever is later.</p>

5.7 Regular Meetings</h3>
By resolution, the Board may specify the date, time and place for the holding of regular meetings without other notice than such resolution.</p>

5.10 Place of Meetings</h3>
All meetings shall be held at the principal office of the Corporation or at such other place within or without the State of Washington designated by the Board, by any persons entitled to call a meeting or by a waiver of notice signed by all Directors.</p>

5.12.2 By Attendance</h4>
The attendance of a Director at a meeting shall constitute a waiver of notice of such meeting, except where a Director attends a meeting for the express purpose of objecting to the transaction of any business because the meeting is not lawfully called or convened.</p>

5.13 Quorum</h3>
A majority of the number of Directors in office shall constitute a quorum for the transaction of business at any Board meeting. If a quorum is not present at a meeting, a majority of the Directors present may adjourn the meeting from time to time without further notice.</p>

5.14 Manner of Acting</h3>
The act of the majority of the Directors present at a meeting at which there is a quorum shall be the act of the Board, unless the vote of a greater number is required by these Bylaws, the Articles of Incorporation or applicable Washington law.</p>

5.18 Removal</h3>
At a meeting of the Board, one or more Directors may be removed from office, with or without cause, by two-thirds of the votes cast by Directors then in office.</p>

5.19 Vacancies</h3>
A vacancy in the position of Director may be filled by the affirmative vote of a majority of the remaining Directors though less than a quorum of the Board. A Director who fills a vacancy shall serve for the unexpired term of his or her predecessor in office.</p>

5.20 Compensation</h3>
The Directors shall receive no compensation for their service as Directors but may receive reimbursement for expenditures incurred on behalf of the Corporation.</p>

6.5 Vacancies</h3>
A vacancy in any office created by the death, resignation, removal, disqualification, creation of a new office or any other cause may be filled by the Board for the unexpired portion of the term or for a new term established by the Board.</p>

7.1 Loans</h3>
No loans shall be contracted on behalf of the Corporation and no evidences of indebtedness shall be issued in its name unless authorized by a resolution of the Board. Such authority may be general or confined to specific instances.</p>

7.2 Loans or Extensions of Credit to Officers and Directors</h3>
No loans shall be made and no credit shall be extended by the Corporation to its officers or Directors.</p>

7.5 Accounting Year</h3>
The accounting year of the Corporation shall be the twelve months ending December 31.</p>

8.3.2 Interested Person</h4>
Any director, principal officer, or member of a committee with governing board delegated powers, who has a direct or indirect financial interest, as defined below, or organizational affiliation, as defined above, is an interested person.</p>

8.8 The Bevy Sponsorship Pledge</h3>
Each director that receives money for their work on Bevy must sign and adhere to the Bevy Sponsorship Pledge. A copy is available on the Bevy website: https://bevy.org/sponsorship-pledge</a>.</p>

History</h2>

Initial Bylaws adopted by the Bevy Foundation board on February 3rd, 2024.</li> </ul>