AimTechOpen sourcing these tools won't neccessarily fix the issue of fewer devs being around. Who is gonna review these PRs? Who agrees what should and shouldnt change? Whos gonna filter out the 7 million PR generated slop PRs and banned player XYZ making a PR to change serve.me to tf2isfullodpedos.me.
We cant even agree as a community whether spoon should be banned.
fully agree with this take, since I was/am responsible for the way ETF2L works from a technical perspective, since 2019 I'll give my two cents
I cannot imagine opening for instance etf2l code where we used a scanner for steamids which was changed in 2012? last time because noone had time to implement modern OCR solutions like something based on tesseract because most of the people who are/were "site coders" did nothing or almost nothing for years
what I'm trying to say by that is, the code has or had some vulnerabilities, some with CVSS 7+ score and I couldn't sleep safe if I knew that some malicious actor could find a portion of a code letting you pull database data and find idk some data about admin investigation where very sensitive data are shared and without disclosing it to us used it against the site in order to gain data or access to the container of any sort
yes opening code let's some good people look at it fix it, but you have to look at both sides of a medal and in this specific scenario it's a bad idea