| Danwe reopened this task as "Open". Danwe added a comment. |
@Lydia_Pintscher According to Thiemo, “it should definitely be fixed”. There will always be some non-critical issues for long periods of time in almost any serious software project and that's fine.
Also no reason to decline this according to the Mediawiki bug report life cycle:
A report is given the Declined status when the problem can not be reproduced, when missing information has not been provided, or when an acceptable workaround exists to achieve a similar outcome as requested. This status is also set when there's a consensus that implementing a particular bug report or feature request would be a bad idea. For example, when a report contradicts a particular project's scope or the principles of the project and fixing would be barred from approval by the project's Developers/Maintainers (or product managers, if existing). Depending on the specifics, a user preference, a global configuration variable, a re-implementation, or forking the code can be alternatives to marking a report as declined.
If that gets into the way of your team's internal planning then you could e.g. simply introduce a new tag signaling that your team has currently no intentions to fix this but leave it open for other developers and as proof that this is a valid issue.
Cc: Danwe, Wikidata-bugs, thiemowmde, Denny, adrianheine, Snaterlicious, Lydia_Pintscher, daniel, Soteriaspace, JakeTheDeveloper, QZanden, Izno, aude, TheDJ, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
