How about a "Meet the TPG" session? Could be pretty casual, just meeting folks and talking about what we do and our goals.

@KLans_WMF i like it!

@KLans_WMF, @ggellerman - Any other thoughts?

I think that this is a great idea!

I know that say hi is always nice, but... Why not using the opportunity to bring a complex topic involving more than your team alone that email / hangouts / wiki pages / Phabricator seem not to be enough to solve?

@ggellerman, @KLans_WMF what do you think?

One thing that pops quickly to mind is doing a session on (semi/fully) distributed team best practices? That would have a lot of appeal, and could include voices from across engineering.

Works for me.

@ggellerman
http://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#How_to_schedule_a_session

This session is in the schedule: T86681: Team Practices Group talk about collaboration techniques: remote best practices, backlogs, burndown charts, etc... because communication

Is this task resolved, then?

TPG TLA WTF BBQ. Please write tasks in English, not some hyper-abbreviated version of it. :-)

Maybe a joint TPG-QA thing? I recently floated the idea of actually doing Acceptance Test Driven Development somewhere:

• At the start of an iteration, create Cucumber Scenarios for the user-facing features being developed for that iteration.
• Over the course of the iteration, create the code that the Scenarios describe. Run the Cucumber tests in Vagrant on unmerged branches
• At the end of the iteration, merge the code and the UI tests to the master branch and have them all pass in beta labs for existing Jenkins builds.

I'd like to get a sense of what prevents us doing this.