Architecture

The Architecture Working Group

The architecture working group is in charge of developing the overall architecture for the GPII and for overseeing its implementation. This includes the general architecture and defining all of the standards for communicating between the different elements of the architecture.

Useful Starting Points

To learn more about the GPII Architecture and how it works, read these pages first:

• GPII Architecture Overview
• GPII Technical Governance
• Security and Privacy
• GPII Development Platform
• Models for Deploying and Scaling the GPII
• Setting Up Your Development Environment
• Architecture Dashboard

Participation

The architecture group uses a mail list, weekly meetings, and this wiki to carry out most of its work. Participation in the working group is open to all subject to the standard working group participation criteria. These criteria are easy to meet and designed only to ensure that our work remains open and free and that all feel welcome to participate.

Meetings

Most of the GPII architecture work (including Cloud4All and Prosperity4All) is done asynchronously via the architecture mailing list. Anyone can join the list and participate. We meet synchronously once a week to discuss major issues, provide updates on our work, and plan our next steps:

• Wednesdays at 16:00 UTC / 18:00 CET / 19:00 EET / 12 Noon EST / 10 am MST

We meet on the GoTo Meeting server. Log in as a guest.

Mailing List

• Subscribe to the architecture list
• Read the architecture list archives

Source Code

The Cloud4all/GPII source code is open source and available to everyone. We use Github for all our development. See also Source Code.

Issue Tracker

Issues with the GPII architecture and codebase are managed in the GPII JIRA at http://issues.gpii.net/.

See also How to Write a Good Bug Report.

Releases

Note: We have moved away from creating "releases" and now keep version-agnostic installation instructions synchronised with the state of the code repository.

Contributing to the GPII

• Setting Up Your Development Environment.
• GPII Technical Standards.
• Coding Conventions.
• Licensing (licences to use in source files and documentation).
• Implementation APIs: lists what GPII needs to know about an application in order to integrate it.
• Building A Simple Solution: explains how to integrate an existing application into the GPII as a solution.
• Architecture - Available transformation functions: explains how to write transformers that translate settings expressed as common terms into settings expressed as application-specific terms.
• Writing Acceptance Tests: explains how to write acceptance tests for application integrated into the GPII.
• Debugging with Node Inspector.
• How to Write a Good Bug Report.

Demonstration Releases

• Linz Planning - July 9-13, 2012, Geneva, Switzerland
• WSIS Planning 2012 - May 14-18, 2012, Geneva, Switzerland.

Currently Active Members in the Architecture Working Group

• Colin Clark (IDRC, Toronto, Canada)
• Antranig Basman (Raising the Floor International, Cambridge, UK)
• Steve Githens (Raising the Floor US, Carlsbad, CA)
• Kasper Markus (Raising the Floor International, Copenhagen, DK)
• Gregg Vanderheiden (RtF, Geneva and Trace Center, Madison, USA)
• Javi Hernandez, (RtF, Brussels, BE)
• Avtar Gill (IDRC, Toronto, Canada)
• Joseph Scheuhammer (IDRC, Toronto, Canada)
• Steve Lee (Open Directive, Exeter, UK)
• Michelle D'Souza (IDRC, Toronto, Canada)
• Tony Atkins (Raising the Floor International, Amsterdam)
• Simon Bates (IDRC, Toronto, Canada)
• Cindy Li (IDRC, Toronto, Canada)

GPII Committers

The full list of active GPII committers is available on the technical governance page and in our Github Organization.