[Linux-aus] MemberDB is a great short term solution, but we need a broader rethink

[Neill Cox]

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.

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.

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.

Cheers,
Neill Cox

Sent from a phone.  Please forgive brevity and "interesting" auto
correction.
On 19/01/2015 8:36 PM, "James Purser" <jamesrpurser at gmail.com> wrote:

> 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.
>
> As I recall from previous investigations the only thing that civicrm
> lacked was the ability to hold elections.
>
> On Mon, 19 Jan 2015 20:29 Joshua Hesketh <josh at nitrotech.org> wrote:
>
>>  Hi all,
>>
>> 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.
>>
>> I think, to be clear, the highest priorities before the extra features
>> would be:
>>
>> 1) Feature parity with memberdb (registering, maintaining membership,
>> elections, voting etc)
>> 2) Communication (a way to email members on mass)
>>
>> 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.
>>
>> 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.
>>
>> Cheers,
>> Josh
>>
>>
>> On 19/01/15 19:05, James Polley wrote:
>>
>> 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.
>>
>>  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.
>>
>> On Fri Jan 16 2015 at 3:38:56 AM Mark Ellem <mark at colmiga.org> wrote:
>>
>>> A potential feature that could be looked at in the scope is a
>>> possibility of offering user groups a way of having an 'instance' where
>>> they could manage their membership affairs as a service of LA.
>>>
>>> Either that or look at making a new membership database solution usable
>>> for a user group. Our local user group, HUMBUG, would love to have such
>>> software as we have not been able to find anything that suits.
>>>
>>> If you need any support I would be happy to help.
>>>
>>> Thanks,
>>> Mark Ellem
>>>
>>> On Fri, 2015-01-16 at 15:46 +1300, Michael Cordover wrote:
>>> > On 16 January 2015 at 14:39, Kathy Reid <kathy at kathyreid.id.au> wrote:
>>> > > While this is a great short term solution, I think we should (in
>>> parallel)
>>> > > discuss and debate a MemberDB replacement, likely something like
>>> CiviCRM.
>>> > > This is a bit more work and effort, but I think would have good long
>>> term
>>> > > returns, and address the pressing need for targeted member
>>> communications.
>>> >
>>> > On this, I think it would be useful to do some project scoping - not
>>> > just around membership, but around all of the web-based systems we are
>>> > thining of upgrading. I know there's also been talk of a zookeepr
>>> > upgrade/rewrite. There are also probably other needs we should be
>>> > considering: other LA events, potential lobbying/other LA activities,
>>> > grants, Mailman 3 integration, Hurd compatibility etc etc etc.
>>> >
>>> > The first step here would be wishlisting *everything*, and then
>>> > scoping it down into actual projects, then commencing work. Strategic
>>> > planning, yo.
>>> >
>>> > Michael
>>> > _______________________________________________
>>> > linux-aus mailing list
>>> > linux-aus at lists.linux.org.au
>>> > http://lists.linux.org.au/mailman/listinfo/linux-aus
>>>
>>>
>>> _______________________________________________
>>> linux-aus mailing list
>>> linux-aus at lists.linux.org.au
>>> http://lists.linux.org.au/mailman/listinfo/linux-aus
>>>
>>
>>
>> _______________________________________________
>> linux-aus mailing listlinux-aus at lists.linux.org.auhttp://lists.linux.org.au/mailman/listinfo/linux-aus
>>
>>
>>  _______________________________________________
>> linux-aus mailing list
>> linux-aus at lists.linux.org.au
>> http://lists.linux.org.au/mailman/listinfo/linux-aus
>>
>
> _______________________________________________
> linux-aus mailing list
> linux-aus at lists.linux.org.au
> http://lists.linux.org.au/mailman/listinfo/linux-aus
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.org.au/pipermail/linux-aus/attachments/20150120/3ce5a1d2/attachment.html>