On 25/01/16 12:29, Martin Lucina wrote:
Apart from the unresolved question of the JSON parser and rumpconfig dependencies on libc interfaces, is there anything else that's fundamentally blocking this work being merged to master? Specifically, notwithstanding the current implementation (which can be changed), is there anything unacceptable about the specification as the future *public interface*?
The problem, at least for me, is that the proposal is too massive for me to manage to put enough time aside for to process atomically and reach 100% confidence that I thought of everything that I possibly could. Therefore, it goes on the pile of "I can get something done today or I can write one email". It's easy to guess which one wins ... sorry :(
Can we do a divide and conquer discussion where we go over the top-level spec blocks -- just them completely ignoring the implementation for now -- one-by-one in separate threads?
The other approach I can propose is that a few dozen people start shouting comments. IOW if 90% thinking is 10% of the work, with 20+ people we'll reach quite a high probability that all bases were covered. Of course, that depends on a few dozen volunteers on this list ;)
After we get the spec nailed down, let's take it from there and figure out the other points in order of diminishing carved-into-a-rock-ness to get your revamp into the tree.
Assuming we don't get dozens of commenters overnight, can you start by posting the first thread, and a new one every two-or-so days after the comments on the previous thread die down?
It's always difficult redoing something because you need to be sure it's better than the left-handed first attempt :/
