Team Info:

Room - D1-84

Sub-teams:

CMFMember-to-Membrane-and-Remember Migration
Refactoring+
Documentation
Functional Testing
ArchGenXML
PAS
Remember Bug Fixing+

Membership

Plone / CMF

• removal of member / user dichotomy at the CMF layer
• migration away from current memberdata / groupdata tools
• improve handling of volatile users [bitmonk/justizin: define volatile users?]
  
• improve handling of large and small numbers of users and groups
• PAS/PlonePAS merging

membrane

• develop working examples (with tests) of users where authentication is not via a membrane plug-in, but properties and/or groups and/or roles _are_ provided via a membrane plug-in.  also of users which get some properties from membrane, some from other sources
• ensure that membrane-based users will work in a site alongside non-membrane-based users
  

remember

• make it work like a standard Plone site, with functional tests to prove it
• ensure remember will work with member objects that are not in portal_memberdata, with tests
• ensure remember will work w/ other auth plug-ins and in sites w/ non-remember-based member objects, with tests
• tests, tests, tests; many CMFMember tests can be ported forward
  
• CMFMember migration
• add utility which defines policy for default new member type and location
• remove custom membership tool; all custom behaviour currently in the membership tool should be moved to PAS plug-ins, to which the default memberdata tool is already delegating

• custom member search code goes in IUserEnumeration plugin / adapter
• member creation goes in IUserAdder plugin / adapater
  

teamspace

• refactor using interfaces and adapters
• write membrane-based PAS groups plug-in that uses teamspace teams to drive groups
  
• cache security settings by team, use Z3 events to invalidate cache and to trigger recataloging of allowedRolesAndUsers for all pertinent objects

  bitmonk/justizin: I think the general idea of driving groups with something like teamspace teams is good, and think it is important to focus on the core problem solved by teamspace: delegation-based group membership.  If you can manage real groups the way that teams are managed in TS, you don't need a "space", a folder will do.  I think the 'teams' portlet from TeamSpace would be better served  I also think it's important to remove the single-manager design of TS in favor of roles / permissions-based group management, and if it were possible to have roles in a group, they could apply also to folders and other content the group has access to, though the implementation details of this last bit might get hairy.

b-org

• reference / relation-based group membership with delegation (optilude says that at least the relation bit wouldn't be difficult)
  
• talk about moving delegation-based group membership into PAS / PlonePAS / Plone as standard functionality