Writing this while waiting for github for windows to install...
About organisation, i hate formal titles and all but it is true that developers will tend to fall within certain roles in this project. Multiple people may fill a single role and a single person may fill multiple roles, but this I feel is a good initial guide for work subdivision:
Project Head - Creates repos and takes basic responsibility (sublight?)
Build Manager - Primary responsibility for project and build files. Confirms mono compatibility.
UI Dev - Developer(s) of the winforms UI as well as the viewmodels to connect UI to the backend
Simulation Dev - Developer(s) of the simulation and updates, orbits, ship movement, population and resource growth
(Combat Dev) - Developer(s) of the combat system, weapons, targetting, damage and such
Generation Dev - Generation of realistic star systems (interest from myself and clement)
(Scripting System Dev) - If we are doing scripting, a developer needs to maintain the bindings
(Scripting Dev) - Maintains the script and data files
(AI Dev) - Developer(s) of the AI
Meta-Maintainer - Maintainer of ticket system, wiki and such
UI Designer - Mockups and designs for the UI. Doesn't need C# experience
Economy Designer - What planets do
Ships and Technology Designer - What you can research and what it means, how subsystems on ships interact
Artist - Not a graphics intensive app, but we still need icons and such at the LEAST
Sound - While default windows tones can be used, it is possible to do better
(Testers) - Eventually we need someone to make sure everything works the way we intend it
Those in () brackets imply only needed later in project.
This is propably horribly incomplete, but these are the 'roles' I can think of right now.
There are several tasks we need help with that does not involve programming, largely around the side of design which is an especially critical aspect right now. We are currently working off of an assumption of: 'Like Aurora unless said otherwise' I suppose though.
EDIT:
I threw together this:
http://pulsar4x.pentarch.org/wiki/index.php?title=Source_CodeI would like to get the basic solution and project structure up asap. I dunno when we'll be able to get the devs together for a chat, but I don't think too many disagree with my proposed structure here. MrBear suggested splitting the Lib project into multiple projects, but I agree with clement in that others can be extracted later. Test and installer projects are possible 3rd and 4th projects that will happen, but those won't affect the structure of the basic gameplay.
I'm considering doing a quick WPF UI as a side-project on the repo simply because I find it faster to prototype with it as output for testing mechanics. Since we want cross-platform compatibility though Winforms will remain the main supported UI.