Thread: Michigan, be honest, how is the district model?
View Single Post
  #71   Spotlight this post!  
Unread 01-07-2011, 11:23
gblake's Avatar
gblake gblake is offline
6th Gear Developer; Mentor
AKA: Blake Ross
no team (6th Gear)
Team Role: Mentor
  
Join Date: May 2006
Rookie Year: 2006
Location: Virginia
Posts: 1,934
gblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond reputegblake has a reputation beyond repute
Re: Michigan, be honest, how is the district model?
Quote:
Originally Posted by ratdude747 View Post
...
due to this, if Kentucky ever went to a district setup, my dream of bringing FIRST to the Indiana side of the river city, would be much more difficult.
...
Remember, it isn't the notion of a "District model" that is the root of this situation. The root cause is that so many folks have a knee jerk tendency toward drawing district boundaries along state borders.

Force them to realize that being in one state or another (or one county/city or another) has nothing to do with being on a robotics team, and tell them to tell local and state officials that you think both they and the robotic programs simply don't need or want to create artificial boundaries at state borders.

When the old canard about state/local funds only being used to pay for folks inside of a boundary gets raised, simply tell them to go right ahead and do it; but to not confuse that support with saying that tournaments or other activities can only include those supported teams. They will find a compromise fast enough if folks like yourself stick to your guns. "Rules" like those get broken constantly.

Sure, in-state teams might get funding or other support from their state; but! that doesn't mean that the only way to draw a district boundary is to create one that excludes contact with or sharing costs with other teams and jurisdictions.

There is a huge difference between deciding to support a group of teams and deciding to exclude a group of teams. Folks often make the jump from one decision to the next for absolutely no good reason.

Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Reply With Quote