Define roles and responsibilities for stats gathering

[cogat]

The current (documented) arrangement is that "someone" (me, de facto) updates the statistics every 6 months. The reports google spreadsheet has a tab that automatically compiles stats for a given year, and they need to be copied from that tab into the published account, which is currently in statistics.md and on https://www.djangoproject.com/foundation/committees/#conduct.

IMO there isn't currently enough change in statistics to be worth doing more frequently than that, but there may well be in future.

Ola has stated a preference for doing this more regularly, ie every 2-3 months. I'm curious about the reasons for this - ie what use can be made of having the statistics updated more regularly.

There's also the question of what statistics we compile, which I think can be covered in #2.

[jefftriplett]

IMO we should update every 2-3 months as a canary test. If something major comes up in the interim then there's no harm in updating sooner.

[olasitarska]

I think having a smaller job more frequently is better than having a bigger job less frequently, as it does make it easier to maintain -- hence my thinking of 3-4 months that I mentioned in line comment yesterday.

I'm also happy to pick up that role sometimes, it doesn't all have to fall on you. Maybe we should just state that "whoever volunteers during a meeting that month does it, and if no one volunteers then committee chair is responsible"?

[olasitarska]

One more thing -- once we decide how often this should be updated, we should also update transparency chapter.

[cogat]

It feels like every 3 months is the intersection of Venn diagrams. I'm happy to do that for the time being at least. I'll update the docs unless someone gets there first; Ola, can you set up an automated email to conduct@ on 1st August and every 3 months thereafter to act as a reminder?