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?
5
- What general direction would you like to see membrane/remember
development take? Select one or rank by priority:
[ 3] new features
[ 1] improve performance
[ 2] more simplicity/maintainability
- What specific direction would you like to see membrane/remember
development take? Select one or rank by priority:
[ 2] non-AT option
[ 1] lightweight AT profile schema
[ ] other, please describe
- What do you use membrane/remember for? Select all that apply:
[ x] Archetypes Schema for members
[ x] membership workflow
[ x] extended member searching/cataloging
[ ] other, please describe:
- Do you use membrane without remember? If so please describe.
we don't use remember at all, but we used remember (and borg) thoroughly
as a reference for our own implementations.
regards,
--
Franklin Kingma
Four Digits, internet solutions
Willemsplein 15-1 6811 KB Arnhem
[EMAIL PROTECTED] | http://www.fourdigits.nl
tel: +31 (0)26 44 22 700 | fax: +31 (0)84 22 06 117
KVK 091621370000 | BTW 8161.22.234.B01
--
Archive:
http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/1228296298373
To unsubscribe send an email with subject "unsubscribe" to [EMAIL PROTECTED]
Please contact [EMAIL PROTECTED] for questions.
