I would like samples (at least user-supplied one's) on this site. That would fit to the "love for real code" that lots of folks here seem to have (where "lots" is measured as a percentage, not absolutely...).

I have looked in CodeXchange just a few times within several years, as the samples were of no particular relevance to me, and as is is a somewhat "hidden" (or at least uncommon) resource.

As we all expect that SQLA 2.0 will get a broader audience (don't we?), samples would be fine here. If there's a need, then one could develop some kind of tagging system or template for such samples but I guess this is something time will tell (and should not be regulated just in the starting phase).

Can't tell if the iAnywhere-supplied samples/drivers and the like from CodeXchange should find their place here, too.

We use Domino at our site an IBM has installed product wikis where the post code samples.

We have used this one here for our Site

http://www-10.lotus.com/ldd/dominowiki.nsf/dx/Customizing_IBM_Lotus_Domino_V8.5.x_to_auto-zip_mail_attachments

Not only IBM emplyees can create sites but each registered user can start a page and post his work.

Just my 2 cents

The problem is that #1 "a mechanism for folks to post code that can be easily found and downloaded by other folks" is not a trivial undertaking either.

Although it looks simple on it's face, there are a number of underlying legal and customer service problems that come in to play. Solving those problems isn't "hard" but it does require a company like Sybase to think about the possible implications.

There are several things that made the checklist for any next generation file sharing site:

1. Code Licensing. This is the license we require for anyone with code on the site. In order to make this work well, the license has to be open and non-restrictive for the end users. (Fortunately, this is a question for the lawyers, not for the rest of us. But look at the discussions around GPL and other open-source licenses to see some of the inherent issues on this.)

2. Version control. Samples, like most code, have bugs. We need a method to allow changes to the original samples. Should we version those changes? And who can make changes to a sample once it is posted?

3. Viruses, trojan horses, and other nasties. Since the web site is owned by Sybase, there is a certain amount of liability Sybase picks up in hosting the code. Therefore, we need a mechanism to determine if the code is clean of any potential problems. (And some kind of notification system if someone else discovers a problem.)

4. Verification and worthiness. One question we got a lot was "does anyone check a sample" to determine if it is worthy of the site? That went back and forth a lot. One take is "let anyone post, the community will self police". The other was "Sybase has liability and responsibility, so we should do some checking ourselves".

5. Visibility. Sample writers put up samples not out of the goodness of their hearts, but to gain visibility and to create some marketing buzz around their name. Visibility is good for getting better jobs and better salaries. So how do we maximize the visibility of the author? And how do we recruit new authors? Most samples are crated by the company (Sybase) or by a very small pool of sample writers. How do we expand that field, and get some name recognition for anyone who joins the fray?

This isn't the entire list, just a view to a larger requirements gathering that was done around code samples and other contributions.

A great professor of mine once said "There is one very important thing to remember when designing software: The Wheel is Round." It was his way of saying "stop reinventing the wheel. Someone already has. Goodyear is already way ahead of you." Perhaps that advice will come in handy here too.