Mark Culp asked this question, verbatim, in his comment...
Maybe I am missing something.
Apart from attaching files, are we not already sharing code on this site? When someone posts a question, they post the code that causes the issue, even to the point of how to create the data to reproduce the issue. When people answer with suggestions, those are often in the form of code to try.
If we are talking about samples, those could (and have been) easily be posted as "How would you do xyz" with an immediate answer below. Posting the code verbatim with comments instead of as a file should weed out most of the "nasties." If you use the code and like it you would vote for it just like you do now asserting both the codes worthiness and improving the author's visibility. The author and anyone with high enough reputation would be able to edit the original for version control, as a result of suggestions from the comments.
As far as the licensing I would continue with the stamp "Nothing is guaranteed."
answered 08 Nov '10, 02:26
CodeXchange addressed two needs:
Number 2 is a mammoth undertaking, and the need is satisfied by any number of existing websites. It is of zero interest to me, personally, so I will leave that for others to discuss.
Number 1 is what I want, both as writer and especially as reader of Other People's Code. I have not seen SQLA 2.0 so I don't know whether the attachment mechanism is any good, but in theory it is the perfect solution: Folks can post code, explain it, discuss it, revise it and so on.
CodeXchange was recognized by some (well, by me) as a colossal failure from the day it was introduced. I did not see it before that (another colossal mistake IMO, not showing it to people who might actually use it), but I was shrill in my condemnation as soon as I got my hands on it. As far as I can tell, not one single "Number 2" cooperative project was ever undertaken, while at the same time the monumental bureaucracy it established to support Number 2 made it virtually useless for Number 1 (posting, and especially finding, code).
The folks who picked the software for CodeXchange got it wrong, and the folks who approved the project got it wrong. I'm hoping the same folks have no part in SQLA 2.0.
"But we have to pass the bill so you can find out what is in it, away from the fog of the controversy." http://www.brainyquote.com/quotes/quotes/n/nancypelos411981.html
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.
answered 07 Nov '10, 21:18
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
Not only IBM emplyees can create sites but each registered user can start a page and post his work.
Just my 2 cents
answered 08 Nov '10, 09:29
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:
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.
answered 08 Nov '10, 00:04