Something we should look into in this process: The Haskell Platform does still seem to be leaning on c.h.o quite a bit.
The issue tracker has completed its migration to GitHub (and the trac ticket system on c.h.o. is now starting to accumulate spam). However, many of the most obvious links out there, as well as many obvious Google searches, lead to pages on the trac instance on c.h.o. And the mailing list hosted on c.h.o. does still seem to be active. HP is a pretty important project, so let's keep them in mind. If we are discontinuing services that they need, we should help them migrate and make sure not to pull the plug too early. Thanks, Yitz On Thu, Apr 10, 2014 at 5:24 PM, Yitzchak Gale <[email protected]> wrote: > Gershom wrote: >> I wanted to pose some choices for the future of community.haskell.org > > As someone who did a lot of the support work on c.h.o > in the past, I can say that this is good view of the situation > and a good approach towards moving forward. > > One advantage of offering services via c.h.o is that > it allows anyone active in the community to use > the haskell.org domain name for their project. > I think that contributes both to the feeling of > community, and to the feeling of importance to > those who contribute. Continuing web hosting > allows that to continue, which is nice if we can manage > that. > > Are you sure that none of the mailman mailing lists > on c.h.o are active anymore? Is there a good alternative? > The haskell.org domain is actually quite valuable > for that as well. > > On the other hand, supporting any public facing > service involves a lot more effort nowadays than it > used to due to various security issues. That trend > will likely continue. So whatever we decide to > continue to provide, we need to be realistic about > the human resources we will need in the long term > to sustain it. > > Another point: if we provide any service at all, > we also need to provide a way for people to contact > us for technical support. The RT ticket system on > c.h.o has become nearly unusable due to incessant > spamming. There are a number of alternatives: > we could just use Haskell Cafe, but that would > require making sure that there is always someone > who can respond monitoring the list. > > The RT system is also used as part of the mechanism > to request, vet, and grant new accounts. We may > want to revamp that system. > > Thanks, > Yitz _______________________________________________ haskell-infrastructure mailing list [email protected] http://community.galois.com/mailman/listinfo/haskell-infrastructure
