wiki:GeniProjectLeadPolicy

Version 1 (modified by tmitchel@bbn.com, 7 years ago) (diff)

--

Introduction

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)

Comments should be sent to help@geni.net

Project lead policy

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.

The following people should be granted project lead status:

  • GENI-affiliated principal investigators (PIs)
  • Academic faculty at US academic institutions, but not students and usually not temporary faculty (lecturer [1], post-doc, etc.)
  • Senior technical/IT staff (at academic institutions, commercial businesses, non-profits, or research institutes) affiliated with GENI in some way
    • Typical titles include "CTO", "Director", "Associate Director", "Architect", "Senior Engineer", etc., but not temporary employees or interns.
    • We will often grant project lead to similar staff from institutions that are not GENI-affiliated, but these cases merit review by GPO leads.
  • GENI Rack Administrators
  • GPO full-time staff, but not temporary employees or interns.
  • Anyone approved by the GPO Leads
    • 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.
    • As of March 2015, the GPO Leads are: Mark Berman, Marshall Brinn, Heidi Dempsey, and Vic Thomas.

In all cases, the request should contain enough information (may be quite brief) about the intended use to give us a sense that:

  • There is a reasonable chance GENI will be useful for the intended purpose.
  • The intended purpose does not appear to be illegal, unethical, or likely to harm GENI.

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.

Background: the intent of this policy is that, to the extent possible:

  • 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).
  • 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).
  • Project leads should be at least slightly familiar with GENI.

Notes:

[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)