Well we have a simular agreement, that is emailed to them when they are 'hired'. But alot of the discustion I saw said that, those agreements are void with out the acctul signature and or verifiyable digital signature of the authour. Now from what I've read both the author of the said work, and the mud owner of the work. Both have the rights to use it. The builder cause he created it and the mud owner cause the builder use his tools to express his creativity. I was just wondering if anyone out their has delt with this before, and maybe got a real conclution.
----- Original Message ----- From: "Jamie Harrell" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, November 19, 2002 4:55 PM Subject: Re: OT: Ownership for work done for a mud. Well, here's the contract we have that must be agreed to before you're allowed to do any work on our mud..... Maybe it'll be useful to you as far as where we stand, maybe it won't.... But it's how we handle those situtations. "HELP CONTRACT" ---------------------------------------------------------------------------- ------------------------------------ Below is the contract for both builders and coders for Arthanox. Please read this contract. If you do not agree to the following terms, please inform the implementers so they can give you copies of your work. 1) If you code anything for Arthanox, you grant the implementers the right to use and modify the code as they see fit. If you leave Arthanox, you will receive copies of your code, but it will not be taken out of the codebase due to your departure. The implementers also have the right to remove the code at a later date if they feel it is not needed. 2) If you build anything for Arthanox, you grant the implementers the right to use and change the area as they see fit. You will receive credit for your area in the credits section of the file (what is displayed on using the command area), but if the area undergoes massive changes, you may share the credit with the person who did the changes. You may ask for a copy of your work at any time, and will receive a copy of it if you leave. Your area(s) may or may not remain up after you leave, and requests for them to be taken down because you are gone will be ignored. 3) The head builder has the right to disallow areas. They also have the right to go through an area and balance or remove any mobs or objects they feel would upset the balance of the mud. The Head Builder will not spell or grammar check areas, but may suggest it to the builder, which they should seriously consider. Spell and grammar checking is not necessary, but is highly encouraged as it improves the quality of the areas. 4) Any coding done for the mud needs to be cleared with the head coder (or coder if there is only one), and the implementers if the coder is not of implementer level. ---------------------------------------------------------------------------- ------------------------------------ -----Original Message----- From: Dale Kingston [mailto: [EMAIL PROTECTED] Sent: 11/19/2002 at 4:23 PM To: "ROM" <[email protected]> Subject: OT: Ownership for work done for a mud. Message: >I've have kinda been having a debate with this, And I have gone around >trying to research this to see which statments are true or not. My question >is this. > >Your hired for a mud to be a builder or even a coder. You do some work, but >you and the muds admin have a conflic of interest. Weather you were rude or >you didn't like their rule. So you are force out of the mud. Can you then >demand your work be removed from the game? > >Now I've seen alot of posts on this, some say that the mud can keep the >area >but can't transfer the files in any way. Some have said that the mud and >the >builder owner the work and so they both have the rights to use it as the >wish. And then theirs the ones saying no the builder owns the express work >done, and can demand the instant removal of the area. IDK does anyone have >any insight on this type of a question. I know this is a coders fourm. But >this could also happen to a coder who was 'hired' to work on a muds source. >Any insight would be help full. > > >-- >ROM mailing list >[email protected] >http://www.rom.org/cgi-bin/mailman/listinfo/rom -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
