Thanks for responding Raphael
I'm not a developer, so I'm a bit out of my depth
But I understand that Listen was the product that couldn't cut the
mustard
We have a possibility of quite high load further down the road
(several lists, perhaps a few thousand on each)
I got the impression from our developers that they were worried this
might break things in Plone if Listen was used
The idea they have is to drive both Plone and Mailman authentication
from a separate membership data resource. But once again I could be
blowing air.
The developers are out there somewhere I think -- anyone want to
pitch in?
But we would prefer that the list membership was able to
automatically cross-reference against Plone membership attributes
to avoid too much manual work for administrators if membership grows.
Did you consider "listen"?
http://plone.org/products/listen
Raphael
Our developers have suggested some days of research to establish
development costs, and then the development itself.
We have expressed an interest in finding a solution for the Plone
community, especially if there is enough interest to find a
cosponsor.
Any thoughts?
Regards
Ben Rudder
_______________________________________________
NGO mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/ngo
