Difference between revisions of "MembershipManagement"
From LiluxWiki
Jump to navigationJump to search| Line 21: | Line 21: | ||
== Requirements == | == Requirements == | ||
=== general requirements === | === general requirements === | ||
| − | * | + | * manage membership easily |
| − | * | + | * assigne members to a group / to a activity |
| + | |||
=== Requirements from Hackerspace === | === Requirements from Hackerspace === | ||
https://www.hackerspace.lu/wiki/Membership_Management_Tool#Requirements | https://www.hackerspace.lu/wiki/Membership_Management_Tool#Requirements | ||
Revision as of 17:51, 5 April 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 ...
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
Requirements
general requirements
- manage membership easily
- assigne members to a group / to a activity
Requirements from Hackerspace
https://www.hackerspace.lu/wiki/Membership_Management_Tool#Requirements
Requirements from LiLux
Existing software/tools
software
tools
suggestions:
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
