[Task]: Move specific functionalities into bundles to keep the core leaner

[brusch]

Functionality	Package Name	Notes	Own Git Repo / Package
Custom Reports	pimcore/custom-reports-bundle		❌
Glossary	pimcore/glossary-bundle		❌
SEO	pimcore/seo-bundle	redirects, robots.txt, SEO Editor, HTTP Errors, Sitemap	❌
System Info	pimcore/system-info-bundle	PHP info, OpCache status	✅
File Explorer	pimcore/file-explorer-bundle		✅
Word Export	pimcore/word-export-bundle		❌
Personalization	pimcore/personalization-bundle	personalization and targeting	✅
Google Marketing	pimcore/google-marketing-bundle	Everything in "Marketing Settings"	✅
Web-to-print	pimcore/web-to-print-bundle		✅
Ecommerce	pimcore/ecommerce-framework-bundle		✅
Static Routes	pimcore/static-routes-bundle		❌
Simple Backend Search	pimcore/simple-backend-search-bundle		❌
XLIFF	pimcore/xliff-bundle		❌
Application Logger	pimcore/application-logger-bundle		❌
Admin UI Classic	pimcore/admin-ui-classic-bundle
UUID	pimcore/uuid-bundle		❌
Newsletter	pimcore/newsletter-bundle		✅

Tasks:

• [Task] Move Custom Reports to CustomReportsBundle within bundles folder in pimcore/pimcore repository #12516
• [Task] Move Glossary to GlossaryBundle within bundles folder in pimcore/pimcore repository #12517
• [Task] Move SEO to SeoBundle within bundles folder in pimcore/pimcore repository #12518
• [Task] Move System Info to repository pimcore/system-info-bundle #12519
• [Task] Move File Explorer to repository pimcore/file-explorer-bundle #12521
• [Task] Move Word Export to WordExportBundle within bundles folder in pimcore/pimcore repository #12522
• [Task] Move Personalization to repository pimcore/personalization-bundle #12523
• [Task] Move Google Marketing to repository pimcore/google-marketing-bundle #12524
• [Task] Move Web-to-print to repository pimcore/web-to-print-bundle #12525
• [Task] Move Ecommerce to repository pimcore/ecommerce-bundle #12526
• [Task] Move Static Routes to StaticRoutesBundle within bundles folder in pimcore/pimcore repository #12527
• [Task] Move Simple Backend Search to SimpleBackendSearchBundle within bundles folder in pimcore/pimcore repository #12528
• [Task] Move XLIFF to XliffBundle within bundles folder in pimcore/pimcore repository #12529
• [Task] Move Application Logger to ApplicationLoggerBundle within bundles folder in pimcore/pimcore repository #12530
• [Task] Move Admin UI Classic to repository pimcore/admin-ui-classic-bundle #12531
• [Task] Move UUID to UuidBundle within bundles folder in pimcore/pimcore repository #12532
• [Task] Move Web Analytics to repository pimcore/web-analytics-bundle #12533
• [Task] Also move sitemaps and redirects to SEO Bundle #14260
• Extract Newsletter functionality into a bundle #14802

Also consider #9357 for each functionality

[dkarlovi]

Related #11105.

[passioneight]

@brusch will the bundles stay open source?

[brusch]

@passioneight yes, of course. This task is just about restructuring and possibly also about priorities, but not about licensing 😊

[NiklasBr]

Regarding pimcore/web-to-print-bundle, wkhtmltopdf is no longer being maintained, maybe it should be deprecated and removed in 11?

[brusch]

@NiklasBr thanks for the hint, you're right, that should be deprecated, no reason to further support an unmaintained product.

[brusch]

See #12431

[jdreesen]

Pimcore will still be a monorepo-right? Cause the issues you created read like the code will actually be moved to independent repos, instead of creating subtree splits of this monorepo.

[brusch]

@jdreesen this is not yet finally decided, but currently our favorite is to separate them out into their own repos. There are multiple reasons for that, mostly organizational wise, e.g. this gives us a better control over permissions and responsibilities. Of course we also know about the drawbacks, but as we're currently only talking about additional features, which are not essential core features such as data objects, I think it would be still reasonable.

[dkarlovi]

IMO, the value of having it be a mono-repo heavily outweighs the drawbacks. Symfony proved the mono-repo approach works on a huge scale, I don't see why it would work for Pimcore.

Managing many repos, keeping their settings, tags, GH actions etc in sync, making cross-cutting PRs, doing releases in sync will be a huge PITA otherwise.

[dpfaffenbauer]

CoreShop also successfully uses the mono-repo approach and works flawless. Makes development a lot easier

[brusch]

Strategy is as follows:

1. bundles which will be a community bundle in future, will be moved to their own repos / packages
2. functionality / bundles that are going to be replaced in future should also be in a separate repo (e.g. Classic Admin UI)
3. smaller commonly used functionalities will be extracted into bundles, but remain in the core repo. They are not provided as their own packages via Composer, when using them you just need to enable them in bundles.php.