Calypso Operations (Draft for Review)

Calypso (Open Metadata and Governance) Operations

The Calypso project provides content (standards, data, code and documentation) that is intended for wide consumption across many types of organizations - from those that rely on data in their operation to organizations that have products or technology designed to help manage data and its related processing.

A project of this scope requires input from a wide range of subject matter experts with different backgrounds and allegiances. As such we need a set of principles, roles and operating practices to ensure the results of our contributions are useful, have high quality and are widely consumable.

General principles

The principles set the tone of the operation of Calypso:

• The activities of the project encourage open collaboration. Through this open collaboration we aim is to build a community of people who are contributing to the project.
• The scope of the content is determined by the individuals who are actively contributing.
• The resulting content is publicly available but protected by the Apache 2.0 license.
• An individual's privileges and position is awarded through their contribution and engagement.

These principles should be respected as the procedures used to manage the Calypso project evolve and mature.

What does it mean to be part of the Calypso community?

There are different roles in the Calypso project.

Calypso project members

Anyone can become a member of the Calypso community by signing up to the mailing list. As a member you are able to attend our meetings, just to listen, or to play an active part in the discussion.

When you attend your name will be recorded in the meeting minutes along with any remarks or suggestions you make.

The agenda and minutes of our meetings are publicly available on the data-governance wiki.

A member may make contributions to the Calypso content by submitting a Git change (Patch or a Git Pull Request) to the Calypso maintainers.

Calypso project maintainers

Maintainers are members of the Calypso community that have permission to change the Calypso content. This may be content that they have created themselves, or has been provided by another member.

The initial list of maintainers is drawn from the individuals that created the open metadata and governance content that seeded the project. New maintainers are voted onto the maintainers list by the existing maintainers. The individual sends a note requesting to be made a maintainer, listing their contributions to date to the maintainers distribution list. The maintainers vote and if a majority agree then the requester is added to the maintainers list and given write access to our GitHub.

Data Governance PMC Leader

The data governance PMC is responsible for planning and release management of the Calypso content. Calypso project members can join the PMC meetings and contribute to the discussion.

The data governance PMC has a leader. This position is appointed annually by election by the Calypso maintainers. The position is currently held by Mandy Chessell and expires at the end of 2018.

Calypso project meetings

Some meetings are face-to-face, but most are conference calls.

Attendance is open to all. Conference calls can be joined without an explicit invitation. However, due to physical security requirements at some of the venues we use, it is necessary to ensure you are added to the invitee list of any face-to-face meetings that you wish to attend and complete the necessary formalities for the venue.

For example the face-to-face meeting may be at a conference that requires you to register for the conference to attend. Or an meeting may be at an organization's offices that are required to maintain a list of everyone on site.

Irrespective of whether a meeting is face-to-face or a web conference, all meetings are advertised in the ODPi calendar, the agenda is published before the meeting in the data-governance wiki and the minutes are added once the meeting is complete.

Calypso on Slack

Calypso uses the ODPi's slack community to provide an ongoing dialogue between members. This creates a recorded discussion of design decisions and discussions that complement the project meetings.

Calypso email

Calypso has a number of distribution lists used to advertise events and news for the community.

Calypso content management tools

The Calypso content is managed in GitHub under https://github.com/odpi/data-governance. It may be developed using patches, branches from master, or forks/git pull requests. Each change should have either a Jira or Git issue explaining why the change is being made. The new or updated content should follow the Calypso developer guidelines.

The ODPI Jira system can be used to describe and manage large enhancements to Calypso since it has support for epics and user stories and tasks. Git issues are adequate for tracking simple defect fixes.

Calypso project releases

The Calypso team aim to create an official release of the open metadata and governance capability twice a year. This release will be available to include in products and other technology through Maven's Central Repository, or through a download from the ODPi site.

In between official releases, the latest build is also available to developers, through the ODPi site.