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