I sometimes feel hesistant to close certain feature requests, or how similar things need to be to mark things as duplicates. There haven't been any complaints so I can only assume no one minds (although bulia has corrected some of my sloppier less accurate comments but some days you are tired and __it happens).
One of the requests I closed just today was for asking for Inkscape to use the platform native file chooser. Given how the Inkscape developers have already removed this mis-feature from the codebase I'm just hoping for agreement that it is impractical to do something like that on a per application basis and any future requests should be referred to GTK?
https://sourceforge.net/tracker/index.php?func=detail&aid=1550205&gr...
The more general issue I am trying to deal with is how can I better know what bugs to close and make sure I dont go too far? It is always possible some developer somewhere will be inspired to add wacky and interesting features, but it would be helpful if there was something the developers could or say to do to cut down on the guess-work when closing request for things which are likely to be beyond the scope of Inkscape.
Does anyone have an ideas about cutting down the quantity of duplicate requests? (I've always said anonymous requests put the barrier too low, and users should at least be interested enough to provide follow up information if needed.)
Should I start to carve out some kind of Anti-Roadmap in the wiki and try to explain some of the things which fall beyond the scope of Inscape?
Thanks in advance, back to trawling through the tracker for another while
Sincerely
Alan Horkan
Inkscape http://inkscape.org Abiword http://www.abisource.com Open Clip Art http://OpenClipArt.org
Alan's Diary http://advogato.org/person/AlanHorkan/