|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
|||||
|
|||||
|
Re: Team 1676-2006 Source Code Released!
Quote:
|
|
#17
|
|||||
|
|||||
|
Re: Team 1676-2006 Source Code Released!
This code will be off the internet in a few hours. Nothing to worry about - their programmer just did not go on CD for a while so I brought this to his attention.
|
|
#18
|
|||||
|
|||||
|
Re: Team 1676-2006 Source Code Released!
Quote:
Sorry about that, we weren't aware of the issue until your post. As Bharat mentioned, it will be addressed immediately. The short version is just as Bharat wrote: 'nukem' just wasn't on CD for a while, and did not see your message. Don |
|
#19
|
|||
|
|||
|
Re: Team 1676-2006 Source Code Released!
Sorry about all this, I have been away from cd for awhile working on other things. Anyway I posted the code thinking it would be a gracious and professional thing to do trying to help other teams with our source code. I only included Kevin's code so people could download the code all in one place. I looked in the readme, and for a license file, both which did not mention anything about not releasing the code but I did not think to look in the source code itself (my code is in separate files so I rarely look at Kevin's stuff). Anyway the code is hidden now on the project page.
Sourceforge has a policy of only deleting project files on a case by case basis, I have put in an urgent request for the files to be deleted Sourceforge. I hope in the future Kevin, the FIRST foundation, and the FIRST community will take a GNU approach to things, but until then I will do my best to get the code removed from the site as quickly a possible. |
|
#20
|
|||
|
|||
|
Re: Team 1676-2006 Source Code Released!
Quote:
Quote:
|
|
#21
|
|||
|
|||
|
Re: Team 1676-2006 Source Code Released!
You just need to make sure you clearly state that if you use a fork of a piece of software that you can only goto the place you got it from not the place they got it from. In the open source community you always work up, for example if I had a problem with gaim I would file a bug with gentoo(my distro) and if they couldnt resolve it and gentoo developers decided it was a gaim problem it would be resolved upstream and I would then file a bug with gaim. The Linux kernel has a definition were you can defined what extra version it is(like if your using the gentoo patches its call 2.6.16-gentoo). All the code needs is a version definition and state in the readme that if you redistribute the code you need to change that to your team number.
|
|
#22
|
|||
|
|||
|
Re: Team 1676-2006 Source Code Released!
Also keep in mind that Kevin stated on this thread that patch files were ok. There are three problems with that.
1. If you look in a patch file parts of the original code are in the actual patch file not just the the newly added code. 2. Under what was said in the pervious post by devicenull people will still go back to Kevin I dont think that distributing a patch file instead of the full source would make any difference. 3. Sooner or later some teams are going to include a script file in there zip file that will look like this Code:
wget http://kevin.org/frc/frc_camera.zip cat camer_code | team_xxxx.patch -p1 |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 2006 CMUcam2 Code | Kevin Watson | Programming | 81 | 10-02-2007 20:17 |
| 2006 FRC Team Update 01 | dez250 | General Forum | 0 | 11-01-2006 11:32 |
| Improving the Efficacy of a Team | Jaine Perotti | Team Organization | 5 | 24-05-2005 19:27 |
| Need Help and Suggestions - Creating a TEAM | Freddy Schurr | Team Organization | 7 | 30-03-2005 22:00 |
| heres the code. y this not working | omega | Programming | 16 | 31-03-2004 15:18 |