I'm back from vacation, had alot of fun in florida. most good. on the down side, i seem to have caught some virus on the way home or something, cause i've had a quesy stomach all yesterday and continuing today. not fun at all.

gaim
faceprint and chipx86 kept the tree in sync with gaim's main tree and got things mostly usable. one annoying bug with multiple accounts left on the online tab, and of course gtk styles continue to be a pain, especially in the tooltips. Sean decided he wants new dialogs that i write to be in gtk2, not gtk1.2, so faceprint and i have to start the blist editing work part way over again. given that neither of us know gtk2, and that i'm not all that great with gtk1.2 even, this will be non-trivial. not too much seems to have happened with gaim's main tree, at least not as much as i'd hoped based on some of the things sean was saying before i left. The new preferences are finally in place, but they have significant bugs. That's what happens when you code something in isolation, it just doesn't get the testing it needs. BUT, that's why we have cvs, and why we haven't released 0.60 yet, that and the fact sean wants the 0.60 release to coincide with the next trillian release.

I saw chipx86's article, and i have to agree with him for the most part, though i'm certainly guiltly of falling into mini-holy wars more often than he is. in the end, what i MOST agree with is the reply complaining about the lazy users and the way they ask for help. Before my vacation, i respond to a significant portion of the help requests that hit #gaim and the source forge bug tracker, support tracker, and forum. a recent example is perfect for several reasons. a user posted an inflamitory "bug" report yesterday. its a report that duplicates 10 or so previous reports, 3 of which had been marked as "invalid" in the past week or so. as i said, i'm not feeling well, so irritably, i responded very harshly, i'm not proud of that. fortunately it was a reasonable perosn on the other end, and in a series of posts, he came to understand why we don't consider it a bug, and how my work on person support will remove the issue anyway by 0.61 or 0.62 depending on how fast faceprint and i can get the blist editing working. (both numbers assume current release rates, not the 2 week schedule we used to have), but it goes to show how easily people forget that thier personal uses of a project might not exactly correspond with how developers see things, and also how easy it is for people to fall into insulting when they meet less clued people.