* Agenda: Team roles* The only subject. There are two reasons to discuss it:
- *Huge* misunderstanding of Artem's role (Customer) by him and Andrey Lapin (code owner) and Denis. - Misunderstanding of Andrey's (L) responsibilities: seems that he forgot that he is a design maker, not the code monkey. Seems some administrative stuff should be applied in a team, like: templates for feature requests&info about designs that was made, a policy to reject to implement any undocumented&unsended&undiscussed requests, pure differences between feature request and implementation, rollback policy, milestone policy, etc. And the last thing I want to share before the meeting: Andrey Lapin showed that it's still hard for him to be a code owner. I think he can share this role with Andrey Bukirev. -- Best Regards, Fedor Korshunov -- You received this message because you are subscribed to the Google Groups "SourceAnalyzer Team" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sa_team?hl=en.
