As for a CVS repository, I reccomend Subversion since it uses WebDAV, an
internationally accepted standard in a versioning system.  WebDAV is
open-source and many clients such as Dreamweaver, MacOSX, and Windows now
are compatable with WebDAV.  CVS is a great 'ol repository system but the
newer systems out there such as subversion allow greater flexibility for
project management.  I could write a book on this subject but its worth
looking into as a versioning system.

As for the code stealing, I really can't reccomend any other action than a
legal one which will amount to nothing in the end.  If you are willing to
spend the money on taking him to court, then you will need some hard
evidence this guy actually stole code from your mod.  It truely is sad to
hear some people are willing to steal code, but I guess thats the real world
for ya.  I am always picky about whom I let into my projects now as I would
need to see a full history of their work and their capabilities to
contribute to the project.  Goodluck to you though in finding a solution,
love the Sven-Coop mod ;)

-Theiggsta
Mapcore Senior Staff

----- Original Message -----
From: "Commando" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 04, 2002 10:58 AM
Subject: RE: [hlcoders] What to do when people blatently steal your code?


> At 08:28 AM 12/4/2002 -0500, you wrote:
> >The mp3 player was completly written by me ( with advice&help from
> >another1 another ex-coder of svencoop), and its just lying that he
> >claims he wrote it.
> >
> >Anyhow, we are trying to get it sorted, but im not sure there is much we
> >can do, any thing you can think of?
>
> I think that technically all you can really do is take legal action
against
> them and I highly doubt that would be worth it for a free game.  Even
then,
> you would have to prove who actually wrote the code.  In our mod, we use
> CVS as a source code repository.  With it, you can track down and know who
> added or changed every line of code in your mod and when.
>
> We don't use it for this, but I would recommend that anyone coding any
> project use a repository for their code.  It will allow you to easily go
> back to previous versions if you make a mistake, it is a form of backup
and
> the best way I know for multiple developers to work on the same code at
the
> same time (it can merge changes from multiple developers).  Lastly, you
can
> know who is responsible for every line of code in your mod and know every
> change with dates.  Then if you run into problems like this, you at least
> have some sort of proof to the community.
>
> Hopefully it never comes to this, but it is also fun for figuring out who
> created the most recent killer bug in your mod and the resulting taunts
> between the coders :D
>
> CVS is my first recommendation for a repository.  It is mature, free,
works
> over the Internet and has a number of front ends.  It also does not
require
> that you lock code that you are working on which is good for multiple
> developers.  Subversion and BitKeeper also look good (better?) but I do
not
> have much experience with them.  My only strong dislike is of Source Safe,
> a nightmare for distributed development...
>
> Back to the original problem though.  If you have proof that you wrote the
> code, then present it to the community.  Beyond that, it is just your word
> against his.  Sux, but let it be a lesson learned :(  If your proof is in
> the form of a repository that cannot be easily shown to the community,
find
> someone in the community that is trusted, willing to help and unrelated to
> your mod, give them temporary access and have them vouch for the
> proof.  You may not be able to prevent the other mod from using your code,
> but you will at least give the community evidence of the 'crime' and
> prevent this sort of thing from happening with this person/mod again.
>
> Rob 'Commando' Prouse
> http://www.tourofdutymod.com
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>
>


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders

Reply via email to