Dev team calls

Since December of 2024, the dev team has been holding a Discord call every 2 weeks to make decisions on whether to approve new features and to talk about a variety of other topics related to OoTR development. This article is an archive of summaries of each call, ordered reverse-chronologically.

The next call will be held on January 27, 2025 at 21:00 UTC.

January 13, 2025

Participants: Fenhl, Kirox, ShadowShine57

1. setting to add specific dungeon reward requirements for the rainbow bridge (e.g. Light medallion + Forest medallion + Goron ruby)
2. move relevant Trello tasks to GitHub issues
3. went through all PRs under consideration
4. use the settings migration feature also to avoid breakage when settings types change?
5. ask Roman about the status of the extra cosmetics on Dev-R

December 16, 2024

Participants: Fenhl, Kirox, TestRunner, TreZ, Zannick

1. legal implications of using decomp code → TreZ thinks it's fine
2. update compressor/decompressor to MIT-licensed versions?
3. remove binaries from git repo and generate Dev versions in CI?
4. optimization — mypyc, rewriting performance-critical parts in C/Rust? (see PyO3)
5. check why the fuzzer is disabled, potentially reenable
6. mentoring issues e.g. #2106 for decomp-based fixes
7. publish these notes on the OoTR wiki
8. offline releases: new icon (new macOS icon shape), automation, Universal binary for macOS
9. release numbering: previously based on whether there were big features added — now that we have a release schedule, use major version bumps for scheduled releases and minor version bumps for hotfixes and preset backports?
10. postpone the feature freeze by a week to allow people to work on features for this release during holidays? → ask in #dev-public-talk
11. next call on January 6 due to holidays postponed to January 13

December 5, 2024

Sketch of the proposed magic meter model

Participants: Fenhl, ShadowShine57, TestRunner, TreZ

1. considering moving the Python files from the root of the repo to a subfolder to clean things up a bit, not sure if it's worth the extra work for PR authors
2. idea to allow individual options of dropdown/multiselect settings to have separate tooltips → does the UI framework support this?
3. new magic meter model: making it a cosmetic setting would be bad for watching other runners, new idea see image, Maple will look into it
4. approved some nominated PRs, left comments on others, asked race mods^{[private link]} about #2302
5. to encourage work on features we want to see (e.g. stats screen), we could put up bounties, open tracking issues, and/or create feature branches directly on the OoTRandomizer fork
6. triforce-pog-rework branch can probably be deleted, it only exists because the repo was still TestRunner's personal fork when it was created
7. we can assign PRs to ShadowShine57 for review
8. separate Discord channel for nominations? → not necessary
9. next call on the 16th (Mondays work better for TestRunner), maybe start an hour earlier if that makes it possible for Kirox to join? (though ShadowShine57 would most likely have to join late then)