P2Pvalue – Techno-social platform for sustainable models and value generation in commons-based peer production in the Future

Programme: FP7-ICT-2013-10 Project: 610961 Start date: 2013-10-01 Duration: 36 months

Deliverable D5.1

Website and P2Pvalue node

Submission date: 2014-03-21

Organisation name of lead contractor for this deliverable: UCM

Dissemination Status PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) P2Pvalue Deliverable 5.1

Document information

1.1 Author(s)

Author Organisation E-mail Pablo Ojanguren UCM [email protected] David Rozas UniS [email protected]

1.2 Other contributors

Name Organisation E-mail Samer Hassan UCM [email protected] Nigel Gilbert UniS [email protected]

1.3Document history

Version# Date Change V0.1 2014-03-14 Starting version - Draft V0.2 2014-03-19 Added section 1 V1.0 2014-03-20 Approved version to be submitted to EU

1.4Document data

Keywords P2Pvalue CBPP Kune Wave Collaboration Editor address data [email protected] Delivery date Month 4

1.5Distribution list

Date Issue E-mail Consortium members [email protected] Project officer [email protected] EC archive [email protected] .eu

II Website and P2Pvalue node

P2Pvalue Consortium

University Of Surrey (Coordinator)

Centre National De La Recherche Scientifique

Stichtung Peer To Peer Alternatives (P2P Foundation)

Universitat Autònoma De Barcelona

Universidad Complutense De Madrid

Università Degli Studi Di Milano

III P2Pvalue Deliverable 5.1

Project objectives

The project’s objectives are:

• Development of a software platform o Understand, experiment with, design and build a collective intelligence techno-social federated collaborative platform that will foster the sustainability of communities of collaborative production. o Deploy several customised nodes of the federated platform in which real-world communities will interact, participate, and collaboratively create content • Theory and Policy o Develop CBPP theory, based on multidisciplinary and multi-method research on CBPP, and determine the factors for success, productivity, and resilience in communities (“best practices”). o Develop a set of value metrics and reward mechanisms that incentivise the participation of citizens in CBPP. o Simulate the new sustainability models proposed, showing how robust they are in the face of diverse community conditions. o Verify the compatibility of the proposed models with innovation policies and provide a series of policy recommendations for public administrations to encourage CBPP-driven social innovation. • Data and Resources o Provide a directory of existing CBPP communities, together with their main characteristics. o Maintain an open web-based CBPP archive, with the collected data-sets, surveys, reports, Open Educational Resources and open-access publications, freely available to other researchers and third-parties under an open copyleft license. This includes a project public repository with all code available as free/open source.

IV Website and P2Pvalue node

Executive Summary

This deliverable reports the results of the work performed during the first four months of the project to set up a project Website and a set of communications tools for the project based on an early version of the P2Pvalue platform.

V P2Pvalue Deliverable 5.1

Contents

1 The P2Pvalue Website...... 1 Main sections of the site...... 1

2 The P2Pvalue platform node...... 9 Platform background...... 9 Infrastructure and Development...... 10 Current Platform Features...... 11

3 References...... 16

VI 1 The P2Pvalue Website

The P2Pvalue website has been built using QScience (QScience, 2014), a free/libre/open source software (FLOSS) platform tailored to support the needs of modern scholarly communities developed as part of the FP7 project QLectives (QLectives, 2014). QScience is based on the FLOSS content management framework Drupal (Drupal.org, 2014), used by at least 1.9% of the websites worldwide (W3Techs, 2014). The platform has been customised to allow collaborative production, but also ensuring that certain functionalities are only accessible to specific sets of users in a granular way. This has being achieved by providing a different set of permissions depending on the role of the user. For example, users holding a “consortium member” role can add new blog posts, but they cannot access administration tasks such as the creation of backups. Additionally, user manuals were created for the consortium members. The production site is hosted at the University of Surrey and can be reached at http://www.p2pvalue.eu/ A testing instance is also hosted in a different server at the University of Surrey at http://www.drupal-research.org/p2pvalue The code is publicly available in the P2PValue Github project page at https://github.com/P2Pvalue/p2pvalue-website-code. An early version of the website was made public in mid October 2013, and the completed website with professionally designed and crafted styling was available from March 14, 2014. The following section provides a brief tour of the main areas of the site.

Main sections of the site

