Add a chapter on accountability

[semioticrobotic]

This seems like a big one: How do open source projects and other open organizations maintain high degrees of accountability? What can remote, distributed teams learn from them?

[LauraHilliger]

Podcast?

[semioticrobotic]

Are you suggesting that teams use a podcast to maintain accountability in distributed environments, and we should write a guide chapter on how to do this? Or are you suggesting that we answer this question with a podcast rather than something written for this guide?

Sorry, perhaps I'm being dense—coffee still kicking in.

[LauraHilliger]

This: suggesting that we answer this question with a podcast rather than something written for this guide

And then we can transcribe it :D

[semioticrobotic]

Ah! Okay. Thanks for clarifying. 😄

Would be great to see. And our community has already written tons on openness and accountability, so today I plan to trawl through our archives and see if something already written could begin addressing this (no need to re-invent). And then maybe as part of that we could:

• Do an interview with the author, asking for an update, then link out to it
• Record an interview with someone who has a different perspective, then link out to that
• Record a round-table discussion in response to the piece that's in the guide

Or none of those. Just thinking.