On Developer Relations Team's Reasons for Using Repositories

Fontão, Awdren; Cafeo, Bruno; Bonifácio, Bruno; Santos, Rodrigo Pereira dos; Dias-Neto, Arilo Cláudio

doi:10.1145/3387940.3392170

Cited by 2 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Similar lessons learned were grouped together to form a single one. Thus, a total of 62 lessons learned were reached: 27.5% for awareness (17), 17.7% for reference (11), 17.7% for recognition (11), 16.1% for retention (10) , 11.3% for onboarding (7), and 9.7% for activation (6). The set of lessons learned is presented throughout the description of the current version of the DevGo model (Section 5).…”

Section: Discussionmentioning

confidence: 99%

“…DevRel can be defined as: 10 “it is about creating a vibrant ecosystem of third‐party developers, by being the interface between those developers and the platform's product, engineering, and design teams”. DevRel consists of an internal organizational area that builds relationships among developer communities, partner companies, and the organization 11 . This area is responsible for creating and communicating technical resources (e.g., APIs, code samples), planning and performing developer events (e.g., hackathons), and managing developer programs (e.g., AWS Heroes, Google Developers Experts, Microsoft Valuable Professional), to cite some tasks 10 .…”

Section: Introductionmentioning

confidence: 99%

“…DevRel as the public interface of ecosystem products and platform is responsible for the critical task of translating developer community interactions into trusted relationships with the organization 12 . DevRel can be understood as a set of instruments to forge and nurture a thriving community that maintain collaborative relationships between developers and keystone 11 . DevRel must be conducted in a win‐win context: balance between developers' goals and ecosystem platform's value 13,22 .…”

Section: Introductionmentioning

confidence: 99%

“…12 DevRel can be understood as a set of instruments to forge and nurture a thriving community that maintain collaborative relationships between developers and keystone. 11 DevRel must be conducted in a win-win context: balance between developers' goals and ecosystem platform's value. 13,22 It affects business and economic features of industry and the quality of ecosystem platform.…”

Section: Introductionmentioning

confidence: 99%

“…DevRel consists of an internal organizational area that builds relationships among developer communities, partner companies, and the organization. 11 This area is responsible for creating and communicating technical resources (e.g., APIs, code samples), planning and performing developer events (e.g., hackathons), and managing developer programs (e.g., AWS Heroes, Google Developers Experts, Microsoft Valuable Professional), to cite some tasks. 10 As part of SECO governance, planning and execution of DevRel activities are not trivial and focus on delimiting developer actions without excessively restricting the desired level of value creation.…”

mentioning

confidence: 99%

See 4 more Smart Citations

A Developer Relations (DevRel) model to govern developers in Software Ecosystems

Fontão

Cleger-Tamayo

Wiese

et al. 2021

J Software Evolu Process

View full text Add to dashboard Cite

Software Ecosystem (SECO) comprises third-party developers cooperating and competing when contributing to a platform provided by a central organization (keystone). There are keystones investing in Developer Relations (DevRel) internal team as a global business strategy to attract and engage a critical mass of third-party developers in producing and evolving contributions. For this reason, the DevRel team should promote social relationships among SECO actors and synergy among keystone' goals and developers' expectations to survive to inherit changes. However, the understanding of DevRel structure and the way DevRel team can act on a SECO to better engage the developers' communities establishing a robust VCN (Value Creation Network) remain a challenge. In this article, we advance on the structure for developers' governance from DevRel by proposing and refining a model because of the following research methods: grey literature review, opinion survey, and interviews. The model is called DevGo (DEVeloper GOVernance) and consists of four focus areas, three developer advancement phases, six stages, enablers, and value transfer objects. In addition, a set of 62 lessons learned from DevRel practitioners is associated with DevGo stages.

show abstract