Rob Miller <robm@...> writes:

> we've had extensive off-line conversations and are pretty much on the
> same page about the current state of things, although i know he's very
> interested in hearing feedback from all of you about your opinions
> about where remember should go from here.

Before I start getting any feedback on specific directions, I'd like to
get a sense of the use or membrane and/or remember in the wild and the
interests of all stakeholders.  If you will, please take a few seconds
to answer as many of these questions as you care to.  Feel free to be
brief, in fact I prefer it.  :)

- How many membrane and/or remember deployments are you responsible for?



- What general direction would you like to see membrane/remember
  development take?  Select one or rank by priority:

  [ ] new features
  [ ] improve performance
  [ ] more simplicity/maintainability

- What specific direction would you like to see membrane/remember
  development take?  Select one or rank by priority:

  [ ] non-AT option
  [ ] lightweight AT profile schema
  [ ] other, please describe



- What do you use membrane/remember for?  Select all that apply:

  [ ] Archetypes Schema for members
  [ ] membership workflow
  [ ] extended member searching/cataloging
  [ ] other, please describe:



- Do you use membrane without remember?  If so please describe.



Thanks in advance for all your responses!

Ross