I don't think the issue is specifically about having someone on the committee who can look after the infrastructure - the committee's role should be one of oversight, not implementation.
There's nothing to stop people who look after the infrastructure /also/ being on the committee, of course. I volunteered as an admin while on the committee mostly so I could quickly implement decisions of the committee, given the lack of admins in general - but in principle (IMO) the approach should be that the committee decides something an asks the admin team to implement it. The real problem is more fundamental, I think - looking after the infrastructure is time consuming and for some items like requests and security issues, quick responses are also needed. There just isn't enough admin time being invested and what work is done lacks coordination and long-term focus. People have tried before to get things on a firmer footing without success, e.g. http://community.galois.com/pipermail/haskell-infrastructure/2011-February/000326.html The idea of paying someone to do it has been discussed before, and wasn't ruled out; but we'd still need to find an appropriate person as well as an appropriate amount of money. Haskell.org does have money and an income stream from GSoC, and could probably generate more income easily just by advertising for donations. We might also consider whether it's worth having the community server at all in these days of ubiquitous public code hosting. One argument for keeping it is that many, but not all of the current users are using it for paper collaborations, which aren't suitable for public repos. Even if we did get rid of the community server, there's other parts of the infrastructure that need maintenance and so the sysadmin problem would still exist. On 13/06/2013 14:25, Edward Kmett wrote: > If we look back the causes of the current stall is pretty obvious. > > We had a very large turnover in the committee 2 years back when I > joined, with 3-4 people stepping down all at once as I recall. > > Then Ganesh spotted the fact that we didn't have anyone left with access > to the infrastructure and stepped up to do maintenance work, which is > why we didn't have any issues last year, but he left the committee ~6 > months after his term as chair ended. > > There is almost nobody left on the committee who was here 2 years ago, > and it was initially stacked with many of the folks who knew how the > infrastructure worked. > > Most of our discussions in the meantime has been on getting the > arrangement with SPI set up and in dealing with random summer of code > overhead, so this rather large gap in our capabilities hadn't been > apparent until now. > > -Edward > > > On Thu, Jun 13, 2013 at 8:36 AM, Edward Kmett <[email protected] > <mailto:[email protected]>> wrote: > > Gershom has taken the initiative to contact the folks who have root > and see how we can get people on the box. > > -Edward > > > On Thu, Jun 13, 2013 at 8:10 AM, Simon Peyton-Jones > <[email protected] <mailto:[email protected]>> wrote: > > This is serious.____ > > __ __ > > Haskell.org committee, this is your moment of glory -- the > moment for which the committee was born! Please rescue us from > deadlock. I’m begging you.____ > > __ __ > > Simon____ > > __ __ > > *From:*Edward Kmett [mailto:[email protected] > <mailto:[email protected]>] > *Sent:* 13 June 2013 13:07 > *To:* Simon Peyton-Jones > *Cc:* Ian Lynagh ([email protected] > <mailto:[email protected]>); [email protected] > <mailto:[email protected]>; > [email protected] > <mailto:[email protected]>; > [email protected] <mailto:[email protected]>; [email protected] > <mailto:[email protected]>; Amr Sabry; Edward Yang > *Subject:* Re: Haskell Community Server stuck____ > > __ __ > > My request for the core-libraries-committee alias / mailing list > to the haskell-infrastructure list also basically wound up stuck > in limbo as well.____ > > __ __ > > Who do we have currently on the committee who actually has > access to those boxes? I think the last person here who actively > accessed stuff was Ganesh.____ > > __ __ > > -Edward____ > > __ __ > > On Thu, Jun 13, 2013 at 4:56 AM, Simon Peyton-Jones > <[email protected] <mailto:[email protected]>> wrote:____ > > I've had no reply. Does this mean that *no-one* is > responsible for the Haskell Community server? > > Maybe the Haskell.org committee might appoint someone then? > > thanks > > Simon____ > > > | -----Original Message----- > | From: Simon Peyton-Jones > | Sent: 10 June 2013 13:37 > | To: Ian Lynagh ([email protected] > <mailto:[email protected]>); [email protected] > <mailto:[email protected]> > | Cc: [email protected] <mailto:[email protected]>; > [email protected] <mailto:[email protected]>; 'Amr > Sabry'; Edward Yang > | Subject: Haskell Community Server stuck > | > | Dear Ian, Haskell.org committee > | > | Who is responsible for the Haskell Community Server? > | > | I have two collaborators who need an account on it, and > have duly > | applied. But several weeks later nothing has happened. > | > | Could someone possibly unglue this? And how would one > find out who the > | person/responsible is? > | > | Thanks > | > | Simon > | > | | -----Original Message----- > | | From: Amr Sabry [mailto:[email protected] > <mailto:[email protected]>] > | | Sent: 10 June 2013 13:07 > | | To: Simon Peyton-Jones > | | Cc: [email protected] <mailto:[email protected]>; > [email protected] <mailto:[email protected]>; > [email protected] <mailto:[email protected]> > | | Subject: Re: State... > | | > | | Cameron had applied to a haskell account but as far as I > know hasn't > | | gotten one yet. Can one of you ping whoever is responsible? > | | > | | Meanwhile I see that both Simon and Cameron have pushed > new versions > | to > | | different repositories. (I am the only one who has > access to both.) > | Not > | | sure about the most efficient way to resolve things > especially since I > | | am on the road... > | | > | | --Amr____ > > __ __ > > > > > > _______________________________________________ > 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
