<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Connecting the lives of the Drupal community</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Iain Emsley, David De Roure Oxford e-Research Centre University of Oxford Oxford</institution>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>- The Drupal content management system has a vibrant, widely distributed community that develops, documents and evangelizes the software. It supports itself through the main site, the DrupalCon conferences, user groups and an association. We discuss the use of social coding and software credit to develop the software community and social documentation to provide documentation and tutorials. We argue that there are subcommunities, using different social machines, which are linked as a concept. Index Terms-Social coding, social documentation, Drupal, social machines, software credit</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>I. INTRODUCTION</title>
      <p>
        The Drupal content management system has a vibrant, widely
distributed community. It supports itself through the main
Drupal sites[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], the DrupalCon conferences, user groups and the
Drupal Association.
      </p>
      <p>
        The Getting Involved Guide states “[w]e depend on our
diverse community of passionate volunteers to move the
[Drupal] project forward” [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. We might infer that the
community is a homogenous entity through the use of the
singular. We present work in progress exploring how
homogeneous it is or whether is it is an umbrella for
heterogeneous communities. If the latter, then do the
subcommunities interact with each other? It is implied that there is
more than one community and we conduct exploratory
investigations into types of community using web mining.
Looking at related works from social coding and social
documentation, we discuss how these sub-communities support
the main community. We focus on a sample of actors who
bridge these social machines, “processes in which the people do
the creative work and the machine does the administration”[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ],
that are emergent socio-technical entities, such as GitHub.
      </p>
    </sec>
    <sec id="sec-2">
      <title>II. RELATED WORK GitHub users are interviewed in [4] about social coding but the scope is limited. The network effect of developers within</title>
      <p>
        This work is licensed under a CC-BY-4.0 license
GitHub is explored in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Loose social links between projects
and developers in GitHub are discovered in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        The role of social media in the shared writing of formal and
informal documentation with the use of YouTube is discussed
in [
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ] to use screen casts as an alternative to traditional
documentation. The authors discuss the use of social media to
write documentation but not the intersection with other parts of
the community.
      </p>
    </sec>
    <sec id="sec-3">
      <title>III. METHODOLOGY</title>
      <p>We focus on the intersections of three data streams, YouTube,
GitHub and Twitter, focused on keywords taken from the
Drupal community during September 2015. DrupalCon Europe
was being held in Barcelona and Drupal 8 was being prepared
for release.</p>
      <p>We focus on the committers due to the difficulty of matching
identities. Their Drupal profiles are used to discover their
Twitter names and verified these by looking them up. As the
YouTube data was small enough, we identified a unique list of
all names and checked these against Twitter as well as
intersecting them with the Twitter identities.</p>
    </sec>
    <sec id="sec-4">
      <title>IV. RESULTS</title>
      <p>Out of the 8 committers, only 3 link Github and Twitter and
they are associated with the new release. We discover a
maintainer of an older branch and project maintainer linking
YouTube and Twitter, but organizations are the more
significant entries. There are no matches across YouTube and
Github in this data set.</p>
    </sec>
    <sec id="sec-5">
      <title>V. DISCUSSION</title>
      <p>
        Social coding [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] is the application of social media practices
to software development. The Drupal community uses this
model within its own issue queues where developers may
subscribe to updates through subscription or contribution. This
practice enhances the distributed community through ensuring
that interested parties are involved in the discussion process.
Commits can be made by project owners or co-maintainers[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
This latter group is made of users who participate across a
project and its issues and must also have significant patches
committed to the relevant codebase. Becoming a co-lead
requires interaction with the relevant community and work
contributions, suggesting a strong focus on developing a
subcommunity.
      </p>
      <p>
        Patches committed to the code base reflect this social spirit. The
commit messages link to the Drupal issue and attribute all
contributors, so software credit is embedded into this
subcommunity. There is a standard format:
Issue #[issue number] by [comma-separated usernames]: [Short
summary of the change]. [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]
This model also encourages the tagging of organizations who
funded the developer or for whom the work was done [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
Organizations must have an account on the Drupal site to be
tagged. This initiative encourages those entities to promote
themselves and the developer community to promote those
organizations on the main Drupal site.
      </p>
      <p>We expected the maintainers to be more active across the social
machines than they are in this snapshot. The ones who have
community roles as well and this would suggest a stronger focus
on the development community than the “Drupal community”.
Social documentation is the application of social media to
documentation, such as YouTube videos. Tutorials and talks are
posted to the social media sites as enhancements.</p>
      <p>
        The DrupalAssociation [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] channel presents the talks from
DrupalCon Barcelona, covering business and technical
development, and Drupal 8. Set up to support and develop the
community, it is key factor in sharing practices and promoting
the concept of a community. The use of Symfony [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]
components in Drupal 8 requires the communities to adopt new
practices and code, such as PSR-4 [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. As the Drupal
Association publish the videos, the internal conversation
becomes external and showing the community expertise and
experiences, where individuals focus on demonstrating their
talents.
      </p>
    </sec>
    <sec id="sec-6">
      <title>VI. FUTURE WORK AND CONCLUSIONS</title>
      <p>Although the social machines of GitHub, YouTube and Twitter
are relatively new, they build on existing social and technical
practices. Future work includes extending the model of
contributors to companies and machines. We want to look at the
community over a longer time period and look at other
communities, including Symfony.</p>
      <p>
        YouTube provides a community driven, multimedia experience
building on the documentation at [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], although it does not
always link to project. We want to look at StackOverflow to
view any overlaps and changes in practice.
      </p>
      <p>Social practices are more apparent within the more focused
development group where it is encouraged as part of practice.
The Drupal project is at a watershed with new and old code and
documentation requiring maintenance. The sub-communities
sustain themselves and are linked by a small group who have
gained social and technical trust. The community presents itself
as homogeneous but is a loosely coupled, heterogeneous set of
communities.</p>
    </sec>
    <sec id="sec-7">
      <title>ACKNOWLEDGMENT The work in this paper is sponsored by the Oxford e-Research Centre as part of an MSc in Software Engineering dissertation.</title>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Drupal</surname>
          </string-name>
          , http://www.drupal.org
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Drupal</given-names>
            <surname>Getting Involved Guide</surname>
          </string-name>
          , https://www.drupal.org/gettinginvolved-guide
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>T.</given-names>
            <surname>Berners-Lee</surname>
          </string-name>
          ,
          <article-title>Weaving the Web: The Original Design and Ultimate Destiny of the World Wide Web by its Inventor</article-title>
          , Harper San Francisco,
          <year>1999</year>
          , p
          <fpage>172</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L.</given-names>
            <surname>Dabbish</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Stuart</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Tsay</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Herbsleb</surname>
          </string-name>
          ,
          <article-title>"Social coding in GitHub: transparency and collaboration in an open software repository</article-title>
          .
          <source>" Proceedings of the ACM 2012 conference on Computer Supported Cooperative Work</source>
          ,
          <year>2012</year>
          ,
          <fpage>pp1277</fpage>
          -
          <lpage>1286</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>F.</given-names>
            <surname>Thung</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T</given-names>
            <surname>Bissyandé</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Lo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Jiang</surname>
          </string-name>
          ,
          <article-title>"Network structure of social coding in GitHub."</article-title>
          <source>Proceedings of the 17th European conference on Software Maintenance and Reengineering</source>
          , IEEE,
          <year>2013</year>
          , pp
          <fpage>323</fpage>
          -
          <lpage>326</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>J.</given-names>
            <surname>Jiang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Li</given-names>
            <surname>Zhang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Li</surname>
          </string-name>
          .
          <article-title>"Understanding project dissemination on a social coding site."</article-title>
          , 20th Working Conference on Reverse Engineering, IEEE,
          <year>2013</year>
          , pp
          <fpage>132</fpage>
          -
          <lpage>141</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7] MA. Storey,
          <string-name>
            <given-names>C.</given-names>
            <surname>Treude</surname>
          </string-name>
          ,
          <string-name>
            <surname>A. van Duersen</surname>
          </string-name>
          , L Cheng.
          <article-title>"The impact of social media on software engineering practices and tools</article-title>
          .
          <source>" Proceedings of the FSE/SDP workshop on Future of software engineering research</source>
          . ACM,
          <year>2010</year>
          , pp
          <fpage>359</fpage>
          -
          <lpage>364</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>L. MacLeod</surname>
          </string-name>
          , MA. Storey,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Bergen</surname>
          </string-name>
          .
          <year>2015</year>
          . “
          <article-title>Code, camera, action: how software developers document and share program knowledge using YouTube”</article-title>
          ,
          <source>Proceedings of the 2015 IEEE 23rd International Conference on Program Comprehension</source>
          ,
          <year>2015</year>
          , pp
          <fpage>104</fpage>
          -
          <lpage>114</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>Drupal</given-names>
            <surname>Committer List</surname>
          </string-name>
          , https://www.drupal.org/node/21778
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>[10] GitHub on Social Coding, https://help.GitHub.com/articles/besocial/</mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <article-title>Best Practices for Co-maintaining projects</article-title>
          , https://www.drupal.org/node/363367
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Commit</surname>
            <given-names>Messages - Providing</given-names>
          </string-name>
          <string-name>
            <surname>Credit</surname>
          </string-name>
          and History, https://www.drupal.org/node/52287
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Attribute</surname>
          </string-name>
          this Contribution, https://www.drupal.org/node/2451283
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Drupal</surname>
            <given-names>Association</given-names>
          </string-name>
          , https://assoc.drupal.org/
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Symfony</surname>
          </string-name>
          , http://symfony.com/
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <article-title>PSR-4 Namespaces and autoloading in Drupal 8</article-title>
          , https://www.drupal.org/node/ 2156625
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>