So I’m home from Toronto; FSOSS was a success, and I think my presentation went well. People seemed to respond well to it, at any rate, which is all I can ask for. Supposedly it will be available online at some point, so if you didn’t get to see it in person, you should be able to before long. I’ll try to post a link over to it once it’s online.
If you did see it, I’d appreciate your feedback on it, since I get the impression I’ll be doing other presentations in the future. My wife hopes that means getting to go to interesting places where she can get a ticket and go along too. :)
I do my presentation on documentation in open source this afternoon, at 3:00. My slides are done, and I’m forcing myself not to mess with them anymore. I’m gradually ramping up my stage fright, right on schedule. Awesome.
I just downloaded an unofficial Intel Mac optimized build of BonEcho. I’m going to go install it and see what I think of it.
Not sure how it compares, performance-wise, but the Aqua UI features aren’t working all that great for me, so I’m back to the official build for now.
I’ve been pretty busy lately, so I’ve not been posting here much. I’ll be doing a presentation on doing open documentation projects at the Free Software and Open Source Symposium in Toronto this week, so I’ve been busy preparing for that instead of doing much writing. If you’ll be there, drop on by. I can use all the support I can get!
My presentation will use MDC as an example of how a collaborative, open documentation project can be run successfully.
Among the many things on my plate for documentation is this: I want to produce a number of articles providing code snippets and how-tos for extension authors helping solve assorted problems often run into as they develop. The thing is, I don’t actually know what people commonly need help with. Any suggestions?
I’ll also be poking toward making real headway on migrating the Mozilla hacking guide into MDC finally. Not sure when content will actually start showing up on MDC, but I’m poking through it to figure things out.
We pretty badly need another writer on staff at Mozilla. There’s a huge amount of documentation to be written, and while we have lots of awesome contributors, we could really use more full-time help. Anybody in the Mozilla community interested? :)
I saw this on the MacDevCenter blog and thought I should share it: FireBug Makes the World Flatter. A nice little tale of Firefox advocacy in action.
So my decision to start a push on Thunderbird documentation seems to be extra well timed, judging from the news about Eudora and Thunderbird. This is pretty exciting; I know Thunderbird will benefit from having more people thumping on the code.
I’d like to start getting some documentation work done on Thunderbird before the end of this month, so suggestions are still more than welcome!
We’ve got a new keyword set up for Bugzilla — dev-doc-needed — that can be applied to bugs that require developer documentation changes.
For example, let’s say there’s a bug “add a method foobar() to the nsIFunkyTown interface”. Adding the dev-doc-needed keyword will let the documentation team know that when that bug gets fixed, a documentation change will be required.
We writer-type folks can then watch a list of bugs with that keyword and easily know when stuff happens that we need to pay attention to.
This could be a huge help in avoiding “what, you needed that documented?” problems that come up at the last minute. So I’d like to urge everyone that uses Bugzilla to make use of this keyword so we can continue to make progress toward getting our documentation whipped into shape.
So the North Koreans tested a nuke. What do we do now? I certainly don’t like the idea of a country run by a loon like Kim Jong-Il having nuclear weapons. In my ideal world, we’d test one of our own in their country. Maybe two or three. You know, until they learn that nuclear weapons aren’t very nice at all.
Of course, in an ideal world, nobody would have them — or, more to the point, feel the need to have them.
In reality, I don’t know what to do, although something has to be done. The problem is that once a country has them, the options of ways to take care of the problem get pretty slim.
What a mess.