public
Description: A Haskell web application server.
Homepage:
Clone URL: git://github.com/tibbe/hyena.git
hyena /
name age message
file .gitignore Sun Sep 14 12:00:29 -0700 2008 Added a .gitignore. [tibbe]
directory Data/ Wed Jun 24 12:06:08 -0700 2009 Enumerate ByteString in chunks. [syg]
directory Hyena/ Wed Jun 24 12:06:23 -0700 2009 Fixed infinite loop for keep-alive sockets. [syg]
file LICENSE Wed Mar 19 12:05:13 -0700 2008 Added a README and LICENSE. [tibbe]
directory Network/ Sat Jan 17 22:16:28 -0800 2009 update to work with base 4, extensible-exceptio... [thoughtpolice]
file README.markdown Wed Jun 24 12:30:13 -0700 2009 Renamed the README to indicate content [tibbe]
file STYLE Thu Jan 22 06:13:40 -0800 2009 Added a coding style guide. [tibbe]
file Setup.hs Tue May 13 13:06:17 -0700 2008 Added a build system. [tibbe]
file TODO Mon Sep 15 14:48:39 -0700 2008 Added a TODO. [tibbe]
file hyena.cabal Wed Jun 24 12:59:17 -0700 2009 Added a link to the git repo [tibbe]
README.markdown

Hyena

Hyena is a simple web application container that can be used to run Haskell web applications behind more robust web servers like Apache.

Contributing

Prerequisites

Make sure you read the Haskell Style Guide.

The existing code doesn't follow the style guide fully but you should follow it for all new code.

Creating patches

The preferred way of contributing changes to the project is to use Git and send the patches over email using the Git commands format-patch and send-email. Step by step instructions:

Clone the repository:

git clone http://github.com/tibbe/hyena

Make your changes:

cd hyena
$EDITOR <file>

Commit your changes in one or more commits:

git add <file>
git commit

Make sure you write a good commit message. Commit messages should contain a short summary on a separate line and, if needed, a more thorough explanation of the change. Write full sentences and use proper spelling, punctuation, and grammar. See A Note About Git Commit Messages for more information.

You might want to use git rebase to make sure your commits correspond to nice, logical commits. Make sure whitespace only changes are kept in separate commits to ease reviewing.

Prepare the e.g. last five patches for sending:

git format-patch -5 -n

This will create one patch file per patch.

git send-email --to <maintainer> <patch files>

The maintainer is specified in the Cabal file. The maintainer will review your changes and may ask you to make changes to them. Make the changes to your local repository and use git rebase to massage them into nice, logical commits and resend the patches.