Talk Is Silver, Code Is Gold? Beyond Traditional Notions of Contribution in Peer Production: The Case of Drupal

Peer production communities are based on the collaboration of communities of people, mediated by the Internet, typically to create digital commons, as in Wikipedia or free software. The contribution activities around the creation of such commons (e.g., source code, articles, or documentation) have been widely explored. However, other types of contribution whose focus is directed toward the community have remained significantly less visible (e.g., the organization of events or mentoring). This work challenges the notion of contribution in peer production through an in-depth qualitative study of a prominent “code-centric” example: the case of the free software project Drupal. Involving the collaboration of more than a million participants, the Drupal project supports nearly 2% of websites worldwide. This research (1) offers empirical evidence of the perception of “community-oriented” activities as contributions, and (2) analyzes their lack of visibility in the digital platforms of collaboration. Therefore, through the exploration of a complex and “code-centric” case, this study aims to broaden our understanding of the notion of contribution in peer production communities, incorporating new kinds of contributions customarily left invisible.


INTRODUCTION
What is value? Aristotle's writings (Brown, 2009) on value as, in essence, an exchange of two things; Adam Smith's dichotomy of value in use and value in exchange (Robertson and Taylor, 1957); and the identification by Marx and Engels (1990) of concrete and abstract forms of labor associated to those; are just a few examples of the myriad of conceptualizations historically discussed around the concept of value.
In this article, we explore perceptions of value in the context of the collaborative economy, in which forms of value are increasingly created by crowds and communities of diverse participants. The growth of the collaborative economy has encompassed an increasing lack of common ways to assess, control and measure these forms of value (Arvidsson and Peitersen, 2013). These changes can be understood in the wider context of the Information Economy, in which, as a result of changes in technological conditions, information has become a fundamental source of productivity and power (Castells, 2011).
Concretely, we explore perceptions of value in Commons-Based Peer Production (CBPP). This term, originally coined by Benkler (2002), refers to an emergent model of socioeconomic production in which groups of individuals cooperate to produce shared resources without a traditional hierarchical organization (Benkler, 2006). There are multiple, well-known examples of this phenomenon, such as Wikipedia, a project to collaboratively write a free encyclopedia; OpenStreetMap, a project to create free/libre maps of the World; or Free/Libre Open Source Software (FLOSS) projects, such as the operating system GNU/Linux or the browser Firefox. Research carried out drawing on crowdsourcing techniques (Fuster-Morell et al., 2016a) found examples of the broad diversity of areas in which collaborative work on the commons is present. This includes citizen science, urban commons, peer funding and open design.
The existence of value beyond measure (Hardt and Negri, 2001) poses a great challenge for researchers. The study of such perceptions in specific contexts, such as CBPP communities, provides us, however, with ways to escape the hegemonic price system to determine value (Pazaitis et al., 2017). In other words, if as argued by Graeber (2001), the capitalist mode of production has transformed the perceptions of value, defining meaningful actions within the broader capitalist social totality, then CBPP provides us with spaces in which to understand such actions as meaningful or not with respect to the internal social totality of these communities themselves. In this article, we develop from Graeber's (2001) perspective of value as a coordination mechanism, which in the case of CBPP is contextualized as the actions which emerge as part of meaningful contribution activities to the participants of such communities and, to a certain extent in some cases, find a reflection in the artifacts that these communities employ to collaborate. We agree, in this respect, with Wittel's (2013) argument on contribution being a key notion around which the framing of perceptions of value operate in the context of CBPP. As a result, we decided to carry out an exploration of what activities are considered contributions or not in CBPP communities, with the aim of shedding light on the perceptions of value in these communities.
With this aim, we investigate notions of contribution in CBPP, posing the question: what types of activities are perceived and valued as contributions in Commons-Based Peer Production and how are they recorded in the tools employed for coordination ? We explore notions of contribution in a large and complex case of CBPP: Drupal. Drupal is a FLOSS content management framework for the development of web applications that was released in 2001. The Drupal project currently powers more than 1.9% of websites worldwide 1 . The Drupal community has experienced significant growth over the years: there are currently 2 more than 1.3 million people registered on the main collaboration platform (Drupal.org, 2017): www.drupal.org.
Thus, the study of activities considered as contributions by community members becomes especially relevant in a complex and large case of CBPP, such as the Drupal community. Drupal has been described as "code-centric" in the literature (Zilouchian-Moghaddam et al., 2011;Sims, 2013). Namely, the Drupal community possesses a shared belief that the most valuable type of contribution by participants is source code: the sets of computer instructions which dictate how the Drupal software works. This "code-centrism" is also illustrated by the wellknown Drupal motto: "Talk is silver, code is gold 3 " which is not uncommon in FLOSS communities. In sum, through the exploration of a complex and "code-centric" case, this study aims to unveil perceptions of contribution in peer production which would be less visible in smaller and simpler communities.
Our contribution is two-fold: firstly by broadening our understanding of the notions of contribution in the study of CBPP, providing a set of categories which emerged from our empirical analysis and which highlight activities not widely studied due to their traditional lack of visibility. Having identified these categories, we explore the relevance of activities which have remained less visible. Secondly, by drawing on the previously identified categories, we explore the recording of these forms of contribution in the main platforms employed for collaboration, showing an uneven representation of contribution activities. This analysis of the degree of representation of value attached to meaningful collaborations contributes by following previous calls on CBPP (e.g., De Filippi and Hassan, 2015;Pazaitis et al., 2017) and FLOSS (Carillo et al., 2014) studies to explore the systems of value of CBPP communities in order to further our understanding of how to systematize them into the technological artifacts which support collaboration, with an awareness of the communitarian context.

