akari.tlug.jprepo? (Or everything that reasonably belongs there. That includes config files related to any web services.) This will ensure a reasonably large group of responsible people have access to this information.
From the tlug/tlug.jp@8d857a7:
TLUG.Hello and its test are simple tests originally added to demonsrate [sic] that the test framework actually works. It's an open question as to whether these are actually still needed, but they do serve as a handy, simple example and as something to tweak when playing around with Haskell.
I'm open to ways to clarify this, which maybe even we should add as a comment to the files.
I'm surprised it was slowing you down; is something wrong with the build that the dependency check (followed by not recompiling it) was slow? Or was that just a random change that you hoped would optimize things but didn't? :-)
TLUG.Hellois to keep it because I think it makes a good place to start for non-Haskell developers wanting to start playing with our code here. But I'm open to counterarguments. I don't think that compilation speed is one, though, because it's a pretty small fraction of an initial compile and nearly infitesimal in subsequent compiles when it's not modified.
KCinJPAnyone going to the オープンソースカンファレンス on the 21st (Fri) & 22nd (Sat) of this month?