Karsten Wade wrote:
On Wed, Feb 11, 2009 at 01:22:24PM +0100, Max Spevack wrote:
(4) Being able to analyze the data in time slices. Monthly, quarterly, and yearly are what interests me most.
Although it won't normally be as relevant, seeing down to the day or even hourly level might be interesting.
For example, we usually have an uptick of interest in joining Docs following a release. I'd like to be able to look for that trend in other sub-projects and show that trend to other team leaders so they can be prepared for such an uptick. (This one is perhaps tracked by emails where the subject contains .*[I,i]ntro.*
So, there are a few points in time each year where this matters. As another example, I'd be interested to see what happened to mailing list traffic following last Fall's security incident. Maybe nothing, maybe something that lends weight to another argument.
- Karsten
I had a conversation recently where I experessed, about EKG, the desire to choke out impulses to collect data that we can't use to some actionable end.
That being said, I don't think trying to learn about things that we can't /use/ is a good use of time.
I'd rather find data we can use that will help us make decisions and influence projects.
Another problem is that correlation != causation, so it's impossible to draw a line between list traffic and any one particular event.
Perhaps people wash more clothes on Tuesday in February than Tuesdays in January. Is that because of the stock market or the super bowl? Or just because it's cold outside.
EKG's mission, I think, should be two things: -- to learn what projects people are interested in and have strong communities around them -- to learn which projects could use more help on the community side, and to point out other projects they could look to as examples
--Michael
ekg mailing list ekg@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/ekg