Adam,<br><br>I like HCoop. I'm just beginning to come up to speed on our organization and am am sorry -- and concerned! -- to hear your frustration.<br><br>I can not offer much in the way of problem solving, yet, as I have a number of hurdles to overcome before I *understand* the problems.<br>
<br>Further, I am sorry I missed the recent IRC planning meetings. This is, I assume, part of the problem, and your frustration.<br> <br>So what admin issues/responsibilities are we discussing...?<br><br>Best Regards,<br>
Scott Bailey<br><br><br><br><br><div class="gmail_quote">On Fri, Nov 20, 2009 at 1:50 AM, Adam Chlipala <span dir="ltr"><<a href="mailto:adamc@hcoop.net" target="_blank">adamc@hcoop.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In August, I posted a message suggesting that I would be leaving HCoop<br>
admin/planning responsibilities very soon if there weren't signs that<br>
other people were working to take over the responsibilities assigned to<br>
me. (I was/am willing to continue [still temporarily] with Domtool<br>
admin, since I have special knowledge of the tool; and treasurer duties,<br>
since I'm set up with official bank account access.) Frankly, there<br>
have been no signs that this has happened, and I think someone with less<br>
of an emotional commitment to HCoop would have packed up and left already.<br>
<br>
A few people have volunteered to take over facilitating decision-making,<br>
but no one has followed through. It's the "herding cats" element that's<br>
most critical here. The crucial contribution that I've tired of making<br>
is organizing people to make decisions and get work done in reasonable<br>
time frames. Upon volunteering to do this kind of organization, the<br>
volunteer is invariably surprised to see that merely starting a mailing<br>
list thread is insufficient to get a decision made. Where I have always<br>
kept pushing on people to make progress, the recent volunteers for this<br>
role have just faded away into silence. This is understandable; it's a<br>
thankless role, and I can see why people would want to avoid it.<br>
Nonetheless, we need to accept that HCoop is over unless we find some<br>
way to make decisions without using me as the operating system.<br>
<br>
I sent out my first plea of this kind about four months ago, and the<br>
critical issues are still "languishing in the mailing lists," waiting<br>
for some imaginary consensus decision-making process to produce final<br>
plans. We at least managed to fix the mire Apache DoS problems, but<br>
that turned out to have a simple software solution, of the kind that<br>
geeks have no problem organizing to implement.<br>
<br>
So, what do you want to do? (I think it's important for me to finally<br>
stop writing "we" in connection with HCoop, because that can only lead<br>
people to keep assuming I'll shoulder the same recurring burden.) I<br>
have to admit that I'll be skeptical of any offers to take over<br>
people-organizing responsibilities, but I still feel like giving people<br>
a chance to offer.<br>
<br>
_______________________________________________<br>
HCoop-Discuss mailing list<br>
<a href="mailto:HCoop-Discuss@lists.hcoop.net" target="_blank">HCoop-Discuss@lists.hcoop.net</a><br>
<a href="https://lists.hcoop.net/listinfo/hcoop-discuss" target="_blank">https://lists.hcoop.net/listinfo/hcoop-discuss</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Scott Bailey<br>