Hi Pete,
May I suggest to make things step by step:
1. Finish the upload of all the concerned files to GIT ;
2. Update the sphere filesystem organization so the changes are easier to
implement (for the moment, each user has a specific access to the server and
specific permission on files). Once all files are on GIT, we'll have to find a
proper solution to reflect changes "down" to Sphere.
3. Once this step is done, we'll have a better view on the whole stuff, able to
delete "old" files, make things common, etc.
4. Finish "our" to-do list (mostly mass import + 3D models import): this will
save time for Martin and others - and enable him to work on other scenery
important stuff.
5. Then, go on on "big" scenery-website enhancement (such as smarty, or others)
to make things easier to maintain on the long term.
Oliver
N.B. : let's say Jon, Martin, and myself now quite have a good overview on how
this works (at least for the "real" scenery stuff). We also have our RL
timetables. With you, we would - will be 4. However, making cooperation work is
something needing steps 1 and 2 to be achieved. Will be happy to welcome you on
the 3 to 5 steps, but for the moment, we have to keep things simple - I'm sure
you'll understand once all files are "gitted".
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
