Software Ecosystems (SECO) depend on platforms that serve as environments for developers’ interaction. The SECO may die when the organization that owns the platform does not support the synergy between organizational goals and developers’ expectations. The death results in the suspension of vital activities, such as code development and maintenance, impacting developers who lose work, learning, and experience gained. On the other hand, the responsible corporation loses resources invested in SECO. These signs indicate a SECO death is an important event for the community and should be analyzed. This paper reports a GitHub (GH) study focusing on three web SECOs: AngularJS, PhantomJS, and MomentJS. We analyze metrics based on developer community engagement and collaboration to understand what happens in these SECOs before, during, and after the platform’s death.
P: Pedro Arantes Federal University of Mato Grosso do Sul, A: Felipe Soupinski Federal University of Mato Grosso do Sul, A: Awdren Fontão Federal University of Mato Grosso do Sul (UFMS)
