<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>Neil, it’s actually not clear to me what’s broken about the current memberdb … I actually think we’re concentrating on technical issues when the problem isn’t technical.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'>I commend your work on membershipdb-ng.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> Neill Cox [mailto:neill.cox@ingenious.com.au] <br><b>Sent:</b> Thursday, 11 February 2016 10:13 PM<br><b>To:</b> David Lloyd <lloy0076@adam.com.au><br><b>Cc:</b> Kathy Reid <kathy@kathyreid.id.au>; linux-aus <linux-aus@lists.linux.org.au><br><b>Subject:</b> Re: [Linux-aus] Re-igniting the Membership Committee<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>To be honest, I chose flask because I wanted to learn about it. memberdb seemed like something that might be useful to LA. I was aware of the problems with the current implementation and thought a rewrite might be helpful.<o:p></o:p></p><p>I've had some fun and learned quite a bit, it may yet prove to be useful, but if it isn't it's still been a worthwhile exercise for me.<o:p></o:p></p><p>I encourage any LA members with knowledge of CiviCRM to step forward and help implement a replacement for memberdb.<o:p></o:p></p><p>In the meantime I'll keep working on the flask version - gratefully accepting any help, and without expecting LA to feel any obligation to use the final product.<o:p></o:p></p><p>This is one of the strengths of free software - we're all free to contribute and LA as an organization is free to choose the platform that best meets their need.<o:p></o:p></p><p>I personally have a preference for python over php, but it's just that - a preference. I don't have hard data to back it up, just feelings :-)<o:p></o:p></p><p>Reinventing the wheel can be fun, but feel free to stick with Wheel 1.0 if you prefer.<o:p></o:p></p><p>Cheers,<br>Neill<o:p></o:p></p><div><p class=MsoNormal>On 11 Feb 2016 10:25 PM, "David Lloyd" <<a href="mailto:lloy0076@adam.com.au">lloy0076@adam.com.au</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal><br>CiviCRM is already a stable product, based on Drupal and no doubt could<br>leverage the various Drupal modules already developed with sufficient<br>technical knowledge. I doubt there's insufficient technical knowledge in<br>Linux Australia to do so...<br><br>...why would we reinvent the wheel? Sure choosing a PHP based solution<br>might hinder those who don't know PHP but choosing a Python based one<br>hinders those who don't know Python. In fact, choosing a solution based<br>on X will hinder those who don't like X and let's face it, we can't even<br>sort out a name for the organisation - we're not going to settle on the<br>best technical solution.<br><br>This last point is probably a good thing BUT I would argue that Linux<br>Australia doesn't exist to create a confounded CRM system. Or reinvent<br>electoral systems. Or even create open source software itself.<br><br>The tools we use for membership management are important but they're not<br>our goal in life unless I've seriously misread Linux Australia's<br>constitution and policies.<br><br>The question I would actually put to the membership committee, would be:<br><br>"Can you find ways that would cause the membership of Linux Australia to<br>increase such that we needed a technical replacement urgently?".<br><br>TL;DR - I think we're concentrating on the technical side and missing<br>the actual issue...<br><br>> -----Original Message-----<br>> From: linux-aus [mailto:<a href="mailto:linux-aus-bounces@lists.linux.org.au">linux-aus-bounces@lists.linux.org.au</a>] On<br>Behalf<br>> Of Kathy Reid<br>> Sent: Thursday, 11 February 2016 8:25 PM<br>> To: <a href="mailto:linux-aus@lists.linux.org.au">linux-aus@lists.linux.org.au</a><br>> Subject: Re: [Linux-aus] Re-igniting the Membership Committee<br>><br>> Thanks AJ for the thought you've put into this, and to Neill for the<br>work<br>> that you've done around this as well.<br>><br>> I'd be very comfortable with this approach - ie pitching for your idea<br>to<br>> be developed further, with iterative proof points before an<br>> implementation.<br>><br>> Are there any other people who'd be keen on being on "Team CiviCRM"?<br>><br>> Kind regards,<br>> Kathy<br>><br>> On 11/02/16 16:32, Anthony Towns wrote:<br>> > On Wed, Feb 10, 2016 at 10:00:43AM +1100, Kathy Reid wrote:<br>> >> I'd like to<br>> >> reinvigorate the debate over our Membership Committee[0],<br>> Membership<br>> >> platform[1] and related pieces[2].<br>> > I wonder if it would work to structure this more along the lines of<br>> > <a href="http://linux.conf.au" target="_blank">linux.conf.au</a> bid teams, rather than as a sub-committee. ie, the<br>> > council posts a date for bids to be in; Kathy does as civicrm<br>demo/bid<br>> > showing how cool it could be, maybe someone does a drupal<br>> bid/demo,<br>> > and maybe Neill does flask/memberdb-ng bid. The council gives a few<br>> > rounds of feedback to see how if the bids can be further improved,<br>> and<br>> > then chooses the most promising bid (and a committee is formed at<br>> that point if needed).<br>> ><br>> > (Personally, I'm more philosophically inclined towards Neill's<br>> > approach; but Donna pointed me at some drupal election modules<br>> which<br>> > seemed pretty impressive, and while looking for survey software, I<br>> > noticed civicrm actually has some and is already packaged for<br>Debian,<br>> > both of which seem like plusses to me)<br>> ><br>> > If people like this idea it could be implemented by the council<br>doing<br>> > a call for bids asking for:<br>> ><br>> > - a bid document describing what's great about the proposed<br>solution<br>> > - a public demo site where people can try things out<br>> > - access to the demo site's management side, so the secretary at<br>least<br>> > can review that as well<br>> > - instructions/packages/config items/etc for how to deploy the<br>> system<br>> > (for public review, but more importantly for the admin team to<br>> review)<br>> > - and anything else that seems helpful and enlightening<br>> ><br>> > and setting deadlines of maybe "now" for interested people to get<br>> > together and start doing things, April 4th for sending expressions<br>of<br>> > interest to the list/council, June 1st for initial submissions and<br>> > feedback, and August 1st for final submissions, so a decision could<br>be<br>> > made and rollout begin in September or October?<br>> ><br>> > Cheers,<br>> > aj<br>> ><br>> > _______________________________________________<br>> > linux-aus mailing list<br>> > <a href="mailto:linux-aus@lists.linux.org.au">linux-aus@lists.linux.org.au</a><br>> > <a href="http://lists.linux.org.au/mailman/listinfo/linux-aus" target="_blank">http://lists.linux.org.au/mailman/listinfo/linux-aus</a><br>><br>> _______________________________________________<br>> linux-aus mailing list<br>> <a href="mailto:linux-aus@lists.linux.org.au">linux-aus@lists.linux.org.au</a><br>> <a href="http://lists.linux.org.au/mailman/listinfo/linux-aus" target="_blank">http://lists.linux.org.au/mailman/listinfo/linux-aus</a><br><br><br>_______________________________________________<br>linux-aus mailing list<br><a href="mailto:linux-aus@lists.linux.org.au">linux-aus@lists.linux.org.au</a><br><a href="http://lists.linux.org.au/mailman/listinfo/linux-aus" target="_blank">http://lists.linux.org.au/mailman/listinfo/linux-aus</a><o:p></o:p></p></blockquote></div></div></div></body></html>