My perspective is that quality is a process and a project rather than just a goal or a fixed property of a team. This new team is like a project that's barely b

My perspective is that quality is a process and a project rather than just a goal or a fixed property of a team. This new team is like a project that's barely begun and you're coming off a project that was in maintenance mode. So like any project it works best if you do one thing at a time and build up some momentum. You can't fix everything at once. See if you can get people to buy in to just getting the indentation consistent (my favorite place to start), or preventing the development software from touching the production database. Get one win, give it a little time, and then go for another pass. Meanwhile set an example in your own contributions. It is very possible to improve things but it takes patience, planning how to deal with setbacks, flexibility, and recognizing what the real priorities of the company are and what quality means in context.