<p dir="ltr">I'm interested in working on a flask and angular solution as I have skills in python and javascript. Unfortunately I have next to no php or drupal skills.</p>
<p dir="ltr">If the concensus is that drupal is the way to go then I will quietly bow out and wish you the best of luck :) I'm not being precious about this, I just don't think I am the right person to work on a drupal replacement.</p>
<p dir="ltr">I do agree that we should have more than one person working on this so ad to avoid the run over by a bus problem. </p>
<p dir="ltr">Cheers, <br>
Neill Cox</p>
<p dir="ltr">Sent from a phone. Please forgive brevity and "interesting" auto correction. </p>
<div class="gmail_quote">On 19/01/2015 8:36 PM, "James Purser" <<a href="mailto:jamesrpurser@gmail.com">jamesrpurser@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">If we're going to stick with drupal then I think the best option is to use a drupal based membership management system, if nothing else, it reduces the "walk in front of a bus" problem.</p>
<p dir="ltr">As I recall from previous investigations the only thing that civicrm lacked was the ability to hold elections.</p>
<br><div class="gmail_quote">On Mon, 19 Jan 2015 20:29 Joshua Hesketh <<a href="mailto:josh@nitrotech.org" target="_blank">josh@nitrotech.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi all,<br>
<br>
This is some great feedback. I know those interested in this are
thinking about declaring a hack day (or working bee) to tackle the
changes, however I'll leave that to them to arrange.<br>
<br>
I think, to be clear, the highest priorities before the extra
features would be:<br>
<br>
1) Feature parity with memberdb (registering, maintaining
membership, elections, voting etc)<br>
2) Communication (a way to email members on mass)<br>
<br>
After that I would agree with James that some sort of subcommittee
registrar would be incredibly useful and I would probably rate it as
the next most important.<br>
<br>
The current approach to the development as I understand it is to
create a REST interface to the existing database. From there a web
ui can be built. Again though I'll leave it to those working on it
to expand.<br>
<br>
Cheers,<br>
Josh</div><div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<div>On 19/01/15 19:05, James Polley wrote:<br>
</div>
<blockquote type="cite">For user groups which are run as sub-committees of LA,
having the ability to piggyback on MemberDB would be very useful -
as a way to manage any members-only mailing lists, and as a way to
manage elections, at the very least.
<div><br>
</div>
<div>If we're compiling a wishlist, I'd like to add the ability
for sub-committees (including the UG subcommittees) to have
their own drupal/wordpress/civicrm/something instance - I don't
really care what, as long as it gives the UG the ability to have
their own web presence without needing to worry about cost of
hosting or having sysadmins. I'd also love for them to be able
to set up and manage their own public mailing lists.<br>
<br>
<div class="gmail_quote">On Fri Jan 16 2015 at 3:38:56 AM Mark
Ellem <<a href="mailto:mark@colmiga.org" target="_blank">mark@colmiga.org</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A
potential feature that could be looked at in the scope is a<br>
possibility of offering user groups a way of having an
'instance' where<br>
they could manage their membership affairs as a service of
LA.<br>
<br>
Either that or look at making a new membership database
solution usable<br>
for a user group. Our local user group, HUMBUG, would love
to have such<br>
software as we have not been able to find anything that
suits.<br>
<br>
If you need any support I would be happy to help.<br>
<br>
Thanks,<br>
Mark Ellem<br>
<br>
On Fri, 2015-01-16 at 15:46 +1300, Michael Cordover wrote:<br>
> On 16 January 2015 at 14:39, Kathy Reid <<a href="mailto:kathy@kathyreid.id.au" target="_blank">kathy@kathyreid.id.au</a>> wrote:<br>
> > While this is a great short term solution, I think
we should (in parallel)<br>
> > discuss and debate a MemberDB replacement, likely
something like CiviCRM.<br>
> > This is a bit more work and effort, but I think
would have good long term<br>
> > returns, and address the pressing need for
targeted member communications.<br>
><br>
> On this, I think it would be useful to do some project
scoping - not<br>
> just around membership, but around all of the web-based
systems we are<br>
> thining of upgrading. I know there's also been talk of
a zookeepr<br>
> upgrade/rewrite. There are also probably other needs we
should be<br>
> considering: other LA events, potential lobbying/other
LA activities,<br>
> grants, Mailman 3 integration, Hurd compatibility etc
etc etc.<br>
><br>
> The first step here would be wishlisting *everything*,
and then<br>
> scoping it down into actual projects, then commencing
work. Strategic<br>
> planning, yo.<br>
><br>
> Michael<br>
> _______________________________________________<br>
> linux-aus mailing list<br>
> <a href="mailto:linux-aus@lists.linux.org.au" target="_blank">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" target="_blank">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>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
linux-aus mailing list
<a href="mailto:linux-aus@lists.linux.org.au" target="_blank">linux-aus@lists.linux.org.au</a>
<a href="http://lists.linux.org.au/mailman/listinfo/linux-aus" target="_blank">http://lists.linux.org.au/mailman/listinfo/linux-aus</a>
</pre>
</blockquote>
<br>
</div>
______________________________<u></u>_________________<br>
linux-aus mailing list<br>
<a href="mailto:linux-aus@lists.linux.org.au" target="_blank">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/<u></u>mailman/listinfo/linux-aus</a><br>
</blockquote></div>
<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></blockquote></div>