The frontpage is being used to highlight the latest news of the project (for example the recent P2PData Jam event) and is being edited collaboratively by several members of the consortium (http://www.p2pvalue.eu/home).

1 The “Blog” section (http://www.p2pvalue.eu/blog) displays the latest blog posts created collaboratively by the members of the consortium:

2 The “Project” section (http://www.p2pvalue.eu/project) consists of a set of static webpages, describing the “Concept and objectives” (http://www.p2pvalue.eu/project/concept-and-objectives) the “Work plan” (http://www.p2pvalue.eu/project/work-plan), the “Work packages” (http://www.p2pvalue.eu/project/work-packages) and the “Milestones” (http://www.p2pvalue.eu/project/milestones).

3 The “Consortium” section also consists of static pages, offering information about the institutions that form the Consortium (http://www.p2pvalue.eu/consortium) and the “Stakeholder Board” (http://www.p2pvalue.eu/consortium/stakeholder-board).

The “People” section displays the information of all the members of the consortium:

4 The profiles can be updated directly by the members of the consortium accessing his/her profile:

5 The “Publications” section consists of a set of static pages with information about the “Project Deliverables” (http://www.p2pvalue.eu/publications/project-deliverables), “Presentations” (http://www.p2pvalue.eu/publications/presentations), “Journal articles” (http://www.p2pvalue.eu/publications/journal-articles) and “Working Papers” (http://www.p2pvalue.eu/publications/working-papers).

The “Contact” section provides a contact form whose messages are forwarded to [email protected]:

6 Finally the “Engage” section (http://www.p2pvalue.eu/engage) provides a list of the different ways to engage with the project: social media channels, newsletter, mailing list, etc. Some of these channels are highlighted in the site, by including blocks displayed in all the pages with links to them, the latest stream, etc.

7 8 2 The P2Pvalue platform node

Platform background

The P2Pvalue platform is being developed on the top of an existing free/libre/open source software (FLOSS) tool named Kune (Kune, 2014). Kune is collaborative software licensed under the GNU AGPLv3 license (GNU, 2007) that encourages the use of FLOSS web services. It is based on robust technology and several existing software projects and protocols: • GWT Framework: Google’s FLOSS framework to develop Web applications (Hanson & Tacy, 2007) • The Apache Wave open protocol for collaborative/real-time editing in federated environments (Wave, 2010) • The XMPP (Saint-Andre, 2011) open protocol for the chat and notifications system.

Although Kune's stage of development is Beta (i.e. a stable prototype still with bugs and under testing), it is an appropriate stable starting point to develop the features of the P2Pvalue platform. The project will tackle improvements and general issues in order to take the initial platform in a further step of quality, sharing its improvements with the mentioned Kune and Apache Wave.

In addition to the base software platform development, new features will be provided by the development of new pluggable runtime components called “Gadgets” ( ~Apps) which can be embedded within the documents.

9 Infrastructure and Development

The platform node is publicly available at this address: http://platform.p2pvalue.eu ready to be used by the different partners of the P2Pvalue project.

In order to provide a reliable service we have additional infrastructure that we have set up during the past months:

- A test environment (a.k.a. Staging, Preproduction or UAT environment) at

http://platform.p2pvalue.eu:10000

This is a mirror of the previous public node used to test new functionality, bug fixes and investigate issues without the risk of real and personal data loss or poor quality of service during those processes.

The server infrastructure for both services is provided by the FLOSS-friendly EU-based company OVH, with Debian GNU/Linux machines.

In order to manage the software development process we rely on the following services:

- An internal Git (Loeliger & McCullough, 2012) repository hosted by the UCM / Grasia Research Group providing the source code version control system, with visible access from

http://grasia.fdi.ucm.es/p2pvalue/redmine/projects/kune/repository and with public mirrors in the well-known Git services

GitHub: https://github.com/P2Pvalue : https://gitorious.org/p2pvalue

- A software development management tool and issue tracker at

http://grasia.fdi.ucm.es/p2pvalue/redmine

10 with a valuable Wiki section for technical topics at

http://grasia.fdi.ucm.es/p2pvalue/redmine/projects/kune/wiki and a Scrum Project management add-on named Scrum2B.

Concerning the Scrum agile methodology (Rising & Janoff, 2000) we follow a continuous integration (Duvall, Matyas & Glover, 2007) approach in the software engineering process where continuous compilation and and test of the software is performed from : https://travis-ci.org/P2Pvalue/kune

Current Platform Features

The node is intended to provide collaborative spaces to the whole P2Pvalue project as well as to specific working groups, e.g. workpackages, partners, task-related groups. As long as users are registered in the platform they can participate in any group at any time.

Users and group spaces share a same visual aspect and tools:

At this moment three working groups are hosted:

11 • The P2Pvalue project group - the collaborative space for the project itself to work and communicate on the project’s specific topics. For example, a discussion list for the WP leaders is currently in use there.

• The P2Pvalue platform open group - it stands for the users of the node/platform in general. Issues and discussions about the software itself should be handled there.

• The UCM P2Pvalue group - specific group for the platform’s development team from the UCM. For example, WP3 work scheduling is managed here with a shared calendar and a shared scrum task summary board.

Along with these examples, the platform in general provides to users and groups

• Online spaces • Author text documents with collaborative real-time edition • Management and sharing calendars (integration with 3rd party tools such as ) • Management of discussion lists • Sharing polls, videos and other collaborative tools • Chat and group-chatrooms • Management of friendship-relations

Some examples of the platform tools follow:

Documents tool with a folder organization:

12 Example of embedding a video Gagdet to a document:

13 View of the calendar tool and an appoinment:

14 A view of the Inbox space, from where users can manage all the conversations and documents they are working with:

15 3 References

• Comunes Nonprofit, Kune Project (Accessed in March, 2014): http://kune.ourproject.org • GNU (2007) : GNU Affero General Public License http://www.fsf.org/licensing/licenses/agpl-3.0.html • Hanson, R., & Tacy, A. (2007). GWT in Action: Easy Ajax with the . Dreamtech Press. • Apache Software Foundation (2010), Apache Wave project in Apache Incubator: http://incubator.apache.org • Saint-Andre, P. (2011). Extensible messaging and presence protocol (XMPP): Core. Internet Engineering Task Force. RFC 6120 (based on 2004 version RFC 3920). • Loeliger, J., & McCullough, M. (2012). Version Control with Git: Powerful tools and techniques for collaborative software development. O'Reilly Media. • Rising, L., & Janoff, N. S. (2000). The Scrum software development process for small teams. IEEE software, 17(4), 26-32. • Duvall, P. M., Matyas, S., & Glover, A. (2007). Continuous integration: improving software quality and reducing risk. Pearson Education. • W3Techs, “·Usage of content management systems for websites”, (Accessed in March, 2014): http://w3techs.com/technologies/overview/content_management/all • QScience, (Accessed in March, 2014): http://qscience.inn.ac • QLectives, (Accessed in March, 2014): http://www.qlectives.eu/ • Drupal.org, (Accessed in March, 2014): https://drupal.org/

16