Collaborative process

[connorhsm]

Now that there's at least three of us with push access to master, it's probably necessary for there to be a solid process surrounding this.

Will add more info.

[Arcurus]

I would be happy if i can continue for now to now work / push rapidly on the server stuff.

For now I mainly work on game logic. If some one wants to work on other server stuff like being able to use 2HOL data or client stuff should be no prob. For working on AI i suggest to make a common lib and base Ai and let everyone who wants work on his own Ai version that can use common ai lib.
If one wants to change game logic or a general refactoring i would be happy if we first can correspond about it, since often there is a reason behind something (like all movement related stuff in the MovementHelper). Of course there is also tons which could need a rework now that the main functionality is in and known. Very happy for suggestions...

[PXshadow]

Hey thanks for opening, I want to specialize on working on a client in this repo to go along with the OpenLife client to have a full complete package under one mono repo.

I'm sure there is plenty of tweaks that can be shared across both the server and client, and my view is that each one of us with write access find a spot to specialize in and then communicate with others on spot not within your specialized spot.

So for example I can make rapid changes to the upcoming OpenLife client and then coordinate with Arc when I make tweaks for the shared Ai engine or the server.

My view is that stuff that is not very warm commits wise is free to be touched without communication such as build scripts README, helper classes, new pieces to the project etc.