> Alternativelly, we can start making a raw list of improvements
> and issues that need to be addressed and we can work from that,
> which it seems to me that should be easier to prepare than a
> full proposal. Whatever works best for you.
I think an even easier approach is to work incrementaly so that it's not too much effort spent if at anytime one of my proposal doesn't fit the needs and I need to revert to the previous proposal.
I've already started something on my personal wiki and plan to send you a 1st proposal in PDF in the next few days. My goal is more to spark discussion than to have it accepted at 1st try :-)
Anyway, I'll also surely benefits from a raw list of improvements and issues. Please feel free to throw your idea here or wherever you want. In the mean time, my current list of possible improvements and issues is currently the following:
both places have their value and serve a different purpose:
a large source of redundacy in the documentation comes from the fact that we have
POD docs in our tooling. We should better link to manpages.debian.org
That's all I know for the moment.