Re: [Koha-devel] [Koha] Problem with BarcodeFallbackSearch
At 10:36 PM 12/9/2015 +0100, someone wrote:
El 09/12/15 a las 22:13, someone else escribió:
If this is a desirable feature, a good place to start would be to file a bug at http://bugs.koha-community.org. :)
That's from the "user" list, and while some of you consider me $whatever, I have concerns regarding the use of the term "bug" that I genuinely believe to be in the best interest of koha-community. "A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways." (Wikipedia) 'bugs' -- quantifiable shortcomings in software 'issues' -- potential problems that aren't directly to related code e.g.design decisions 'enhancements' -- ideas that haven't been implemented yet. 'security' -- must be considered separately; breaches are fundamental, not bugs. If backwards correction is not possible, this must be announced. "Security by obscurity" is a fallacy. Suggest[1]: If you are: a) Requesting a new feature (enhancement), or b) Having build problems, or c) Not sure what the behavior should be, or d) Disagreeing with current intended behavior, or e) Not TOTALLY sure that others would agree this is a bug, or f) For any reason at all not sure this should be filed, ...then please post to the dev list first. You'll get a faster response, and others won't be forced to use the bugs.koha database to have the initial real-time conversations. Nothing is lost this way. If it is eventually concluded that it is a bug, then we can still file it later, after the description and reproduction recipe have been honed. Enhancements, improvements and new features: a good starting point is the user list, (IRC?) and possibly the dev list. If there is consensus, this should be filed at ??? <enhancements.koha-community.org> (similar to bugzilla) Best -- Paul [1] loosely based on Apache 2002.
Hi, On Wed, Dec 9, 2015 at 6:46 PM, Paul A <paul.a@navalmarinearchive.com> wrote:
Enhancements, improvements and new features: a good starting point is the user list, (IRC?) and possibly the dev list. If there is consensus, this should be filed at ??? <enhancements.koha-community.org> (similar to bugzilla)
It is hardly unusual for a "bugs" database to be used to record both reports of defects with the software and requests for enhancements. The Koha project has done so for years; procedures for doing are documented in the project bug reporting guidelines [1]. Using Bugzilla for both bugs and enhancements serves the Koha community by providing a single place where all requests for changes to the software can be found -- and to consolidate multiple requests for the same change. It also gives us a way to readily reclassify change requests; there are and will be plenty of grey areas where a given request could reasonably considered either a bug or an enhancement. Creating a separate database for enhancements, as you appear to be suggesting, would make such reclassification more difficult. The existence of bugs.koha-community.org does not, of course, preclude somebody from discussing a potential enhancement on the mailing list, and doing so can be a useful way to gauge interest or find folks interesting in collaborating in making an enhancement happen. However, discouraging folks from using the bugs database would be a disservice to the Koha community; given the number of users who are interested in changes to Koha, *some* system for organizing requests is needed. Bugzilla is not perfect, but it is what we have. [1] http://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
participants (2)
-
Galen Charlton -
Paul A