09:52:54 <HugoDaniel> hi
10:24:36 <HugoDaniel> whats up around here ?
14:29:29 <stepkut> HugoDaniel: i am hacking on the timeout code
14:47:50 <HugoDaniel> :D
14:47:52 <HugoDaniel> cool
14:48:24 <HugoDaniel> stepkut, what would you like me to hack ? i want to join the happstack dev team :)
14:49:58 <stepcut> sweet!
14:51:08 <stepcut> this looks easy to start with, http://code.google.com/p/happstack/issues/detail?id=138&q=milestone%3D6
14:52:30 <stepcut> I'll get back to you later, gotta get ready go out for a bit
14:52:53 <stepcut> the only real code change left for happstack 6 is fixing the timeout code
14:53:21 <stepcut> which is being moved out into separate (non-happstack) library
14:54:22 <stepcut> then we need to make sure that everything in happstack-server has good haddock documentation
14:55:36 <stepcut> http://code.google.com/p/happstack/issues/detail?id=25&q=milestone%3D6
14:56:52 <stepcut> once 6 is out, there will be more fun stuff to work on. 7 will focus a lot on happstack-state
15:09:34 <HugoDaniel> yes
15:09:35 <HugoDaniel> :D
15:09:41 <HugoDaniel> do you have a test suit ?
15:09:52 <stepcut> for ?
15:09:54 <HugoDaniel> i would be quite happy to work on a few unit tests
15:10:25 <HugoDaniel> well... for the functions in happstack, to ensure their functionality doesn't break when something changes and stuff like that
15:10:29 <stepcut> in each of the project directories (happstack-util, happstack-data, happstack-server, etc), there is a tests subdirectory
15:10:56 <HugoDaniel> ah cool
15:11:05 <stepcut> there is a make file in each tests sub-directory that you can run
15:11:37 <stepcut> it has two targets. One target tests against the installed version of happstack, and the other runs the tests against the local source directory
15:12:29 <stepcut> also, when you run the, bin/build-install-test-all.sh, script, all the tests are built and added to a single test-suite which runs all the tests for all the modules
15:13:01 <stepcut> in theory, due to cabal issues, we really ought to split the test suite into a separate library or set of libraries
15:13:14 <stepcut> but the current system mostly works ok
15:14:56 <stepcut> in happstack-server, there is at least one unit test that used to work but is now commented out. That is because the internals of happstack-server changed too much and the test didn't build anymore. That might be one place to start
15:20:11 <HugoDaniel> okey
15:22:17 <stepcut> but, the test suite is pretty weak at the moment, so there are plenty of opportunities to write tests -- so feel free to test whatever you want!
15:22:24 <stepcut> i am off now
15:22:35 <HugoDaniel> ttyl
15:35:13 <Entroacceptor> don't you know you're supposed to write the tests first...
15:35:15 <Entroacceptor> ts tsts
16:02:55 <HugoDaniel> maybe i can help out with that
16:03:20 <HugoDaniel> i end up using happstack quite a lot in my day to day work :/
16:03:27 <HugoDaniel> so its a way to contribute i guess
16:03:36 <HugoDaniel> still pulling the rep here...
16:25:25 <HugoDaniel> ok
16:25:26 <HugoDaniel> done
16:25:39 <HugoDaniel> im hacking my way through happstack-server/src/Happstack/Server/Response.hs
16:25:47 <HugoDaniel> to see if i can get that text instance done
18:12:42 <stepcut> nice
21:55:54 <stepcut> HugoDaniel: how Response.hs looking ?