I have one massively off week and everyone's floating around the place (including the holder of my roogroup account who may fix that for me in the next century).
A) No, I'm not burnt out. I start the AWN an hour early (playing with bugs and QA LISP(Not done with QA)) and then run a final update midnight (or within five minutes after). Now the thing is, this week, I ran off with Cubby at about 10:30 for a casino run (I had forgotten last Sunday that last Saturday I promised to head out with him LISP(In my defense, he was very inhebriated at the time and had a 50% chance at best of remembering)), so, I got back around three, did some chores that I wasn't going to be up early enough for, set TiVo for M*A*S*H and the Packers game (football really can be compressed into one hour), and got back to the AWN around six (no updating). B) I follow much of what Jesper had done because I like it. The table colouration is nice, the format is simple and it flows nicely on most screensizes. As for separate versions for updating (i.e. perhaps a awn117b.phtml), I'll probably make that decision at the last minute. C) I didn't believe someone would mistake the document type definition for a url; however, I could see how that might happen, so, I'll include note. D) XML is not proprietary, AWML is. Proprietary (despite how we typically think of it) does not mean closed source, it means for specific us (like copyright, you don't actually have to trademark/patent your format to ensure it's yours). Proprietary is the correct term, and if you doubt that, ask the good (ha) folks in #gimp (some of whom never heard of this GNU Image thing ;o). E) Some text doesn't need updating (like the special interest), though, it was brought to my attention that I completely ignored the hackdown. The only thing being, text or no text, I don't all that much happening there (hub, re-assign it to Mark, so, he can owe dom $20 by his twisted version of what he meant in that bet). F) The reason for the drawn out bugs is two fold. 1) It makes up for a lack of bug graph (but I'll still find a place for Frank's e-monk), and 2) I intend to integrate more QA information, such as, "If you see a bug you've reported or had in RESOLVED, please test to see if the issue has been repaired so it may be moved to VERIFIED," in an effort to encourage reporters to do that more theoretical part where they participate throughout the process. G) WV/DTD/WP, acronymically correct love, I'll include more information for all these lovely things, (what, Mozilla can't display a DTD!) H) Future versions of this email may contain an H It is nice to get feedback. Sorry for not having been in chat, but less than five minutes after the emails went out, I went to bed. Use the QA Contact field and we can ALL be happy (I was SO not going to through "the long list" at the crack of dawn, but I was willing to do it at the stroke of midnight LISP(Well, actually, I was listening to "The Devil Went Down to Georgia" at the time, but I meant in a "looking ahead kind of way"). I probably will go through it tonight/tomorrow for the updated version (which will be ready Monday evening, dom-time). As for burn out, it's just not going to happen. Especially when I do the discussions; there's just something magical about that.... Matthew, you and I should talk about a few more things within the next week; I'll probably email tonight/tomorrow; thanks for the feedback. Alan, start a small business and move out ;o) "And for the rest of you, keep your stick on the ice" -RG O Canadia, our home and native land, where the meese are free and you always keep your stick on the ice -Zen
