On 2 Dec 2008, at 7:19 PM, Ross Patterson wrote:

Rob Miller <[EMAIL PROTECTED]> 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?


a few, but none are actively user-based sites.
At least one or two have end-user content ownership on the roadmap


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

 [3] new features
 [2] improve performance
 [1] more simplicity/maintainability

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

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

I know there's been talk about AT morphing into something else in the future, so clearly, one would hope that remembrane would track future compatibility.


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

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



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

Nope

Thanks in advance for all your responses!

----

Thanks Rob! Hope to run into you again down the road!

Thanks Ross!


Peter Fraterdeus
Exquisite Letterpress
http://slowprint.com

New! SlowPrint Newsletter!
Signup: http://tinyurl.com/slowprint
Current: http://slowprint.com/slowprintnl








--
Archive: 
http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/1228268977718
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]  
Please contact [EMAIL PROTECTED] for questions.

Reply via email to