View Single Post
  #16   Spotlight this post!  
Unread 26-03-2006, 17:45
eugenebrooks eugenebrooks is offline
Team Role: Engineer
AKA: Dr. Brooks
no team (WRRF)
 
Join Date: Jan 2004
Rookie Year: 2001
Location: Livermore, CA
Posts: 601
eugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond reputeeugenebrooks has a reputation beyond repute
Re: Team 1676-2006 Source Code Released!

Quote:
Originally Posted by devicenull
I would check with IFI on that first.. Check out the bottom of any IFI page..


I would also do some more research on that before you say things like IFI doesn't have a copyright on their code..

From here

From my understanding, unless they explicitly say they release the copyright on their code, it is NOT public domain.
Notwisthstanding the post in wikipedia, the authoritative document that
it is, any intellectual property lawyer will tell you that if you want to
defend a copyright on your code, your first step is to include the
copyright in every source file, explaining terms of use that you intend
to defend. I know this because I have dealt with intellectual property
lawyers on such matters. This is the standard practice in the industry
for computer code, and it is not to be confused with the standard
practice for phonograph records.

I did not say that IFI had released their code into the public domain.
That usually entails a copyright notice explicitly indicating such handling,
something that I am also familiar with and use now and then. I did
use the term, the cat is out of the bag, and I think that common sense,
if not case law, prevails here.

IFI releases their code as a template for teams to use, and obviously
from their actions (or lack thereof), does not find teams sharing modified
snippets of their code objectionable as this is the purpose of the FIRST
robotics activity. This is to be applauded and I applaud it. Not to
worry, when I see indications that I should change my view, I will
post the adjustment...

Eugene Brooks

Copyright 2006, Eugene D Brooks III. This is my opinion, which can
be copied and shared in any form desired, but only I get to change it.