VyConf can handle set/delete/commit operations.
Client libraries can interface with it (Python only for the beginning).
At this point we can see how the design works and fix config opeation problems before they get into application code.
Point of no return for: config operation fundamentals, shell top level commands.
Early integration attempts. Good candidates should have a simple config format and built-in warm reload capability: dnsmasq, IGMP proxy, ...
At this point we can see if client API design is any good and fix it until it gets into heavy integration code (IPsec, firewall etc.).
This can be done on any target platform with manual installation/git pull of everything.
Point of no return for: client API, config operations details.
Base OS selection and image build procedure development.
At this point we can make an image with some basic features, ready for expansion.
Point of no return for: base OS choice.
Missing feature development.
At this point we can add what is missing and have a complete operational system.
Point of no return for: everything mentioned before.
<sarcasm>Starting another rewrite<sarcasm>
Incremental expansion and maintenance.