Difference between revisions of "MembershipManagement"
From LiluxWiki
Jump to navigationJump to search| Line 23: | Line 23: | ||
=== See also === | === See also === | ||
* https://www.hackerspace.lu/wiki/Membership_Management_Tool | * https://www.hackerspace.lu/wiki/Membership_Management_Tool | ||
| + | * http://archreactor.org/wiki/index.php/AROS | ||
== suggestion: use LDAP == | == suggestion: use LDAP == | ||
Revision as of 21:08, 16 March 2010
Membership Management
Kick off Meeting
Wednesday 27/01/2010
Points discussed:
* Separate members for each club (a club should not know if a user is in a different club) * Use a pseudo will be used as key for the user. * API to member list to include other tools like libraries ... * Integration with mediawiki/joomla ...
Requirements from Hackerspace
https://www.hackerspace.lu/wiki/Membership_Management_Tool#Requirements
Task List
- setup cvs - ThierryCoutelier
- prepare initial design on wiki
- setup test web page
- Add project to TRAC: (https://www.hackerspace.lu/trac) - David Raison
See also
- https://www.hackerspace.lu/wiki/Membership_Management_Tool
- http://archreactor.org/wiki/index.php/AROS
suggestion: use LDAP
- user data, can be standard schema + whatever we may additionally need
- would facilitate SSO functionalities, incl. integration with misc tools such as CMS, Wiki, shell access, ...
- not complicated to set up and get running
- tutorial available for instance from LinuxDays 2003, server tutorial
- LDAP can be frontend to SQL database
