Difference between revisions of "MembershipManagement"

From LiluxWiki
Jump to navigationJump to search
Line 20: Line 20:
  
 
== Requirements ==
 
== Requirements ==
= Requirements from Hackerspace =
+
=== general requirements ===
https://www.hackerspace.lu/wiki/Membership_Management_Tool#Requirements
 
= Requirements from LiLux =
 
 
*
 
*
 
*
 
*
= general requirements =
+
=== Requirements from Hackerspace ===
 +
https://www.hackerspace.lu/wiki/Membership_Management_Tool#Requirements
 +
=== Requirements from LiLux ===
 
*
 
*
 
*
 
*
 +
  
 
== Existing software/tools ==
 
== Existing software/tools ==
Line 34: Line 35:
  
 
=== tools ===
 
=== tools ===
* nuBuilder [http://#]
+
* nuBuilder [http://www.nubuilder.com]
  
=== See also ===
+
=== related sites ===
 
* https://www.hackerspace.lu/wiki/Membership_Management_Tool
 
* https://www.hackerspace.lu/wiki/Membership_Management_Tool
  

Revision as of 17:41, 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


Requirements

general requirements

Requirements from Hackerspace

https://www.hackerspace.lu/wiki/Membership_Management_Tool#Requirements

Requirements from LiLux


Existing software/tools

software

tools

related sites


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