Hi Chris and Markus, Thanks for your suggestions!
Chris said: > 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. For the user invented feature requests, it is mostly clear: The more voices, the higher is the possibility to get it implemented. The status of code improvements could be sorted out already over the mailing list. E.g. if something is simply not doable - we could say it already here. A good idea that sounds practical, shall go to uservoice. Also, we could agree about something like a prefix, let's say "code improvement: ". With this string, it should easily be possible to find these items again. I think it makes sense to getting things done blockwise, for example all features requested for "vouchers" or all "code improvements:" so we can easily find the recorded entries. > 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 ? Even if something isn't touched for a long time it doesn't mean it will not be done at all :-) As I mentioned, there are a lot of requests (not only from the existing community) a Product Manager has to consider. The first step is about _recording_ the ideas so they will not be forgotten > 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. B2B (catalog without tax) is essential, especially for internationalization, and will be done at all hazards. But the task is tricky: We probably have to change the calculation basis which is a really huge task. It is still in conception on Ralf's desk. > My suggestion would be for OXID to add a note to all oxid.uservoice.com items that say something like: That's actually what we do but not for all items. Some items need some time to "develop" in a manner of getting a buzz and being emphasised by the voices. Remember the image upload thing: I personally never never ever expected this feature request to get such a big huge support. Markus said: > I prefere the bugtracker. Just make a new category(s) for these things. Yes, actually me personally either, especially from handling etc. But as I mentioned, there are some certain reasons against it :-( > The feature-request tool is for me more for users, not developers. Right. Let's just make the best out of it ;) I really don't like the idea of having yet another tool... > Anyway, a good idea and for me its not so importend, what interface I use. The only, what I wanna is a nice view for code examples. Good point! How about (mis-)using the wiki for code examples? It is big enough, supports code highlighting, we could define a special area or category for it and we could link from the certain uservoice entry to the code in the wiki. Regards Marco _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
