View Single Post
  #4   Spotlight this post!  
Unread 04-04-2011, 01:29
MikeE's Avatar
MikeE MikeE is offline
Wrecking nice beaches since 1990
no team (Volunteer)
Team Role: Engineer
 
Join Date: Nov 2008
Rookie Year: 2008
Location: New England -> Alaska
Posts: 381
MikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond reputeMikeE has a reputation beyond repute
Re: Open Source Code

From the definition of COTS parts in section 1 of the game manual:
Quote:
For the purposes of the FRC, generally available software modules obtained from open sources (e.g. professional publications, commonly used FRC community-accessible web resources, industry source code repositories, etc.) that are not specifically affiliated with individual FRC teams shall be considered COTS items.
The Blue Box in <R22> clarifies this further in the last example:
Quote:
... After completing the software, they post it in a generally accessible public forum and make the code available to all teams. Because they have made their software generally available (per the Blue Box in the definition of COTS, it is considered COTS software and they can use it on their ROBOT.
That would seem to add a significant incentive to open source your code: enabling re-use between seasons.
Reply With Quote