Hey, If you are being paid to make a website and the client wants something added but you cannot code it yourself, however, you can get whatever it is on a website, is that ok to do or would you be expected to code everything yourself? I am asking because a client wants some JavaScript added and it would be far easier to get the script online but is that kinda frowned upon or is it completely fine? The way I assume things are is that the client pays you and it is just your job to put it all together, however you do it is not important but I can't help but feel guilty if I use premade scripts unless it is something like a forum.
well i guess it all boils down to a few things. Did you get the script legally, purchased, gpl etc. Is you client aware of this, if not i would tell them, try to be honest, i know i wouldn't hold it against you, though some might.
As a client, I normally care about the results that are delivered -- not how they were achieved. As long as it's all done legally and none of the licenses involved limit what I need to do, I don't care how a subcontractor creates the deliverables.
Exactly. I agree. Clients expect results, and that's what they're paying for. If you can deliver them in an ethical manner, you're good to go.
Personally I don't think they will mind as long as it is all legal and above board. But might be a good idea to tell them so at least they know.
Well that is the way I look at it, they just need a website. I would tell the clients but as most people I have worked for are not always that tech headed I think even trying to explain it to them would either not mean much or they would think that I have ripped them off or something so am not too sure about telling them unless they have some kind of understanding of web design. Would you agree with this?
So what you do is, (assuming you buy it or it's already free or whatever) you sit commented out in the HTML <!--JS courtsey So-And-So at www.soandso.com --> I've seen it in code many times. This is great also because if you use it and later the client finds a bug, you know (or their own geek knows) where to go to check the original code (and to see if the original writer has improved it or something). You don't have to tell the client if you think they don't care either way, but the information is there if someone needs it. Perfect.
if the script is free to use then theres no problem. If it's not then you may need to pay to use it, or just have a link back to where it was you got it.
If the script is open source, just add it. Unless the client specifically wants it hand coded and wants the rights then there is no need to reinvent the light bulb
You also need to look at what you pitched at - if there was a "no outsourcing" or "ownership of all code must transfer" type elements to the agreement then you would have issues. Reality is that it is unlikely that the client would ever know and there is the old addage of "what you dont know cant hurt you" but then again if they do find out there is a risk of them pursuing you for breach of contract or indemnifying them should, for example, you use code that isnt open source/ GPL etc and the owners of the script find out.
So long as the code you are using is open source then there is no need to be concerned. As for telling the client - I wouldn't dream of it. Most clients are unaware of the processes, and quite often get confused over the smallest details. Rule of thumb is only tell the client about any techincal aspect of how a site is put together if they ask, and you are confident they will have some hope of understanding. Most clients want the site up and running, and they don;t care how its done.