Best organisation for a team application [closed]

Question

I'm developing an application based on this structure :

/Root
/--- Index.php
/--- /includes/
/--- /modules/
/-------- /Mod1/
/-------- /Mod2/
/-------- /ModN/

In the future, 2 developers will participate in the project.

I have to restrict the access for the developers. They shouldn't get access for the "/includes/" folder. It contains the system's Core. They just will have to code modules.
I Will use Mercurial. What is the best "organisation" (repository, lock, permissions...) for this kind of project.

A need advices. Thank you :)

paul · Accepted Answer · 2013-01-17 21:05:12Z

up vote 1 down vote accepted

Perhaps you could create two repositories:

then pull a local copy of the modules repository into /modules?

answered Jan 17 at 21:05

paul
66818

	Thanks for your answer. If I do that, how can the other developer "test" their modules as it needs the system's Core ? give them a restricted access to a subfolder ? Is there a solution de deploy directly to FTP ? (I use Bitbucket) – Cartha Jan 17 at 21:47
	@Cartha I'm guessing you'll have a server set up to do testing on, so if you give them access to the /modules directory there and let them update the repo (or have some sort of automated testing framework that could update it) then they could test it there. – paul Jan 17 at 21:57

closed as not constructive by Walter, Martijn Pieters, Robert Harvey, Glenn Nelson, Jim G. Jan 17 at 23:14