|
| 1 | +--- |
| 2 | +collaborating_projects: |
| 3 | + - coala |
| 4 | + - GitMate |
| 5 | +desc: "Make sure that developers get notified about new issues that need their input: Use the tags of the new issue to find developers that have previously solved similar Issues." |
| 6 | +difficulty: high |
| 7 | +initiatives: |
| 8 | + - Research |
| 9 | +issues: [] |
| 10 | +markdown: assign_issues.md |
| 11 | +mentors: |
| 12 | + - fneu |
| 13 | + - sils |
| 14 | +name: "Tag-based Assignment of Developers to Issues" |
| 15 | +requirements: |
| 16 | + - "At least one patch to coala or GitMate should be accepted and merged." |
| 17 | + - "Familiarity with [IGitt](https://gitlab.com/gitmate/IGitt) is advised." |
| 18 | +tags: |
| 19 | + - Workflow |
| 20 | + - GitHub |
| 21 | +--- |
| 22 | + |
| 23 | +Issues are the primary way to organize developer tasks for projects on GitHub including coala. |
| 24 | +The progress of these projects oftentimes relies on the right developers being notified of |
| 25 | +new issues that fall into their territory of expertise. |
| 26 | +With the project growing, the number of incoming issues increases. Not all developers can continuously |
| 27 | +scan all incoming issues. It is therefore likely that developers miss issues that they could have |
| 28 | +great influence on with little investment. |
| 29 | + |
| 30 | +The goal of this project is to analyse incoming issues and evaluate the issue title, text, and tags to |
| 31 | +determine the developer(s) most likely to be familiar with the task or problem at hand. |
| 32 | + |
| 33 | +The scope of this project is aimed at a scientific research thesis. Therefore we would like to see a |
| 34 | +clearly determined and structured approach as to how the appropriate developers will be selected. |
| 35 | +Most appropriate would be a literature-backed approach that is implemented and verified throughout the |
| 36 | +execution of this project. |
| 37 | + |
| 38 | +#### Milestones |
| 39 | + |
| 40 | +##### PROPOSAL |
| 41 | + |
| 42 | +* A credible strategy for selecting developers is proposed |
| 43 | + |
| 44 | +##### EVALUATION |
| 45 | + |
| 46 | +* The data of previous developer activity has been collected and processed |
| 47 | +* A toolchain is in place to automatically collect and evaluate incoming issues |
| 48 | +* The proposed developer selection algorithm has been implemented |
| 49 | +* The developer selection done by the algorithm has been verified or refuted |
0 commit comments