Webdev:Meetings:2008-08-28
From MozillaWiki
- Intro to John Waller, new contractor [laura]
- Dedicated release managers per website [rdoherty]
- Seems to be confusion when releasing AMO
- it's a standard practice for many software teams to have someone responsible for release management
- Would just be one of us per site
- Not too much more responsibility
- Makes a 'go-to' guy when releasing, making it easier for IT to manage
- For AMO, this is going to be me moving forward until we find someone else who has time -- for other projects the lead dev is responsible for this, but there are situtations where there isn't a lead dev and we are "helping out" and those are a little tougher. (morgamic)
- I had an idea of having people work on less projects, but be more focused. [rdoherty]
- We lose a lot of time switching between sites
- Gives people more time to become experts instead of doing drive-by patches
- Sure, we just need more people -- it would be very cool to be able to give each person just 1-2 projects, but that's not possible sometimes. When it comes to that, some people are better at context-switching than others and I've tried to give those people more things at once while letting others remain focused. There's a balance here, and I'm aware of the ideal situation but if you're resource constrained you start to add residual overhead switching people between projects, and that's frustrating/wasteful but temporary. (morgamic)
- Do we have lead engineers/architects per site? Might be a good idea to have someone with lots of knowledge of how a site works who can review big patches/ideas and push for an overall architecture. [rdoherty]
- Yes, with the exception of projects we did not start but are being asked to work on (morgamic)
- Started this spreadsheet to clear this up a while before summit, and straightening out roles and responsibilities for this many projects across 5 full-time people is pretty difficult (morgamic)
