>
> - How many membrane and/or remember deployments are you responsible for?
> One
>
>
> - 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
>   [ ] 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.
>
> No
>
> Thanks in advance for all your responses!
>
> Ross
>
>
>
> --
> Archive: http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/1228267212368
> To unsubscribe send an email with subject "unsubscribe" to remember@....  Please contact remember-manager@... for questions.
>
>   

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

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?


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

Hi Ross and List.

I didn't want to derail your survey so I've started this as a separate
thread.

I've recently been thinking that Plone needs an overhaul of its core user
apis (lets assume for these purposes that .cpy etc counts as an api).
Why is this relevant? Well remember would be much simpler if we had a
cleaner api for customising the Plone user/registration system and there
really isn't an owner for this core subsystem so perhaps this is a good
place to put effort?

N.B. I'm not saying replace Plome members with membrane, I'm saying create a
nicer api so remember and other usecases can be done much more cleanly.

I'm guessing I'm not the only person who's thought of this so I was
wondering if it was on the roadmap you hinted at Ross?

My interest in this is:
I want to make Plone easy to learn for developers
Which led me thinking we need to unify the technology under the hood and get
rid of all code in skin folders.
A big chunk of the .cpy etc is user registration and login etc.
I was about to raise a ticket on this issue but this discussion started...

My other interest is PloneSocial and the upcoming paris sprint for open
social in Plone [1].
In particular if we had a nice api then use cases like [2] "user invites
another user to share a document" become much easier to integrate. And
usecase where you want customised profiles and friendslists etc but you may
want to store that all in a relational db instead of membrane.


1: http://groups.google.com/group/plone-social-networking
2:
http://groups.google.com/group/plone-social-networking/web/usecase-invite-to
-share



Dylan Jay
Technical Solutions Manager, PretaWeb.com
---
M:+61421477460 ~ MSN:djsq@... ~ Y!+Skype:dylan_jay ~ ICQ:520341 

> -----Original Message-----
> From: news [mailto:news@...] On Behalf Of Ross Patterson
> Sent: Wednesday, 3 December 2008 12:20 PM
> To: remember@...
> Subject: [Remember Mailing List] Survey of membrane/remember users
> andstakeholders (was: passing the torch)
> 
> 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
> 
> 
> 
> --
> Archive:
> http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/
> 1228267212368
> To unsubscribe send an email with subject "unsubscribe" to
> remember@....  Please contact remember-
> manager@... for questions.

> - How many membrane and/or remember deployments are you responsible for? 
 
 Just trying it on one instance....we have about 15 plone sites 
 
> - What general direction would you like to see membrane/remember 
> development take? Select one or rank by priority: 
 
 [ 2 ] new features 
 [ 3 ] improve performance 
 [ 1 ] more simplicity/maintainability 
 
I'm currently running a test site, and finding it a bit painful.  
 
> - 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 
 [ ] other, please describe 
 
> - 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. 
> 
> No 
> 
> Thanks in advance for all your responses! 
> 
> Ross 
> 
> 
> 
> -- 
> Archive: http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/1228267212368 
> To unsubscribe send an email with subject "unsubscribe" to remember@.... Please contact remember-manager@... for questions. 
> 
> 

Hi,

Details are as follows:

On Dec 02, 2008 08:20 PM, Ross Patterson wrote:
> 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?

About 3.

> 
> 
> 
> - What general direction would you like to see membrane/remember
>   development take?  Select one or rank by priority:
> 
>   [ ] new features
>   [ ] improve performance
>   [X] more simplicity/maintainability
> 
> - What specific direction would you like to see membrane/remember
>   development take?  Select one or rank by priority:
> 
>   [X] non-AT option
>   [ ] 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.

Yes, the implementation was done by another developer, though, so a bit
sketchy on details.

> 
> 
> 
> Thanks in advance for all your responses!
> 
> Ross
> 

Ross Patterson wrote:
> 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?
>
>   
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
franklin@... | 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 

> - How many membrane and/or remember deployments are you responsible for?
3
 
> - What general direction would you like to see membrane/remember
>   development take?  Select one or rank by priority:
> 
>   [1] new features
>   [2] improve performance
>   [3] 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
>   [ ] 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.
-

