Important Notice

There was a recent change to Fossil that requires you to get the latest binary for your platform. If you want to build fossil from source, use that binary to resync your fossil source repo and then rebuild and you'll be set. You can read the mailing list post about it for more information.

Welcome to the support site for the Lamson Project. Here is where you can submit tickets for bugs that you've found, write and read third party wiki docs, and get the latest lamson source code.

If you would like to get the source to Lamson, you can either do:

1. Click on Timeline in the menu above.
2. Click on the most recent leaf you want.
3. Click on the ZIP archive link for the leaf and download it.

Or, you may optionally install Fossil and access it the way you would any other RCS (like git, hg, svn, bzr):

1. Get the fossil binary for your platform. Fossil supports Linux, Windows, and OSX and builds on anything really.
2. Copy the binary to /usr/local/bin or similar.
3. mkdir ~/fossils
4. fossil clone http://support.lamsonproject.org/ ~/fossils/lamson.fossil
5. mkdir -p ~/projects/lamson
6. cd ~/projects/lamson
7. fossil open ~/fossils/lamson.fossil

After that you'll have a complete fossil install, and you will be able to sync the source, tickets, and wiki in a distributed fashion.

Contributing

If you get fossil working and want to contribute some patches, then you'll want to first read up on the fossil docs:

• Quick Start
• Fossil Concepts
• Branching, Forking, Merging

After that, you'll want to do the following to get started on making local changes:

1. One time only, turn off autosync: fossil settings autosync off
2. Make your changes. Use fossil ui to also edit wiki locally, change tickets, etc.
3. Use fossil commit -m "summary" to commit locally.
4. Make sure you fossil up periodically to stay in sync.
5. Use fossil server to serve your repository and then contact a project developer to pull changes from you. We hang on #lamson@irc.freenode.org and lamson@librelist.com.

And remember that since fossil stores the repository in a .fossil file, you can serve easily off a remote server of your choice by just rsyncing the .fossil file to that host, and doing fossil serve from there. No special access or protocols are needed either, it's all HTTP.

If this is too much work, you can also just do fossil diff and mail that to zedshaw@zedshaw.com.

Becoming A Contributor

If you submit enough patches, we'll become annoyed and just give you commit rights. No special ceremony or anything. At this point you'll need to turn fossil settings autosync on to make sure you avoid forking when you commit.