What next?, Big picture

[Hal Murray]

This is what I've been thinking about.

What do you want to do and/or what should we work on?

---------

1) Convert everything to Go or Rust
  From recent discussions, this seems to be on the back burner.
  I'd like to learn more about Go, but don't have a good plan/excuse.
  Does waf support Go or Rust?
    Is there some utility (ntpq?) that we could convert to Go?
  There is NTP work in Rust.  I haven't investigated.

2) Port to Windows
  I know next to nothing about Windows.
  Anybody know anything about POSIX on Windows?
  Is there a good book/whatever to get started?
  Does waf work on Windows?
  Does Gitlab CI have a Windows option?

3) I'd like to build a fast server.
  (It's just the sort of hacking I like to do.)
  A server with nothing else is actually pretty simple.
  With threads, a good workstation can keep up with a gigabit link.

4) Split up ntpd
  Client, Server, info/monitoring, refclocks
  One layer deeper, this means using threads
  and separate sockets (and port numbers) for each server
  so they don't need to use the main socket (port 123)

5) Clean up info/monitoring
  I don't have a detailed plan.
  I think I want to put the data into shared memory.
  I think we need a file to describe the data
    and programs to turn that into a header file
    and whatever ntpq needs

6) Clean demo/sample SNTP client
  I'd like a clean, well documented sample SNTP client that people can copy
  The idea is to try to reduce the crap that servers have to support.
  [Probably separate from our main code.]
 
7) Testing/support plan
  It would be great if we had a list of things to test before a release
  and/or a list with dates and names when they were last tested.

-----------

There are a bunch of medium and/or small items in devel/TODO and gitlab 
issues



-- 
These are my opinions.  I hate spam.