Replacing the usual sail meeting with the beginning of a sail-core audit seems fine to me.
But others might want to use that time to continue a discussion started at the last meeting. I don't believe we'll be able to finish the cataloging in one meeting, I expect it to take several days worth of meetings. We could split it up and do it individual, but I wanted to try to use this as an opportunity to go over all the code with Hiroki. We'll start out slow and meticulous, but if that appears unreasonable we might speed it up a bit. Turadg, you might get bored, but you are welcome to check it out. We'll be putting the catalog in one or more wiki pages. An example from doing this to my own code is here: http://confluence.concord.org/display/CSP/OTrunk+Old+View+System+Analysis In that case I was making suggestions for improvements as I went along. Scott Turadg wrote: > I'd like to be at the cataloging meeting. Will that be next Wednesday > at 3pm ET? > > On Aug 23, 6:40 pm, Scott Cytacki <[EMAIL PROTECTED]> wrote: > >> Earlier, I proposed another agenda where we would do an audit of the >> sail-core project and catalog all the classes by their functionality. >> That meeting will be postponed. >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
