468,249 Members | 1,513 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,249 developers. It's quick & easy.

help: how to organize collaboration to write PHP code?

I'd like to write a web-application with other people.
It is the first time I write code together other person.
I'd like to ask you some advices:
1)have an advice?
2)wich program to use for VCS (for windows)?
3)how to organize the work?

Thank you in advance,
Andrea.

Jul 17 '05 #1
3 2118
"_andrea" <sd**@sfgsd.it> wrote in message
news:d4**********@news.flashnet.it...
I'd like to write a web-application with other people.
It is the first time I write code together other person.
I'd like to ask you some advices:
1)have an advice?
2)wich program to use for VCS (for windows)?
3)how to organize the work?


well, different people, will have different needs and solutions, here is how
I usually work. The team typically consists of:

-html designer (or two)
-few programmers
-translator (s)

first we set up cvs thaht will be accessible to all of us. Usually this
means server hosted somewhere on the internet, and we connect by ssh.On
windows machines we use TortoiseCVS for cvs related stuff.

Further for development we use TemplateTamer, in which designer gets his
directory with html files, and he is pretty much free to do whaever he wants
with them, and for most of the changes he just needs to commit his stuff
when modifed. If there are some huge structural changes, that he needs to
communicate that to the programmers so they could adopt the structure of
their code.

Programers also get their directory where php logic files are stored. Work
between programers is usually divided as follows:

- lead programer does general classes, typically page class that gets
inherited by all pages on the site. This class will have logic for basic
session management, basic outline, menues, banners, and similar stuff. On
more refined site, he will create a few of those cornerstone classes, for
instance one for the simple user pages one for the admin, and so on.

- additional programers usually get a number (of usually related) pages to
work on. They inherit general class, and add specific stuff for that page

And lastly, translators get their file with translations and they commit it
as needed.

rush
--
http://www.templatetamer.com/
http://www.folderscavenger.com/
Jul 17 '05 #2
On Windows MS Visual SourceSafe is reasonably good.

As for how to organize the project, that really depends on the people
on the team. At my workspace we have a fairly egalitarian system. Each
programmer has a part of the site that he/she is responsible for. When
something breaks, the person who wrote the code takes the blame.

Jul 17 '05 #3
JDS
On Mon, 18 Apr 2005 15:10:30 +0200, _andrea wrote:
1)have an advice?


Communication is key! *Talk* to each other! Do not work in a vacuum.

--
JDS | je*****@example.invalid
| http://www.newtnotes.com
DJMBS | http://newtnotes.com/doctor-jeff-master-brainsurgeon/

Jul 17 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by mx2k | last post: by
29 posts views Thread by Bill Marsden | last post: by
reply views Thread by SPE - Stani's Python Editor | last post: by
2 posts views Thread by key9 | last post: by
1 post views Thread by Thomas Wittek | last post: by
reply views Thread by kermitthefrogpy | last post: by
reply views Thread by zattat | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.