Thor's point here is very important. Many publishers and developers are watching Ashes' development and taking notes about the community's reception of a transparent process. When I am at GDC or DICE and other game directors and executives come to speak with me about our development, there is often a moment of hesitancy in their voices about the transparent approach. Because it is all too easy to misunderstand the process, and an inability to see the vision come together at different points in the products development. It is difficult sometimes within certain teams to achieve this even internally among developers, let alone in the eyes of the consumer. There is a real fear of community backlash in showing a feature or piece of content that may be reworked, and then get flailed for doing so...
There is an opportunity to help change that in the industry right now with many projects taking a more open approach, but it involves some investment not just on the developers end but also on the community's end as well.