Hi John, On 28 Dec 2010, at 12:09, John Deal <bassd...@yahoo.com> wrote:
> Hello Max, > > OK I see where I screwed up. Oh well :-(. Anyway it most likely is better > to drop my branch and use Alan's fix since his fix is integrated with other > functionality. Mine also has some coding standards issues (no "_" between > variable name words). Don't worry about it! It was a good exercise, and you're now aware of how to do it next time. > I am a bit confused about how bugs are reported and assigned. For example, I > can't find any mention of the Workplace Summary space problem in the bug list > in Launchpad so I assumed it was unreported (implying not known although that > was not the case). It is mentioned in Alan's branch information. This bug was a peculiar one. I think I spotted it during an IRC meeting, where we had a public Mira Server running and were using Mira simultaneously. If I remember correctly, Alan fixed it (in his branch) on the spot. That is why it was never reported on Launchpad; there was no time lag between discovery and fix. In hindsight, it should have been reported and the fix should have been assigned by that revision, if only for the purpose of providing a complete record on Launchpad. > The Launchpad bug display does not have an "assigned" field. How do you know > if a bug is being worked on? If you look at the bug page, you will see an 'Assigned to' field, where the bug can be assigned to a particular developer: https://bugs.launchpad.net/mira/+bug/694335 The bug's status can also be changed from 'New' to 'Confirmed' (if it has been reproduced by a developer), or 'In Progress' (if a developer is working on a fix). I think that answers your question. :) > As far as next tasks, I am very interested in the database work which does > not seem to be implemented yet (ex. soci library). There seems to be a > disconnect between the text documentation in the Wiki and the "Mira Groupware > Infrastructure - Layers Diagram" graphic. The graphic shows the Database > layer and Directory layer in parallel while the text implies the Directory > layer consists of separate plain text, database, and LDAP components. The > text also seems to indicate the Storage layer contains a database component. > Anyway I think this is interesting. > > I would not mind working on doxygen documentation (I see the comments are > there but I have not seen any resulting documentation) or bugs. You are welcome to work on either, but the Database layer might be more interesting! You are right in that the Layers Diagram does not offer an accurate representation; the reality is a little more complicated than that. The Database layer would be a low-level layer offering access to a database - I think that is the basic idea. In terms of implementation, this probably means a Mira-friendly wrapper for the soci library (or equivalent). Why would we want to offer access to a database? - To store Directory layer data in a database instead of an XML file - To store (some) Utility data. We also need to bear in mind that a RDBMS will usually only be available on the server-side. So do we only allow access to a database backend with Mira Server, and force an alternative backend with the Client? Or do we provide a small, embedded DBMS with Mira Client (and possibly also Server) to allow a database backend to be used on both sides? These are some of the things we might wish to discuss in advance. I am free all day every day, for the next week or so, so I would be happy to attend a meeting to flesh out some of these points. Please let me know! :) Regards, Max Bossino Project Manager http://miragroupware.org ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Mira-development mailing list Mira-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mira-development
