Work plan prpoosal for the next year

[Eric S. Raymond]

James Browning via devel <devel at ntpsec.org>:
> I do not consider myself an expert C developer.

You're good enough to contribute materially to *this* project, which
is by no means the easiest C gode to grok.  That makes you expert in
my book.

> I think the proposed schedule is overly serial. ntpkeygen and keygone
> for example have no dependency on pylib/ IIRC. Also none of the other
> ntpclients/ depend on ntpq. This would (in theory) pull CLIENTS up to
> month 5 (late November/December)

I was deliberately vague about the subproject dependencies and what
can be done in parallel, because the point of this document is a
scope-of-work estimate that might get us some money for things like a
hardware test lab.  Also it would be nice if Ian and I could pay our
rent and grocery bills while we're doing the Go port.

If this work plan looks like it'll fly I'll do a more detailed
dependency chart.

> I think the open 'issue' count would be lower if people actually
> tended to close issues.

Agreed.  I occasionally do a triage pass to catch these.  I guess we're
due for one.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>