TY - GEN
T1 - "We are dying!" On Death Signals of Software Ecosystems
AU - Soupinski, Felipe
AU - Arantes, Pedro
AU - Steinmacher, Igor
AU - Wiese, Igor
AU - Borges, Hudson
AU - Cafeo, Bruno
AU - Fontão, Awdren
N1 - Publisher Copyright:
© 2022 Association for Computing Machinery. All rights reserved.
PY - 2022/10/5
Y1 - 2022/10/5
N2 - Software Ecosystems (SECO) depend on platforms that serve as environments for developers interaction. When the organization that owns the platform does not support the synergy between organizational goals and developers' expectations, the SECO may die. The death results in the definitive suspension of vital activities, directly impacting developers, who lose part of the learning and experience gained. Projects that depend on the SECO platform may be discontinued. Ultimately, the responsible corporation loses the resources invested in the development and maintenance of the software and communities. Thus, understanding the signs that may indicate a SECO death is important. In this paper, we report a study conducted on StackOverflow (SO) and GitHub (GH) focusing on Web SECOs: AngularJS, PhantomJS, and Moment.JS. We analyzed metrics based on answer rates, closed issues, and modified files to understand what happens in these SECOs before, during, and after the platform's death. We identified that an SO answer rate below 0.8 is a sign of risk. In GH, the files that involve source code and text are the ones that concentrate on the activities before and during death.
AB - Software Ecosystems (SECO) depend on platforms that serve as environments for developers interaction. When the organization that owns the platform does not support the synergy between organizational goals and developers' expectations, the SECO may die. The death results in the definitive suspension of vital activities, directly impacting developers, who lose part of the learning and experience gained. Projects that depend on the SECO platform may be discontinued. Ultimately, the responsible corporation loses the resources invested in the development and maintenance of the software and communities. Thus, understanding the signs that may indicate a SECO death is important. In this paper, we report a study conducted on StackOverflow (SO) and GitHub (GH) focusing on Web SECOs: AngularJS, PhantomJS, and Moment.JS. We analyzed metrics based on answer rates, closed issues, and modified files to understand what happens in these SECOs before, during, and after the platform's death. We identified that an SO answer rate below 0.8 is a sign of risk. In GH, the files that involve source code and text are the ones that concentrate on the activities before and during death.
UR - http://www.scopus.com/inward/record.url?scp=85139118990&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85139118990&partnerID=8YFLogxK
U2 - 10.1145/3555228.3555264
DO - 10.1145/3555228.3555264
M3 - Conference contribution
AN - SCOPUS:85139118990
T3 - ACM International Conference Proceeding Series
SP - 363
EP - 369
BT - CBSOFT 2022 - 13th Congresso Brasileiro de Software; Proceedings - 36th Brazilian Symposium on Software Engineering, SBES 2022
PB - Association for Computing Machinery
T2 - 36th Brazilian Symposium on Software Engineering, SBES 2022
Y2 - 3 October 2022 through 7 October 2022
ER -