Spaces should not depend on features

I think this is one facet of an underlying circular dependency issue with Context, Features, and Spaces. Contexts are included in Features, and Features are enabled by Spaces, and Spaces activate Contexts. Feels kinda like an incestuous relationship.

Anyway, it seems like the role of Spaces needs to be clarified. Either it is just primarily a tool for activating Features, in which case it shouldn't be used for as many other random things. Or else it is a multi-purpose tool, in which case the explicit dependency on Features should probably be removed.

Removing "critical" since worse comes to worse, you can just enable the Features module for the time being even if you aren't using that functionality.

The Features project's self-stated goal is to capture configuration components that, taken together, satisfy a certain use case. From a pragmatic perspective, this is exactly what you want to be able to enable/disable per space. I hear what you're saying that it would be nice to define a "space feature" else where, but how different would that be from doing so in a feature module? What would adding a new class of entity get us?

I think Damien's "space features" was bad wording.

A better example would be if you wanted to use spaces to turn on a context that would make changes to the template or such. No need for Features in that case.