My reading of this Q&A is pretty straightforward:
They want the team associated with the robot to be the ones primarily working on the robot - not any other team.
They want teams to be able to help each other, but not build entire mechanisms for another team.
I think this is fair and 100% within my interpretation of what FRC is about.
Why this thread even exists is because it's
nearly impossible to come up with a rule that distinguishes between helping another team vs building an entire mechanism for them. I don't envy the GDC/Q&A responders, because I couldn't come up with a ruling that effectively distinguishes between the two myself.
But, I believe in the spirit of this response, and intend to respect it.
In hindsight, I'll be the first to admit that we broke this rule at GTRC. Our tote-based ramp was constructed from COTS materials at the event, but it was designed, constructed and tested only by members of our team. Because the ramp had to be completed and tested before alliance selections began, we wouldn't have known who our 3rd alliance partner was in order to involve them.
However, I honestly believe it would have been a better experience for everyone if teams who included the ramp as part of their robot were also the ones who constructed it. Now we're being asked to ensure that this happens, and I think that's pretty reasonable.
Does this ruling eliminate the possibility of ramps entirely?
No. But you have to go about the process differently now. Release your
ramp designs publicly, and see if there are any teams who are willing to construct them. Truthfully, this is probably what we should have done at GTRC, and had we done so, I think it would've been a pretty awesome experience. It's too bad our ramp didn't come together until Saturday late morning, but I guess we'll have another chance to do it right in Hawai'i next weekend.