Hello everyone!
I am in the middle of developing a web application that makers can use to track a tour. It is web based with the backend written in Python and using SQLite as the data store.
If that sounds interesting to you or you have a desire for a particular feature, then please read on. Otherwise, it’s pretty safe to ignore the rest of this post. 
This will be free web based software that I will make available through sourceforge or github. By free, I mean you can use it for any purpose, including commercial applications. (BSD license) By web based, I mean that the tour participants will enter their own data in a web form. The programming is nothing fancy, but I will not “release” it until it is stable. (If you want to see what I have so far, thats no prob, but I warn you that it’s messy and in active development.) I am going for complete and easy to modify.
Features: (not an exhaustive list)
- Users will have a login ID and a password, along with a verified email address.
- Users will enter their own information, after reviewing the rules and agreeing to a disclaimer.
- Users will also be able to log in to find out how the tour is progressing.
- The tour owner will be able to send emails to blocks of people, or to individuals in the database. The blocks are defined by an individual’s status. For example people who have not seen the whistle yet will have the status of “unseen” You can send everyone in the database with that status an email. All users have one or more statuses.
- The tour owner will have the ability to manually add/delete/modify users.
- The admin will also be able to put in notes that are connected to individual people. If the admin wants to keep notes of some kind, then they can connect the note to themselves.
- Stuff like the SMTP server to use are kept in the database.
As extra goals, that are beyond what I really need:
- A simple yet complete email client that can receive email as well as send it. Received email will be attributed to a particular person, so you don’t have to hunt for the thread every time you communicate with them. Notes are a half-vast solution to that problem.
- Events.
a) An even could be triggered when a user changes status of via a timer.
b) Event notification could happen via email to the sysadm, or via a page listing the evens when they log in.
c) An event could also be posted to a user, such as “it’s time to send the whisle and here’s the address”.
There are lots of other stuff around this concerning logging people in a managing sessions and all. I am mainly just throwing this out there to see if anyone thinks it would be useful besides me.
All the best!
-=chuck=-