On Tue, Aug 26, 2025 at 5:15 PM Matteo Golin <matteo.go...@gmail.com> wrote: > Was browsing the issues today and noticed that there are currently two > projects on our GitHub page for tracking issues: > one for NuttX in general and the other for GSOC. > > I was wondering what your opinion would be of adding a project as a roadmap > for the RPI 4B board support. It's quite a > complex board (being a mini-computer) and there is still quite a few > peripherals that need implementing and testing to > be performed before it can be marked as not experimental. I thought a new > project on the GitHub might be helpful to > track what still needs to be done and maybe draw more attention to it from > contributors. > > Not to sound like a broken record, but I personally think if NuttX on the RPI > 4B can be made somewhat stable/pretty > complete in its implementation, it would draw a lot of new users. Virtually > every hobbyist I know uses an RPI. It's also > pretty well-rounded for testing audio and graphics implementations on NuttX. > I would love to see more students get > involved using NuttX and I think supporting mid-range hobbyist boards is a > great step. > > Let me know what you think!
Hey there Matteo! :-) All RaspberryPi devices are very popular and important to support by NuttX :-) Thank you for all of your contributions!! :-) I like rPI 0 2W most, its kinda rPI 3B, but tiny, cheap, and powerful enough to run big OS :-) But this "GitHub Projects" application name is really confusing. I would call it "dashboard" or whatever else not to mislead with, well, git hub project repository o_O You know, you say "NuttX GSoC" project and everyone instantly want to search for that repository, not a "Projects" tab under "NuttX Repo" that leads to Apache projects anyways but contains only few manually added issues from NuttX repos, its totally simple right? :D :D :D All this only tracks existing Issues from the NuttX repo (and Apps and Website). So the issue have to exist in that repo anyways. Its just a way to put several issues together in one place, maybe show which one is first, and what are sub-issues. And all this has to be done manually by hand with every issue. And its not really clear enough to provide any sort of useful structural insight. You cannot even split issues into groups, or by label, create new task types, there is only "tasks", "todo", and "roadmap" views with zero customization. Nothing has changes in several months and probably won't. I guess its just to hire someone in a big company to copy paste issues from repos to "github projects", so someone can be "gihub projects manager", what a fancy name! I started this as experiment, just to see how it works, but I am disappointed. I still don't know how to mark things on the timeline :-P Do you think its working okay and is useful anyhow? https://github.com/orgs/apache/projects/455 We may sure create a separate "project" for "NuttX / rPI 4B". But we may also create more generic "NuttX / RaspberryPi" where all rPI issues would be gathered? That would be more clear but not relate to other ongoing works in NuttX. Or we may put this under current NuttX dashboard (link above), with other "top level issues", and just mark this top level issue as "NuttX / rPI 4B" and then you could link other sub-issues to that top level issue? That would relate to other ongoing works in NuttX but may not be clear to read. You may want to create a "Projects" and see yourself how / if that works for you? I am not really happy with this application myself to be honest, it seems messy and counter-intuitive, but I tried my best, maybe I just don't understand it, maybe it will disappear in several months :-P -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
