Conversation with my sister.
oh i just remembered you were in my dream this morning
we were about to have some coffee in a car or something and then the fire department stopped us and said we could not drink in the car as it was a choking hazard and they took our coffee mugs and water bottles
And I cried
Then i tried to twitter about it in outrage but couldn’t get my twitter app to work
we were both going “this is bullshit! and we haven’t had our COFFEE!!!”
i had a whole pointless fantasy this morning that i was taking a watercolor class from this guy who only paints half naked women. so in the workshop i waxed poetic about painting mens balls and how important it was to get the effects of light glinting off ball hair.
needless to say i will NOT be taking that workshop
i considered taking the workshop and actually doing this. but quickly discarded the idea.
also: white guy: mostly painting partially clothed women of color gazing into the distance. probably/hopefully plotting his death
I really thought my crying in my sleep about firefighters stealing my morning coffee was going to win some sort of award for ridiculousness but the waking dream of telling off a real life annoying art teacher eclipsed it.
David Baron wrote an interesting post recently, Moving bug history out of the primary display of a bug report. I have noticed this problem in Bugzilla, that even if a bug is “ready to be fixed” or has patches submitted it is necessary to read through 5, 10, or 50 comments to understand what is supposed to happen next (if anything). dbaron proposes that the main page of a bug report should show its current state. What is true about it? And what is to be done next? This would be obviously awesome for some bugs, but not for others for which there isn’t a clear state of truth. My first instinct is to question dbaron’s idea, as there might be bugs for which the conversation is the most important aspect.
For example Bug 130835 – Make Bugzilla’s index.cgi (home page) useful for logged-in users has over 150 comments, stretching back 10 years. Here the problem may actually be that the bug (or enhancement request) was not well defined in scope, so had no clear end. It might be worth untangling the useful ends of these 150 comments to close this bug, and open several new and more specific ones for which “current state” *could* be summarized as dbaron suggests.
But what about a bug like Bug 83192184 – Make the plugin click-to-play UI look less like ‘plugin broken/crashed’ UI , where there is a useful active conversation? In that case trying to synthesize the conversation at every step of the way, each time someone comments, is probably not useful.
So in some cases there is clear “current state” or content, as there is on a Wikipedia page, but in some, the conversation is the content. I don’t want to have (or read) conversations in a Bugzilla equivalent of Wikipedia talk pages and am not sure that would be an improvement on the current state of Bugzilla comments. For bugs with a long history, especially ones which have mutated significantly since their beginning, the “current state” field might be an easy way to untangle the mess.
2nd exercise –
had name brainjam before knew what it was.
all my life trying to help people connect the dots, help them move forward, omg have you seen this book, do you know this person? I get a big jolt to help peple connect with each other in that way. so, people oudl jam in a one on one situation. how migh that look? j split up rgroup of peopel in 2 halves, segment. inner circle facing out, outer facing in. 12 five minute meetings with each other.
(i know this as a rotating fishbowl. the other fishbowl is a discussion in the inside and the outside peopel have to only listen.)
ask each other what work ignites your true passion?
Vanessa A. Smith
(to be filled in later from notes)