Submission + - FIFNIC: An Open Source Bane
BrendaEM writes: Firstly, Thank you to all the heroic open-source coders, as well as the many people who support open-source projects by helping the masses of computer users on forums.
For the lack of a better term, the problem is: Fixed in Forum, Not In Code, a condition that exists when there is insufficient feedback to the actual coders of software--yet the problem and even the workaround may be known elsewhere on the forums. So, old bugs persist.
With an inclusive library-based tree-like structure of a large open-source project--rising to the level of a Linux distribution. It can be hard to tell at which level the problem lies. Some well-documented bugs and fixes on the forums never reach the people who write the code, so the issue does not get fixed at the source. So, then the huddled masses continue to pour into the forums and mailing lists for answers and workarounds--to issues that might have been fixed at the source. This is why a quick NOTABUG and a quickly closed thread can cause issues downstream, and why more distro-to-programer communication might help.
For the lack of a better term, the problem is: Fixed in Forum, Not In Code, a condition that exists when there is insufficient feedback to the actual coders of software--yet the problem and even the workaround may be known elsewhere on the forums. So, old bugs persist.
With an inclusive library-based tree-like structure of a large open-source project--rising to the level of a Linux distribution. It can be hard to tell at which level the problem lies. Some well-documented bugs and fixes on the forums never reach the people who write the code, so the issue does not get fixed at the source. So, then the huddled masses continue to pour into the forums and mailing lists for answers and workarounds--to issues that might have been fixed at the source. This is why a quick NOTABUG and a quickly closed thread can cause issues downstream, and why more distro-to-programer communication might help.