CONCEPTUAL BACKGROUND
The concept of contribution in FLOSS literature has been widely employed in studies, but mainly in reference to activities related to source code. This can be understood as a form of "codecentrism": reducing the conceptualization of participation and performance in FLOSS projects to the understanding of the activities surrounding the development of source code (Carillo et al., 2014, p. 3276). This is despite, as we shall see, the diversity of activities carried out in FLOSS communities, such as the organization of events, mentoring and training practices, and the creation of documentation and translations. Krogh and Von Hippel's (2006) literature review on FLOSS shows how studies that include the notion of contribution have principally examined the development of source code as the main type of contribution. This can be observed, for example, in studies focused on motivations to contribute (e.g., Bergquist and Ljungberg, 2001;Ghosh et al., 2002;Lerner and Tirole, 2002;Lakhani and Wolf, 2003;Stenborg, 2004); as well as in those focused on the relationship between organization and contribution (e.g., Dempsey et al., 2002;Koch and Schneider, 2002;Franck and Jungwirth, 2003;Grewal et al., 2006;MacCormack et al., 2006). Another illustration of this "code-centrism" in research on FLOSS can be found in the literature review of Crowston et al. (2012), in which they developed a framework based on an inputs-mediators-outputs-inputs model 4 (Ilgen et al., 2005) to review 135 papers. In the case of inputs, most of the literature related to individual participation considers source code related activities (e.g., Luthiger, 2005;Robles et al., 2005;Roberts et al., 2006;Fershtman and Gandal, 2007), or more recently between governance and authoritative structures associated with the management of such contributions (Shaikh and Henfridsson, 2017), as well as in the development of theory of how such forms of collaboration are organized (e.g., Howison and Crowston, 2014). A similar "code-centric" character can be observed with regard to outputs, for example regarding FLOSS team performance (e.g., Bezroukov, 1999;Samoladas et al., 2004;de Joode and Egyedi, 2005;Gyimothy et al., 2005). This issue is not, however, exclusive to FLOSS. Jemielniak (2014, p. 39-41) describes an analogous phenomenon in Wikipedia ("editcountitis") around the number of edits as a major measure to evaluate participants' contributions, in spite of an awareness of its reductionism. In other words, a similar "object-centric" character, in which the objects are digital commons, such as articles and maps, can be found regarding the notions of contribution with respect to CBPP communities. For example, the writing of articles in Wikipedia (e.g., Kittur et al., 2007;Kostakis, 2010;Crowston et al., 2013;Jemielniak, 2014;Matei and Bruno, 2015) or the editing of maps in OpenStreetMap (e.g., Haklay et al., 2010;Neis and Zipf, 2012).
With the aim of questioning our understanding of the notion of contribution in the study of peer production beyond the most traditional "object-centric" conceptions, we carried out an analysis of these perceptions. We framed our analysis drawing on the three layer system of value for CBPP communities developed by Pazaitis et al. (2017). Concretely we explored the (1) production of value and the (2) record of value. The first layer refers to the modality of production: what particular actions are rationalized as meaningful contributions according to the communitarian needs? In this respect, we queried the notion of contribution, framing it as a set of meanings which are constantly evolving through negotiation among community members according to their internal logics of value. The second layer relates to the tools employed to record these forms of value. For this, we carried out an analysis of the previously identified activities considered contributions, showing a lack of visibility in the collaboration platforms of some despite their relevance for the sustainability of the community. The third layer, (3) actualization of value (Pazaitis et al., 2017), concerns the rationalization of such meaningful actions within the logic of external economic systems. For example, through monetization. Since our research question focused on internal production, perception and recording of value, Fuster-Morell et al.'s (2016b) conceptualization of internal systems of recognition and rewarding of value creation in peer production, meant we excluded this last outer layer 5 from our analysis.
Next, we describe the qualitative research design and methods employed in order to further our understanding of the subjectivities of how such forms of value are perceived and how they are recorded in the tools employed for collaboration.

