On Tue, Mar 24, 2015 at 2:31 PM, Lorenzo Colitti <[email protected]> wrote: > On Tue, Mar 24, 2015 at 4:02 PM, Dave Taht <[email protected]> wrote: >> >> My basic request was basically that everyone on homenet dogfood what >> exists (hnetd, babel) to see all the real problems renumbering induces >> on their networks, their printers, OSes, and devices like file >> servers, audio gear, roku, any of the thousands of devices now >> available that semi-support ipv6, etc. Go have a shopping spree on >> amazon. > > > It would be great if there were an easy-to-follow recipe on how to do this > (what to buy, how to install it, etc.)
I have generally found that the best way to get good documentation is to couple the core developers of the software with new users, while recording (video or audio) the results, and/or while taking extensive notes. Usually major improvements to the software AND documentation quickly emerge. It is often best to do that at a face to face meeting, over beer, when one could be arranged. Often it takes a dev exposure to many new users to understand what their expectation and abilities are. The only company that has done this sort of usability study right recently is Apple, IMHO. F2F while taking notes works really, really, well. I had hoped this ietf that could happen. A lot of what has gone wrong in the world (not just in software, but in the design of aircraft and other pieces of hardware) is that everyone seems to have forgotten "kelly´s rules", particularly rule 9 with the folk doing the spec completely disconnected from those on the factory floor. http://www.lockheedmartin.com/us/aeronautics/skunkworks/14rules.html As for the recommended hardware portion of this problem, let me try that in another email. > >> To me, making wifi work better - given the projected >> growth in it over the next 4 years in the 10 billion device range - is >> far more important than ipv6 is, right now. > > > People saying "$PROBLEM is more important than IPv6 right now" for 20 years > is why it's taking 20 years to deploy IPv6. :-) Touche'! However my own skills are best applied to wifi now, and the growth rate of wifi exceeds that of ipv6 also. We don´t break ipv6 along the way as we treat it as a first class object in all our testing. -- Dave Täht Let's make wifi fast, less jittery and reliable again! https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
