Gijs de Rooy wrote:
> To give one recent example that applies to most of these reasons: LOWI. It
> has an updated airport layout, custom landclassing
> and is under heavy development. The author told me that he'll put all of it
> in the database once it is finished.
Just for the record, that's one of the common, big, but most avoidable
mistakes: "Submitting when it's finished". I know, it's _really_
common, but always carries the risk of making the same mistake with
every of the included models.
Guess how many hours I spent fixing the same stupid mistake in a row of
models, mistakes which could have been avoided if people would have
sent me each of these models _early_ !? Submitting early allows for
early feedback and, as a consequence, for preventing avoidable mistakes
early in the development phase of an airfield scenario, thus
facilitating the rest of the submission process.
I didn't track the number of hours, but, believe me, it kept me busy -
and just for the stupid reason because people neither bothered reading
our "Contribute" recommendations nor considered my advice.
I know, Gijs, it's not your fault, I just hooked up because you
mentioned.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
