English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Architecture information is vital for Open Source Software (OSS) development,and mailing list is one of the widely used channels for developers to share andcommunicate architecture information. This work investigates the nature ofarchitecture information communication (i.e., why, who, when, and what) by OSSdevelopers via developer mailing lists. We employed a multiple case studyapproach to extract and analyze the architecture information communication fromthe developer mailing lists of two OSS projects, ArgoUML and Hibernate, duringtheir development life-cycle of over 18 years. Our main findings are: (a)architecture negotiation and interpretation are the two main reasons (i.e.,why) of architecture communication; (b) the amount of architecture informationcommunicated in developer mailing lists decreases after the first stablerelease (i.e., when); (c) architecture communications centered around a fewcore developers (i.e., who); (d) and the most frequently communicatedarchitecture elements (i.e., what) are Architecture Rationale and ArchitectureModel. There are a few similarities of architecture communication between thetwo OSS projects. Such similarities point to how OSS developers naturallygravitate towards the four aspects of architecture communication in OSSdevelopment.

Architecture Information Communication in Two OSS Projects: the Why, Who, When, and What