Membership Committee To Do List

  • Document the new voting system
    • New voting system should be embedded to mango. However this has to wait discussion on improved voting system.
  • Document the new membership management system (Baris)

  • Document rt3 usage and guidelines for FoundationMembership

  • Add elections integration in mango (create/modify elections and candidates, create the temporary tokens, mail the instructions to the voters, etc.)
    • This action is waiting for decision on improved voting system.
  • Move to RT3 for the membership applications queue

  • Write a "being a candidate" howto (see this thread)

  • f.g.o/vote/ improvements:
    <thos> vuntz|away, you didn't use <label>'s on vote.php :-(
    <vuntz|away> thos: where is <label> not used?
    <thos> vuntz|away, on the optinos
  • problem with the script that sends the ballot?

    <cam> and also the script ;P it stopped working due to wide chars
  • Add a new table to foundation database to store denied applications

    • Isn't it enough to have this in rt3?

      • If rt3 has track of this record, (or at least if we can trace it through mail archives, it's enough.

  • Add an url field to the db pointing to the application of each member, so it's possible to find why he was accepted (RT3 would be enough for that)

  • last_update in the db should be updated to NOW() at each update of the row

  • Keep record resigned members in membership database. (Baris) "database will only hold date if member is resigned"

  • We need auto mails for membership management system for:

    • Renewals

    • Application Approved

    • E-mail update (to previous mail to prevent fraudent requests)
  • Cronjob application (php-cli) for daily check of current members, and if there needs to be a renewal warn those having their membership expired

  • -- (Call for new Membership Committee Volunteers)--

MembershipCommittee/ArchivedMCPages/ToDo (last edited 2011-06-02 21:48:50 by AndreaVeri)