[HCoop-Discuss] Filesystem poll results

[Adam Chlipala]

Adam Megacz wrote:
> The real issue is the deliberate and systematic miscategorization of
> issues as "AFS issues", because declaring something to be "an AFS
> issue" is a sure-fire way to get an admin (me) to look at it.  I
> deeply resent this attempt to manipulate my volunteer time, and I hope
> it is remembered at the next board election.
>   

I want to encourage you again to put things in perspective.  This past 
bug is, to me, almost 100% likely to have been caused by failures to 
access files on AFS volumes:
    https://bugzilla.hcoop.net/show_bug.cgi?id=696
We have error logs and messages output by web applications themselves 
stating inability to access files in AFS as the direct causes of 
failures, coming from a diversity of different dynamic content systems, 
such that those problems go away when Apache is restarted.  Something 
may have fixed this bug since then, but I think it's far from 
"maliciously misinformative" of me to assume that reports of similar 
recent behavior stem from the same cause.

I've sunk huge amounts of time into HCoop, losing whole days of other 
work at a time responding to emergencies, with real finanical and stress 
costs to me.  I'm not going to spend time on detailed diagnostics of 
problems, especially those that look just like past problems with clear 
causes.  It seems wildly unempathetic of you to demonize me for my snap 
judgments when you aren't willing to respond to all technical issues at 
HCoop and be the one to decide which components need to be tweaked to 
keep our services running.  If you had some experience with that, you 
might realize why it's generally cost-effective to be willing to live 
with inaccurate assessments until they're proven wrong.

And I really don't think there's any credible evidence that anyone is 
mislabeling bug reports to try to get you to spend more time on HCoop stuff.