Asmutils would never become what they are without submissions from various hackers. As any open project, it relies much on contributions. Hence, if you've got an intention/inspiration to contribute something, you're more than welcome!
So, if you are the person who follows the challenge of UNIX assembly programming and wants your code to be included into asmutils, do examine this section carefully. It contains extremely important information, your contribution may not be accepted if you ignore suggestions below.
Although I think most of what is said in this section is evident to experienced developers of distributed free software, there might be brand new developers from proprietary software world, unaware of common contribution practice; if you are the one, read with double attention.
Before you begin make sure you are using the latest version of asmutils, I can reject contributions based on old versions.
So, get the latest version of asmutils and look what is already done.
Even if the program you want to contribute is not there, look at
ChangeLog, or
CVS cvs.linuxassembly.org:/pub/asm/asmutils
(using ssh and pserver),
or contact maintainer first, may be somebody is already doing (or has done)
what you're only going to do (ditto if you want to improve existing utils).
This is very important! Asmutils are growing rapidly,
do not duplicate effort of other hackers.
Here are few obvious requirements for the source code:
Note: I can accept utilities written in GAS, but this will just give me more boring work of converting them to NASM syntax and asmutils macro set. This is to be avoided when possible. I mean, do it on your own :)
While writing your program take care of portability! Basically, this means:
I think you've got an idea. Just try to imagine your program on other OS, and ask yourself: what one will need to do make it run? what should I do to make compile on as many OSes as possible? Even your program is OS specific (f.e. lsmod), at least try to make it readable.
I reject submissions eliminating these simple rules.
And of course, your code must do something useful, not just be written according to the above requirements :). Usual UNIX utils are preferred, but you can also contribute your very own program. Keep in mind that asmutils are not just fun. They are used in (and targeted on) small distributions and embedded systems. Thus, they should be as small as possible, use very few memory, and be fast as kernel. Neither more, nor less :)
When, finally, you think your program is ready, here again comes administrativia.
First, try to test your program. If it still works, rest a day, then look at it again.. I mean, I know you're very excited that your program works, but just try to look what now you can improve; do not send maintainer a new version every day, this will save him (and you) from the mess of versions.
New programs should be sent to project maintainer, while improvements of existing -- to particular util maintainer first.
Since asmutils programs are usually quite small, please send full source of program instead of patches when possible.
Sometimes maintainer (or I) will modify your code a bit. Please use that modified code for next program version.
Simple, huh? :)
With any additional questions refer to the asmutils webpage or contact asmutils maintainer.