[Linux-aus] Proposing a membership subcommittee

[Michael Still]

Ok, so hi.

I just came back to a business trip to discover I am drowing in
memberdb threads. That's exciting, because its way better than no one
caring enough to even reply to email. Give me a couple of days to
digest the various emails, and then let's try for a quick IRC meeting
of interested parties to come up with a plan.

Michael

On Wed, Jan 28, 2015 at 1:55 PM, Stewart Smith <stewart at flamingspork.com> wrote:
> Neill Cox <neill at ingenious.com.au> writes:
>> I am definitely interested in modernising memberdb.
>>
>> At this point I have a proof of concept that:
>>
>> - Uses the current database schema
>> - Exposes a REST API via a flask/sqlalchemy
>> - Provides a UI built on AngularJS and bootstrap
>>
>> It's very early but looks like it should work.
>>
>> There's lots still to do though and I'm keen to talk to anyone else
>> interested in being involved.
>>
>> I'd also like to thank Stewart Smith for all of his work on the current
>> memberdb, it's nice to have a sane design to start from!
>
> This all sounds awesome, and exactly the direction that things should go
> in. The MemberDB code is not-exactly-best-practice of a dozen years ago,
> so there's an awful lot that can be improved. Considering the tricky bit
> is actually just the voting, it's quite likely that redoing the rest of
> it in a modern framework would be excellent and not too hard.
>
> Probably a bunch better than all the manual PHP from way back when.
>
> --
> Stewart Smith



-- 
Rackspace Australia