Cheers,

  Joerg

Ross Patterson wrote:
> 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?
> 

4, with another one in the works.

> 
> 
> - 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
>   [ ] other, please describe
> 
> 
> 
> - What do you use membrane/remember for?  Select all that apply:
> 
>   [x ] Archetypes Schema for members
>   [ ] membership workflow
>   [ ] extended member searching/cataloging
>   [ ] other, please describe:
> 
> 
> 
> - Do you use membrane without remember?  If so please describe.
> 

No - use a ArchGenXML-created remember product tied into MySQL to do additional 
user registration verification.

> 
> 
> Thanks in advance for all your responses!
> 
> Ross
> 
> 
> 
> --
> Archive: http://www.openplans.org/projects/remember/lists/remember/archive/2008/12/1228267212368
> To unsubscribe send an email with subject "unsubscribe" to remember@....  Please contact remember-manager@... for questions.
> 
> 

On Dec 02, 2008 08:20 PM, Ross Patterson wrote:
> 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
> 


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

4

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

  [ ] new features
  [x] improve performance
  [x] 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
  [ ] 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
  [x] other, please describe:
For one client, we have a hybird custom member/remember-based class that is
part Archetypes/attribute storage and part PostgresSQLStorage (with overrides
on PG CRUD methods, but SQLStorage is still very inefficient.)  This allowed
us to graft the client's legacy relational member data onto the Plone member
profiles/objects and gain all the typical workflow, etc. we want out of
membrane.


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

Ken W.

On Dec 02, 2008 08:20 PM, Ross Patterson wrote:
> 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?

1

> - What general direction would you like to see membrane/remember
>   development take?  Select one or rank by priority:
 
 [2] new features
 [3] 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
 [ ] other, please describe

Maybe it's a plone, 

> - What do you use membrane/remember for?  Select all that apply:
 
[ ] Archetypes Schema for members
[x] membership workflow
[ ] extended member searching/cataloging
[ ] other, please describe:

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

On 12/2/2008 8:19 PM, Ross Patterson wrote:
> - How many membrane and/or remember deployments are you responsible for?

1

> - What general direction would you like to see membrane/remember
>   development take?  Select one or rank by priority:
> 
>   [ ] new features
>   [ ] improve performance
>   [X] 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
>   [ ] other, please describe

> - 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:

The technology (AT or other) is not nearly as important as that there is 
a low barrier to treat members as content in a way that is easily 
installable, maintainable, and migration friendly. The biggest glaring 
gaping hole in Plone is that members are not first class content.

-- 
Sincerely,

Chris Calloway
http://www.secoora.org
office: 332 Chapman Hall   phone: (919) 599-3530
mail: Campus Box #3300, UNC-CH, Chapel Hill, NC 27599

> - How many membrane and/or remember deployments are you responsible for?
3
> - What general direction would you like to see membrane/remember
>   development take?  Select one or rank by priority:
> 
>   [2] new features
>   [3] improve performance
>   [1] 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.
One project involved subclassing borg.employee and borg.project, which are
both membrane-only types

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

6

> - 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

I haven't noticed remember being particularly slow, has anyone  
benchmarked it's usage?  I think the biggest thing to watch out for at  
this stage is to maintain compatibility, we don't want to break  
everyone's installations :)

> - 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

Better ways of handling multiple member types/profiles.  Usually the  
difference is just the profile, so as has been discussed already.  A  
better way of handling member profiles is needed.

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

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

Typically when our clients start wanting custom member information it  
is easiest to start implementing something with remember.  The  
requests will typically evolve into something that really fits what  
remember is currently doing for us.  The approach can be a bit heavy  
handed but integrates with typical Plone development nicely.

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

No

Clayton
-- 
S i x  F e e t  U p ,  I n c .  |  "Nowhere to go but open source"
Silicon Valley: +1 (650) 401-8579 x603
Midwest: +1 (317) 861-5948 x603
Toll-Free: 1-866-SIX-FEET
mailto:clayton@...
http://www.sixfeetup.com  |  Zope/Plone Custom Development