-----Original Message----- From: Andrew M. Kuchling [mailto:akuchlin@mems-exchange.org] Sent: Thursday, August 12, 1999 05:48 To: 'zope@zope.org' Subject: RE: [Zope] Zope-mail gateway
Jay, Dylan writes:
I'm not really looking for a way of implementing this now. What I'm trying to say is that I think there would be a need for a closer intergration of mail and web and zope is a perfect candidate. At the moment email processing
Yes, this would be an *excellent* idea, and would be a natural component used to implement bug-tracking systems, group memories, customer service response systems, and so forth. Zope's a powerful platform, and it makes sense to tie it into as many things as possible, so you have a unified means of accessing resources. For similar reasons, I really like Ty Sarna's idea of uploading data from a Pilot directly into a Zope database, and then writing Zope methods that would do things with it.
As someone once said, "It is correspondingly argued that the right way to build reliable systems is to put all your eggs in one basket, after making sure that you've built a really *good* basket." (http://www.tuxedo.org/~esr/jargon/html/entry/airplane-rule.html). Zope is a pretty decent basket now, and it'll get better in the future.
Someone should start a list of potential Zope projects and components, to be implemented when free time is available. :)
I think this is an *excellent* idea. A web based list. A place people could put their names down as expressions of interest for developing, for testing etc, so that virtual teams can be easily and ideas can be thrashed out amoungst those interested. Those not directly involved can also get a feel for the progress of the idea. Also you can intergrate in something I'm about to work on for my site. This is a "bug-parade" type system for new features. Users have a limited number of votes which they can put on the ideas they would most like to see come to fruition. Also a neat way of organizing the contributed software section of the zope site, as this area has not nearly enough information.
participants (1)
-
Jay, Dylan