[Linux-aus] What's happening with the Membership Committee?

[Michael Cordover]

On 15 June 2015 at 13:29, Joshua Hesketh <josh at nitrotech.org> wrote:

> However, memberdb is in desperate need of an update. If we have nobody
> volunteering to implement a CRM type system for Linux Australia, and we do
> indeed still have volunteers looking at improving our membership management
> platform, then I think we should take them up on that kind offer as it'll
> be a great improvement.
>

You won't get any dissent from me on this.

However, I think we may be overestimating the effort involved in a CRM
implementation. My understanding is that CiviCRM meets all our membership
management requirements, it just doesn't have a voting. Is this correct?

I'd be happy to spend a couple of weekends hacking together a voting
module; it's basically the existing nominate/vote/count parts of memberdb
Drupalised.

Until something is written and rigorously tested we can manage membership
in CiviCRM and then pull the database into a memberdb instance. There are
hooks in CiviCRM so that process is not particularly strenuous to automate
(provided we know enough about memberdb internals to update the database
directly, which I think we self-evidently do).

Someone pull me up if I'm drastically underestimating the scope of this,
but otherwise I'm happy to put my hand to at least spin up a CiviCRM test
so we can start poking at something.

Regards

Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.org.au/pipermail/linux-aus/attachments/20150615/4f906ffe/attachment.html>