Things to look out for when getting a dev to code a plugin?

[Troaxx]

What are some things my developer should have in agreement when I hire them to code a plugin/core for me if I want the full rights to it?

 

[Troaxx]

Make sure you mention what will happen if they don’t deliver on time or at all

Yes I'm aware of that. I'm mostly looking for what to tell the dev if I want the full rights to it bc I want it to be used exclusively for my server.

Just tell him you want the right to distribute the product, and that the product is being solely and exclusively developed for your use.

Thanks for this response!

 

[Kjell]

What are some things my developer should have in agreement when I hire them to code a plugin/core for me if I want the full rights to it?

Are you talking about a NDA?

 

[Troaxx]

Are you talking about a NDA?

I think so. What does a NDA do in this case?

 

[Troaxx]

An NDA is a non-disclosure act. Let's say I am hiring you to make a super awesome omega idea. However, I dont want ANYONE else to know this idea. I have you sign an NDA which is an agreement that you will not speak to anyone about this or use anything you make in anything else.

If I understand this, you want to be able to tell a dev that you wanna resell the plugin? That shouldn't be an issue. Just say "Hey, I want you to make this super awesome omega idea plugin and I'd like to have resell rights on it"

I see. I'd like to make the plugin for my own server, but in the case that I ever sell it, I'd want to have the green light on it. But I also want to keep the details (the code I assume?) private. So I ask for resell rights + get them to sign an NDA?

 

[Troaxx]

Yup. Though 99% of the time an NDA is unnecessary unless it a $1k+ kind of plugin

Do signing NDA's actually cost money? And without a NDA, do devs usually keep the code private from other clients?

 

[Kuchy]

So I’m not a plugin developer but as a web developer we want both want to sell our product. In my belief, any product that is being sold as fully exclusive should belong to the person buying it. Since you’re selling something fully exclusive, the rights of the product should follow with the deal. I’m not saying anyone who doesn’t do this is sketchy but simply as that’s what I practice and would look for if I were in the need of a plugin or build or whatever. Obviously, every seller has a right to have their own TOS and control their product. If I’m buying something fully exclusive, I’d want all rights to the product as well. Remember, you have a voice too. If the developer has a clause where he/she holds all rights to the product and it raises caution for you, bring up that concern with them. If they don’t want to alter the terms for your request, simply thank them for taking the time to hear about your commission and move on. A deal with concerns usually doesn’t end well (mostly by cancelling the commission).

A developer holding rights to their product isn't necessarily bad. Let's assume they are around for a long time. You have someone you know who can get the job done, should you need revisions or upgrades made to your plugin or whatever product you are purchasing. Again, you're assuming they are around for a while. The developer knows the product (hopefully, they made the product so I assume they should know what they coded) so making revisions or upgrades might not be too hard (if it's not a big change). If you take the product to a different developer, odds are they may take some time understanding the code that's written. Normally, a developer would place comments in the code to specify what does what.

Personally, I'd still want all rights to the product but I think it's only fair to provide the counter argument above (again, my opinion).

A very nice resource the staff team has provided is the Merchant Agreement. I used this wiki as a guide for my own TOS and I highly recommend looking through it to make your own. Please note that the guide is not the primary terms in a deal and the terms set between buyer and seller is what would be used in a dispute (should that occur). Obviously it’s up to you if you want to use that guide. Don't just link the Merchant Agreement as your terms. I'm not sure how well that would hold up in a dispute but from a business standpoint, you should have terms that fit your needs. Again, see it as a guide, not something that's absolute.

Hopefully this helps out. I don't want to tell you how to conduct business. You should be allowed to conduct your own business. I simply relayed what I think. It's entirely up to you if you want to heed my advice (it won't hurt my feelings if you disagree with me).

Best of luck!

 

[Troaxx]

No, but actually enforcing them does.

It depends on the dev and how cheap they are. Some devs dont resell, some do, and some vary on the price. I'd just make sure to pick a person with a good reputation (10+, no negative reviews) on this site and specifically state that you want it to be private and not resold

I see. Alright will do. Thank you!

So I’m not a plugin developer but as a web developer we want both want to sell our product. In my belief, any product that is being sold as fully exclusive should belong to the person buying it. Since you’re selling something fully exclusive, the rights of the product should follow with the deal. I’m not saying anyone who doesn’t do this is sketchy but simply as that’s what I practice and would look for if I were in the need of a plugin or build or whatever. Obviously, every seller has a right to have their own TOS and control their product. If I’m buying something fully exclusive, I’d want all rights to the product as well. Remember, you have a voice too. If the developer has a clause where he/she holds all rights to the product and it raises caution for you, bring up that concern with them. If they don’t want to alter the terms for your request, simply thank them for taking the time to hear about your commission and move on. A deal with concerns usually doesn’t end well (mostly by cancelling the commission).

A developer holding rights to their product isn't necessarily bad. Let's assume they are around for a long time. You have someone you know who can get the job done, should you need revisions or upgrades made to your plugin or whatever product you are purchasing. Again, you're assuming they are around for a while. The developer knows the product (hopefully, they made the product so I assume they should know what they coded) so making revisions or upgrades might not be too hard (if it's not a big change). If you take the product to a different developer, odds are they may take some time understanding the code that's written. Normally, a developer would place comments in the code to specify what does what.

Personally, I'd still want all rights to the product but I think it's only fair to provide the counter argument above (again, my opinion).

A very nice resource the staff team has provided is the Merchant Agreement. I used this wiki as a guide for my own TOS and I highly recommend looking through it to make your own. Please note that the guide is not the primary terms in a deal and the terms set between buyer and seller is what would be used in a dispute (should that occur). Obviously it’s up to you if you want to use that guide. Don't just link the Merchant Agreement as your terms. I'm not sure how well that would hold up in a dispute but from a business standpoint, you should have terms that fit your needs. Again, see it as a guide, not something that's absolute.

Hopefully this helps out. I don't want to tell you how to conduct business. You should be allowed to conduct your own business. I simply relayed what I think. It's entirely up to you if you want to heed my advice (it won't hurt my feelings if you disagree with me).

Best of luck!

Thanks for this response! I totally understand both sides of the developer and the client, and I will check out the link that you've stated.