Here is my draft PR for a CODEOWNERS file in our repository: https://github.com/apache/nuttx/pull/16962
Already got some good feedback. If you could please take a look and see what you think about the layout/proposed use case, I will then auto-populate it from the git logs and prune it by hand to get it merged. Thanks, Matteo On Tue, Sep 2, 2025 at 3:06 AM Alin Jerpelea <jerpe...@gmail.com> wrote: > Kudos Tomek for taking this initiative > > I think we should group the issues and start on improving the highlighted > areas. > > Best regards > Alin > > On Tue, Sep 2, 2025 at 12:41 AM Tomek CEDRO <to...@cedro.info> wrote: > > > On Mon, Sep 1, 2025 at 11:35 PM Nathan Hartman <hartman.nat...@gmail.com > > > > wrote: > > > On Mon, Sep 1, 2025 at 2:58 PM Tomek CEDRO <to...@cedro.info> wrote: > > > > 4. Code owners, we tried, maybe we should retry. I like the idea that > > > > if someone contributes somewhere that means they have insight and > will > > > > help others so they will be assigned to "ownership" based on git > > > > history :-) > > > > > > Hmm, "code owners" implies only the owner can make changes, others will > > be > > > afraid to contribute. Maybe "code experts" instead? The more you > > contribute > > > to an area, the more expert you are likely to be there! > > > > Yup exactly :-) Code Gurus :-) :-) > > > > The problem is we are really small team overloaded with daily tasks > > and existing backlogs. Its a spare time tasking. Last time we tried > > that people were afraid to take even more work on their head and I am > > in the same situation :-P > > > > But its more like who can we ask about specific subject, or take a > > look at changes, or ask for hints, not necessarily take responsibility > > and burden of all of the work to do for someone :-) > > > > I like the idea to identify based on past contributions. But how to > > implement this? :-) > > > > -- > > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > >
