009/3/23 Karsten Wade <kwade(a)redhat.com>:
On Mon, Mar 23, 2009 at 12:39:14PM -0400, Yaakov Nemoy wrote:
>
> I'm not sure how to go about this offhand. PISG does things in a
> fundamentally different way. It's also written in the Pathelogically
> Eclectic Rubbish Lister, which means it's hard to airlift chunks of
> code from one place to another. I think making EKG a part of a
> toolkit is a better plan in the long run, but i'm wondering, a toolkit
> of 'what'?
Community health measurement and tracking toolkit.
In a hospital ICU, there is the main machine that goes 'Ping', and it
tracks O2 sat levels, heart rate, blood pressure, etc. Then there are
other machines that are occasionally or regularly used. Twice a day a
couple of nice lady vampires from the lab drop by to take yet more
samples. Etc.
In that comparison, I see EKG as filling the first roll. No other
tool we know of does that for communities, and it is an
essential/ongoing function. So it's a central part of a toolkit that
can include other measurement methods.
We have Smolt, Damned Lies, etc.. :)
Without having read your opinions on tracking IRC, I am interested
in
tracking and analyzing IRC usage in contributor situations. It seems
to me it should be part of our central tracking, but then we'd have to
rewrite it in to EKG. Sounds pretty silly if there is an active
project that does it, regardless of your opinion of the language used
to write the project. So, is there a way to use e.g. PISG and pull
the data in to where EGK can use it for reports, etc.?
My main issues are perceived ideas of privacy on IRC. It's a
quasi-ethical one that has to do with what people expect from an IRC
channel vs. mail.
PISG does its analysis completely differently from EKG. Ethical issues
aside, getting IRC logs into EKG is *very* simple. I could do a test
demo using logs i have on my shell server. My comments were about
adapting the graphs and reports that PISG generates. Since it's
written in Perl, i couldn't reuse anything there easily without just
rewriting.
If you're interested, we could set up PISG and EKG side by side for
any reason in particular, but i think alot of the general purpose
analysises i have planned for EKG would rival what PISG can already
do. I'm definitely not planning on rewriting what i have to work with
PISG code in Perl, 2 rewrites is enough. PISG can't handle mailing
lists, and EKG has the capability but not ability to handle IRC
channels.
-Yaakov