Re: Work plan prpoosal for the next year

2021-06-29 Thread Eric S. Raymond via devel
James Browning via devel : > 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 >

Re: Work plan prpoosal for the next year

2021-06-26 Thread Hal Murray via devel
I don't like it much. > Our major objective for this year will be to move the NTPsec codebase from C > and Python to a single memory-safe language. I think that restructuring is as important, maybe more, than switching languages. > There is now a better alternative: the Go language. What

Re: Work plan prpoosal for the next year

2021-06-25 Thread James Browning via devel
I do not consider myself an expert C developer. 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 thin

Work plan prpoosal for the next year

2021-06-24 Thread Eric S. Raymond via devel
Developers, please weigh in on this so we can finalize it. The final version will become part of a grant proposal which may get us money for a hardware test lab and code bounties. = NTPsec work plan This is a rough-draft work plan for the NTPsec project over the period July 1st 2021 to July 1st