-
A lot of projects use mailing lists as their development methodology, eg.
Linux.
-
Each has its quirks. In essence, patches go through a process of review.
Multiple revisions submitted to the mailing list. Ultimately they are
accepted and applied to the repository or ignored.
-
This process is scalable. Accessible to everyone.
-
How do we analyse this somewhat crude method.
What?
-
Tool for detecting similar patches.(forms patch groups)
-
Can map patches in mailing lists to commits in repositories.
-
Can keep track of multiple revisions of a patch.
How?
-
Analysis using various heuristics.
-
Blackbox (need to study more about this.)
Why?
-
Security applications for open source projects using mailing lists for their
workflow.
-