Brainstorm first; define 1.0 later

Andrew Carter ascarter at gmail.com
Sat Jan 16 15:20:47 PST 2010


Yes, the standard db backend is a great idea. Nothing wrong with a compatible port on another OS like Linux. SQLite seems like a nice candidate.

Andrew


On Jan 16, 2010, at 1:55 PM, Ben Reubenstein wrote:

> I really, REALLY like the idea of using a standard database. That layer gives users flexibility as well as allows a diverse group of developers to tap into the data.
> 
> ~ Ben
> 
> On Sat, Jan 16, 2010 at 2:45 PM, Gus Mueller <gus at flyingmeat.com> wrote:
> On Jan 16, 2010, at 1:41 PM, Brent Simmons wrote:
> 
> > It's too soon to talk about the specifics of a 1.0 release -- let's first just brainstorm, then we'll have a pretty good idea of what people are looking for.
> >
> > What are you looking for in an email client?
> 
> A good UI, and extensibility via plugins.  So it would have to have some sort of a defined plugin api for programmers to code against.  It's really hard to this for a 1.0- so I'd suggest it be marked as "experimental", but it would be nice to have.
> 
> It would be also nice, if there were a standard database / message store that it wasn't tied to too closely.  That way forks could happen, and maybe a new client would be able to read the database without any problems.  Or maybe even another process (python?) could be able to read/write to the message store.
> 
> -gus
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ranchero.com/pipermail/email-init-ranchero.com/attachments/20100116/5833ee2b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2415 bytes
Desc: not available
URL: <http://lists.ranchero.com/pipermail/email-init-ranchero.com/attachments/20100116/5833ee2b/attachment.bin>


More information about the Email-init mailing list