[Toybox] Proposal for TODO items and progress tracking
Conroy, Bradley Quentin
bconroy at uis.edu
Fri Jun 5 23:30:43 PDT 2015
For the remaining unimplemented commands, would it be desirable to create
a separate folder with basic stubs for each command with the following:
* URL of the applicable standard and/or man page
* toybox'ed short and long options to be implemented
* any applicable notes; such as possibly useful toybox functions
* stubs of functions in toybox coding format standards
This could go a long way toward lowering the entry barrier to competent
C programmers who are simply unfamiliar with the toybox specifics.
While I am on the issue of _adding_ a folder, let it be known that it is
not my intention that toybox go the way of busybox with commands
divided up into so many categories that it makes them difficult to
locate. I'd like to see something more like ./toys/todo, ./toys/pending
and ./toys/complete with the use cases handled by simply adding a
special line in the config section such as:
USED_BY LSB DEVELOPMENT KLIBC DEFCONFIG ...
or
select gunzip if LSB || DEVELOPMENT || KLIBC || DEFCONFIG ...
Using this type of directory structure based on completion would not
only help would-be contributors to get right to coding, but also ease
progress tracking.
Contributors wanting to code something from scratch could go straight to
./toys/todo or ./toys/pending for major cleanup or ./toys/complete to
optimise/improve an existing toy.
Progress tracking could be automatically generated based on the
directory it is in, as well as any USED_BY or //TODO lines.
R,
Brad Conroy
1433572243.0
More information about the Toybox
mailing list