QA/Team Meeting/QA Team Meeting-2015-07-08: Difference between revisions

Line 48: Line 48:
* Blog posts related to your experience in Whistler?
* Blog posts related to your experience in Whistler?
** http://bit.ly/1KTxE22
** http://bit.ly/1KTxE22
** Justin Potts: http://garblemasher.com/2015/07/06/reflections-on-mozillas-whistler-work-week/
* ashughes: QA meeting proposals to address our disconnected organizational structure (''Disclaimer: these are just '''my''' ideas -- I would encourage everyone to seriously think about what we truly want for ourselves and the community -- contribute your own ideas and leadership to our success'')
* ashughes: QA meeting proposals to address our disconnected organizational structure (''Disclaimer: these are just '''my''' ideas -- I would encourage everyone to seriously think about what we truly want for ourselves and the community -- contribute your own ideas and leadership to our success'')
** Open this meeting up to all QA people. I know the meeting has not technically been "closed" to people outside the circle of folks who reported directly to Clint prior to his departure. However, I think we should repeatedly encourage participation from people we've lost touch with and try to pull them back in (B2G QA is a prime example). One way we can achieve this is by re-branding this as more of a "meetup of Mozilla testers" and less of a "meeting of ex-QA team members".  
** Open this meeting up to all QA people. I know the meeting has not technically been "closed" to people outside the circle of folks who reported directly to Clint prior to his departure. However, I think we should repeatedly encourage participation from people we've lost touch with and try to pull them back in (B2G QA is a prime example). One way we can achieve this is by re-branding this as more of a "meetup of Mozilla testers" and less of a "meeting of ex-QA team members".  
canmove, Confirmed users
7,108

edits