Demo Data from VLDB 2026 / reviewers in the wild / expert
Christopher Wiley
dblp:121/2689
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2012
—ORCID · unresolved
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › forking
cross-system porting |
0.1 | 1 | 2012 | REPERTOIRE: a cross-system porting analysis tool for forked software projects · SIGSOFT FSE 2012 |
Software maintenance and evolution › forking
forked project maintenance |
0.1 | 1 | 2012 | REPERTOIRE: a cross-system porting analysis tool for forked software projects · SIGSOFT FSE 2012 |
Software maintenance and evolution
forking |
0.1 | 1 | 2012 | REPERTOIRE: a cross-system porting analysis tool for forked software projects · SIGSOFT FSE 2012 |
Methods — techniques the papers use, named apart from their topics
version history analysis · 0.1patch comparison · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2012 | REPERTOIRE: a cross-system porting analysis tool for forked software projectsabstractTo create a new variant of an existing project, developers often copy an existing codebase and modify it. This process is called software forking. After forking software, developers often port new features or bug fixes from peer projects. Repertoire analyzes repeated work of cross-system porting among forked projects. It takes the version histories as input and identifies ported edits by comparing the content of individual patches. It also shows users the extent of ported edits, where and when the ported edits occurred, which developers ported code from peer projects, and how long it takes for patches to be ported. Baishakhi Ray, Christopher Wiley, Miryung Kim |
SIGSOFT FSE | 2 |