Hi, If help with code review is still needed, I'd like to volunteer for that work. I can help with changes that touch arm64, risc-v and especially the memory protected modes (CONFIG_BUILD_KERNEL) / address environments.
You might know me as pussuw on Github. Br, Ville Juven ________________________________ From: Nathan Hartman <hartman.nat...@gmail.com> Sent: Friday, September 6, 2024 3:23 AM To: dev@nuttx.apache.org <dev@nuttx.apache.org> Subject: Re: Help wanted! Hello Matteo, Thanks! I don't think we have documentation on exactly how to review PRs. Right now, I guess it's just a process of picking a PR, reviewing the code, commenting on any issues that might be found, etc. I guess it's just using your best judgment and if in doubt, feel free to ask on list! Cheers Nathan On Thu, Sep 5, 2024 at 9:24 AM Matteo Golin <matteo.go...@gmail.com> wrote: > Hello Nathan, > > I'd be interested in helping out where I can. Is there a list of > steps/processes that normally go into a PR review so that I could reference > something while reviewing to make sure I don't miss anything important? Or > is the review process more on a per-PR basis of deciding what to check and > how much testing should be done? > > Matteo > > On Thu, Sep 5, 2024 at 7:27 AM Nathan Hartman <hartman.nat...@gmail.com> > wrote: > > > Hi folks, > > > > Help wanted: > > > > The number of open PRs is usually around 80-90, but recently that > > jumped to around 150-160!! > > > > Only a few people are reviewing PRs, so the backlog is likely to > > continue growing. > > > > We need your help with reviewing! > > > > Also, if you have open PRs that are not ready for review, please > > consider marking them as "Draft" to help the reviewers focus on PRs > > that are ready. > > > > Thanks! > > > > Nathan > > >
