#9328: content im-/export
----------------------------+-----------------------------------------------
Reporter: csenger | Owner: csenger
Type: PLIP | Status: assigned
Priority: minor | Milestone: 4.x
Component: Infrastructure | Resolution:
Keywords: |
----------------------------+-----------------------------------------------
Comment(by tomster):
Replying to [comment:30 limi]:
> Could we ask Quintagroup to donate it to the Foundation?
you just did... all three developers have added themselves cc: to this
ticket already some time ago :)
>If we're going to do this, it should be in the Plone repository — or at
the very least in the Collective. Private repositories are painful. :)
indeed. seeing that none of them has responded yet (neither to this thread
nor to my PM) we might consider copying the necessary bits from
quintagroup.transmogrifier into plone.app.transmogrifier (q.transmogrifier
is contains more features than we really need for this plip, anyway.)
also, from a UI perspective i've been thinking of adding a 'proper' "click
here to dump" and "click here to import your old site" controlpanel
instead of sending people to the ZMI.
and that could live in p.a.transmogrifier, or we create a new package
p.a.contentmigration or somesuch.
IMHO we should have two separate products, one which you install into your
old site for exporting and one for importing that dump which you install
into your plone 4 (or later plone 5) site.
any feedback on this approach?
--
Ticket URL: <http://dev.plone.org/plone/ticket/9328#comment:31>
Plone <http://plone.org>
Plone Content Management System
_______________________________________________
PLIP-Advisories mailing list
plip-advisor...@lists.plone.org
http://lists.plone.org/mailman/listinfo/plip-advisories
