|
|
| Author |
Message |
Guest
|
 Posted: Apr 07, 2004 8:07am Post subject: |
 |
|
| Quote: | | how much of modification is needed before you can realy say its your name of IRCd ? |
That's really a judgement call. I suppose legally, as far as the GPL is concerned, you don't have to modify it at all. However, ethically, you probably should make a significant change because you claim someone elses work as your own, and even then you should give credit to those who wrote the original. |
|
| Back to top |
|
 |
DjMadness-
Newbie
Joined: 10 Jan 2004
Posts: 70
|
| Posted: Apr 07, 2004 8:09am Post subject: |
|
|
| Anonymous wrote: | | Quote: | | how much of modification is needed before you can realy say its your name of IRCd ? |
That's really a judgement call. I suppose legally, as far as the GPL is concerned, you don't have to modify it at all. However, ethically, you probably should make a significant change because you claim someone elses work as your own, and even then you should give credit to those who wrote the original. |
okay
All credits come no matter what, to make no fights at all, i have mainly only added some handy commands
ThX for the help, gonna release soon then  |
|
| Back to top |
|
|
Howard
none
Joined: 16 Nov 2003
Posts: 34
|
| Posted: Apr 08, 2004 12:25am Post subject: Re: Are you allowed to modify a modified ircd ? |
|
|
| DjMadness- wrote: | | how much of modification is needed before you can realy say its your name of IRCd ? |
In theory, as long as you've *looked* at the original work, and produce something based on it, it's still a derivative. Go back to the Award and AMI bios creations. They had to have two teams, one that looked at the published IBM bios code, and develop a set of specifications which were THEN handed to the folks who actually wrote the bios code. No one who actually wrote any of the Award/AMI bios code could look at the ibm books at all.
In practice, it depends on how much legal talent the copyright holder has on tap and at what price.
Difference between copyright and patent is that you can get around a copyright by proving an 'independent derivation' of your code. If it's patented, it doesn't matter how you come up with it, you still are at the mercy of the patent holder if you want to even *use* what you make.
As for the folks at Unreal, my hat's off to 'em, they done good; but there were a few places where I needed it done a bit differently, and I can write a bit of c when the moon's in the right phase and no one's sneezing too hard within a mile or two.
I've sold my share of code over the years - both in object and source - and put enough of it into other folks' hands gratis. It's only fair that if you pull something out of the well, it's best to put something back. And, while you got to get *some* kind of revenue stream coming in to feed yourself and those for whom you've got some responsibility, doing it by thievery will catch up to you sooner or later. |
|
| Back to top |
|
|
|
|
| |
Register
Log in
