you can post it in the programming forum: http://opengameart.org/forums/programming-0 or submit it as a document. screenshots of it in action will probably be very helpful in drawing the eyes of the 'right people' regardless of which place you post.

Also: creating a code section would go against the grain of OGA quite a bit and could have a negative impact on search. See also this similar discussion.

I would support to introduce a code section

i have posted my code here befor 

http://opengameart.org/content/bitmap-font-maker

but a code or program section would be nice

Sorry for bumping this thread, but I just remembered a couple trio of relevant points:

1. My games often rely on vector art, either partially or completely. In fact, my latest submission is made of hand-crafted SVG files ported directly from HTML5 canvas code.
2. I recently devised a simple turtle graphics system in one BASIC function, that can be used to generate complex repeating patterns based on a short command string.
3. Some of the most popular products on itch.io are apps for procedurally generating and/or manipulating tile art.

Code can be the artwork. A dedicated section here would make a lot of sense.

Put the code on GitHub and include a link to it on the thread of your project/the art being used.

They can already be uploaded (as in PreciousRoy's example).

I'm not sure that having a separate section for code would anything - if the code is generating a particular type of art, then I'd say it's better to put it in the section for that kind of art (2D, 3D, whatever). Lumping them all in a code section takes away that categorisation. If someone is looking for code specifically, that can be handled with the tag "code".

If we're talking about more general code/tools, then I'd agree with the Github suggestion - more generally, there are lots of places that are dedicated to hosting code, and do it much better. For example, it's not even possible to browse the code online for code uploaded to OGA. Also the available set of licences isn't very well suited to code. So I'd be wary of doing more to encourage OGA as a code hosting site without those improvements.

I'd forgotten about the licensing angle. Good point. Very well, GitHub it is then.