- Joined
- Dec 2, 1999
- Messages
- 12,249
I had this weird idea, what if we did a "Tour of America, the 50 State Pass Around". There would be one person in each state.
Here's my questions:
Time, absolute best case would be probably 1 year to complete. Worst case would be 2 years, or never.
Would there be enough excitement to be able to substain a continued interest? How would we keep the interest up over 1 or 2 years?
Could we ask Spark to add a forum specifically for passarounds so they don't get lost in the "noise" of the general forums?
In reference to the above, it would be great to have a little database accesable over the web that lets you signup for passarounds, View who is next, etc. so that the "book keeping" of who is next wouldn't fall on one person.
I actually could rig something up using mysql and perl, but I don't know how to "deliver" the application, or even if perl and mysql would work for Spark and if there is a simpler way.
The problem in a nutshell is that a lengthly pass around just doesn't "scale" well in terms of time and substained interest.
Any ideas?
Here's my questions:
Time, absolute best case would be probably 1 year to complete. Worst case would be 2 years, or never.
Would there be enough excitement to be able to substain a continued interest? How would we keep the interest up over 1 or 2 years?
Could we ask Spark to add a forum specifically for passarounds so they don't get lost in the "noise" of the general forums?
In reference to the above, it would be great to have a little database accesable over the web that lets you signup for passarounds, View who is next, etc. so that the "book keeping" of who is next wouldn't fall on one person.
I actually could rig something up using mysql and perl, but I don't know how to "deliver" the application, or even if perl and mysql would work for Spark and if there is a simpler way.
The problem in a nutshell is that a lengthly pass around just doesn't "scale" well in terms of time and substained interest.
Any ideas?