>
> |
| META TOPICPARENT |
name="WebHome" |
1. Purpose
The goal of this policy is to define membership within the GROWTH partnership in order to set expectations and provide a framework for effective and fair cooperation among individuals. Existing and future members of GROWTH are expected to make a meaningful contribution to the partnership where ‘a meaningful’ contribution includes, but is not limited to:
- Development of data analysis software, tools and techniques to facilitate and/or optimize coordinated observation within the GROWTH network
- Carrying out observations for GROWTH
- Perform data analysis to study astrophysical implications of GROWTH data sets
- Mentoring a student or postdoctoral research associate in GROWTH projects
- Teaching a data-driven discovery course as part of GROWTH’s education charter
- Management work within GROWTH
- Financial or in-kind support for personnel, hardware or telescope access time
2. Membership Categories
The following describes the categories of membership for individuals and/or organizations which fulfill the above requirements:
Principal Partners are the founding organizations in GROWTH plus any new institution that joins the GROWTH partnership. Principal partners have one or more representatives in the Management Team. New Principal Partners have the right to one seat in the Management Team.
Management Team Members
include the GROWTH PI, Co-PI and one or more Co-I(s) from each Principal Partner.
Full Members
are graduate students, post-docs or senior researchers/faculty members at Principal Partner institutions directly involved in GROWTH activities.
Junior Members
are undergraduate students who are part of the GROWTH summer research program or have conducted a research project on a topic relevant to GROWTH with a Full Member.
Collaborators are
individuals who are not considered Full Member, but who are approved to collaborate with GROWTH members on specific, proscribed GROWTH science analyses. Individuals can be proposed as collaborators only by GROWTH full members and they must be approved with a majority vote by the Management team.
Legacy Members
are former Full Members who are no longer active (e.g. have moved out of the field, or joined a different collaboration) but have a lasting contribution to the GROWTH partnership either through partial ongoing work or recent development (e.g. of software which they are still being consulted about).
3. Membership Process
Membership in GROWTH is open to any researcher who is willing to make meaningful contributions to GROWTH’s scientific or educational goals. New membership requests should be submitted to the GROWTH PI (also the Chair of the Management Team) in writing and should include a concise (~ one page) description of the contribution the potential member intends to make. Potential new members can contact any current member of GROWTH for help in writing the request. New membership requests shall be accepted continually throughout the year. Each request shall be reviewed by the GROWTH MT and discussed at their next meeting.
Unless any MT member voices an objection, the membership application shall be accepted. In the case of one or more objections, the membership application shall be subject to a vote among all MT members and accepted in the case of a majority vote (for Collaborators) and supermajority (for Principal Partners).
Conversion to Legacy Membership is either voluntary or recommended by the MT.
Organizations wishing to become Principal Partners negotiate their MoU with the Management Team. Ratification of Principal Partners’ MoUs requires a supermajority of the MT members voting. Principal Partners may request to terminate their membership. The request will be reviewed by the MT members within a period of 3 months and a decision will be made based on a supermajority voting.
4. Membership expulsion
Serious breach of any of the GROWTH policies and procedures may warrant the expulsion of a member from the partnership. Expulsion requires a supermajority vote among the MT members.
-- IvaKostadinova - 19 Oct 2016 |
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.