View Single Post
  #14   Spotlight this post!  
Unread 20-03-2011, 20:22
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: I was wondering...

Quote:
Originally Posted by Joe Ross View Post
Grammatically, the modifier goes immediately after the item it's modifying. In this case, saying not affiliated with an individual team goes immediately after open sources, not after software modules. It says that the code must be posted somewhere not affiliated with a specific team. You can't post it on your team website or your team forum, because teams wouldn't be expected to look there. You can post it on a FRC community accessible we resource (eg chiefdelphi, FIRST Forums, NI FIRST community, think tank, etc) or a industry source code repository (eg google code, github, etc).

This does not conflict with <R22>
Joe - I hadn't interpreted the combination of R22 and the COTS definition as requiring publication on a non-team site, and was intending to publish our 2011 code in a new technical section of our team's web site, posting links on CD to our resources.

However now I've looked around a bit more, I think we will be using the Google Code solution.