There are many ways in which you can contribute to the MCONV project.
Most of them involve
- Let me know that you have tried it
Simply letting me know that you have downloaded the source code and tried
to compile the contents, whether successfully or not, is very helpful -
often it shows up subtle bugs that I wouldn't normally notice. It also
means I get the impression that people might be actually using my code,
which is an impetus to further development...
- Success reports
Obviously it is nice to hear of successful use, eg a BBS set up
somewhere using the MCONV code. It also means you have a point of
contact to send suggestions to from your users, bug reports, and so on.
- Bug reports
If something goes wrong or doesn't do what you expect it to, please let me
know - after all, I can't fix problems I don't know exist!
Those of you who have the time and the inclination, feel free to email patch
files to me if you've fixed a bug yourself. If you do so, be sure to mention
which version you are patching against. Context diffs preferred; mail me first
then I can let you know where to send the patch.
- Become an MCONV developer
If you really feel like helping out, make yourself a
SourceForge developer account and
email me your username. I can then add you to the MCONV developer list,
which means you will get full read/write access to the
I don't mind if you don't actually do anything with this access, really,
it's the thought that counts ;-)
So, send any flames, praise, suggestions, bug reports, patch files, developer
access requests, or whatever to me via the