The importance of socio-technical resources for software ecosystems management

- A survey on the relevance of socio-technical resources for SECOs based on literature.
- Expert opinion on the main roles, activities and artifacts in ecosystem platforms.
- Discussion of socio-technical resources in two real ecosystems, BPS Portal and GitHub.
- A second survey on the usefulness and ease of use of two real ecosystem platforms.
- The top 12 socio-technical resources evaluated in two real SECO platforms.

Software Ecosystem (SECO) is often understood as a set of actors interacting among themselves and manipulating artifacts with the support of a common technology platform. Usually, SECO approaches can be designed as an environment whose component repository is gathering stakeholders as well as software products and components. By manipulating software artifacts, a technical network emerges from interactions made over the component repository in order to reuse artifacts, improving code quality, downloading, selling, buying etc. Although technical repositories are essential to store SECO's artifacts, the interaction among actors in an emerging social network is a key factor to strengthen the SECO's through increasing actor's participation, e.g., developing new software, reporting bugs, and communicating with suppliers. In the SECO context, both the internal and external actors keep the platform's components updated and documented, and even support requirements and suggestions for new releases and bug fixes. However, those repositories often lack resources to support actors' relationships and consequently to improve the reuse processes by stimulating actors' interactions, information exchange and better understanding on how artifacts are manipulated by actors. In this paper, we focused on investigating SECO as component repositories that include socio-technical resources. As such, we present a survey that allowed us to identify the relevance of each resource for a SECO based on component repositories, initially focused on the Brazilian scenario. This paper also describes the analysis of the data collected in that survey. Information of other SECO elements extracted from the data is also presented, e.g., the participants' profile and how they behave within a SECO. As an evolution of our research, a study for evaluating the availability and the use of such resources on top of two platforms was also conducted with experts in collaborative development in order to analyze the usage of the most relevant resources in real SECO's platforms. We concluded that socio-technical resources have aided collaboration in software development for SECO, coordination of teams based on more knowledge of actor's tasks and interactions, and monitoring of quality of SECOs' platforms through the orchestration of the contributions developed by external actors.