MATERIALS AND METHODS
This section details the study's research methodology; firstly, the principal author describes the approach and his position as a researcher, then details his data collection methods.

Ethnographic Approach
From 2013 to 2016 the first author collected and generated the materials employed in this article through participant observation in the Drupal community.
We selected an ethnographic approach in order to highlight the understanding of perceptions of value from the point of view of the participants. This allowed us to access participants' interpretations, experiences, and perspectives of intangible contributions which have been inaccessible through quantitative approaches. We decided to focus on a single, in-depth, complex "code-centric" case of CBPP in order to tackle overgeneralization, over-simplification and neglect of complexity, issues which have previously been criticized (Viégas et al., 2007;Mateos-García and Steinmueller, 2008) in the study of CBPP. Choosing this approach was also a response to calls to understand how effective forms of collective action and self-organization are constructed in Commons-Based Peer Production (Txoler, 2014, p. 191).
On beginning this research, the first author was already an active member of the Drupal community with over three and a half years' experience. Therefore, his position as an ethnographer was as an insider researcher (Brannick and Coghlan, 2007), who had "natural access, " being an active participant in the community, in similar terms as other participants.
This experience enabled faster access to the community, including understanding of meanings surrounding software and the community, to more direct access to the field site and certain activities, such as the organization of events or the maintenance of official Drupal projects. It also eliminated the necessity to acquire the social and technical skills to avoid being considered a "newbie." This previous experience entailed the need, however, to address several challenges relevant to the dynamics of insider research, such as role duality and pre-understanding (Brannick and Coghlan, 2007). The first author dealt with such issues through a constant process of introspection and a continuous review of his roles as both researcher and Drupalista (a communitarian term used to refer to members of the Drupal community). For example, his previous experience within the Drupal community was primarily as a software developer and site builder. As a result, the first author would reflect on the need to widen his understanding from the perspectives of Drupalistas occupying different roles (see Appendix B in Supplementary Material), switching the focus during participant observation, documentary analysis or when selecting interviewees for semistructured qualitative interviews on these perspectives.

Data Collection Methods
We followed a qualitative approach combining 3 years of participant observation, the analysis of an archive of 8,613 documents and 15 semi-structured interviews. We drew on purposive sampling (Palys, 2008), in which the collection and generation of data was led by questions and emergent themes to produce a relevant range of contexts that enabled the establishing of strategic and cross-contextual comparisons to build a wellfounded argument (Mason, 2002). For example, the emergence of a theme regarding the representation of contribution activities in the collaboration platform led to an in-depth study of 73 user profiles until saturation was reached. Data collection and analysis was supported by the Computer Assisted Qualitative Data Analysis Software (CAQDAS) NVivo 10, which facilitated tasks, such as coding or the development of models to refine such codes.

Participant Observation
Participant observation began in October 2013 and concluded in November 2016, throughout which field notes were systematically created. Due to the digital nature and global scope of the Drupal project, the great majority of the community's activities are carried out through online media. However, the large number of face-to-face events suggested that they also play an important role in the life of the community. For these reasons, the field site considered for this case study was the emergent set of online and offline spaces in which the day-to-day activities of the community unfold. Analogous approaches have previously been followed by similar studies in which both dimensions are relevant, as in Coleman's (2013) study of FLOSS communities and hacker culture. Concerning the online, the first author engaged in the numerous collaborative tasks that are regularly carried out in the Drupal community. Such tasks included engaging in discussion groups, writing code, maintaining and coordinating Drupal projects, creating documentation and conducting discussions via social networks and chat channels. Beyond "official" channels, various other online spaces emerged as relevant to this study. For example, communication with Drupalistas through WhatsApp and Telegram groups, in addition to other external platforms, such as Slack, StackExchange, and Meetup. The offline engagement also took diverse forms, including attending and participating in the organization of events, sprints focused on source code development, as well as presenting parts of this research at Drupal events of different scopes: local events, DrupalCamps (national/regional), and a DrupalCon (international) as a keynote speaker. In total, the first author carried out F2F participation at thirty-two events (see Appendix C in Supplementary Material). The majority of participant observation at local events was carried out in London, UK, and the surrounding areas, as well as active participation within the local Drupal community of Madrid, Spain.
Participant observation proved to be essential in gaining an in-depth understanding of Drupalistas' perceptions of value. This allowed the first author to identify and then experience which contributions were or were not considered valuable by the community. Furthermore, he gained firsthand knowledge of how these forms of value are embedded into the technical artifacts employed for collaboration within the community. This method was also beneficial in other ways; for example, it enabled the first author to build a rapport with key informants, which facilitated the evaluation of relevant materials in the documentary analysis.

