[hackerspaces] member management software

michael howard mik.howard at gmail.com
Wed Jan 13 21:42:27 CET 2016

Someone suggested implementing delays in opening doors for people when they
are late.

2016-01-06 13:35 GMT-02:00 Joshua Pritt <ramgarden at gmail.com>:

> We use Seltzer at Melbourne Makerspace.
> https://github.com/elplatt/seltzer
> And we made our own RFID door lock that automatically denies access to
> those who haven't paid their dues in 3 months.
> https://wiki.melbournemakerspace.org/projects/RFIDDoorLock
> Two other hackerspaces have already duplicated or in the process of
> duplicating our RFID door lock.
> Prishtina Hackerspace in Kosovo http://www.prishtinahackerspace.org -
> http://www.prishtinahackerspace.org/haccsy-hackerspace-access-control-and-check-in-system
> and another one has emailed me with questions.
> On Wed, Jan 6, 2016 at 10:31 AM, sheila miguez <shekay at pobox.com> wrote:
>> What do people use for member management? I'm looking for open source
>> projects.
>> Requirements and nice to haves off the top of my head
>> * Open source license
>> * Easy to contribute too
>> * Community/dev culture that scores well on being able to run sprints
>> according to OpenHatch's event handbook, <http://opensource-events.com/>
>> * Written in a language that our active technical members use (python, go)
>> * Easily adaptable to our space member logic (membership tier, equipment
>> permissions, &c.)
>> * Service API that provides enough member data so that we can use it with
>> our RFID stuff
>> * SSO
>> * Approachable deployment
>> I've done some googling and found a few. One that jumped out at me is
>> Tendenci, <https://www.tendenci.com/>.
>> * It has a service API, yay. It uses django tastypie which is a little
>> meh compared to django rest framework because the latter has more active
>> development and support from the community. On the other hand, I use
>> tastypie at work and have experience with it.
>> * Their repo, <https://github.com/tendenci/tendenci>, and it has a lot
>> of recent activity.
>> * I haven't looked for evidence for contributor friendliness yet. Looking
>> at the graph on github shows mainly the employees of the company. There are
>> advantages/disadvantages for that. Risks: It might become abandonware. It
>> might not be easy to contribute to. Benefits: Active development, option
>> for hosting, &c.
>> * I haven't tested the ease of deployment.
>> * The code base is a bit large, which may be a code smell.
>> * It looks like they've architected the project so that it is pluginable.
>> This might mean it is easy to adopt to our rules. I haven't dived in to
>> verify this.
>> --
>> shekay at pobox.com
>> _______________________________________________
>> Discuss mailing list
>> Discuss at lists.hackerspaces.org
>> http://lists.hackerspaces.org/mailman/listinfo/discuss
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20160113/bfb8906b/attachment.html>

More information about the Discuss mailing list