<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">Actually,</div><div class=""><br class=""></div><div class="">Why do we need a COMMITTEE to do this? We’re sounding like the Trade Federation and Intergalactic Senate…</div><div class=""><br class=""></div><div class="">:(</div><br class=""><div><blockquote type="cite" class=""><div class="">On 15 Jun 2015, at 2:52 pm, Michael Cordover <<a href="mailto:la@mjec.net" class="">la@mjec.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On 15 June 2015 at 13:29, Joshua Hesketh <span dir="ltr" class=""><<a href="mailto:josh@nitrotech.org" target="_blank" class="">josh@nitrotech.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000" class="">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.<br class=""></div></blockquote><div class=""><br class=""></div><div class="">You won't get any dissent from me on this.</div><div class=""><br class=""></div><div class="">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?</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">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).</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">Regards</div><div class=""><br class=""></div><div class="">Michael</div></div></div></div>
_______________________________________________<br class="">linux-aus mailing list<br class=""><a href="mailto:linux-aus@lists.linux.org.au" class="">linux-aus@lists.linux.org.au</a><br class="">http://lists.linux.org.au/mailman/listinfo/linux-aus<br class=""></div></blockquote></div><br class=""></body></html>