12LTS Crowdfunding Campaign

Crowdfunding campaign for TYPO3 12LTS compatibility

This extension will be compatible with TYPO3 12LTS. However, this requires quite a lot of work. This crowdfunding campaign will collect the funds for this work.

The goals are to

have clean 11LTS compatibility
replace the use of AbstractPlugin and marker-based templates with a partial rewrite with Extbase/Fluid

TL;DR Overview

12 LTS Compatibility status

Extension	12LTS-compatible release	12LTS testing branch
phpunit	(to do)	(not available yet)
oelib	(to do)	(not available yet)
feuserextrafields	(to do)	(not available yet)
onetimeaccount	(to do)	(not available yet)
seminars	(to do)	(not available yet)

❓ How does this work?

To contribute to the campaign, please send an email with the net sum you would like to pledge (at least 100€), your billing address, your company name and URL (for the list of pledges) to typo3-coding AT oliverklee DOT de.

As a campaign backer, you will get a backlink from the seminars manual, regular update emails and beta versions to test and use.

I will start work on each top-level milestone (and send the invoices for that milestone) once the corresponding milestone is finished. (And as long as a milestone is not completely financed, you will not receive an invoice for your pledge that covers the corresponding milestone.)

You can always increase you pledge, but you cannot reduce or cancel it. After milestone 1 is financed, you can also pledge for a certain milestone. I'd prefer to do the milestones in order, though. Also, pledging for a certain milestone will spread out the pledges, hence reducing the probability of more milestones getting full funding.

All prices listed in the milestones are net prices.

🌑 Milestone 1: Fix some open bugs in the extensions and do some cleanup

oelib: 3 bugs
onetimeaccount: 7 bugs
seminars: 23 bugs
also switch TypoScript includes to always use @import
raise all extensions to PHPStan level 9 (without fixing the additionally-found issues)
enable the bleeding edge PHPStan rules for all extensions

🌑 Milestone 2: Tests streamlining

switch the seminars tests from nimut/testing-framework to typo3/testing-framework
- 79 unit testcases
- 44 functional testcases
make all data providers static (in preparation for PHPUnit 9)
- feuserextrafields: 4
- oelib: 84
- onetimeaccount: 6
- seminars: 91
stop using setMethods() in the tests: 7 (seminars)

🌑 Milestone 3: Drop old things

drop TYPO3 10LTS support
drop things marked as deprecated
- phpunit: 1
- feuserextrafields: 2
- oelib: 49
- seminars: 16
drop support for PHP 7.2 and 7.3
move the removal of some deprecated thing one major version later (where it is not practical to update the callers yet)

🌑 Milestone 4: PHPUnit and PHP language level upgrade

switch to the latest TYPO3 Rector version
upgrade all extensions to PHPUnit 9
upgrade the code use PHP 7.4 language level features
add more native type declarations (also with callables)
reformat the code with the TYPO3 Core CS-Fixer rules
upgrade all extensions to typo3/testing-framework V7
switch the DB fixtures from XML to CSV

🌑 Milestone 5: Stop calling deprecated code

feuserextrafields: 52 calls
oelib: 367 calls
onetimeaccount: 7 calls
seminars: 367 calls

🌑 Milestone 6: Basic 12 LTS compatibility for the ecosystem extensions

Just get the automated tests and the code to work, but do not make it clean of fix any deprecations. Also update the TCA as needed. Go through all extension scanner warnings and fix the positive cases.

testing TYPO3 distribution
testing site package
phpunit: 1 extension scanner warning
feuserextrafields: 4 extension scanner warnings
oelib: 18 extension scanner warnings
onetimeaccount: 1 extension scanner warning

🌑 Milestone 7: Basic 12 LTS compatibility for seminars