Hi Peter! Glad to hear you still want to volunteer. I'm actually taking point for the Haskell.org committee in figuring out how to get things sorted out. I've been trying to figure out who still does what, out of the current group with admin access, and list what services there are to begin with.
The wiki page collecting information is here: http://www.haskell.org/haskellwiki/Haskell.org_infrastructure Since things have been communally run for some time, its been quite hard to pin down names to particular aspects. The current set of names, apparently, rightfully doesn't want to be pinned down, because they've been tending to have monotonically less time than before, as career, family, etc. responsibilities have grown on them. I sent out a survey that has thus far garnered very little in the way of response (in itself a sort of response) as well. My next step was, and is, reaching out to people who have volunteered to help in the past, as well as, depending on the response, canvassing for others. You were very high on my list :-) (Any other potential volunteers on -infrastructure who I haven't contacted yet, feel free to reach out!) In the short-medium term, the plan as it now stands is to get some fresh blood in, and start getting people up to speed on what runs how, as well as what (typically minimal) maintenance is required and how to distribute that. I'll probably be able to be more concrete on this in the next week or two, at the outset. We also have, separately, a plan for a server move, which I know Ian will be coordinating. The problem hasn't been from the side of people doing -infrastructure, I think. Rather, its the committee's job to set policy, including policy for how we actually manage infrastructure, and we've been fairly poor at that for a period. We now recognize the problem, and are going to step up to change it. Cheers, Gershom P.S. There are also some ideas in the longer term floating around about using funds/getting funds to hire some part-time sysadmin help or etc. That's not on the immediate agenda, but its certainly not out of the question once we start to get a handle on what we need/would like. On Tue, Jun 18, 2013 at 4:16 PM, Peter Simons <[email protected]> wrote: > Hi Simon, > > > If there are no volunteers, then maybe we (i.e. the committee) has to > > say so, and advertise the fact that the community server will shut > > down for lack of support. > > well, there *are* volunteers. I, for instance, have volunteered to help > administer the haskell.org machines and services before on this mailing > list. It's just that I never got any response. So what can I do? > > My impression is that the infrastructure community -- whoever that is -- > is quite unresponsive to people who try to report issues, try to suggest > improvements, or try to volunteer. > > And that is a vicious circle: the infrastructure community doesn't > respond to outsiders, apparently because there is not enough man power > to do so. And this very unresponsiveness is one of the main reasons why > things will stay that way. > > Just my 2 cents, > Peter > > _______________________________________________ > haskell-infrastructure mailing list > [email protected] > http://community.galois.com/mailman/listinfo/haskell-infrastructure >
_______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
