|
Status Updates
We are looking for a Mozilla community member to maintain these status updates on a regular basis (weekly or every two weeks.) This would involve keeping an eye on Bugzilla, Bonsai, the newsgroups and Mozilla-related websites, and summarising the interesting events on a regular basis for an audience of thousands :-)
1.3
The Mozilla 1.3final release is approaching, and is now on
its own branch. QA contributors are requested to keep testing the branch right up until release, to avoid another 1.2.1-style situation.
OS/2
mkaply says that there are two major things on the OS/2 horizon:
- "We are switching away from VACPP(IBM compiler) to GCC
(bug 177799). Over the next few weeks there will be checkins and we will be switched to GCC completely by 1.4a.
- We are hiring Jonas Sicking as a co-op for a few months which is pretty cool."
Calendar
Mike Potter says (summarised):
"On a trip to South Carolina last week, I did two presentations at the College of Charleston, South Carolina. This is because a group of students will be working on the calendar project, as part of their 4th year computer programming course. The students will be working on one of the following projects: redesign the week view, implement a new date picker (that can be localized), implement a new time picker (that can allow text input, and be localized) and allow color coding of tasks and events based on the calendar they are in (as in Apple's iCal).
For the calendar project in particular, I think we are in a pretty good state right now. I've removed the features that don't work, and have been concentrating on firming up those that do. We still hope to land it on the trunk in the 1.4 cycle."
Rhino
Rhino is Mozilla's JavaScript implementation in Java. Norris Boyd writes:
"We're getting ready for 1.5 Release 4. See the
description of the new features and fixed bugs."
Staff Meeting Minutes
In the interests of transparency and accountability, minutes of mozilla.org staff meetings are now being posted in the newsgroup netscape.public.mozilla.seamonkey between three days and a week after the meetings. Although for confidentiality and security reasons, they can't contain everything that is discussed, staff hope that people will find them interesting.
|