Hi Marco, I think this is a good idea but if you want to use oxid.uservoice.com feature request list, you need to make the status of items on this list clear.
As you suggest, dev-general is a good way to check if an item makes sense to the internal and external development community, but what should happen after that, when items are added to oxid.uservoice.com ? For example, it seems like the most popular item (B2B) has been there for a long time without really moving forward. I can fully understand that items like this are not easy or maybe even possible for OXID to implement, but items need either to move forward or should be killed. My suggestion would be for OXID to add a note to all oxid.uservoice.com items that say something like: "good idea - will be implemented soon" (or will be implemented by xxx) "good idea, but difficult - will be implemented some time" (or will be implemented in release xxx) "good idea, but not feasible - sorry, will not be implemented at the moment" Hopefully, if items have already been through a dev-general discussion, there should be no need for a "bad idea" status... Chris ________________________________ From: Marco Steinhaeuser <[email protected]> To: [email protected] Sent: Wed, October 20, 2010 2:55:24 PM Subject: [oxid-dev-general] Where to store your good suggestions? Hi everybody, on this list, during the last few weeks and months there were discussed and just suggested a couple of very good ideas concerning the improvement of the code. Now, we have got an organizational flaw and I wanted to request your ideas about it: As you know, there is a bugtracker that contains clear bugs and a feature request list where we tell people to store features. But between bugs and features there is a wide gray area of "(code) improvements", "maintenance", and however you would call it. Where especially to store the code improvements? - As the bugtracker shall be reserved for bugs only, we unlikely want to use it for such ideas: It could easily happen that the bugtracker will be flooded and will become confusing. Also, we cannot get out real metrics for our QA. - We dont want to introduce a third tool besides bugtracker and feature request list for it to keep the structures clear. Would you have any objections if we would store such things including maybe code examples in the feature request list - after we discussed it on dev-general? http://oxid.uservoice.com/ Thanks and regards Marco _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
