You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of my PhD research on code authorship, we calculated the Truck Factor (TF) of some popular GitHub repositories.
As you probably know, the Truck (or Bus) Factor designates the minimal number of developers that have to be hit by a truck (or quit) before a project is incapacitated. In our work, we consider that a system is in trouble if more than 50% of its files become orphan (i.e., without a main author).
Coda was the author of the majority of the code. He left the project around a year ago. I had noticed some issues were going a long time without resolution, at which point I offered to maintain the project. Currently, I am the main developer. If I hadn't, I believe that other people who wrote modules would have stepped in and maintained it.
As part of my PhD research on code authorship, we calculated the Truck Factor (TF) of some popular GitHub repositories.
As you probably know, the Truck (or Bus) Factor designates the minimal number of developers that have to be hit by a truck (or quit) before a project is incapacitated. In our work, we consider that a system is in trouble if more than 50% of its files become orphan (i.e., without a main author).
More details on our work in this preprint: https://peerj.com/preprints/1233
We calculated the TF for Metrics and obtained a value of 1.
The developer responsible for this TF is:
Coda Hale - author of 77% of the files
To validate our results, we would like to ask Metrics developers the following three brief questions:
(a) Do you agree that the listed developer is the main developer of Metrics?
(b) Do you agree that Metrics will be in trouble if the listed developer leave the project (e.g., if he wins in the lottery, to be less morbid)?
(c) Does Metrics have some characteristics that would attenuate the loss of the listed developer (e.g., detailed documentation)?
Thanks in advance for your collaboration,
Guilherme Avelino
PhD Student
Applied Software Engineering Group (ASERG)
UFMG, Brazil
http://aserg.labsoft.dcc.ufmg.br/
The text was updated successfully, but these errors were encountered: