[Mailman-Developers] Storing additional user data

[Kevin McCann]

Chuq's right on the money here. I'd be happy to do stuff on the PHP
interface side. This would allow connectivity with PHP-Nuke, Postnuke,
Xaraya, and any other PHP-based CMS.

Barry, continuing our recent conversation, I'd be happy to try to do
something on the PHP side but I'll need to get some pointers on how to
do things in a more elegant way than I had initially suggested - running
$mailman/bin commands and parsing (yuck).

- Kevin



On Thu, 2003-07-10 at 15:05, Chuq Von Rospach wrote:

> 
> Personally, I wouldn't try to extend Mailman to do this. Instead, I'd 
> set it up so Mailman could use external data sources easily, and allow 
> people to write adaptors to fit into that. That way, users could write 
> adaptors for their favorite system (php-nuke, slashcode, drupal, yada 
> yada yada), where there's already an existing account management system 
> in place, and let it manage the subscriptions and feed delivery data to 
> mailman, and have mailman feed undeliverable data back to the system.
> 
> you risk turning mailman into yet another CMS, rather than allowing 
> mailman to interconnect with all of the existing CMS's... the latter is 
> a much easier and more powerful task.
> 
> If I were to do this, I'd find two volunteers, one running php-nuke, 
> one running slashcode, and have them write the plug-ins for those CMSes 
> while Barry wrote the interface they'd talk to, and once Mailman worked 
> friendly with both of those, it'd likely work easily with any CMS.
> 
> chuq (nope. haven't been thinking about doing that myself. nope. not 
> me. Just shooting from the hip here)
> 
> 
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> http://mail.python.org/mailman/listinfo/mailman-developers