en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/CODEOWNERS#f944f6a6 A couple small `CODEOWNERS` tweaks (#11036)* Add wasmtime-wasi-reviewers team as code owner of WASI cratesWe already have been maintaining membership in this team, but weren't actuallyconnecting it to the `CODEOWNERS` file.* Give compiler-reviewers team ownership of additional compiler-related crates List of files: /wasmtime-44.0.1/CODEOWNERS Fri, 13 Jun 2025 16:33:12 +0000 Nick Fitzgerald <fitzgen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/CODEOWNERS#c48a8ce1 Add `crates/fuzzing` as owned by fuzz reviewers (#8545) List of files: /wasmtime-44.0.1/CODEOWNERS Fri, 03 May 2024 19:12:04 +0000 Nick Fitzgerald <fitzgen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/CODEOWNERS#01b82adf Use GitHub teams as code owners (#6114)The teams named in this revised version of the `CODEOWNERS` file arecurrently configured with the same members as are listed in the filenow.We wanted a single member of the selected team to be assigned as areviewer, but listing people explicitly in CODEOWNERS causes all thenamed people to be assigned. Using teams instead allows us to configurethe load-balancing policy.This also will allow us to add and remove reviewers without needing a PRevery time. List of files: /wasmtime-44.0.1/CODEOWNERS Tue, 28 Mar 2023 23:10:39 +0000 Jamey Sharp <jsharp@fastly.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/CODEOWNERS#d54c00ba Initial designation of code owners (#6084)We want to make sure every contributor gets some kind of meaningfulresponse in a timely fashion. To that end, this PR configures GitHub toauto-assign somebody to every newly-opened PR.People must only be added to this file if they've agreed to thisobligation. The details of what's expected are listed in the file. I'llonly merge this if it's signed off by everyone listed in this initialversion. List of files: /wasmtime-44.0.1/CODEOWNERS Tue, 28 Mar 2023 18:13:34 +0000 Jamey Sharp <jsharp@fastly.com>