|
From: Daniel B. <Dan...@bi...> - 2003-06-18 23:33:28
|
Hi all, I'm sorry I've not responded to any forum messages lately, I've been offline, and then been busy the last few days. (I was going to reply to your mail, Alex, about the CVS stuff. It's perfectly alright for me about Ryan being CVS admin. :) But, I still miss a design document (program flow, base functionality/library) and a basic framework (API) for the groupsuite application. And thus many questions arise, here are just a few to show some examples: How should modules communicate? E.g. how can the mail client (when it gets written) read entries from the address book? How should modules store their data? How/where will modules be called? How will authentication be performed? E.g. how will the calendar read user info? (e.g. to display a list of other users' calendars) I feel we can't just start by implementing a module (calendar, for example). We need the framework/API. The base on which to build it all. On Wed, 2003-06-18 at 22:08, RT wrote: > I figured the best place to announce this would be the mailing list so=20 > everyone knows. Groupsuite has been imported to the CVS > repository. It's available as the module 'groupsuite' . The import was=20 > successful (I have run a checkout). Due to problems at Sourceforge > ViewCVS isn't displaying it yet. This problem is because ViewCVS is currently running on the backup CVS servers at Sourceforge, so content may be up to 24 hours old. Expect to see the checkin sometime tomorrow. I also want to mention that all changes to CVS will be emailed to gro...@li... so those that want to see what's going on to the groupsuite CVS tree can subscribe to that list. Alex: The email containing the import by Ryan may have been held by the mailing list manager. Can you check groupsuite-cvsinfo and see if any posts are held for approval? -Daniel |