> Hello, > > since kiozen asked me not to "produce too much noise" in the QMapShack > issue list, I dare to continue discussion on this list. Is this OK? > >
This is not just for Wolfgang but for many others, too. No personal offense intended. In general it's a good practice to discuss things on the mailing list or IRC first. The issue tracker is to keep track of real bugs (concerning the source code of QMapShack!) and feature requests that have kind of a chance to be implemented. Managing issues consumes time. More time than a short answer on IRC or the mailing list. For every issue I have to consider to close/reject/resolve/whatever it. And I have to do it on a cyclic base long after the user filing the issue lost interest. For you it's 5 minutes to file your crazy idea. It's probably more than factor 10 of the time for me until it's closed. Therefore try to discuss it prior to filing it. And if you file an issue try to find a good compromise between writing too much and too less. It's no fun to extract every single bit of information by asking a user multiple times. But it's no fun either to read thru someones thinking aloud resulting in multiple paragraphs with important and unimportant information and a couple of other ideas. Phewwww. Try to focus on one topic in one issue. Supply all details necessary but do not start to brag about whatever moves you. And as the Wiki tells you: Always keep in mind that filing an issue is to ask someone to work for you. If you have nothing in your hands for exchange make it as pleasant as possible at least. Another topic that's often misunderstood leading to a somewhat grumpy developers is the pure ignorance of what Open Source is about. It's not asking for features, help and assistance for free and calling it "contributing to the project". This is "generating work for the project". Contributing is "taking away the work". It's not the developer publishing the source code that has a dept with the users. It's the users enjoying the software for free (beer and speech). The idea is to return the favor by enhancing the code, fixing bugs, enhancing the GUI, the artwork, the documentation. And if you do - finish the job. No one wants to clean up behind you. I do understand that not everyone is able to code, to write documentation, etc. I do understand that often you just want to use software without thinking about how to contribute. That is completely fine with me. But I get instantly pissed by the sentence "By using the software and reporting bugs and feature requests I contribute to the project". No, you don't. Sending a patch is contributing. Asking for one is not. If you do it, simply do it. But please spare me the bullshit talk about contributing. Hope that clarifies when to open an issue, what to write and what is to be avoided. Oliver ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
