Mozilla Status Updates
Saturday June 10th, 2000
The Mozilla status update page, now maintained by Chris Blizzard, is a great resource to catch up on the state of Mozilla development. Old updates are archived, so you can see Mozilla's progress over time. The updates occur every two weeks, and this week Chris has updates from the XPToolkit, Mail/News, "Gecko XML+DOM", Composer, "Necko/Imglib", and OS/2 development groups, as well as status updates on the Mozilla Architecture meetings.
you can see from te uodates, the the module owners send status updates *every* week. Would be nice, if the page updated weekly as well.
Couldn't this process be automated somehow? I don't have anything against Chris handling it, but I'm wondering if it could be more up to date all the time?
It could be a kind of news posting system. Every module owner could post news whenever he want.
news.mozilla.org - many of the module owners post weekly updates to their respective newsgroups.
#7 So let's have a common location...wum
Monday June 12th, 2000 11:44 AM
How about a n.p.m.status-updates newsgroup that all module owners crosspost their status updates to? That way you can subscribe to that if you're interested in general status information even if you can't keep up with *every* individual component.
#9 Re: So let's have a common location...wum
Monday June 12th, 2000 1:35 PM
Preferably robomoderated so only messages crossposted to another n.p.m.* group and with followup-to set to the other group. That should keep it fairly free of non-status-related stuff.
Yeah, we need some kind of status-news page where module owners and other developers can checkin their weekly bits of news. This could be realized with PHP and mySQL (Chris?). I'd love to see such a system... cu Tintsch
We could use a newgroup as proposed in the other subthread (which is a good idea IMO) and then use a NNTP->WWW gateway to still display the status on the website (so visitors find it and see we're actually working :) ).
Yes, we need to display the status on the website. It would also be great to have it moderated so that the pieces of status-news get reduced to the absolutely necessary. All the "bla bla" isnt required at all. The visitor wants to know what the developers did, quick and firmly.