Dissemination of Information From FIRST

[EricH]

Originally Posted by JaneYoung

If you feel there are problems with the way information is gathered and distributed, develop a better system and suggest it directly to FIRST.

That's the problem... The current system is just like democracy; it's the worst system, except for all the others that have been tried.

I'm not going to propose a system directly, but I'm going to outline some key aspects.

1) Must be made known to all teams. Why? Because Bill's Blog may or may not be known to all teams. CD certainly isn't (we wish it was). The Q&A? Who knows. The only way to get information out to all teams is to use an Email Blast, which is kind of impractical.

2) Must be central. Also known as online. ONE site that isn't blocked much, or can be unblocked by special request, would be preferable. 2-3 at the most.

3) I want to say that you must sign in to access material, but that's going to be hard and I don't think it's a good idea. The reason is so that usage can be tracked. Did team WXYZ check within build season? No? Maybe a nearby team can be contacted to help them. This is also highly impractical.

4) Must link to places to get more information. How many helpful links does CD have? How many times are users referred to a place not on the site?

Maybe one page on the FIRST website, with the Documents and Updates, that lists all the resources available and what they cover; e.g., Control System forum--Control system questions. This too would have its failings; I know I don't read all the documentation! (For example, I don't think I have ever read the Guidelines, Tips, and Good Practices.)

[JaneYoung]

Originally Posted by EricH

I'm not going to propose a system directly, but I'm going to outline some key aspects.

The post above mine by eagle33199 holds a lot of wisdom and common sense.

And, if this thread was used to gather some in-put/suggestions such as the ones you are mulling over, Eric, that could have positive benefit for the community.

In years past, folks have complained that members of FIRST were not accessible. In my opinion, Bill's Blog is a way of addressing that complaint. It is also another avenue, not the only avenue, for providing information. Chief Delphi is an informal resource and quite frankly, excellent discussion opportunities can often turn into quibbling and useless nattering rather than staying informative and helpful. The Q&A on the FIRST website and the team updates are formal resources and teams should be aware of them. It is true that new teams or teams with poor organizational skillsets can get bogged down and it is great to think of ways to help them. It is also true that teams have to learn to swim on their own at some point. It is always good to think of and develop ways to help the process but in the end, it is up to each mentor to read the manual, the updates, the FIRST website, and to learn about the resources and help direct the team in how to access and use them.

If the resources can not be readily accessed then it is wise to let FIRST know that and what the problems are.

[GaryVoshol]

In the Communications section of the manual (you know, one of those sections no one reads) it mentions Team Updates, Email Blasts and Q&A. They even note that some teams have someone dedicated to keeping track of these sources. Teams are informed if they choose to be informed.

Every year FIRST has evaluations, by written survey or seminars or both, in which teams can give feedback. If you have a better idea about disseminating information, let them know about it.