MOU-2.1(pdf)

Memorandum of understanding for TANGO Collaboration
The European Synchrotron Radiation Facility, hereinafter referred to as “ESRF”
located at 6, rue Jules Horowitz, BP 220, F-38043 Grenoble, France
Represented by …..
Preamble
TANGO is an open source distributed control system toolkit. In order for TANGO to evolve and
continue to profit a maximum of people the TANGO Collaboration has been created to steer the
direction of TANGO and to facilitate decision making. This document describes how the
collaboration is managed.
Article 1
Collaboration Membership
1 - 1 Collaboration membership
Membership of the collaboration management board is obtained by signing the Memorandum
of Understanding (MOU) for Tango collaboration (this paper) and if the collaboration
executive committee agrees (cf. below). An institute is free not to sign the MOU and use
TANGO and come to the TANGO meetings. Not signing simply means the institute or
individual is not part of the TANGO management board and therefore does not have a right to
vote (cf. below) on TANGO issues.
1 - 2 Membership type
A member of the collaboration management board is either considered as a “Contributor” or
as a “Committer” .
•
A Committer must contribute resources to the collaboration, and is responsible of one
or more TANGO core packages.
•
A Contributor can propose code modifications to the committers for TANGO core
packages and / or submits TANGO Device classes to the public TANGO Device
classes repository.
Article 2
Management Structure
2 - 1 Collaboration management structure
The collaboration management structure is made up of three levels:
•
•
•
Executive Committee
Collaboration Coordinator
Project Leads
Signed
Collaboration
Agreement
Executive
Committee
Collaboration Coordinator
Project Leads
Article 3
Executive Committee
3 - 1 Executive committee members
The executive committee makes the strategic decisions about developments in the TANGO
collaboration. There should be one member from each institute who has signed the
collaboration memorandum of understanding (this paper). The member should be the person
who is highest in each institute's hierarchy and has sufficient technical knowledge about
TANGO. This representative should have enough power to decide on allocating resources to
developing software for Tango. To ensure that the right decisions are made and match those of
the user community, advice must be sought by the committee from their respective users and
developers on a regular basis.
3 - 2 New executive committee member
The existing collaboration members are free to accept an institute as a new member or not. A
unanimous decision has to be taken by the executive committee members before a new
member is accepted.
3 - 3 Executive committee meeting
The committee will meet at least just after the TANGO collaboration meetings.
3 - 4 Executive committee decision
The TANGO executive committee has the role of making decisions in the TANGO
community. Decisions are required whenever the collaboration coordinator or the executive
committee thinks it is necessary to have an official TANGO decision. Decisions are made by
voting. At least 2/3 majority is required (equal or greater) to have an official decision. The
vote of each executive committee member is weighted according to its status as collaborator
and committer (cf. above). Each committee member has at least a weight of 1. An extra vote
is acquired if the committee member represents an institute which is also a committer to at
least one of the TANGO core packages. The weight is re-evaluated every year. The members
weight will be available in the Tango Web site (http://www.tango-controls.org). In case the
total weight number is not a multiple of 3, the threshold to take a decision will be rounded
down.
Article 4
Collaboration Coordinator
4 - 1 Collaboration coordinator rule
The collaboration coordinator is the center of the organizational structure and liases between
the project leads and the executive committee. The collaboration coordinator will chair the
executive committee meetings and is responsible for informing the collaboration of the
strategic decisions made at these meetings. The management responsibilities of the
collaboration coordinator will include:
•
organize and coordinate the executive committee meetings, to produce a report of the
committee meeting and to give feedback to the TANGO community
•
maintain a project plan for each task, including requirements, schedule, resource
requirements
4 - 2 Collaboration coordinator designation
The collaboration coordinator is elected by the executive committee for a minimum period of
2 years. He/she should be a staff member of one of the collaboration members. In case of
repeated problems with the executive committee, the committee can decide to revoke him/her.
The collaboration coordinator election/revocation follows the rules described in rule 3-4.
Article 5
Tango Core Software, Project Leader
5 - 1 Tango core software
Besides the Tango core libraries, several packages are considered part of the Tango controls
system core. A list of these packages is maintained up-to-date by the collaboration coordinator
and any changes to this list are decided by the executive committee. Each package which is
part of the Tango core has to have a project lead in charge.
5 - 2 Project leader
Each identified project (task) must have a project leader. For the Tango community, the
project leader is the contact person for all questions/remarks concerning that particular
project. He/She is in charge of following the project schedule and ensuring the requirements
are satisfied. In case of problems impacting on other Tango project(s), the project leader refers
questions to the collaboration coordinator and eventually to the execute committee. The
project list and their respective leaders will be available in the Tango Web site
(http://www.tango-controls.org)
Article 6
Tango Collaboration Meeting
6 - 1 Tango collaboration meeting frequency
Tango collaboration meeting is held at least once a year. In addition to these meetings, regular
video-conferences or meetings of working groups on particular Tango projects are to be
encouraged.
6 - 2 Tango collaboration meeting organisation
The TANGO collaboration meeting should be organised by one of the collaboration members
by rotating in a round-robin fashion. The collaboration members are entitled to request a
registration fee from the collaboration meeting attendees to cover the costs of the meeting.
Article 7
Planning
7 - 1 Deadlines
The parties shall make their best efforts to comply with the deadlines and action plans
7 - 2 Delays
If an action is, or has to be delayed for any reasons whatsoever, the project leaders shall
inform the collaboration coordinator and their respective management as soon as possible, and
take all required measures to reduce the delay as much as possible.
Article 8
Financial Conditions
8 - 1 Costs
Unless otherwise provided in an implementing agreement, each party shall bear all its costs
and expenses connected with the fulfillment of the agreement. This shall include all
manpower costs as well as each party's personnel, travel and subsistence costs.
Article 9
Intellectual Property, Exchange of Information, Publications
9 - 1 Knowledge sharing
For the purpose of collaboration the parties will make available to the others, free of charge,
their existing knowledge and the knowledge generated in the frame of this co-operation,
protected or not, pertinent to the fields of this co-operation.
9 - 2 Licensing
All software that is going to be developed in the framework of the collaboration as well as the
software already produced in the Tango project will be published under the GNU General
Public License agreement (http://www.gnu.org/copyleft/gpl.html) or the GNU Lesser General
Public License (http://www.gnu.org/licences/lgpl.html). Refer to the license text for the terms
and conditions for copying, distributing, modifying as well as running the software.
9 - 3 Publications
During the time of this collaboration any publications pertaining to the scope of the
collaboration shall be submitted to the collaboration coordinator. If no explicit objection is
made within 10 days after submission, the publication is deemed to be agreed upon.
Article 10
Liability
10 - 1 Liabilities
The parties undertake to act according to best knowledge. They do not, however, guarantee
completeness or correctness of knowledge made available or results achieved with the frame
of this collaboration. Hence, neither party will hold the other ones liable for any damage
resulting from the application of such knowledge and results.
Article 11
Withdrawal procedure
11 - 1 Member withdrawing
As soon as a member decides to withdraw, its executive committee representative will inform
the other partners of this decision. The software developed by the withdrawing party with the
collaboration has to stay free for non commercial purpose following the open source spirit. In
the same spirit, the withdrawing member can continue to freely use any software developed
with the collaboration.
Article 12
Entry into Force, Duration
12 - 1 Agreement duration
This agreement shall remain in force until a common decision to change this agreement is
taken.
For ESRF
Prof XYZ
….....................

Download Report