s/he/here/
On 3/8/23, Alan C. Assis <acas...@gmail.com> wrote: > Hi Sebastien, > > Yes, that commit list is mostly for people who don't want to use > github but still wanting to see what is going on. > > Sometimes when a very important PR raises some concern on GitHub PR, > people post their concern he, it already happened many times. > > But again: the best way to guarantee that current changes please you > is to keep actively reviewing the PRs and contributing to the project. > > BR, > > Alan > > On 3/8/23, Sebastien Lorquet <sebast...@lorquet.fr> wrote: >> Hi, >> >> I had a look and this mailing list is not made for human consumption. >> >> No one has ever sent a message on it manually, right? >> >> In practice, important changes are still NOT discussed on the DEV >> mailing list. >> >> You said yourself that "all development has moved to github". >> >> As soon as automated tests are passed, every commit is considered with a >> similar level of importance, however this is clearly not the case. >> >> Sebastien >> >> Le 08/03/2023 à 13:21, Alan C. Assis a écrit : >>> HI Sebastien, >>> >>> It is already done, you just need to subscribe to >>> https://lists.apache.org/list.html?comm...@nuttx.apache.org to receive >>> all commits messages and discussions. >>> >>> Everything is archived on apache side! >>> >>> BR, >>> >>> Alan >>> >>> On 3/8/23, Sebastien Lorquet <sebast...@lorquet.fr> wrote: >>>> Apache projects are required to use mailing lists for long term >>>> archival >>>> purposes. >>>> >>>> It seems to me that this project is avoiding that rule and moved all >>>> development to github >>>> >>>> This is in contradiction with the Apache project rules. >>>> >>>> >>>> I request clarification on this situation and requirement (instead of >>>> just asserting it), including a review by the apache boards. >>>> >>>> >>>> If it is proved that development happens primarily in github and not >>>> here I will request the following: >>>> >>>> -every people committing patches and submitting pull request to be >>>> registered on the mailing list so they are able to reply to questions >>>> >>>> -forwarding of all pull requests traffic to the mailing list >>>> >>>> For two reasons: (1) Archival purposes, and (2) open discussions with >>>> members that follow Apache Foundation mailing list rules and do not >>>> take >>>> part in github. >>>> >>>> >>>> Thank you >>>> >>>> Sebastien >>>> >>>> >> >