Documentary Analysis
Defining an initial point of collection of relevant documents was required, given the large amount of information generated by a large community, such as Drupal. Software was developed to generate a live archive of Drupal Planet 6 , which contains Drupalistas' posts made within the community beyond "official channels." The data collection process yielded 8,613 documents from the Drupal Planet archive and, to help select their relevance, the first author conducted several further selection inspections. This process was regularly informed by participant observation. This resulted in a total of 586 documents being fully coded, comprising 6.8% of all of the documents collected. A summary of this data is presented in Appendix D in Supplementary Material.

Semi-structured Interviews
As well as hundreds of unstructured conversations carried out as part of the participant observation process, fifteen semi-structured qualitative interviews were carried out with key participants involved in organizational processes related to contribution activities (see Appendix E in Supplementary Material). These interviews provided rich qualitative data, furthering the understanding of Drupalistas' perceptions of value.

Ethical Considerations
The ethical principles described by the University of Surrey (Gallagher, 2013) were followed, as well as the recommendations from the Association of Internet Researchers (Markham and Buchanan, 2012). Drawing on these guidelines, we constantly reassessed so that the discovery of any new issues resulted in remedial action. These actions include anonymizing participants in field notes, in addition to the design of interview consent forms and requesting permission to use materials gathered outside of the public sphere (for example, conversations in Telegram). The use of data about any individual adhered to the UK's Data Protection Act 7 (1998). The excerpts shown in the next sections show how long the Drupalista had had a drupal.org account, their main roles and gender.

