On Thu, Oct 14, 2021 at 2:28 AM Nathan Hartman wrote: > On Tue, Oct 12, 2021 at 12:49 PM Gregory Nutt wrote: > > > Matias N. made some progress before; > > > Unified device interface, callback based initialization and devicetree > > > (DTS) · Issue #3031 · apache/incubator-nuttx (github.com) > > > <https://github.com/apache/incubator-nuttx/issues/3031> > > > [RFC] Using devicetree (DTS) to improve board support · Issue #1020 · > > > apache/incubator-nuttx (github.com) > > > <https://github.com/apache/incubator-nuttx/issues/1020> > > > > The conversation that I was trying to initiate here is NOT whether these > > features are good or bad, but to propose a way to create a feature road > > map for the OS. Through the established voting process we can determine > > in advance whether features are needed by the community or not. > > I think we need 2 CWIKI pages: Wish List and Road Map. > > In Wish List, everyone can go and propose whatever features they'd > like to see someday. There's no guarantee any of them will be > implemented, but could serve to get the ideas flowing. > > Wish List ideas that gain traction become a [DISCUSS] thread where > details are hashed out and arguments made, leading to a [VOTE]. > > Items voted Yes move from Wish List to Road Map. > > Items voted No go to /dev/null. > > Rinse and repeat :-)
I am not really familiar with CWIKI sorry. I turned all my wiki into MarkDown files and/or WIKI being part of the repository. Having separate CWIKI may be easier to use with no mess in the repository, in that case GitHub offers WIKI and that would be all-in-one-place approach (easier to find and maintain). In addition GitHub WIKI uses MD format and it may be easier to copy paste some text into respository. GitHub also introduced DISCUSSIONS where wish list ideas could be introduced, when accepted transferred to WIKI WishList, and then to the RoadMap if voted up by the developers community. Again this is all-in-one approach that makes work easier to maintain. I saw 10.2 release discussion. Release Notes could be part of GH WIKI, then copy-pasted into release message (uses MD formatting). Also having ChangeLog file directly in the repository is good for tracking changes and progress of the project (also uses MD formatting). > > This prevents misconceptions that arise because a few people are very > > impassioned and vocal but do not reflect the majority. This may happen > > if the majority are less vocal. The vocal minority can lead in a path > > that may not be preferable to the silent majority. Voting gives a voice > > to everyone. > > > > Similarly we can identify features in advance that ARE needed by the > > community and make that need visible to potential implementers. > > > > If we had such a feature roadmap, we could more easily coordinate the > > evolution of the OS in an orderly fashion. > > Agreed. Furthermore once there's a roadmap that looks reasonable, I'd > propose to put it on the NuttX website. Or this could be simply GH WIKI (simpler to maintain closer to the source code) or copy-paste (more work to maintain). Have a good day folks :-) ps/2: Some folks moved away from GitHub to GitLab (open-source) after Microsoft took over GitHub. Migration is easy, both use MarkDown formatting. This may be important for risk assessment if someone considers GH a single point of failure. Both platforms git can be synchronized too. I am not sure about Issues/Wiki though. -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
