linguini1 commented on PR #18397: URL: https://github.com/apache/nuttx/pull/18397#issuecomment-3910032749
> This is quite clear to me: most of the feedback here is valid and I agree with it. That said, I'd like to raise a broader point. Many of you are experienced not only with NuttX but with RTOS development in general. Have you considered how many developers stay away from NuttX simply because the learning curve is steeper than it needs to be? It took me nearly a year to feel comfortable with this system — and that kind of friction keeps good contributors out. It is definitely an issue; there is a learning curve to be able to contribute to NuttX as well as just use it. There are ongoing efforts to try to fix that (i.e. pushing for better documentation, pushing for better quality in PR requirements, etc.) but it is definitely an ongoing battle. This is why the project really appreciates contributors like you! Your feedback is really important to making the experience smoother (this PR already found some ways we could improve). > I'm not saying my approach is correct. But I am committed to pushing NuttX in a direction that is more accessible, alongside the technical quality it already has. This PR was never just about the board port — it was also a proposal for a conversation. And I think it was a good start. While it I'm fixing what I can fix. Thank you for your time and feedback :) It's great to move things in a more accessible direction! However, as an Apache project, there is some "red tape" for doing so. Major changes are meant to be discussed in the mailing list first (mostly to avoid wasting a contributor's valuable time spent on a change that the community has suggestions for) in order to collect community feedback/find as many possible stumbling blocks beforehand. For instance, as raiden and Alan mentioned on this PR, although the different directory structure isn't necessarily "wrong" or "bad" on its own, having multiple different standards in the repository makes things even more confusing for newcomers. As mentioned, your ideas are always welcome! If you think there is a better layout for the `board/` tree, please start a discussion on the mailing list! As raiden said, that change could be helpful if we can migrate multiple boards at once to your proposed format (that way there isn't a mix of differing standards in the tree). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
