dev/Sorting/Thoughts

Journal of development Sorting Thoughts and more…

Communicate code changes – But how?

Posted on May 17, 2008 in KM, Programming, Tools

What is the best way to communicate source code changes? Write a mail, send an instant message or hope the next cvs sync will inform all your co-worker? Vincent Massol suggests two solutions: “Diff emails on SCM commit” and “RSS feeds”. This solutions are good ideas for small projects, but with a lots of changes (important and unimportant) this doesn’t work.

I think the best way to communicate important source code changes is a project team Wiki with the ability to create source code links. This links should have two possible targets. When you click on a source code link in a standard browser, you will directed to the source code in a WebCVS view and a click in the Eclipse embedded web browser will open the source code.

If you use SnipSnap as project wiki tool, you can install my IDE Wiki Plugin for Eclipse to use source code links:

ide wiki

Links

Screenshot wiki editor

1 Comment

  1. Hi Hendrik,

    as a user of snipsnap I like seeing that you chose this wiki as part of your project.

    What is your opinion on the development of core snipsnap? Would you take part in the development at the sf project?

    Kind regards,
    Michael

Submit a Comment

Your email address will not be published. Required fields are marked *

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close