Now that I've got a few DIP reviews under my belt, I've got a
good enough handle on the process to lay it out in documentation
form. To that end , I've kept the general structure that
Dicebot initially set down, changing the details to better
reflect my view of how it should all work (I still need to update
the existing DIPs to reflect a couple of changes). I've also
revised Dicebot's guidelines on DIP writing . Much of his
original advice is still there. That document is sure to evolve.
Feedback on all of this is welcome.
While I have your attention, Sebastian recently revived an old
DIP on in-place struct initialization. I invite everyone to come
and give feedback on that , but *please* read the updated
README before doing so, particularly the section titled 'Review
Process' so you can fully understand what's expected of reviews
at this stage of the process (what I now call the 'Draft Review'
stage). I haven't looked at it yet, but I expect to do so next
I still need to review the recent updates to Zach Tollen's
proposal  (Improve Contract Usability), and if all checks out
I'll be merging it as DIP 1009. You can expect the first review
round shortly thereafter.