[Framework-Team] migration to plone.app.contenttypes

[Philip Bauer]

Dear Framework-Team, 

at the wine and beer sprint we wanted to allow users that update to Plone 5 to keep their Archetypes-FTIs working until they actually migrate their content to dexterity.

When migrating using the provided migration-form only the currently migrated type's old FTI is replaced by the new FTI. This does not affect the creation of new sites (which will by default only have p.a.contenttypes).

For this we decided to have a profile for each type. The default profile of p.a.c still installs all types (by depending on all the types profiles which themselves depend on a core-profile. 

The profile-dependency-chain looks like this
plone-content (frontpage…) -> default -> [one profile for each type] -> core (permissions…)

Timo objected haven so many profiles would make our code more complex and harder to maintain (https://github.com/plone/plone.app.contenttypes/commit/e1fa1a235703ea48d1563eae5e18ee1fb21ca7cf#commitcomment-5877482)

We think this implementation is more elegant than replacing with FTI's using python and can be nicely reused by developers that maybe want to create sites only with certain types by simply running
       portal_setup.runAllImportStepsFromProfile(
           'profile-plone.app.contenttypes:document'
       )

Here ist the corresponding ticket: https://github.com/plone/plone.app.contenttypes/issues/142 
IMHO a discussion of this should take place there.

Philip

--
Starzel.de
Philip Bauer
Adlzreiterstr. 35
80337 München
Tel: 089 - 189 29 533
Fax: 089 - 189 29 535
bauer at starzel.de
www.starzel.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20140403/a3b88e30/attachment.asc>