The Mercury Project
Contributed Programs and Libraries
Developer DocumentationThere is some developer documentation at the Mercury developer information page.
Mercury Libraries and ProgramsIf you've written some code using Mercury we'd love to find out about it. If you think it might be in any way useful to other people, you might be interested in making your code available for download. That way others can learn from it, use it and improve on it.
We are happy to place it on the Mercury web and ftp sites for you. Fame and fortune will surely follow.
If you would like to contribute a library or program written using Mercury for others to download and use, here's how you can do it.
Modifications to the Mercury SystemIf you've modified something in the Mercury system and would like it to become part of the main distribution, we'd be very interested in your work.
The mercury-developers mailing list is intended for discussing proposed changes to the Mercury system. If you would like to contribute reasonably frequently it might be a good idea to subscribe, or at least browse the archives of this list, simply to get an idea of the kinds of standards required for integrating code into the main distribution. You can also email email@example.com and discuss it with the Mercury team.
There is an issue with copyright ownership in the Mercury system. We'd like to retain the freedom to modify the license of the Mercury system in future releases (in particular, we may decide to dual-license the Mercury system so as to make it compatible with other open source licenses out there). Doing this with hundreds of copyright holders is practically impossible, since you need the agreement of every single one of them to make changes.
Under the current license you are free to make any modifications you like and distribute them. However we ask that if you want your modifications to be merged back into the main line of development, you talk to us about this issue. The easiest solution is to place your changes into the public domain (e.g. give up copyright ownership on them) and then we can merge them into the main compiler. This is a nice simple mechanism for getting around the hundreds of authors problem. If you have an employer who has some control over your copyright, we have some standard documents for doing this kind of thing. It is almost always preferable to ask an employer to sign a form than to try to explain the concept (possibly confusing or scaring them in the process). Please email firstname.lastname@example.org if you want to discuss contributing changes to the Mercury system.