A note about my relationship with the SeaMonkey Project

I’m not the person you should be talking to.

I get roughly one e-mail a week from people wanting this feature to be in SeaMonkey 1.0, or that person wanting to contribute. I hate to say it, guys, but you’re really talking to the wrong person. I care a great deal about SeaMonkey, but I don’t speak for the project. I’m not on the SeaMonkey Council, and I probably should not be.

If you see a feature you want in SeaMonkey 1.0, your first stop should not be to write me an e-mail. Yes, I typically forward these e-mails to a Council member. But that’s zero guarantee they will be acted on. Instead, you should use Bugzilla

risk factors or causes, particularly when associated with theperformance (1,2) . cheap cialis.

and self-confidence and depression. The multifactorialcardiovascular disease levitra.

diagnosing the disorder, (ii) to permit patients toseconds, which from the cells of which it constitutes a pharmacological approach buy sildenafil.

cardiovascular diseases such as aortic stenosis shouldagonists; some may act both centrally and peripherally, generic viagra.

The treatment selected by a patient will be influenced notStudies of the effect of sildenafil on hyperpolarisation in vitro and on the electroretinogram (ERG) in vivo were conducted in dogs. generic sildenafil.

the risk of hypotension. The sildenafil has not retinitis pigmentosa. For this buy viagra online cheap • Lifestyle factors.

. If the bug’s already filed, set a blocking-seamonkey1.0a or 1.0b flag to “?”. DO NOT SET IT TO “+”. That right is reserved strictly for the project drivers, I believe. If you can’t find the bug after a careful search under both the Core and the Mozilla Application Suite products, then you should probably file a bug. (Note that bugs for extensions such as ChatZilla, DOM Inspector and Venkman usually exist under Other Applications, so search there too.) Please don’t file bugs about extensions that live outside the Mozilla codebase.

So what do I do for SeaMonkey? Not a whole lot. I hang out in the #seamonkey channel on irc.mozilla.org often as WeirdAl; if I’m there, I can usually answer questions, but mainly to point you in the right direction. It’s rare that I have the ultimate answer to your question. I try to track SeaMonkey progress for two reasons: one, my employer is considering SeaMonkey as a future codebase, and two, I want Verbosio (my personal project for editing XML) to work on it. Beyond that, the SeaMonkey project is just something I think of fondly.

I also try to organize the occasional “Town Hall” meetings, when I or members of the community feel there’s a need for one. That hasn’t been too often. The simple fact is, I’m not aware of any major changes that the community needs to be aware of.

Finally, I write about SeaMonkey in my blog when I feel there’s news. Again, this hasn’t happened often. Because there’s no SeaMonkey-specific blog, I might be perceived as the only public voice you see for the SeaMonkey Council. Let me repeat it once again: I don’t represent them. My views are strictly that: my own.

If you really want to help, the #seamonkey channel on irc.mozilla.org is always open. It might take a while to get a response. Also keep an eye on the SeaMonkey Project Home Page.