FINDINGS "Object-Oriented" and "Community-Oriented" Contribution Activities
When studying what types of activities are perceived as contributions in the Drupal community, two main types of contribution activities emerged. The first was "object-oriented" contributions, encompassing all activities whose main focus of action are objects, typically digital commons, such as source code, documentation, and translations. The second category was "community-oriented" contributions, the focus of which is directed toward the community. Examples are the organization and participation in face-to-face events, activities related to supporting other users, and mentoring. Table 1 provides a summary of the contribution activities identified in this study.
The activities are firstly classified according to the main categories: "object-oriented" (G 1 ) and "community-oriented" (G 2 ). Contribution activities related to source code (SG 1.1 ) are further classified into three subgroups: core (SG 1.1.1 ), contributed (SG 1.1.2 ), and FLOSS custom projects (SG 1.1.3 ) not included in Drupal.org. The reason for this distinction is the significant differences found in the organizational aspects of the sociotechnical systems that surround these contribution activities (Rozas and Huckle, 2021), despite the type of object being the same: source code. For example, the possibility of performing modifications in the digital commons for the core group is more formalized, typically harder to achieve, and more specialized. As a consequence, new contribution activities emerge and are considered valuable. For example, the "creation of summaries of the issues, " in which hundreds of comments are summarized, is perceived as a valuable contribution. This type of contribution is typically carried out by newer members to save core developers having to read the whole list of issues. It is encouraged as a way to "contribute to core, " whilst enabling the newest members to become familiar with the organizational processes and technicalities. The following excerpt, extracted from field notes taken when participating in a local event, illustrates how these activities are valued as contribution activities: "[...] I joined then a Drupal Ladder 8 session coordinated by Karen.
[...] Karen explained to us ways to contribute to core. One of them I was completely unaware of was summarizing the messages of the issues lists for the developers: ' A good way to contribute initially is doing some issue summaries' and encouraged us to visit https:// drupal.org/issue-summaries, in which we could find very detailed rules on how to do it. The idea is that you find and read a whole issue and, following certain templates and instructions, make a summary so the developer doesn't have to spend a lot of time reading all of the comments. [...]" Extracted from full field notes during the participant observation at a Drupal Coding Sprint in London on 31st May 2014.
Within the "community-oriented" group (G 2 ), a distinction is made with regard to contribution activities related to the organization and participation in face-to-face events (SG 2.5 ). In this case, they are differentiated by their scope. The second of these subgroups (SG 2.5.2 ) includes regional, national and rolespecific events. This is because the dynamics, organizational processes and identified contribution activities in these events are similar. As in the case of the subgroup SG 1.1 , the main difference between SG 2.5.1 , SG 2.5.2 and SG 2.5.3 is with regard to the level of formalization and the ease of participation in their organization. For example, DrupalCon activities, largely organized by the most formal institution within the Drupal community, the Drupal Association, are at the formal end of the spectrum. As in the case of the subgroups of G 1 , organizational processes with a higher degree of complexity in G 2 involve significant organizational changes overtime, including more clearly defined roles (Rozas and Huckle, 2021) and the emergence and perception of new activities which are valued as contributions, such as the peer reviewing and selection of presentations carried out by "track chairs, " as I 10 explains: Developer and system architect, M, 11 years.
While, as previously discussed, "object-oriented" activities have been widely employed in studies drawing on the notion of contribution, those whose main focus of action is the community have received less attention. This is despite the relevance of these activities to sustain the community. A comment from I 3 illustrates, for example, the relevance of activities, such as the participation in and organization of local face-to-face events for the health of the community:  Furthermore, Drupalistas explain and are aware of the differences with respect to the internal logics of value when compared with "object-oriented" activities, such as contributing source code. The following excerpt from field notes illustrates how some Drupalistas identify the participation in and organization of face-to-face events as contributions and the awareness of the perception of differences in value: "[. . . ] She explained to me that we, as a community, are not aware sometimes of the relevance that other activities have, such as the organization of events like this one [referring to the DrupalCamp] or the 'Tour de Drupal 9 '. She thought that organizing and attending events like this one are definitely types of contribution, but they aren't so popular. She explained to me that we tend to think a lot about contributing code, especially to core, but she highlighted: 'thanks to things like this [referring to the F2F event], the community is very healthy'." Designer and front-end developer, F, 5 years. Extracted from full field notes during the participant observation at DrupalCamp North East 2014.
Participation in face-to-face events as those mentioned in the previous excerpt, was commonly described as a way to humanize the community. Drupal is regarded not just as "a piece of software" anymore, but rather a community in which Drupalistas become commoners through "commoning" (Linebaugh, 2008). 9 It refers to an initiative (https://groups.drupal.org/tour-de-drupal) of Drupalistas to cycle together over several days to the city in which the DrupalCon is held.
By affecting the emotional experiences of Drupalistas these contribution activities play a relevant role in the sustainability of the community, and increase the commitment to participate in the community. The following excerpt from I 2 , a newcomer, while reflecting on how attendance at local meetings changed his emotional experiences, illustrates this: Another common outcome of "community-oriented" activities was help with overcoming barriers, and increasing the will to contribute, providing opportunities to participate in the community to those who are not technical and, thus, facilitating the diversity of participants beyond the most technical profiles. The following excerpt from a new member after attending a DrupalCamp for the first time illustrates this type of outcome: "Walking in the door, I didn't feel like a part of the community. I wasn't sure where I fit in since I wasn't a developer, designer, or vendor. I wasn't sure what to expect at the NYC Camp [...]. [After participating in the event] I never got a sense of feeling inferior for lack of experience or an inability to code. We had really engaging and valuable sessions. [...] The experience came together for me during several discussions both in the sessions and on the side. Drupal is about community. The community builds, maintains, advocates, cautions, and develops the platform. [...] For me, this triggered the idea of giving back to the community in a way that made sense for us." Content editor and manager, M, 1 year. Retrieved 22nd May 2014, from https://assoc.drupal.org/content/guest-postwhy-olympus-gives-back-drupal under a CC BY-SA 2.0 license.
These perceptions of what can be considered contribution contrast with those represented in the main collaboration platform. In other words, the rationalization of certain activities as meaningful contributions according to the Drupal community's needs-the first interrelated layer of value conceptualized by Pazaitis et al. (2017)-mismatch with the systematization of the assessment of such activities to track and record such forms of value in the main collaboration platform-the second interrelated layer of value conceptualized by Pazaitis et al. (2017). This mismatch is illustrated, for example, in the main pages that explain how individuals could contribute to Drupal, as depicted in Figure 1.
On the one hand, encouragement and explanations of how to contribute to "object-oriented" activities (G 1 ) are represented on the "Get Involved" page (Drupal.org, 2014d) relating to contribution in the main collaboration platform. Some of them are differentiated and highlighted. For example, in the case of contribution activities related to source code (SG 1.1 ), there is an explicit distinction between "theming" and "backend" development.
On the other hand, "community-oriented" activities (G 1 ) are only partially reflected in user support, donations and marketing on the main page (see Figure 1). References can be found when a deeper navigation into the platform is made through less relevant and less visible spaces. For example, a sub-page named "Contribute to Drupal.org" (Drupal.org, 2014a), provides information about contributions related to the main collaboration platform itself. This area also refers to some of the "online community management" (SG 2.4 ) contributions. However, no explicit mention is made of the "organization and participation in face-to-face events" (SG 2.5 ) in primary and secondary levels of the platform. The first reference to events can be found only after navigating through more hidden and tertiary links in the "General Resources" section to the Drupal Groups (Drupal.org, 2014c), which allow participants to start browsing by geographical location after several steps.
Overall, this analysis shows a need to widen our understanding of contribution activities beyond the traditional view of source code or other "object-oriented" activities, and the existence of differences with regard to the internal perceived value. Additionally, evidence is provided with regard to the lack of visibility of "community-oriented" activities in the main collaboration platform. To further understanding of this lack of visibility, the next section explores the representation of the identified contribution activities at an individual level, by studying user profiles.

Representation of Contribution Activities in User Profiles
User profiles have been previously identified as a key element in the generation of other participants' perceptions in FLOSS communities (Marlow et al., 2013). They are an important source of public references, used to evaluate the reputation of other members, and play a significant role in the process of status attainment in FLOSS communities (Stewart, 2005). In Drupal, there are several ways to access profiles. The main way, however, is the main profile page at Drupal.org. Tables 2, 3 present a summary of the analysis carried out to study how the identified activities are represented on the main collaboration platform in individual profiles for the "objectoriented" and "community-oriented" groups, respectively. The analysis was carried out in all platforms and sub-platforms (e.g., https://groups.drupal.org, https://localize.drupal.org, or http:// assoc.drupal.org) that form part of the main platform of collaboration. The nomenclature for the subgroups is the same as previously employed in Table 1. For those which are fully or partially represented, the items employed in user profiles and the quantification of the activities, if any, are detailed in the column for observations. Figures illustrating these items are also referred to in this column, and presented subsequently in Appendix A in Supplementary Material.
The analysis shows an uneven representation of contribution activities in user profiles at Drupal.org. Overall, this affects the activities within the "community-oriented" category (G 2 ) far more than those in the "object-oriented" category (G 1 ). The exceptions for G 1 are "design" (SG 1.4 ) and "custom projects" (SG 1.1.3 ). In the case of the former, it was found that, as we shall see with "community-oriented" activities, Drupalistas use generic open text fields to overcome these limitations. For the case of the latter, the lack of representation can be explained on the basis of the lack of perceived value of code outside the main platform of collaboration. These projects are not subject to community peer-reviewing processes and are commonly disregarded, as I 10 explains: The most prominent lack of representation is found within the "community-oriented" category (G 2 ) and it is especially significant for contribution activities related to the organization of and participation in local events (SG 2.5.1 ), DrupalCamps and role-oriented events (SG 2.5.2 ). In these cases a prominent use The clearest exception found regarding the lack of representation of community-oriented activities was the indicator of mentorships, depicted in area CO 3 of Figure 2. This indicator allows recognition to be given to Drupalistas as mentors and, reciprocally, users can indicate, on their profile, who has mentored them. This goes in line with a more general need of the community to find indicators which visibilize "communityoriented" activities, as indicated by the emergence of initiatives (Drupal.org, 2014b;Nordin, 2014) to improve how activities are represented in user profiles at Drupal.org, to "[...] go beyond 2 | Summary of profile elements for "object-oriented" contribution activities (G 1 ).

Activities for subgroup Degree of representation Observations
Core project (SG 1.1.1 ) Fully represented In the main profile by four checkbox items, such as "I contributed Drupal modules" and "I contributed Drupal patches" (see Figure A.1 in Supplementary Material). They are quantified by number of commits (see Figure A.2 in Supplementary Material).
Contributed projects (SG 1.1.2 ) Fully represented In the main profile by six checkbox items, such as "I contributed Drupal modules," "I contributed Drupal themes," and "I reviewed project applications" (see Figure  code creation activity and into more community-oriented contribution stuff, since that's also a huge part of what makes Drupal healthy." This example of peer-to-peer mentorship references indicates the path and will to follow in that direction of recognition of "community-oriented" contributions. In sum, this analysis of user profiles provides, firstly, a descriptive account of how the contribution activities identified in the previous subsection are represented in different user profiles on the main collaboration platform; but most importantly the analysis provides empirical evidence of the uneven representation of certain contribution activities, affecting especially those identified as "community-oriented." It has been seen, however, that "community-oriented" activities, such as these are understood as a type of contribution and play a key role in the sustainability of the community, as shown in the first section; but in spite of this relevance to fostering collaboration, they are commonly not recorded and unequally represented in the main collaboration platform, as seen in this last section.

DISCUSSION AND CONCLUDING REMARKS
Our research explored perceptions of value and how such forms of value are reflected in the platforms employed for coordinating a large case of CBPP. We provide two main contributions for the literature on FLOSS and, more widely, for the literature on CBPP.
Firstly, our exploration of the rationalization of certain activities as meaningful contributions according to the internal logics of value shows the need to broaden our understanding of valued contributions. We provide evidence of the perception of identified "community-oriented" forms of contribution, how they are valued as well as their relevance for the sustainability of the community.
Secondly, through an analysis of the representation in the main collaboration platform, we contribute empirical evidence of the uneven representation of some of these contribution activities, affecting especially those identified as "communityoriented." Next, we detail each contribution and provide implications for future research.
Talk Is Silver, Code Is Gold? Beyond "Code-Centrism" in FLOSS and "Object-Centrism" in CBPP A few studies on the level of commitment in FLOSS moved the focus from code contribution to explore communication contributions (Crowston and Howison, 2006) and support contributions (Lakhani and Von Hippel, 2004). Furthermore, Coleman's (2013) work on FLOSS and hacker culture showed a relationship between face-to-face events and the political, moral and affective dimensions of FLOSS communities. "Objectcentrism" is, however, still commonly present in the studies of FLOSS and, more widely, in studies of CBPP communities (e.g., Kittur et al., 2007;Haklay et al., 2010;Neis and Zipf, 2012;Crowston et al., 2013). In spite of having received less attention in the literature, we show how "community-oriented" contribution activities, such as the organization of events, are indeed understood and valued as contributions. Furthermore, we show how they are fundamental for the sustainability of the community. A modest hackathon organized in a small venue, for example, may not be at first sight perceived as the most relevant way to contribute to the global project. Nevertheless, as shown in this study, the interactions which occur in these spaces are key to increasing collaboration beyond solitary endeavors when contributing (Chełkowski et al., 2016, p. 16), the commitment to participate in the community, humanizing it and increasing the diversity of participants.
The issue identified in this research is not particular to this case study, nor is it specific to the time period (2013)(2014)(2015)(2016) in which this study was carried out. Overall, there is a lack of common ways to measure intangible forms of value as those identified in this study as a result of a "value crisis" (Arvidsson and Peitersen, 2013), which has also been described in other 3 | Summary of profile elements for "community-oriented" contribution activities (G 2 ).

Activities for subgroup Degree of representation Observations
Usage and support (SG 2.1 ) Partially represented In the main profile for the internal forums by the checkbox item "I help in the Drupal support forums" (see Figure 1). They are not explicitly quantified, but they are present in the secondary tab "Posts" (see Figure  CBPP communities (e.g., Jemielniak, 2014, p. 39-40;Chełkowski et al., 2016, p. 13-14). In this respect, the implications for research are two-fold. Firstly, on the need to consider these less visible forms of value when carrying out studies of such communities. Secondly, on understanding its dynamic nature since, as we have seen, new contribution activities may emerge and be considered valuable over time according to the internal logics of value. Further work could explore forms of value, such as those which emerged from this case study in a wider range of CBPP communities. Furthermore, studies to compare "object-centric" contributions, such as the numerous studies on the number of code commits in FLOSS referred to in section Conceptual Background, with respect to "community-centric" contributions could be carried out. A mixed-methods approach triangulating qualitative data, as from this study, with quantitative data, for example carrying out a Social Network Analysis of the identified networks of mentorship, would offer opportunities to further our understanding of the development and changes experienced over time in the acknowledgment and distribution of value in CBPP communities. The quantitative side could be undertaken, for example, by the study of the networks and the changes experienced over time of "community-oriented" contributions, which could also be compared with networks of "object-oriented" contributions. In addition, this approach would offer the possibility to carry out comparative studies of the characteristics, such as gender, age, or location, of the participants who perform these activities.
In sum, we hope the questioning of our understanding of contribution in FLOSS and CBPP carried out in this research will help researchers to frame studies on the forms of value present in such communities from new perspectives.

Recording and Representation of Value in Collaboration Platforms
We extend FLOSS and CBPP literature by providing a descriptive account of how the contribution activities identified in the previous subsection are represented on different user profiles on the main collaboration platform; but most importantly the analysis provides empirical evidence of the uneven representation of certain contribution activities, affecting especially those identified as "community-oriented." Hence, not only "community-oriented" activities, such as these are understood as a type of contribution and play a key role in the sustainability of the community, as previously discussed; but they are commonly not recorded and unequally represented in the main collaboration platform. In other words, by drawing on the three layer system of value for CBPP communities developed by Pazaitis et al. (2017), we found a mismatch between the (1) production of value and the (2) record of value. This unequal representation was found at an "official" level, such as in the main sections of the platform dedicated to contribution, as well as at an individual level, such as in the study of user profiles.
Overall, "community-oriented" contributions are poorly represented in the main collaboration platform as compared to "object-oriented" ones. This disjunction between the relevance and lack of visibility of "community-oriented" contributions casts doubt on the "object-centric" belief traditionally present in CBPP communities, illustrated by the motto "Talk is silver, code is gold" for the specific case of FLOSS communities.
The lack of representation of "community-oriented" activities found in this study cannot be understood as due solely to sociocultural reasons. The "code-centric" character of the community offers only a partial explanation. Technical limitations also have a major impact. For example, while certain activities are easily quantifiable (e.g., the number of commits of source code, or the number of edits of wiki pages), others are more difficult to quantify or represent in concise, useful ways. As we have seen, the issue is not exclusive to Drupal and other FLOSS communities. For example, Jemielniak (2014) identifies the number of edits in Wikipedia as "one of the few quantified measures of usercontribution value [...] Everybody on Wikipedia knows that [...] is flawed [...], but in the absence of other quantified indicators, it is used nevertheless" (p. 40). In other words, the main challenge resides in the difficulty to provide indicators to acknowledge and aggregate the value of some types of contribution, or to find interoperable ways to have this value recognized by other communities; an issue that is under exploration by researchers (De Filippi and Hassan, 2015) as well as CBPP communities 10 themselves. The Drupal community is also attempting to find suitable indicators, as illustrated when discussing peer-to-peer mentorship references.
Thus, a broader understanding of the notion of contribution also has implications for the provision of indicators that acknowledge, aggregate and incorporate these forms of value in the technical artifacts employed to support the organization of peer production. This aspect is particularly relevant for large and global CBPP communities as they scale up since, due to their growth and their global character, the generation of perceptions between unknown members becomes more frequent in these communities, and the role of the platforms employed to support their self-organization (e.g., through the creation of trust) becomes more crucial. In this respect, the potential of blockchain technologies to facilitate the dynamics of social sharing, as proposed by Pazaitis et al. (2017), offers the possibility to experiment with new systems of value in which to record the perception of such actions as meaningful or not with respect to the internal social totality of these communities themselves (Graeber, 2001). In other words, these decentralized technologies are offering novel opportunities  for the development of open and transparent indicators expressing the different dimensions of value in CBPP, including those which have remained less visible, and their impact could lead to the emergence of innovative ways for commoners to coordinate, scale up self-governance or share these forms of value amongst different CBPP communities in interoperable ways.
Future research should investigate the indicators of value and the various models of distribution of value which are emerging in CBPP, such as those identified in this case study. Overall, this broader understanding is also relevant for more technical fields, such as Computer Science, as well as research initiatives aiming to develop platforms to support and foster the development of CBPP. For example, a high degree of flexibility is expected for the design of mechanisms that indicate forms of value in the collaboration platforms employed by these communities. In other words, rather than creating tools which impose "onefits-all" indicators, such as "likes, " a broader understanding of contribution in CBPP implies, for these platforms, the need to offer mechanisms that enable communities to define these indicators dynamically, allowing them to reflect the results of their processes of negotiation of what is considered valuable.
In sum, there remains a need to further our understanding of the provision of indicators which measure and aggregate less visible forms of value, as well as how to incorporate them into the technical artifacts employed to support the organization of CBPP. We aim for the identification and evidence of the lack of visibility of "community-oriented" activities presented in this study to contribute to furthering our understanding on how to recognize and incorporate such forms of value.

DATA AVAILABILITY STATEMENT
The datasets presented in this study can be found in online repositories. The names of the repository/repositories and accession number(s) can be found at: https://davidrozas.cc/lab/ drupal_planet_archive.php.

ETHICS STATEMENT
Ethical approval was not provided for this study on human participants because in order to ensure this study fulfills the ethical principles described by the University of Surrey, an evaluation was undertaken as to whether this study should be referred to the University Ethical Committee to seek an ethical review. This research did not fall into any of the categories described by the Ethical Principles Procedures for Teaching and Research (http://www.surrey.ac.uk/fhms/Ethics%20Committee/ ethicsfiles/Ethical_Principles_and_Procedures.pdf), and hence, it was concluded that it was unnecessary. Nevertheless, the study was carried out considering the recommendations at all times. For example, when the processing of personal data required the personal consent of the participant, such as in the case of qualitative interviews, the process was carried out according to the suggested Data Protection Act (1998). In addition to the guidelines provided by the University of Surrey, the Recommendations from the Association of Internet Researchers Ethics Working Committee (http://aoir.org/reports/ethics2.pdf) were evaluated and constantly considered during the course of this study. This document provides a set of guidelines to facilitate the process of ethical assessment in the field of Internet studies, as well as a set of common questions to help the researcher to raise ethical considerations. The patients/participants provided their written informed consent to participate in this study.

AUTHOR CONTRIBUTIONS
DR coordinated the elaboration of the paper and participated in all the phases, including data collection, conceptualization, literature review, structuration, analysis, and overall writing of the article. NG, PH, and SH discussed the paper's general approach, reviewed the paper, and contributed to parts of it across all sections. All authors contributed to the article and approved the submitted version.

FUNDING
This work was partially supported by the project P2P Models (https://p2pmodels.eu) funded by the European Research Council ERC-2017-STG (grant no.: 759207) and by the project Chain Community funded by the Spanish Ministry of Science, Innovation and Universities (grant no.: RTI2018-096820-A-100).