This is my report on my activities related to the Mozilla Foundation for the week ending June 22, 2007.
Projects for the week
Here’s a partial listing of what I and others did this past week:
Grants and related activities. Eitan Isaacson completed the intermediate milestone on a project we’re funding to complete development of the Accerciser accessibility test tool. (This work supports our efforts to improve accessibility for Firefox on Linux.)
Next action(s): Evaluate a funding request for sponsorship of a developer workshop (Mozilla-related but not Mozilla-specific). Do a blog post summarizing our accessibility-related efforts, as well as a brief meeting report on CSUN and G3ICT.
IP/legal issues. I worked more on internal legal issues.
Next action(s): Work with the SeaMonkey Council and others on appropriate policies for the SeaMonkey trademarks. Work more to get the contributors agreement moved forward.
Other. While we were out in Mountain View last week David Boswell and I met with a number of different people; thanks to all who took time to talk with us. Topics discussed included the Foundation and Corporation grant programs, the various mozilla.org web sites, the Mozilla Store, and other areas the Foundation is involved in today or might be in the future. More on these in future.
For more information see the weekly status reports published by other Mozilla Foundation people:
- I’ll be out of the office on Monday, June 25, and won’t be participating in the weekly Mozilla call.
- I’ll be in Atlanta on July 2 to speak at the annual meeting of the National Federation of the Blind in Computer Science.
- I’ll be on vacation July 3 through July 6.
- I’ll be attending at least part of OSCON 2007 July 23–27.
- I’ll be in Boston on July 30–31.
When I was in Mountain View last week I stayed at the Hotel Avante on El Camino Real. It was a nice hotel (and relatively inexpensive by Silicon Valley standards) but it had one major drawback from my perspective: The hotel wireless network apparently not only does transparent proxying of web traffic, but also attempts to do the same thing for outgoing SMTP mail traffic on port 25. This may not bother most people, but in my case I have a very specific SMTP configuration that uses password-based authentication over TLS to my “home” mail server. Needless to say this got totally bollixed up, and I didn’t have the time and inclination to try to get the configuration working properly. I guess the world is telling me to forget this whole IMAP/SMTP thing and just use Gmail.