Why We Engage in FLOSS: Answers from Core Developers · HackerPapers discussions

Why We Engage in FLOSS: Answers from Core Developers — mentioned by jolmg

Sat, 02 Jun 2018 16:52:18 GMT

The paper also addresses that at section 3, Barriers[1]: - Large and complex project - Lack of time of the project leaders - Non-clear, complex or buggy codebase - Lack of time of the own contributor - Inappropriate design or architecture - etc. [1] https://www.arxiv-vanity.com/papers/1803.05741/#S3.SS3

Paper and discussion history. A mention is not an endorsement.

Why We Engage in FLOSS: Answers from Core Developers — mentioned by bfirsh

Sat, 02 Jun 2018 12:44:12 GMT

If you're on a phone, here's an HTML version of the article: https://www.arxiv-vanity.com/papers/1803.05741/

Paper and discussion history. A mention is not an endorsement.

Why We Engage in FLOSS: Answers from Core Developers — HN submission

Sat, 02 Jun 2018 11:09:21 GMT

Why We Engage in FLOSS: Answers from Core Developers

103 points; 61 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Why We Engage in FLOSS: Answers from Core Developers — HN submission

Fri, 06 Apr 2018 12:56:23 GMT

Why We Engage in FLOSS: Answers from Core Developers

2 points; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.

Why We Engage in FLOSS: Answers from Core Developers — HN submission

Fri, 16 Mar 2018 10:37:39 GMT

Why We Engage in FLOSS: Answers from Core Developers

1 point; 0 discussion replies on HN. Paper and source history. A submission is not an endorsement.