Oleg,
I'm interested in learning about the embedding of sample code in project comments, etc. What you described above sounds very efficient and would help the test effort.
I've barely touched the source code so far, but I'm looking at the SynchronizeDirectories feature today. How would I find the developer who contributed that? Say, if I had questions or wanted to generate documentation on it, or even contribute a change to it?!
For example, I did some testing and got unexpected results. I tracked it to a region of the source code "upload the difference" which has this comment:
// TODO: Use md5 to detect a difference
//ltang: File exists at the destination => Using filesize to detect the differenceWhich in my use case makes it less useful.
I guess if I were documenting this function, I'd include a note about that.
I'm really new to Codeplex and I imagine there is some way to hunt this up in a project fork and learn who the developer is. I'll investigate a little more today. (Oh, I get it. I have to be a member of the project to use TFS, or I have to use Subversion) I'm more familiar with TFS.
I did try to use the online changeset history and look for it that way. But all of the 375 commits are owned by you and I did find 1 SynchronizeDirectories, #22075, which is a refactoring. But I'm not sure why the web-based diff tool does not present the code changes very well. http://sshnet.codeplex.com/SourceControl/changeset/22075. Maybe what I'm seeing here is that the function is added to Silverlight but already existing in the sftp.client.net?
Obviously I have a lot to learn, but this may get me to put a project up on Codeplex myself. Then I'll learn faster.
Speaking of that, I wonder how good Codeplex is about linking together 'parent-children' projects. If I use ssh.net in my project, I'll be sure to mention that.
Oh, I found one way to see if projects are connected. If another project's coordinator is following your project, it may because he is using your project. For instance, dbsend is using ssh.net but I only discovered it by looking at the author because he was following ssh.net.