Public SourceMage Discussion List

[Hamish Greig <hgreig AT bigpond.net.au>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Now that the Project Lead subscribes to all the perforce change emails, and 
is 
aware of developer's activities, the old procedure of  reporting on the past 
month at the beginning of each admin meeting and updating our team logs 
pre-meeting is no longer strictly necessary.  
All the leads (and developers) should now be receiving these change notices 
and activity, or lack of activity, would already be known so the focus of the 
meeting could become supporting the teams that are falling behind and 
planning ahead, refining the shortterm roadmaps for each team and for the 
entire project. And if necessary, opening up positions for people with more 
time or skills to take over. 
The existing management structures allowed for vastly different levels of 
improvement between grimoire, sorcery and ISO teams, but with this format, it 
might have been possible to save the February 1.0 release deadline. 
I know this disparity of achievement is being addressed now, but wouldn't it  
have been better addressed at meetings when it became apparent sometime last 
year ?

Similarly the reason to now update the team logs is only so users and the 
general public are aware of our activities, without them having recieved the 
perforce notices. 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAgPQv8fSufZR6424RAlOxAJ92PRaYE/plDAA/L5WRQIRB1VTOtgCfZ3+h
frCait2kPhoLdju17Q1ieYU=
=hfTO
-----END PGP SIGNATURE-----