been doing a fair bit of mods to memberdb recently – getting features in.<\/p>\n
– new css based look (which is almost correct)
\n– more solid code around the place
\n– better error reporting (that needs debugging… hahaha)
\n– a start on the positions tracking UI
\n– change password UI
\n– sorting of the memberlist
\n– moving look and messages into site customisable directories (so nobody has to get scared by memberdb code itself)<\/p>\n
so, been busy :)<\/p>\n
some of these have made it to the stable branch… i guess i’ll put more of them in there as things actually stabilise. Especially since linux.org.au is actually running the stable 0.2 branch now (which is nowhere near final).<\/p>\n
Have no real schedule or ideas on when to release 0.2, maybe when i’ve done the positions stuff, fixed the CSS and made a “edit member info” (accessible to admin and each member) UI. That’d be a real big leap from 0.1 :)<\/p>\n
I’d like to put GPG stuff on the cards for 0.3…. but it’ll be tricky finding a nice way to integrate everything. I’m thinking along the lines of a UI where a person enters their key ID, fingerprint and keyserver (then we pull the key using gpg). To help verify, we could then send all email gpg signed\/encrypted :)<\/p>\n
we’d then have to have a not-well-trusted GPG key for memberdb installations – which could be… interesting….<\/p>\n
but hey – it’s the one big feature request from an outside group.<\/p>\n
They want to have GPG signed applications – but maybe they’ll settle for sending GPG encrypted mail to the applicant (saying “confirm membership like this”). The validity of the key can always be checked before approving the membership – it’s going to have to be semi manual anyway.<\/p>\n","protected":false},"excerpt":{"rendered":"
been doing a fair bit of mods to memberdb recently – getting features in. – new css based look (which is almost correct) – more solid code around the place – better error reporting (that needs debugging… hahaha) – a … Continue reading