Hi Damien,

Cant' say I blame you in the least. The only way you can pull off any
kind of project like that is first to setup a repository such as
subversion where the developers can check in and out various
revisions, and there is clear communication between all parties of who
is doing what to the project and when. Then, you might want bug
tracking software like bug buddy so bug reports can be filed somewhere
where everyone will be notified at once. Running a development team
and studio takes extremely good manigement skills and the right
software. Obviously, I was trained to use Linux based based solutions
so I have a dedicated Linux machine with subversion and various other
source management tools installed to keep track of what is happening
with MOTA, STFC, Raceway, etc.

As far as deciding who can contribute code the open source community
have a pretty good method for figuring out who has access rights or
not. For one thing if they check the source code out, produce a decent
patch, upgrade, etc and prove themselves to be a competent developer
they can apply to the source maintainers for membership. Since you
might be thinking more comercial you'd have to base membership on
someones past contributions, game projects, and his/her
trustworthiness. If they can't produce any examples of their coding
skill then chances are they might only hinder your attempts to produce
anything. If you don't think they are trustworthy don't add them to
your team. Above all if you do form a team let all members know right
off what the standards are, and that all coding standards, formatting,
etc are to be followed as set forth in your company polacies.


On 3/29/11, Damien Pendleton <dam...@x-sight-interactive.net> wrote:
> Hi Shaun,
> The idea of being a team within X-Sight basically fizzled out. Those
> application forms and policy documents were obviously just a feeble attempt
> on my part to bring some form of order into the world of a rather
> uncontrollable environment. It was generally hard to pass content around,
> especially source code revisions, and since the host moves and college days
> I just haven't had time to set up private mailing lists and monitor the
> progress of things. However, as it was nobody was active on the team back in
> the day anyway.
> As is, I have much more free time now, and with the recent introduction of
> Dropbox things have gotten slightly easier. However there is only really you
> who have expressed an interest to continue, and from what I can remember you
> were not really familiar with my programming.
> I'll have to consider for some time as to whether I will restart with a team
> environment, since it isn't easy to determine who is going to do what and
> when, or even if, they will have the work done. As you know most of the
> people in the team were not producing anything and therefore what was the
> point in being there, just to say they are in a software development team?
> I will also have to think about the privacy and security of my products,
> since I don't want a repeat performance where privileged material is being
> leaked out on the internet. If I am going to start having multiple people
> involved with the development and testing of my products, it will be a
> select few who have helped and supported me over the years to get to where I
> am now or who I know I can trust.
> I'm not sure who leaked my betas out and I couldn't really do anything much
> if I did, and it's twice that it has happened and therefore I hope you'll
> understand why I am put off and am now putting up my guard, as it were.
> Regards,
> Damien.

Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.

Reply via email to