How can we safely employ outside help for site development?

What best practices should we follow when giving access to an outside developer to change our site design?

Is it possible to limit an outside developer's access to network member data, while letting them change site appearance and structure?


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
updated by @researchcooperative: 04/08/16 01:25:07AM

I have the same questions.

Basically a developer would need 'full' access to the Jamroom site so as to take advantage of all its features and development tools, but he he was just doing template work it might be possible for him to progress just using an FTP account access to your server.
The best option would be for you to set up a development site based/cloned on your potential live site and give him full access to that, then when complete, the newly developed skin can be copied to the live site.
Hope that helps


--
Paul Asher - JR Developer and System Import Specialist

When I do freelance work for a client, the steps I follow are:

* We agree on my work terms ( http://www.apicos.com/site/jamroom_developer.php )
* You make a small initial deposit to ensure you are able to pay when the time comes
* You give me a copy of the site. This usually means FTP access to download it so I can setup a copy on my local machine.
* I do the work up to a certain point, you agree that its finished and pay that amount.
* I upload that portion to your site.

So your always in control of the portion that you've paid for.

I think you'll find developers will prefer to do the work on their own machine because they will have more tools available to them, then once its done put it on your machine.

Things that trigger alarms for me:
#1: Please do the work on my machine and I'll pay you once its finished
#2: I want to pay a fixed amount decided upon before we start.

#1: The client can shut off access and refuse to pay, nothing I can do, I've wasted my time.
#2: Signals the client is not confident they understand the scope of what they are asking.

TIPS:
* You get what you ASK for, not what you WANT so ask for what you want.
There have been a few times when I have built what was asked for only to be told, but that's not what I wanted. If the contract is for a 'fixed amount before we start' this immediately causes a problem. If the contract is 'pay per hour' there is no problem, but the client gets a bad feeling because they've paid for something they don't want.

So outline clearly what's wanted.

* Hire the right person for the job. If you want modules, you want a 'programmer', if you want implementation of a design to HTML you want a 'web developer' sometimes call themselves 'coder'. If you want the layout picked and designs done, but not necessarily the code written, you want a 'designer'. Its very rare to find one person who is all of these, and if they are, they will be expensive.

I'm not a designer, but I can take a design and turn it into a skin if the design is provided.

After that, its just finding someone who seams capable and building a relationship with them.

Wow, great advice to go by!


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015

If you hire a developer who is not familiar with Jamroom, this doc is for them:

Docs: "( for Freelancers) README"
https://www.jamroom.net/the-jamroom-network/documentation/development/3513/for-freelancers-readme

Thanks for all of the above.

How can we give (S)FTP access for someone else to download the site?

I found the procedure below. Should I follow this procedure, get a username and password, and send that to the person I employ?

Best regards, Peter

*** from JR ***

Accessing the SFTP Username and Password

The Username and Password that you will use to connect to your server are found in the Server Settings section:

- When viewing your Profile click on "Hosting"

- Click on the "My Jamroom Servers" tab

- Select "Server Dashboard" for the server you want to connect to

- Click on the "Server Settings" button in the server header.

The Username and Password will be found to the right of the "SFTP Login" area.


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
updated by @researchcooperative: 01/06/16 04:44:33AM

Just like a plumber when you have water trouble needs to be able to get inside the house, so too does a developer need to be able to access the server.

However if its a new plumber you're not likely to say "here's the keys, go in whenever you like".

Same with a server.

If you're particularly nervous about them, you download what they need and zip it up and send it to them. Then get the results, and you upload it.

Slightly less nervous, let them have access, then change the password once they have what they need.

Fairly confident: let them have access for the duration of the project.

Once the project is done, change the password. This is for both you and them. If something goes wrong after the project has finished and you HAVE changed the password, the developer is free from blame and you wont suspect them of having 'done something'.

Peace of mind for each.

That's a nice analogy and great advice. Thanks very much.

My next task is to experiment with the download process to see if it is technically feasible on my computer. I have no idea what the software and hardware requirements might be.


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)