Re: Dealing with corporate email recycling
- From
Philip Oakley <philipoakley@iee.email>
- Date
- Mar 15, 2022, 11:15 UTC
- Message-ID
- <eecab055-94bc-2174-0490-28b76cf48b0e@iee.email>
- In-Reply-To
- <87y21c2ehl.fsf@gmail.com>
On 15/03/2022 01:23, Sean Allred wrote:
Show 14 quoted lines
> Philip Oakley <philipoakley@iee.email> writes: >> A broader issue for the corporate email mailbox systems is those that >> are allocated to roles. So you may have Traning1@corp.com thru >> Training9@corp.com (we had) and if that training includes practical low >> hanging fruit examples from a project, it's difficult to disambiguate >> those commits. More likely is say, having TestPC1 - TestPC9 that >> included debug commits, perhaps even with pair programming test & debug >> sessions, so allocation to individuals (rather than mailbox) becomes a >> real problem. Hopefully that's rare in Sean's case. > Yep, this wouldn't happen for us. Lots of other processes depend on > there being an individual making the commit. > > I'd also be surprised if this didn't cause process problems for other > folks, too.
I was in equipment engineering where independent dedicated test equipment was more common, rather than pure software, so the potential for role based commits from TestPC1 - TestPC9 was far more likely (for cases where it's the hardware that needs to be understood, not the engineers' choice of code ;-)