#196: GroupUserFolder removing

Contents

1. Definitions
2. Motivation
3. Assumptions
4. Proposal
5. Implementation
6. Deliverables
7. Risks
8. Progress log
9. Participants

Proposed by

Encolpe Degoute

Proposal type

User interface

State

being-discussed

Definitions

 

Motivation

There were and there are a lot of critical UI bugs around GroupUserFolder by PlonePAS. Because of these, several Plone release had to be delayed. We fix a lot of them in customer branch.

Assumptions

 

Proposal

The first point is to fix UI to use pure PlonePAS API:

1. users and groups control panel
2. members search form
3. sharing tab

 

Then we can cover all these by some functional doctests to prepare GroupUserFolder removing.

 

To remove GroupUserFolder we need to replace 4 tools:

1. portal_membership (yet done)
2. portal_memberdata (yet done)
3. portal_groups (to do)
4. portal_groupdata (to do)

 

As PluggableAuthService and PlonePAS implements all we need, it's more a compatibility step we need to put a depreciation warning on these tools. The removing step should implements an utility that assemble all methods from historical tools and put a deprecation warning tools usage.

 

Implementation

Groups are already implemented in PlonePAS, then we have to give them a group property sheet based on user property sheet.

UI improvements are already deployed  in a private branch.

Deliverables

 

Risks

GroupUserFolder is unusable since two major versions. There is no risk to remove it.

But, implementing a new portal_groups and portal_groupdata would preserve the same API and run the same tests. This could give some headache.

The

Progress log

 

Participants