cederom commented on PR #8924:
URL: https://github.com/apache/nuttx/pull/8924#issuecomment-1489508949
> @patacongo: We really need a published roadmap if where we are and where
we want to go. I worry about _ad hoc_ solutions that are not based on a long
term, POSIX compliant roadmap.
I usually do a simple TODO list with points and subpoints and subpoints for
eatch project in a simple wiki style MarkDown (example below). Then I know what
needs to be done, who is working on it, how much time it cost, what are the
reference pr, etc. This is a really simple file easy to edit. Things may pop up
there as discovered by new (sub)tasks. And it is a good reference point /
worklog in future. It makes vision, planning, implementation, and accounting
easier :-)
Maybe this could be implemented for NuttX (either as part of the source code
text document, or GitGub wiki, or project wiki)?
I know there are tools like Jira.. but the general roadmap should be easy to
read and containted in one place easy to edit / update.
If there is a consensus on how to implement such roadmap I could help in
creating / updating one just let me know :-)
# TODO / Roadmap
* Kernel.
* [ ] implement pid + gid assignment to process inherited by uid/git of
the launching user.
* [ ] commit.
* [ ] testing.
* [ ] implementation.
* [X] design discussion.
* Application.
* [ ] implement `su`.
* Bootloader.
* [X] fix some bootloader stuff.
--
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: commits-unsubscr...@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
