|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Avoiding Post-January 3rd CD Explosion/Confusion
Make the threads that you know will be there in advance. For example, make a strategy thread a day or two before kickoff, or drivetrain discussion. Anything that will always be necessary can be made in advance.
|
|
#2
|
|||||
|
|||||
|
Re: Avoiding Post-January 3rd CD Explosion/Confusion
Quote:
Rather than make draconian rules, if you run across duplicate threads, kindly remind the OP to use the search feature and provide a link to the original thread! This also applies to rules questions - don't just tell the poster to read the manual if they have a question - quote a specific R# or G# rule that will help them. Not searching before making a new thread or asking an [obvious to you] rules question are mistakes that all of us made when we were new. Show some GP and help these users. |
|
#3
|
||||
|
||||
|
Re: Avoiding Post-January 3rd CD Explosion/Confusion
Could we do a community sourced 2015 FAQ?
|
|
#4
|
||||
|
||||
|
Re: Avoiding Post-January 3rd CD Explosion/Confusion
I like the idea, but I don't like the idea of someone giving a bad/non-official answer to a rookie team's question and the team not being able to compete because of it. The FIRST Q&A is the truly official place to go for these things.
However! (just thought of this) - we could do a less official kind of Q&A for the questions that FIRST refuses to comment on - something like 'which drivetrain would be best - 4 CIMs or 6 CIMs?' |
|
#5
|
||||
|
||||
|
Re: Avoiding Post-January 3rd CD Explosion/Confusion
Quote:
|
|
#6
|
|||||
|
|||||
|
Re: Avoiding Post-January 3rd CD Explosion/Confusion
Quote:
When I answer a question, I tend to go "Here's the rule, your setup looks like it's doing this, as a [ref/inspector as appropriate] I'd tend to rule that way depending on actually seeing what's up" on any questionable rule. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|