Page 1 of 2

Why open source can be bad

Posted: Tue Mar 10, 2009 3:35 pm
by Dex
Here is a good reason, why alot of coders stay away from giving there source code away :x
See here: http://woergi.is-a-geek.org/src/asm/os/lukeos/
it a compleat rip off of my OS, the only thing they changed was who coded it and the name of the OS.

They are also so stupid, they left in words like "Function17 dd SetDex4uFonts ; Goes to realmode and back sets 50x80 mode/fonts"
See Function.inc
or 386.inc
What do these people get out of doing this ?

Re: Why open source can be bad

Posted: Tue Mar 10, 2009 4:25 pm
by kmtdk
welll
my sugestion
is
make "water" marks
like code prints ( no string)
and name it some magical, so people dont understand it..

or in the files, make some strings after it has ended ( so the text editor wont see it, but you always can claim "yours")

and some magical things, thouse people leave, becuase it is too compicatet


KMT dk

Re: Why open source can be bad

Posted: Tue Mar 10, 2009 4:34 pm
by skwee
Well I partly agree with you, I mean do they feel good that they use code they probably don't understand, I feel bad when I copy code from tutorial that I don't 100% understand. Anyway:
DexOS version 0.03

Copyright (c) 2002-2008, Craig Bamford.

All rights reserved.



This program is free for commercial and non-commercial use as long as
the following conditions are adhered to.



Copyright remains Craig Bamford, and as such any Copyright notices
in the code are not to be removed.



Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:



1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
Isn't this familiar to you?
I'm not a lawyer but I'm pretty sure they don't have the right to do what they did. IMHO just tell them that they used a copyrighted software and broke the License and can be punished for this (and don't tell its sound lame or etc, its pretty correct IMHO, you didn't put the License just to be, License comes to show what exactly other can and can not do with your soft).

Re: Why open source can be bad

Posted: Tue Mar 10, 2009 4:54 pm
by Alboin
Your problem has not to do with open source, but with a certain individual who doesn't have the decency to follow licenses.

Re: Why open source can be bad

Posted: Tue Mar 10, 2009 4:59 pm
by stephenj
Well, they've violated the terms of your license... To get back into compliance, they need to include the license text file. Email the person, and politely inform them of this... If they don't comply, then you may want to look into taking legal action.

For starters, is-a-geek.org has a lovely page:
If you wish to report a violation of our Acceptable Use Policy at a subdomain of is-a-geek.org, please contact our abuse department at [email protected]. Please be certain to include the full URL of the suspected violation and a brief description, and we will respond to the issue as soon as possible.
Just to note, changing the name of the OS is something you probably want them to do if they modify the source code. You probably wouldn't want your project's name on a shitty version (This is why trademarks are a good thing, I hope you have trademarks on DexOS by now).

Not acknowledging another programmer's contribution to a code base is one of the worst sins a programmer can commit. Give him Hell for it.

I'm curious, how'd you find out about this in the first place? Furthermore, why did a guy named Christoph rename the project lukeos?

Re: Why open source can be bad

Posted: Tue Mar 10, 2009 7:20 pm
by Dex
@stephenj , Thank's, i did not notice that email link.
@all, I for one have no problem with coders using any part of my code, but to just replace your name as coder with theres, is taking it too far.
I will report the case to that email and see what happens.

As to how i found it, i was going to answer another ?, on this forum, i have code in my OS that you call bios to see if you booted using emulation.
I put the function number in google to see if i could get brown's info on the int and what came up was
http://www.google.co.uk/search?hl=en&q= ... arch&meta=
In that link is that site.

Re: Why open source can be bad

Posted: Tue Mar 10, 2009 8:30 pm
by Troy Martin
Another example of blatantly obvious copying: http://woergi.is-a-geek.org/src/asm/os/ ... xFonts.inc

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 1:05 am
by Steve the Pirate
Dex wrote:What do these people get out of doing this ?
I wouldn't worry about it - at most they're probably just going to be able to make a couple of their friends think they're good programmers...

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 1:16 am
by steveklabnik
Steve the Pirate wrote:
Dex wrote:What do these people get out of doing this ?
I wouldn't worry about it - at most they're probably just going to be able to make a couple of their friends think they're good programmers...
This is what it really comes down to. You should be flattered.

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 2:48 am
by AJ
Hi Dex,

If you're concerned about this and they don't respond to your e-mail, I'd whois and then e-mail their domain host. Because a host often doesn't want to be caught with illegally copied software, they will often pull the content without you having to go as far as getting legal advice.

Cheers,
Adam

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 3:06 am
by Solar
...which will get different as soon as they are in a different country. I agree, going through the hoster is probably your best bet.

But first write them an e-mail. Some dudes simply don't understand that "Open Source" doesn't mean "free for all". (Except for PD, of course. ;-) )

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 7:00 am
by JamesM
is-a-geek.org is one of the domain names of dyndns.org - for those that don't know, this is a tool which allows you to have a DNS name for a dynamic IP'd server - the router on the server's end informs dyndns of any IP changes.

This is usually used to set up servers on a standard ADSL connection - i.e. dyndns doesn't host the data, so it is in no way responsible and in fact, can do almost nothing.

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 7:05 am
by Steve the Pirate
JamesM wrote:is-a-geek.org is one of the domain names of dyndns.org - for those that don't know, this is a tool which allows you to have a DNS name for a dynamic IP'd server - the router on the server's end informs dyndns of any IP changes.

This is usually used to set up servers on a standard ADSL connection - i.e. dyndns doesn't host the data, so it is in no way responsible and in fact, can do almost nothing.
Their ISP may be able to do something about it - if they're in the US then you can just send a DMCA takedown notice or something, can't you?

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 8:34 am
by Troy Martin
Steve the Pirate wrote:
JamesM wrote:is-a-geek.org is one of the domain names of dyndns.org - for those that don't know, this is a tool which allows you to have a DNS name for a dynamic IP'd server - the router on the server's end informs dyndns of any IP changes.

This is usually used to set up servers on a standard ADSL connection - i.e. dyndns doesn't host the data, so it is in no way responsible and in fact, can do almost nothing.
Their ISP may be able to do something about it - if they're in the US then you can just send a DMCA takedown notice or something, can't you?
Sure, that's in the States. But stuff like this isn't enforced too much in countries where some licenses do not take affect (non-standard OSS licenses may be justified as being PD.)

Re: Why open source can be bad

Posted: Wed Mar 11, 2009 8:40 am
by yemista
Unless you are selling your program, I dont think you should be too worried about it. People who steal your code most likely will not get very far and probably wont learn anything in the process. Its understandable if it bothers you on a personal level that they are taking credit for your work, but its best to spend your time and energy on something constructive than pursuing these people.