Well, for the alerts / subscription system we talked about - tags seemed MUCHO importante. If your not going to mess things up, I'd love to see tags working, and then review how / if we can still do that. Are you still up for the form / system / yea?
Also - should I perhaps enable galleries / work with one - http://www.tulsanow.org/forum/index.php?action=gallery;sa=view;id=1
That site is running SMF - and I thought about it after seeing it. Course, I think putting them up on Facebook might be a better system heh, dunno.
X A
Here's what we need, people.
a.)
A requirements doc. What are the top ten reasons people come to OKG, and what are the top ten reasons they should come to OKG. Take those 20 things, prioritize them through a series of round tables with the users, drop the bottom 10, and writer your requirement doc.
b.)
Code versioning and a build system. As any project gets larger (especially with multi-personed teams) version control and build systems become more important. Would it be nice to have a sandbox environment on your laptop, a staging server that mirrors production, and a production server that only gets updated when it's been vetted? The answer is yes.
c.)
Reboot OKG. I'm not saying we don't use SMF for the forum, but I think it's time to run the core site on a more robust engine. I'm platform agnostic, so it's definitely something we can talk about.
d.)
More cookies. We need them.
That's my summary of this thread, and I think if we even just build a requirements doc we'd be a long way to saving us a huge amount of hassle in the next 6 months. Scope creep is evil, and a requirement doc will help us keep on track.
Or maybe I'm crazy!