For example, we can have properties with types: 'string', 'integer', 'boolean', 'enum'.
Depending on the type of properties in the admin panel will display the corresponding controls: input[type=text], input[type=checkbox], select with opportunity add new option value.

It should be possible to choose an image representing product from the list of all product images (variants + master)

Product prototype is a really great time saver.
What would be also helpful is an ability to assign default taxon(s) to the prototype.

Automatic, configurable routing of order to Payment gateway routing via currency or payment instrument

It would be cool if extensions could take care of registering observers. This way you could have an extension that observes the order state and does whatever custom logic it needs to when order is canceled, etc.

Changing the locale of the site thru the url like

/en/products or /fr/products for french or english

It would be nice to have an additional Sale Price field for the products. This feature would enable you to put an item on sale and also select a time frame of when to put the item on sale and when to take it off sale.

Also it would be nice to keep a history of this to be able to run reports of sale prices vs # items sold in the reports section. That way you can see if your sale prices are affective or not.

instead :cache option of javascript_include_tag

When going to /admin/product/id/taxon page I should type in name of the taxon to start filtering.
This is probably convenient if the number of taxons is big. But for moderate number (~30 in our case) it is more convenient to select from the list of all available taxons.
So, I propose when landing on the taxon page, we get the list of all taxons. And if we want to filter, then we start type name of the taxon, as it is now.

Then product have many properties, there is a need to display them by groups, rather than one list.
This may be such groups as the "specifications", "work mode", "additional info", etc.
See for example http://www.technopark.ru/product/1/9572/89/x/0.html

Remove redundant spaces not only from JS & CSS with the help of bundle_fu but also postproces HTML.

Take a look at the google.com's html source and you'll get what I'm talking about.

We have found very useful to have a log of specific events to analyze the users behaviour. For example entering in cart, payment, viewing product, home page, landing page, etc...

It only necesary to log user/visitor, ip, browser_string, event, detail, time

It's a complimentary log from the information that google analytics can give you. The advantages:
1) Real time
2) Its based on events, no page views. This lets y ou analyze better the user behaviour.

Hope this likes and will be a good feature to have in standard

In admin panel add some tab in that admin can run check. Or run it automatically when admin logged in and notify about missing settings (such shipping method, zones, taxes, etc).

We have reordering on product variants and options but properties lacks this great feature. Can't understand how to work with catalog products without it!

Standard mechanism to support for recurring credit card payments. If we included this in the new Gateway model, Spree could make use of this as a standard mechansim for storing payment profiles, recording new payments using these profiles, etc.

http://www.openwebanalytics.com/

OWA is licensed under GPL v2.0 http://www.gnu.org/copyleft/gpl.html

http://demo.openwebanalytics.com/ecommerce.php

Motivation: you are integrating Spree into an existing site. It already has a User model and table with data that you want to continue using.

Suggestion: Refactor the User class in Spree to move fields not related to authentication/authorization to another class - for example UserProfile. Right now (v0.9.x) billing_address and shipping_address are candidates.

Doing this, while not providing a replacable User mode would allow someone already using Authlogic or a simlar User table scheme to integrate via an extension - without having to motify their table to add fields.

Create a low traffic, security announcement mailing list, similar to Ruby on Rails: Security (http://groups.google.com/group/rubyonrails-security/about)