I do, in a way.
In FIRST, we help each other. White papers, mentoring other teams, and so on. However, I think that it’s reasonable for teams to withhold a little bit of the “secret sauce” that makes their robots uniquely better-suited for a certain task.
Nearly every field has certain tricks that people keep secret from their competitors to get a slight edge. Using a tool you fabricated yourself to reach that one darn screw hole. Stuffing a 500-HP engine into a small car and making it look stock. Writing the program that does what you want your way. None of these may be particularly public, but nobody raises a stink about them.
That doesn’t mean, however, that you can’t attempt to figure it out for yourself. 25, for example, goes to a heck of a lot of competitions (last year, I recall New Jersey, Palmetto, the Championship, and a bajillion-million off-seasons). Each of those events has a bunch of camera-wielding nuts, all snapping pictures of the robot in action. And going into 25’s pit, there’s no barriers stopping you from getting up close and personal with their robots (unless you count fear of being bearhugged by Big Mike as a barrier). So one could probably get some good views of what they’re doing.
So perhaps a team doesn’t want to let out all of their secrets. That just gives you a bit of a challenge. Go up to the team’s pit. Ask questions. Take pictures. Figure out how it works. Test it out when you get home. Then YOU can post it on Delphi (giving credit where it’s due) and be showered in praises, green dots, and photoshoppage.
As long as there’s a competition involved, someone will have a brilliant idea to give themselves an edge. Sharing it is awesome, and I highly recommend it, but nobody ever said it was a requirement.