Differences

This shows you the differences between two versions of the page.

development:communication:archives:100309_weekly [2010/03/09 02:26]
j_k9 created
development:communication:archives:100309_weekly [2010/04/19 19:29] (current)
j_k9 fixed syntax
Line 7: Line 7:
This meeting's agenda is available [[development:communication:agendas:100309_weekly|here]]. This meeting's agenda is available [[development:communication:agendas:100309_weekly|here]].
-----+===== Summary ===== 
 + 
 +As sent to the Mira Development Mailing List on 09/03/2010 with the subject: "Summary of 09/03/2010 Meeting" 
 + 
 +> Hi all, 
 +>  
 +> Last night's meeting was attended by Alan, Shilpa and myself. You can find a transcript of the meeting here: 
 +> http://miragroupware.org/wiki/doku.php/development/communication/archives/100309_weekly 
 +>  
 +> Our main interest is, of course, in eliminating the final release holds so that we can begin testing and producing an installer in preparation to push the 0.1 release. 
 +>  
 +> One of those release holds is the New Workplace form (based on the NG message), which Alan is working on. He is having to rewrite the MsgNewGroup message parser in order to support a Workplace description field, which was omitted from the specification. He is also working on changing the form's GUI to be more user-friendly. 
 +>  
 +> Alan is then going to work on a Join Workplace form, which will allow users to join Workplaces of which they are not already a member (all Workplaces are going to be 'public' and capable of being joined by all users for 0.1, as we don't have a roles system yet). 
 +>  
 +> Once those two forms are completed, Alan will merge Shilpa's MsgUserStatus code into his branch (to support user statuses in the Chat widget) and then merge his branch with trunk. 
 +>  
 +> The final release hold will then be the MingW bug which is causing the compiler to exit when building Mira (on Windows) due to the Boost Property_tree code. Shilpa is following this up: she is going to contact the Boost mailing list or IRC channel to get some assistance in correcting this error, and she will report back to us on the mailing list if she discovers anything about the bug or a potential solution. 
 +>  
 +> After completing these tasks, we will enter a Feature Freeze and begin testing Mira Client and Mira Server more thoroughly. If they are both bug-free (as far as we can tell), we will package them up with BitRock InstallBuilder and push the release. 
 +> Thurston has said he will try to look into our current BitRock configuration files (in his mira/installer branch) and attempt to get them working again with the new code. Alan and Shilpa have also expressed some interest in this and will try to fix the installer once they've finished the other tasks they are working on. It was suggested that Neeraj could also look into this, if he wishes? 
 +>  
 +> Finally on the agenda, I am working on a User Guide for Mira Client and a separate one for Mira Server. These will be kept in a separate branch until they are ready to be merged into trunk under mira-client/docs/ and mira-server/docs/. The final version of the User Guides for 0.1 will be published as both a single PDF file and as an HTML page (so that they can be accessed on our website). 
 +> The User Guides will feature individual installation instructions for Windows and Linux, and the remainder of the guides will use screenshots from Mira running on Windows (for the Client). The rationale behind this is that the use processes for Mira Client should be identical regardless of the Operating System, and the majority of our user base will be running Windows. 
 +>  
 +> We're making excellent progress, so please keep up the great work! 
 +>  
 +> Regards, 
 +>  
 +> Max Bossino 
 +> Project Manager 
 +> http://miragroupware.org 
 + 
 +===== Transcript =====
[01:03] clsk: hello [01:03] clsk: hello
 
development/communication/archives/100309_weekly.1268126774.txt.gz · Last modified: 2010/03/09 02:26 by j_k9
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki