We also have our gem5-resources and gem5-website repositories, which we tag with "resources" and "website". Though separate repos, it may be worth adding maintainers for these things as they come up on Gerrit either way. I'm happy to volunteer as a maintainer for both.
-- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Wed, Oct 21, 2020 at 7:31 PM Gabe Black via gem5-dev <[email protected]> wrote: > I think when we first split things into areas for maintainers, we just > went with the top level directories in the source tree. That was a good > first approximation, but I think it will often make sense to break things > down a little differently in practice, particularly with directories like > ext which have a bunch of stuff all lumped together. > > "misc" is sort of a catch all, when no particular category (or many > categories) fit. I don't think it makes a lot of sense to have a maintainer > for misc. Anything that falls under only that probably needs to be given > its own bucket/maintainer, and if it has that tag because it falls under > lots of categories then it's just short hand and we (probably) don't need a > special maintainer for that case. > > Gabe > > On Wed, Oct 21, 2020 at 4:26 PM Hoa Nguyen via gem5-dev <[email protected]> > wrote: > >> Hi Jason, >> >> I would like to be a maintainer of testlib, which is in ext/. >> >> I find that the codebase in ext/ itself could be broken down to several >> subcomponents as it consists lots of different projects. >> >> Also, can you elaborate what type of changes fall under the "misc" tag? >> >> Regards, >> Hoa Nguyen >> >> On Fri, Oct 16, 2020, 3:27 PM Jason Lowe-Power via gem5-dev < >> [email protected]> wrote: >> >>> Hi everyone! >>> >>> As you all are aware, we're pushing to increase the stability of gem5. >>> However, at the same time, we're seeing a significant increase in the rate >>> of gem5 changes. Between gem5-20.0 and gem5-20.1 we had over 650 commits! >>> And, that doesn't count the many changes on gerrit that never got reviewed >>> :(. >>> >>> We need help reviewing! One of the steps we're taking to help with this >>> is to assign specific maintainers to review every patch (automatically). >>> >>> There is a change on gerrit to do this: >>> https://gem5-review.googlesource.com/c/public/gem5/+/34737 Please let >>> us know if there are any comments. >>> >>> In that commit is a new file which specifies the maintainers in a >>> machine-readable format. Now, for the ask: We're looking for volunteers for >>> all of the components that are missing maintainers! Being a maintainer >>> comes with the responsibility of reviewing patches in a timely fashion, but >>> it also means that you can influence the changes in gem5! >>> >>> See >>> https://gem5-review.googlesource.com/c/public/gem5/+/34737/17/util/gerrit_bot/MAINTAINERS.json >>> >>> Specifically, if you would like to become the maintainer for any of the >>> following sub-components, simply reply to this email! Additionally, if you >>> have suggestions for other ways to break down these components, feel free >>> to comment on the changeset linked above. >>> >>> - arch-mips >>> - arch-power >>> - base >>> - cpu >>> - cpu-minor >>> - cpu-o3 >>> - cpu-simple >>> - dev >>> - ext >>> - misc >>> - stats >>> - system >>> >>> Have a great weekend! >>> >>> Cheers, >>> Jason >>> _______________________________________________ >>> gem5-dev mailing list -- [email protected] >>> To unsubscribe send an email to [email protected] >>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >> >> _______________________________________________ >> gem5-dev mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > _______________________________________________ > gem5-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
