Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mailpile Truck Factor #1369

Closed
gavelino opened this issue Aug 6, 2015 · 3 comments
Closed

Mailpile Truck Factor #1369

gavelino opened this issue Aug 6, 2015 · 3 comments

Comments

@gavelino
Copy link

gavelino commented Aug 6, 2015

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 Mailpile and obtained a value of 1.

The developer responsible for this TF is:

Brennan Novak - author of 59% of the files

To validate our results, we would like to ask Mailpile developers the following three brief questions:

(a) Do you agree that the listed developer is the main developer of Mailpile?

(b) Do you agree that Mailpile 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 Mailpile 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/

@bnvk
Copy link
Contributor

bnvk commented Aug 6, 2015

(a) Do you agree that the listed developer is the main developer of Mailpile?

No, I, Brennan Novak am not the main developer of Mailpile, @BjarniRunar is. Your 59% statistic is wrong because the repo contains lots of JS & CSS dependencies to the repo which skew the number significantly in terms of code count

(b) Do you agree that Mailpile will be in trouble if the listed developer leave the project

I'm actually no longer working on the project, read this post for more info

For your research to be valid, Bjarni will have answer these questions from his perspective! Cheers :-)

@BjarniRunar
Copy link
Member

To clarify further, a) is wrong because much of the checked in code is auto-generated from other sources, so there is a massive duplication of code involved, artificially inflating the numbers.

Regarding c), the only mitigating factor is that it is open source and a bunch of people have looked at the code already.

The truck factor is still 1 though; if I leave the project at this point, the project is in trouble. However, winning the lottery would reduce the risk of that happening, not the opposite. You're going to have to stick with morbid reasons I think. :-P

@gavelino
Copy link
Author

Thank you. We really appreciate the feedback.
Our research is under development and the answers we are receiving for this survey will help to better interpret the results and improve our approach.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants