How open is the SBES PC community?

Fabio Pacheco, Bruno Cartaxo, Igor Wiese, Igor Steinmacher, Gustavo Pinto

Research output: Chapter in Book/Report/Conference proceedingConference contribution


The Brazilian Symposium on Software Engineering (SBES) is one of the most important Latin American software engineering coferences. In 2019 it completes its 33rd edition. Over these years, many researchers participated in the SBES attending the conference, submitting papers, or reviewing papers. In particular, the researchers that participated in the program committee, playing the reviewers' role, are fundamentally important to the whole event since their evaluations (e.g., deciding whether a paper is accepted or not) have the potential of drawing what SBES is now. Knowing that diversity is an important aspect of any group work, in this paper we wanted to understand how diverse (in terms of gender and geographic location) is the SBES program committee community. Among the findings, we observed that although the number of participants in the SBES PC increased over the years, most of them are men (∼80%) and from the Southeast and Northeast of Brazil, with very few members from the North region.

Original languageEnglish (US)
Title of host publicationProceedings of the 33rd Brazilian Symposium on Software Engineering, SBES 2019
PublisherAssociation for Computing Machinery
Number of pages5
ISBN (Electronic)9781450376518
StatePublished - Sep 23 2019
Externally publishedYes
Event33rd Brazilian Symposium on Software Engineering, SBES 2019 - Salvador, Brazil
Duration: Sep 23 2019Sep 27 2019

Publication series

NameACM International Conference Proceeding Series


Conference33rd Brazilian Symposium on Software Engineering, SBES 2019


  • Evolution
  • Program committee
  • SBES

ASJC Scopus subject areas

  • Software
  • Human-Computer Interaction
  • Computer Vision and Pattern Recognition
  • Computer Networks and Communications


Dive into the research topics of 'How open is the SBES PC community?'. Together they form a unique fingerprint.

Cite this