Thanks for getting this taken care of. I endorse the general notion of removing trac support from community.haskell.org. It doesn’t make much sense to me for us to keep it around at this point.
I did an inventory some time ago and it seemed only one or two projects at most were actually using the service still. There are now certainly many other better and better-maintained free alternatives (there certainly were not at the time this service was launched). In any case though, you’re right that someone will have to go through and sort out what we need to do before “pulling the plug” as you say. And we also may be able to do so in a staged way — i.e. only cutting off new ticket creation for the time being, so as to allow time to migrate data, etc. -g On August 27, 2014 at 8:42:24 AM, Yitzchak Gale ([email protected]) wrote: > Unless there is someone who can take on Trac maintenance > in a more serious way, I'm afraid we have no choice but > to shut down Trac service on c.h.o. > > Does anyone know how to figure out which projects are > still actually using Trac on c.h.o. and are not just spam > honey pots? Not too many, probably, but there may be a > few important ones. We would need to give them some > warning before pulling the plug. > > Thanks, > Yitz > _______________________________________________ > 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
