Difference between revisions of "MembershipManagement"
From LiluxWiki
Jump to navigationJump to searchm (→suggestions:) |
|||
Line 81: | Line 81: | ||
* tutorial available for instance from LinuxDays 2003, server tutorial | * tutorial available for instance from LinuxDays 2003, server tutorial | ||
* LDAP can be frontend to SQL database | * LDAP can be frontend to SQL database | ||
− |
Revision as of 20:35, 28 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
definitions
association
an organisation who will use the application: LiLux, HackerSpace, Scouts, …
member
a member is a person listed in the membership software
group
a group is an combination of diffrent members from the membership software a group can be made of a parent-group and/or can be in a child-group
parent-group --- group --- child-group --- child2-group
activity
an activity can be e meeting / camp / .... The activity is created by an operator but the registered members can subscribe to the activity by answering a mail or completing a web form
Analysis
what do we have as software?
- a php script
what are the functions in the software?
what is the need for the new software?
which are the fonctions needed?
- list printing of groups / activities / ...
- printing of membership cards
- use mail adresses in mailman
- unlimited creation for groups / activities
Requirements
general requirements
- manage membership easily
- assign 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