Melchior, there have been very, very few cases where I applied bug fixes to an aircraft directly, when I thought the fix was absolutely trivial - and was absolutely sure, that the author could impossibly disapprove the fix in general, neither disapprove the particular way of fixing the issue. Like this example:
http://www.gitorious.org/fg/fgdata/commit/20f4ea93e9bcb2a2d10cec47165541f378cab118 In this case, the author didn't feel disrespected, welcomed the trivial change (as can be seen from the gitorious reply). Few days later, same aircraft/author, I noticed another, almost equally simple issue - but since it wasn't clear whether a single XML line was to be commented out, or a file (known to originate from another a/c) was forgotten to be copied, I even created a bug report: http://code.google.com/p/flightgear-bugs/issues/detail?id=363 So, I don't think I'm "messing" with other people's aircraft. Neither do I place "trojans" or the like. I have always contacted aircraft authors before any substantial change. Also, I generally document commits well - making it easy to track, knowing that particular authors/developers monitor change logs closely. This was another reason why I hadn't sent Gijs an email for the first issue, since I knew he'd see the commit anyway - so I spared extra mail for an incredibly simple change. Events and similar circumstances like the above may have caused me to believe, that the commit in question, which I thought to be almost equally trivial, making the bo105 usable after a sim reset, would be highly appreciated as a constructive contribution by the author - especially being close to the release. I had not thought it possible, that this could lead anyone to feel disrespected. I was all wrong here. Melchior, I apologize for touching your aircraft. I had not intended to question your author-/ownership over the helicopter. Of course, you're welcome to revert the patch, especially if you think this is in any way contradicting your original intentions or schedule. With that, and a link to the actual commit that caused the outrage, I'd like to conclude this topic from my part. http://www.gitorious.org/fg/fgdata/commit/0b8dee0f4611f0e90478f48d58951995fbe87069 cheers, Thorsten ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
