Moving forward...
It's obvious that with the number of posts already that Jack-n-Coke hit on a winner for the first test candidate.
In my previous posts I've suggested 2 types of threads - a "working" thread and a sticky "final" product. This was to keep the final reports clean and easy to find. With the great discussion going on here maybe we need 3 types: general discussion related to a test (testing suggestion, testing theories, post-report discussion,and other administrative stuff like "who has an XYZ to use", etc) the "working" thread (where only test protocol and data is posted), and the final work ("sticky" to make it easy for outsiders to find) This would allow us to have a fairly "clean" thread related to the actual testing of a subject, with the discussion in another concise area (to keep it all easy to follow). I don't think that it's practical to have dozens and dozens of posts on a subject in the actual "working" thread - but all of the input is great! (Especially Doc's post) So, to me, it's obvious we need all 3 types.
Please give me some feed back on this - I tend to be an "organizer" and lean towards being very detail oriented and anal about neatness - I realize not everyone is the same way and don't want to seem like I'm trying to take over the whole forum.
This review (Crossfire) is going to be our first, so along the way we're building processes that'll make the subsequent projects much easier. That's what I'm aiming for with different "classes" of threads - a forum that serves us well and one that is easy to navigate for whoever comes to see what we're up to.
-Calvin
It's obvious that with the number of posts already that Jack-n-Coke hit on a winner for the first test candidate.
In my previous posts I've suggested 2 types of threads - a "working" thread and a sticky "final" product. This was to keep the final reports clean and easy to find. With the great discussion going on here maybe we need 3 types: general discussion related to a test (testing suggestion, testing theories, post-report discussion,and other administrative stuff like "who has an XYZ to use", etc) the "working" thread (where only test protocol and data is posted), and the final work ("sticky" to make it easy for outsiders to find) This would allow us to have a fairly "clean" thread related to the actual testing of a subject, with the discussion in another concise area (to keep it all easy to follow). I don't think that it's practical to have dozens and dozens of posts on a subject in the actual "working" thread - but all of the input is great! (Especially Doc's post) So, to me, it's obvious we need all 3 types.
Please give me some feed back on this - I tend to be an "organizer" and lean towards being very detail oriented and anal about neatness - I realize not everyone is the same way and don't want to seem like I'm trying to take over the whole forum.
This review (Crossfire) is going to be our first, so along the way we're building processes that'll make the subsequent projects much easier. That's what I'm aiming for with different "classes" of threads - a forum that serves us well and one that is easy to navigate for whoever comes to see what we're up to.
-Calvin




Comment