code

https://github.com/MalloZup/foresinc

description

Starting on big/medium/small codebases used at SUSE/opensuse projects, i will analyze big codebases with scientific methods/ tools and data. ( not by intuition or feeling )

If you want to learn more you can have a look at the book "Your Code as a Crime Scene" by Adam Tornhill. ( i will use his great suggestions)

As first step we want to find out the hotspot of a large codebase and analyze the weakness of them, visualize the hotspots and try to fix them.

Repositories to be analyzed:

• https://github.com/kubic-project/velum
• https://github.com/openSUSE/trollolo
• https://github.com/SUSE/spacewalk/wiki
• https://github.com/dmacvicar/terraform-provider-libvirt
• https://github.com/saltstack/salt
• https://github.com/SUSE/cloudfoundry
• https://github.com/ceph/ceph
• https://github.com/SUSE/hackweek

I will post some results of my crime scenes