4 ms·
This single-tool-usefulness thing is why, in a former life, I started out administering over 100 instances of Trac. When Trac came out, it did everything confl
by MPSimmons 3y ago
This single-tool-usefulness thing is why, in a former life, I started out administering over 100 instances of Trac.
When Trac came out, it did everything confluence, jira, and bitbucket do, in one open source, easy to use tool that had tons of community-developed plugins.
The thing is, though, that it wasn't meant to be administered. It didn't lend itself to management. It was meant to be deployed, and then not managed, which is _fine_ if you have one or two of them, because they're pets, but in a world of cattle, you can't have 100+ special snowflake systems deployed like that.
I spent years mowing down every Trac instance I could find, migrating them to the actually-centrally-managed Atlassian stack. After I left that team, I would incentivize other people to carry on in my footsteps by buying a bundt cake for anyone who led the charge to remove a Trac instance from the infrastructure.
I gave away a lot of bundt cakes, but the infrastructure was better and more reliable because of it.