| 1 | [[PageOutline]] |
| 2 | |
| 3 | = Introduction = |
| 4 | |
| 5 | This page documents the GENI Project Office (GPO) policy for project leads at GENI slice/member authorities operated by the GPO. This policy applies to users with the "project create" privilege at GENI Portal / Clearinghouse (ch.geni.net) |
| 6 | |
| 7 | Comments should be sent to help@geni.net |
| 8 | |
| 9 | = Project lead policy = |
| 10 | |
| 11 | In general, approving project leads is a human process that requires knowledge and intuition. No policy can clearly denote all who may or may not be project leads, so use appropriate judgment, and please ask. |
| 12 | |
| 13 | The following people should be granted project lead status: |
| 14 | * GENI-affiliated principal investigators (PIs) |
| 15 | * Academic faculty at US academic institutions, but ''not'' students and usually ''not'' temporary faculty (lecturer `[1]`, post-doc, etc.) |
| 16 | * Senior technical/IT staff (at academic institutions, commercial businesses, non-profits, or research institutes) affiliated with GENI in some way |
| 17 | * Typical titles include "CTO", "Director", "Associate Director", "Architect", "Senior Engineer", etc., but ''not'' temporary employees or interns. |
| 18 | * We will often grant project lead to similar staff from institutions that are not GENI-affiliated, but these cases merit review by GPO leads. |
| 19 | * GENI Rack Administrators |
| 20 | * GPO full-time staff, but ''not'' temporary employees or interns. |
| 21 | * Anyone approved by the GPO Leads |
| 22 | * There are exceptions to every rule. If someone seems to be an appropriate project lead but is not covered by the policy, ask the GPO Leads. |
| 23 | * As of March 2015, the GPO Leads are: Mark Berman, Marshall Brinn, Heidi Dempsey, and Vic Thomas. |
| 24 | |
| 25 | In all cases, the request should contain enough information (may be quite brief) about the intended use to give us a sense that: |
| 26 | * There is a reasonable chance GENI will be useful for the intended purpose. |
| 27 | * The intended purpose does not appear to be illegal, unethical, or likely to harm GENI. |
| 28 | |
| 29 | Project leads from countries with which there is not already an active GENI collaboration may require review by NSF. These requests should be referred to Mark. |
| 30 | |
| 31 | Background: the intent of this policy is that, to the extent possible: |
| 32 | * Project leads should understand what taking responsibility for their project members means (so we prefer people who are responsible for others in their organizations as part of their day-to-day job). |
| 33 | * Project leads should be responsive to inquiries about their project members over time (so we prefer people who are expected to have longevity at their current organizations/working with GENI). |
| 34 | * Project leads should be at least slightly familiar with GENI. |
| 35 | |
| 36 | Notes: |
| 37 | |
| 38 | `[1]` At UK Universities, "Senior Lecturer" and "Lecturer" are the names of permanent faculty positions, approximately equivalent to "associate professor" and "assistant professor", respectively. ([http://en.wikipedia.org/wiki/Senior_lecturer]) |