How should a team handle third-party resources like open-source code?

• A. Attribute properly, respect licenses, and ensure compatibility with competition rules.
• B. Use them without attribution to speed up development.
• C. Discard licensing terms so you can modify freely.
• D. Ignore compatibility with the competition rules.

Answer: (A)

When using third-party resources like open-source code, treat licenses and competition rules as part of how you build the project. The license attached to each resource explains what you must do to use it legally—often this means giving proper credit to the authors, including the license text with your project, and sometimes sharing your own changes or restricting certain uses. Because a robotics competition has its own rules about what can be used and how, you also need to verify that the way you use any third-party code is allowed under those rules.

Practical steps to follow include identifying the license for every resource you incorporate, keeping a copy of each license in your repository, and including attribution in your code or documentation where the resource is used. You should also confirm that the license terms won’t conflict with how you deploy or distribute your robot code within the competition framework, and document all third-party components you rely on. If a license would clash with competition rules, you would need to find an alternative.

This approach—proper attribution, license compliance, and alignment with competition requirements—keeps development ethical, legal, and fully aligned with the event’s expectations. Using resources without attribution, ignoring license terms, or disregarding competition rules can lead to legal issues or disqualification, so those pathways are not acceptable.