-
Notifications
You must be signed in to change notification settings - Fork 4
/
gsoc2014-ideas.html
86 lines (75 loc) · 6.95 KB
/
gsoc2014-ideas.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<title>Metrics Grimoire by MetricsGrimoire</title>
<link rel="stylesheet" href="stylesheets/styles.css">
<link rel="stylesheet" href="stylesheets/pygment_trac.css">
<script src="javascripts/scale.fix.js"></script>
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<div class="wrapper">
<header>
<h1 class="header">Metrics Grimoire</h1>
<p class="header">Tools for software & development community analytics</p>
<ul>
<li><a class="buttons github" href="https://github.com/MetricsGrimoire">@ GitHub</a></li>
</ul>
</header>
<section>
<h1>Google Summer of Code 2014</h1>
<h2>Introduction to Metrics Grimoire</h2>
<p>Metrics Grimoire is a toolset to assist developers and researchers to understand better the software practices in their projects. Metrics Grimoire can collect, prepare and create reports from different data sources, such as version control systems, issue tracking systems, mailing lists, wiki pages, IRC logs. Metrics Grimoire consists in different specialized tools for each kind of data source, to collect data and metadata, store them in databases for further data mining, and to visualize them on the web.</p>
<p>Metrics Grimoire supports multiples flavours of each kind of data source. For example, it supports multiple types of issue trackers (Allura, Bugzilla, Gerrit, GitHub, GoogleCode, Jira, Launchpad, RedMine, and SourceForge), multiple types of version control systems (Bazaar, CVS, Git, Subversion, and Tarballs). Thus, Metrics Grimoire allows consolidation of data to be analyzed altogether.
<p>Metrics Grimoire started as a toolset named LibreSoft tools, developed originally by the <a href="http://libresoft.es">Libresoft Research Group</a> at <a href="http://www.urjc.es">Universidad Rey Juan Carlos</a>. After several years of development, a small community started to grow around it, now including developers and users from all around the world. Later, a spin-off company of the research group was founded, <a href="http://bitergia.com">Bitergia</a>, providing professional services around those tools. In parallel to this proces, LibreSoft Tools evolved into a more neutral, community-oriented project: Metrics Grimoire.</p>
<h2>Potential Projects to be developed</h2>
<ul>
<li><strong>CVSAnalY</strong>: Add support for license detection using Ninka (mentor: <a href="http://sanacl.wordpress.com/">Luis Cañas</a>)
<ul>
<li><em>Benefits</em>: Aggregates the analysis of version control systems with the license present in every file to get a better overview of the projects.</li>
<li><em>Requirements</em>: Knowledge in Python and Perl.</li>
<li><em>Notes</em>: Ninka is a powerful tool to analyze the license of each of the files of the product. The integration of Ninka as an extension of CVSAnalY will produce a tool able to analyze per file and revision a complete insight of the license state of any project.</li>
</ul>
</li>
<li><strong>Bicho, CVSAnalY, MailingListStats</strong>: Port to SQLAlchemy (mentor: <a href="http://blog.dizquierdo.es/">Daniel Izquierdo</a>)
<ul>
<li><em>Benefits</em>: Improves the maintenance of these tools in the long term.</li>
<li><em>Requirements</em>: Knowledge in Python (knowledge in SQLAlchemy is a plus)</li>
<li><em>Notes</em>: Each project was developed independently. Although they have a similar structure and can share the data models, those are currently handled in different ways. The work consists in to facilitate future contributions to the project by making the data manipulation consistent across applications, and make easier to build new tools on top of them.</li>
</ul>
</li>
<li><strong>Bicho</strong>: Improve backends to use web APIs whenever is possible (mentor: <a href="http://blog.dizquierdo.es/">Daniel Izquierdo</a>)
<ul>
<li><em>Benefits</em>: Improves long-tern maintainability of issue tracker support.</li>
<li><em>Requirements</em>: Knowledge in Python (knowledge in web services is a plus)</li>
<li><em>Notes</em>: Currently, most backends parse HTML from the issue trackers. These method is useful when the issue trackers did not support access via web API or when they were disabled. These days, it is more common to find them enabled. This work consists in adding support for web API to every backend, and leaving as fallback scrapping the web pages. This should be part of several bugs to fix. See <a href="https://github.com/MetricsGrimoire/Bicho/issues">Bicho's issues</a> to get more ideas.</li>
</ul>
</li>
<li><strong>MailingListStats</strong>: Add support for social network analysis (mentor: <a href="http://calcifer.org/">Germán Poo-Caamaño</a>)
<ul>
<li><em>Benefits</em>: Increase the analytic of interactions in mailing lists to detect different communication patterns.</li>
<li><em>Requirements</em>: Knowledge in Python (knowledge in social network analysis is a plus)</li>
<li><em>Notes</em>: Your work will consist in to aggregate the interactions in mailing lists, determine different metrics from social network analysis, and create automatic reports from as well as a guide to further development. You will need to identify multiple identities of individuals, timing, etc. and combine with other activities happening at similar period of time (for example, to determine actions triggered by discussions, or viceversa). This should be part of other tasks, like extending this work to aggregate multiple identities from the other tools (Bicho, CVSAnalY).</li>
</ul>
</li>
</ul>
<h2>Contact</h2>
<ul>
<li>IRC channel: we usually hang out at <a href="irc://irc.freenode.net/metrics-grimoire">#metrics-grimoire</a> in <a href="http://freenode.net/">freenode</a> (<a href="http://webchat.freenode.net/?nick=webchat..&channels=metrics-grimoire&prompt=1">access via webchat</a>)</li>
<li>Mailing list: <a href="https://lists.libresoft.es/listinfo/metrics-grimoire">metrics-grimoire</a> at lists.libresoft.es, for developers, contributors and users (<a href="https://lists.libresoft.es/pipermail/metrics-grimoire/">archives are available</a>)</li>
<li>Source code: available in several git repositories at the <a href="https://github.com/metricsgrimoire">MetricsGrimoire GitHub project</a></li>
<li>Submitting bug reports: we use the GitHub issue tracking system ("Issues" tab in each of the repositories of the <a href="https://github.com/metricsgrimoire">MetricsGrimoire GitHub project</a></li>
</ul>
</section>
<footer>
<p><small>Hosted on <a href="https://pages.github.com">GitHub Pages</a> using the Dinky theme</small></p>
</footer>
</div>
<!--[if !IE]><script>fixScale(document);</script><![endif]-->
</body>
</html>