Hi Nadya,

Hmmm.....

I would think the original author should be informed of any changes as a courtesy and then make the call as to how an update is posted. For example, I have fielded many, many changes and enhancements to FRX2Word. I have "approved" very few but have never specifically denied that an update be posted.

Simply put, original authors don't necessarily have the time to check revisions and sometimes, the follow up author "breaks" the original code.

>I was thinking about Files section here and these are my thoughts:
>Suppose somebody downloaded a file from here, when found few little bugs and improved the code. What should follow:
> 1) He/she should send this update to the owner of the file for review + memo describing his/her changes
> 2) The author checks and verifies the changes made
> 3) The author changes Readme file and description of this entry and posts a new version (adds his/her grattitude to the colleague)
>
> In this case we would not have too many entries and the files here would be always in good shape.
>
> What do you think?