Hi Chris

I think a lot of folks in UT want to share code as we can see from the download area. But lots of code does not appear because folks feel they have to maintain their reputation.

A lot of the heavy hitters are quite sensitive in this area. I am sure they have lots of code that is 90% good but they dont upload it because they are too busy to fix the other 10%. So they just use it themselves or abandon it because they now use a different technique.

If we gave them a way of posting a contribution they could just delete their names out and write a brief note about the drawbacks of the code. We may spot someones style <g> but could never point the finger:)

I have seen some threads where folks who have written great code get some insulting posts from people who just expect too much from the code. If there was some mechanism to spare them that I am sure they would leap at it.




>I think it is a great idea in theory. But how strong is the want of people to add to such a 'dump' of code.
>I know that contractually I would not be allowed to add code to a public domain. Even if it is a little generic function, every thing I write is the property of my employer, and I dare say there are a lot of people in the same boat.
>I would love however to trawl around through some other peoples code.
>
>
>>>It is perfectly ok, that sometimes, a file uploaded in the Downloads section may contain a requirement for a fix. Thus, in that case, the author is contacted and a fix is then expected.
>>
>>This is the problem though:( Folks dont upload their code because of the support burden that then falls on them and the hassle they get in the threads if it has a bug in it.
>>
>>However I understand that you may not want the UT name associated in this way.
>>Maybe you could provide a link to such a code dump on another VFP site so as to distance UT.
>>
>>
>>
>>>>Many folks have written nice functions which they think are too trivial
>>>>to post in the UT downloads section.
>>>>
>>>>Another reason code is not posted is because we set quite good standards for code in UT and no one wants to face the embarrassment that could occur if their code does does not meet those standards in all respects.
>>>>
>>>>This is a shame, because with .Net posing another challange for us to meet, we should all be helping each other as much as possible.
>>>>
>>>>I propose a free for all dumping ground for code. This area would be completely unatributable and people would use code found there at their own risk.
>>>>
>>>>I call it a code dump instead of a procedure library to make make this distinction clear.
>>>>
>>>>I would love to rummage through this 'code dump'. If I could not understand the code I would not use it. I am confident enough in my own abilities to decide if code could be harmful or not.
>>>>
>>>>Who knows what lies ahead in the future. Lets all help each other and prove that VFP is the best programming environment on the market.
>>>
>>>It is perfectly ok, that sometimes, a file uploaded in the Downloads section may contain a requirement for a fix. Thus, in that case, the author is contacted and a fix is then expected.
>>>
>>>We can't release a dedicated content for such a need. This would lower the image of the UT and the community here. We have minimum standards that we try to apply on each item and that is part of our image.
>>>
>>>If you have some piece of code that you would like to share, don't hesitate to submit it. It'll be our pleasure to make it appears in the proper content. And, as I said, it's perfectly ok that revisions are needed after. We've seen that for several entries so far which have been uploaded such as fixing some piece of code, providing new versions, enhanced with new options and from the feedback requested by the community.