[wplug-internet] WPLUG Membership Roster

[Michael Semcheski]

My initial thought is that one way to handle this would be to create a flat
text file in /home/board and put it under version control.

Letting members edit their own details comes later.  If we did use mediawiki
as the authenticator, I would want to research it a little to make sure it
is suitable.

The better solution might be to create an LDAP directory with members in
there (and their password hash) and see if we can't use that as the basis
for logins to mediawiki.

Mike

On Sun, Jun 22, 2008 at 1:05 AM, Vance Kochenderfer <vkochend at nyx.net>
wrote:

> I am posting this discussion to the wplug-internet list in the
> hope of recruiting others to research and give opinions on this
> subject.
>
> The task is to implement a membership roster for WPLUG.  The
> roster would store a few pieces of information for each member:
> first name, last name, e-mail address, phone number, street
> address, and membership expiration date.
>
> Basic requirements would include
>  * Authentication (detailed below)
>  * Reporting (at least list of current members)
>  * Notification (e-mailed notice to members prior to expiration
>    date)
>
> The authentication would limit changes to a few individuals.
> Ideally other access would be possible, such as members being able
> to see and possibly change their own details, and perhaps all
> members' names being publically available.
>
> If this is to be a web-based system, it would be nice if the
> authentication could tie into the existing Mediawiki sign-in.
> Dave describes one possible workflow below.
>
> Dave Kraus wrote:
> >
> > I may have found a method to introduce a membership roster into
> MediaWiki.
> >
> > There are two extensions:
> > http://www.mediawiki.org/wiki/Extension:Semantic_MediaWiki
> > http://www.mediawiki.org/wiki/Extension:Semantic_Forms
> >
> > When a new member wants to join (either in person or via the web), he
> > or she is instructed to create a wplug.org Wiki account.  The member
> > then proceeds to complete the membership Form creating his or her
> > membership record.  The membership form must be protected allowing
> > completion only by email verified accounts.  The form would
> > automatically assign the member a unique ID, which one of the SysOps
> > (i.e. Secretary) would relate to a controlled membership payment
> > roster.  Once payment is received and processed, the SysOp would
> > update the membership payment roster, and the member's record page
> > stating the effective membership date and expiration.
> >
> > Note, this idea is still at the 10000 ft level.  I am sure more
> > automation could be added.  Please comment.
>
> If anyone has an idea of how this integration could be
> accomplished, or an alternative suggestion, please post here to
> the list.  Thanks!
>
> Vance Kochenderfer        |  "Get me out of these ropes and into a
> vkochend at nyx.net          |   good belt of Scotch"    -Nick Danger
> _______________________________________________
> wplug-internet mailing list
> wplug-internet at www.wplug.org
> http://www.wplug.org/mailman/listinfo/wplug-internet
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.wplug.org/pipermail/wplug-internet/attachments/20080622/7db3e5ee/attachment.html