As I look through these tickets, I see another question about community/team process that I want to raise: How to integrate design reviews.
I mention this because there are many tickets that I'm made in response to the most recent round of design review. I made them without community consultation because, internally within OpenGeo, the relationship between the design review and feature specification is clear to me, even though these requirements don't come directly from the client (rather, OpenGeo's autonomous use of our design resources came with client and management mandate). What would be a good community process for accepting these changes in the future? These are my concerns: * I think design by committee is a very bad idea. I like that we get a fairly unified design perspective. * We do *need* to take the web application user interface into consideration, since smooth user interface is one of GeoNode's main advantages. -- Sebastian Benthall OpenGeo - http://opengeo.org
