[prev] [thread] [next] [lurker] [Date index for 2002/09/24]
On Tuesday, Sep 24, 2002, at 10:51 Europe/London, Simon Wistow wrote:
> So, what's missing?
I think everything still on the hit list needs hitting a little harder.
I'm slightly email-challenged today due to moving malarkey, but
handily the list is already archiving itself.
Outstanding stuff from before:
The api docs still suck ass.
Siesta::Storage::DBI - works well enough, but there's entirely too
much duplicated code, and the config stuff that lives there is still
too clever
Test coverage sucks ass.
I'll throw onto the TODO pile:
Something to turn the maildir archives into web-browseable ones.
Renaming some nacho commands. Recently I was wondering who was
subscribed to a list, so I lucked onto C<nacho show-list siesta-dev>
but to find who was subbed to it the command is C<nacho show-users-list
siesta-dev> whereas my brain guessed it as being show-list-users.
Giving it a little more thought I actually think it might want to be
C<nacho show-users [list]>, where if you don't specify a list you get
all the users on the system.
Ability to serialise all the state in one pass to allow me to do
C<<nacho dump > backup>> and C<<nacho load < backup>>. This'll be good
for upgrades and backups.
> The one thing I've been thinking of is sending out to users. At the
> moment the Send plugin loops though all the users and send a mail out
> to
> each one.
No it doesn't.
> The thing is - for us to do things like per-user NoMail and
> PGP and ReplyTo or whatever instead of just looping through plugins
> before we get to Send we're going to need to do it when we loop through
> all the users as well.
>
> The big question - do we codify this as part of the design or leave it
> as a plugin implementation detail?
The way I see it, per-user configuration needs to be enabled on a
per-list basis, possibly even per-plugin. This leads to a world of
pain.
Some things it makes absolutely no sense to run more than once, and
some it's the only way you'd want to use them. I'll pick on three for
an example; MembersOnly, ReplyTo, and Archive.
MembersOnly you want to run once, probably first.
ReplyTo you may choose to run once for each user.
Archive you want to run once, possibly at about the same time as Send
(so that what is Archived is what is sent)
[I hope Mail.app doesn't fuck this bit up]
--- MembersOnly ---< ReplyTo >--- Archive --- Send
^ ^
| | Danger Will Robinson!
|
\ Expand/process one for each member
And that's where my head starts to fucking hurt.
--
Richard Clamp <richardc@xxxxxxxxx.xxx>
Generated at 13:56 on 01 Jul 2004 by mariachi 0.52