Past software engineering literature has firmly established that software architectures and the associated code decay over time. Architectural decay is, potentially, a major issue in Free/Libre/Open Source Software (FLOSS) projects, since developers sporadically joining FLOSS projects do not always have a clear understanding of the underlying architecture, and may break the overall conceptual structure by several small changes to the code base.\ud \ud This paper investigates whether the structure of a FLOSS system and its decay can also be influenced by the repository in which it is retained: specifically,\ud two FLOSS repositories are studied to understand whether the complexity of the software structure in the sampled projects is comparable, or one repository hosts more complex systems than the other. It is also studied\ud whether the effort to counteract this complexity is dependent on the repository, and the governance it gives to the hosted projects.\ud \ud The results of the paper are two-fold: on one side, it is shown that the repository hosting larger and more active projects presents more complex structures. On the other side, these larger and more complex systems benefit\ud from more anti-regressive work to reduce this complexity
To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.