@iron programmer,
Quote: "I regard your ruling that my "progress" is not to your liking as another way to lock my posts"
*Sigh*
I like team requests. I want to see more team requests. I don't think we see enough. But... there is a minimum requirement, otherwise we get a proliferation of team requests containing one or two lines of text, filled with flames from forum lawyers who have nothing better to do - in exactly the same way we had when we did have a dedicated team request forum.
I'm not locking your posts because you posted them. I'm locking team request posts because they don't meet the very simple requirements on the team request page - I hope you see the distinction.
@OBese87,
We've been there, done that, flushed it down the toilet.
Someone can post a minimal team request in a few minutes, tying up a moderator for those same few minutes. Now multiply that up by 10, 20 or 50 a day from excited new users, and you are tying up a moderator for a large portion of their own time - Now, remembering we're unpaid volunteers, what mod is going to spend even an hour of their day reading through posts in which they have absolutely no interest, knowing they'll have the exact same task tomorrow and every day from that point? One or two maybe, but even as few as 10?
Now consider what we have now - easy-to-follow and explicit rules, where all you really need to do to be allowed to post a team request is show that you are serious about your project, are willing to do what it takes
and can prove it.
Then look at that from my point of view. I see a post every few days or so. I open it and within a minute I can make one of two decisions - I can either lock it after posting a link to the team requests page, or I can post an OK and leave it - Most of the time it's really obvious which is which as soon as the page has loaded.
I know which I prefer, and no offense meant to iron programmer, but that's what I saw and still see after reviewing the posts.
