On Tue, Feb 9, 2010 at 9:32 AM, Martin Spott <martin.sp...@mgras.net> wrote:
> Hi Heiko,
>
> Heiko Schulz wrote:
>
> > So we maybe needs a list of rules what we can do, waht we shall not to do
> etc...
>
> If someone starts a wiki page, or directs me to an existing one, I'll write
down my thoughts.
> The question is wether contributors are inclined to follow these
> guidelines. Basically this is most likely to end up in the maintainers
> being the target of nasty accusations - like the one on this very list:
>
> "My [...] scenery is downloadable but not included into Jon
> Stockill's database as it has been offered but *rejected* by one of the
> maintainers of this database due to the technics I am using to create
> it. So this scenery and the [...] and the new
> coming [...] scenery are only available from my homepage due to this
> rejection which is not my fault (except that I have special technics to
> create them)."
>
>
> This is one of the moderate ones, on the web forum the same author had
> been blaming us for playing "Police" due to the same causa and
> privately I've recieved EMails containing wordings I'd rather not post
> publicly ....
>
> That's unfortunate. Perhaps if we can point to a page of official
guidelines, that will mute some of these reactions? Or perhaps you already
have such a page :) Also, as I've mentioned before, I want to be sensitive
to the modeling workflow and what's possible with the popular tools. If we
need to work on post-processing and optimization at load time, then so be
it.
> In fact this is a rather delicate issue since quite a few modellers
> have rather little understanding beyond the "works for me"-point. The
> current, rather moderate list of guidelines is subject to frequent
> ignorance. On the other hand I'm happy to report that the topic has
> quite a few sunny sides as well since some of 'our' contributors are
> _really_ careful about doing things right and are submitting
> _excellent_ work !
>
This is a difficult problem for the programmers too: people run Flightgear
on machines with a range of performance of several orders of magnitude.
Also, the "works for me" phenomenon is very tricky to deal with graphics
programming: If someone is getting 20fps they are happy to still get that
with their snazzy new model, whereas the user who is getting 60fps will be
pissed when that model causes his frame rate to drop to 30fps. And that
situation is possible even if the modeler follows all the rules.
> Another delicate point is the fact that the understanding of
> "collaborating as a community" among model contributors covers, to put
> it mildly, a wide range of ideas. To be a bit more precise, the "Not
> Invented Here"-attitude is pretty much wide spread and some of the
> involved people behave as if the primary target of their involvement is
> to alienate contributors over to their very own private collection of
> models (there's more than just one single prominent case for such
> effort).
>
> You, see, the topic is not _that_ easy to deal with, especially
> because a) some of the contributors are excellent modellers but not
> highly technical people and b) parts of this rather small side-project
> resemble a wide political mine field.
>
> The fun never stops...
Tim
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
