Microblogging in Open Source Software Development: The Case of Drupal and Twitter

Wang, Xiaofeng; Ilona, Kuzmickaja; Stol, Klaas-Jan; Abrahamsson, Pekka; Fitzgerald, Brian

doi:10.1109/ms.2013.98

Cited by 26 publications

(18 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Part of this investigation will involve understanding the needs of OSS developers about SAD. (2) Obtain architectural information in other documentation sources, for example, OSS project blogs [51], mailing lists [52], social media [41], forums, code comments, and commit data [53], which are not covered and analyzed in this survey. We plan to further investigate these related architectural information sources on how architectural knowledge is shared between stakeholders and employed in OSS development (e.g., using various knowledge-based approaches [54]) with these sources, and how these sources can be collected to enrich OSS SA documentation.…”

Section: Discussionmentioning

confidence: 99%

“…These developers tend to pay more attention to coding solutions instead of documenting SA, which is also demonstrated in general software documentation of OSS development [40]. Second, some architectural information is recorded and scattered in resources outside OSS repositories, e.g., project forums, mailing lists, developer blogs, and social media [41], and developers are not willing to spend extra effort collecting and archiving this information into SAD. This is to be expected since there is no architect role in OSS projects, a person who is explicitly made responsible to design, align, and document SA.…”

Section: Relationship Between Architectural Languages Andmentioning

confidence: 99%

See 1 more Smart Citation

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Ding

Liang

Tang

et al. 2014

2014 19th International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

Abstract-Software architecture (SA) documentation provides a blueprint of a software-intensive system for the communication between stakeholders about the high-level design of the system. In open source software (OSS) development, a lack of SA documentation may hinder the use and further development of OSS, but how much "architecture" documentation is enough and appropriate is largely dependent on the contextual factors of development. In order to understand the state of the practice of SA documentation in OSS projects, we conducted a documentation-based survey to explore how SA is documented in OSS projects. Out of 2,000 OSS projects from four major OSS sources, we found that 108 projects have some SA documentation, which shows that the SA documentation is scarce in OSS development. We analyzed these 108 projects to understand what SA information has been documented and how they have been described. We have found that frequentlydocumented architectural information is model, system, and mission; natural language is the most frequently-used architectural language for specifying architectural information in OSS SA documents. The results also show that the likelihood that an OSS project will document SA is increased when more developers are involved in the project, and industry and research OSS projects are more likely to create SA documents than freelance projects.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Relationship Between Architectural Languages Andmentioning

confidence: 99%

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Ding

Liang

Tang

et al. 2014

2014 19th International Conference on Engineering of Complex Computer Systems

View full text Add to dashboard Cite

show abstract

“…New developments, such as the emergence of new tools have an impact on how developers achieve their tasks and communicate. For instance, in recent years, the use of microblogging through sites such as Twitter and Yammer are becoming increasingly popular, both in closed-source and open-source environments [Wang et al 2014]. Microblogging can help in building a community as well as in communication.…”

Section: Future Workmentioning

confidence: 99%

Key factors for adopting inner source

Stol

Avgeriou

Babar

et al. 2014

ACM Trans. Softw. Eng. Methodol.

Self Cite

View full text Add to dashboard Cite

A number of organizations have adopted Open Source Software (OSS) development practices to support or augment their software development processes, a phenomenon frequently referred to as Inner Source. However the adoption of Inner Source is not a straightforward issue. Many organizations are struggling with the question of whether Inner Source is an appropriate approach to software development for them in the first place. This article presents a framework derived from the literature on Inner Source, which identifies nine important factors that need to be considered when implementing Inner Source. The framework can be used as a probing instrument to assess an organization on these nine factors so as to gain an understanding of whether or not Inner Source is suitable. We applied the framework in three case studies at Philips Healthcare, Neopost Technologies, and Rolls-Royce, which are all large organizations that have either adopted Inner Source or were planning to do so. Based on the results presented in this article, we outline directions for future research.

show abstract

“…In the last few years, research has also started to emerge on analyzing the activities of software developers with respect to software projects on social media channels. Wang et al [18] investigated how open source community uses social media channels through studying the usage of Twitter by software developers of Drupal open source content management system. In another study, Bougie et al [19] found that software developers extensively leverages Twitter's capabilities for conversation and information sharing.…”

Section: Related Workmentioning

confidence: 99%

On the Need of Integrating Social Media Channels and Open Source Software Repositories

Iqbal

Decker

2015

2015 IEEE International Conference on Information Reuse and Integration

View full text Add to dashboard Cite

Abstract-The growing interest in the usage of social media channels have attracted the open source software community to adopt an identity in order to disseminate project-related information to a wider audience. We foresee the need to integrate social media channels and open source software repositories in order to get an integrated view on the software project not only from the software development perspective but also from social perspective. Therefore, in this paper we study the usage of Twitter by software developers through harvesting their project-related activities on Twitter. In particular, we present the most commonly used hashtags by software developers and further investigate if project-related hashtags are the most frequent and commonly used hashtags by software developers. Based on our findings, we argue that relevant information from social media channels should be integrated with the open source software repositories in order to provide a homogeneous view on a software project.

show abstract

Microblogging in Open Source Software Development: The Case of Drupal and Twitter

Cited by 26 publications

References 10 publications

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

How Do Open Source Communities Document Software Architecture: An Exploratory Survey

Key factors for adopting inner source

On the Need of Integrating Social Media Channels and Open Source Software Repositories

Contact Info

Product

Resources

About