Move tool configuration from config/ and the project root to Build/?

[oliverklee]

The TYPO3 Core uses the Build/ folder to store tool-related files that are not intended to be delivered when the package is installed, for example the PHPStan configuration of the PHP-CS-Fixer configuration.

I'm trying to harmonize the setup and style across my projects.

@JakeQZ @sabberworm Would you be okay with us moving the tool configuration files that we currently have in config/ or the project root (like the PHPUnit configuration file) to Build/? (I'd then create PRs for both our projects for this.)

[JakeQZ]

I'd be fine for it to be renamed to build/. However, all the other root folder names use all-lowercase, so Build/ would look a bit out of place.

[oliverklee]

If we used the spelling Build/ instead of build/, we (i.e., my working student Anna and I) could copy'n'paste Composer scripts between our projects without having to remember to change the casing each time. This would remove some headaches for us.

Would you be willing to live with the casing Build/ for this, @JakeQZ?

[JakeQZ]

Looking at the TYPO3 repository (which has quite a lot of subfolders within Build/), I'm guessing that renaming the folder in that project to build/ would involve quite a lot more effort.

It is, and the end of the day, just an arbitrary name, so I can live with it. It just looks odd not having a consistent top-level folder naming convention.

[oliverklee]

Yes, and for changing the casing of the folder in the TYPO3 Core, I'd need to get the consent of the TYPO3 Core Mergers team (which I'm not part of), which won't be likely to happen.