Blog Entries

May 2019
M T W T F S S
« May    
 12345
6789101112
13141516171819
20212223242526
2728293031  

Visualising KDE PIM and PIMLIBS in March 2010

Here are the visualisations of KDE PIM and KDE PIMLIBS for March 2010. Next month I will be expanding the suite of scripts that I run against trunk to include the visualisation which exposes if a project is too dependent on one contributor. I will also have the automated commit digesting finished in the next month or so.

For now, ask yourself “What happened in KDE PIM at the end of the month?” and then wait for an informed reply from tmcquire. If you asked for visualisations of specific modules to be sent to you, they will be on their way today.

Enjoy!

WhoWhat

  • KDE PIM
  • KDE PIMLIBS

Plots

  • KDE PIM
  • KDE PIMLIBS

Network

  • KDE PIM
  • KDE PIMLIBS
Be Sociable, Share!

3 comments to Visualising KDE PIM and PIMLIBS in March 2010

  • Tom Albers

    Can you remove my name from the output. Since you have not published any of your scripts, the output can’t be verified. I object to the assumptions you are making based on your script without being able to verify how you came to those conclusions. So please remove my name from any output please.

    • Paul Adams

      > Can you remove my name from the output.

      In future images I can obfuscate your name, yes. Although it will be obvious you are you as yours will be the only obfuscated SVN account name. Don’t forget all I’m doing is processing public data.

      > Since you have not published any of your scripts, the output can’t be verified.

      Agreed. Scripts will be published in KDE SVN in the very near future.

      > I object to the assumptions you are making based on your script without being able to verify how you came to those conclusions.

      These scripts purely visualise data you are leaving behind when you commit to SVN. There is no analysis taking place. So, no assumptions and no conclusions. Just pretty pictures.

  • Tom Albers

    Thanks for removing me. I’m sure you will find a better way than obfuscating.