* John Denker -- Sunday 28 January 2007: [DME] > I hereby offer to write the code to fix this ... but only > if somebody asks me to.
What I know about VOR and DME I learned from fgfs. So I can't say if there's something wrong, as long as there aren't blatant coding errors. But when Torsten agrees that there's a bug, then a patch would sure be a good idea. > On several occasions in the past I have sent in patches > to solve specific problems, but in all cases such contributions > have been ignored. Same happened to me when I submitted my first patches. I think that's normal. (And yes, I was pissed, too! :-) BTW: on IRC you can often get instant feedback. > Consider for example my patch to hsi.xml. > Nobody said "good patch, let's commit" or "bad patch, try again" > or even responded to my HSI bug report in any way. Not everbody with commit permissions knows all parts of fgfs equally well, or is an expert in aviation or all parts of it. In case of doubt, developers rather wait for someone else to comment/commit. And then a patch is easily lost, of course. Every developer has his areas for which he feels responsible, and for which the other developers deem him responsible. I would, for example, have felt responsible for your location-in-air dialog, as I had worked a lot on GUI matters. There were reasons why I didn't pick it up: (1) I wasn't at my computer at that time. (2) it wasn't submitted as a diff, so I couldn't see what it actually changed. (3) it was utterly overcommented. fgfs isn't a "Literate Programming" project. Place for literature is in the cvs logs, not the code. :-} > -- What are people supposed to do when they find a bug? Report it, and if possible submit a fix in form of a unified diff. Only comment what the code self doesn't tell. Don't write *what* the code does, but why it does it, and only if it's not obvious anyway. If one patch has been ignored for longer, point to it again. > -- Is there a bug tracker somewhere? I wasn't able to find one. Yes, but no developer looks into it. It's only there because every sf.net project has one. Don't use it. But for sake of completeness, here's a two links: fg: http://sourceforge.net/tracker/?group_id=583&atid=100583 sg: http://sourceforge.net/tracker/?group_id=26352&atid=387123 > -- Are we supposed to take seriously the list on the wiki site? IMHO, no. While the wiki is official, and developers occasionally look into it, many TODO/bugs lists there seem to be mere user phantasies and aren't acknowledged by any developer. But I haven't read it for a while. m. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
