Still waiting on the following organizations to update their list of committers 
in this 
spreadsheet<https://docs.google.com/spreadsheets/d/1Z8KI2M5hQldPBm6s4aU0FZa9d3MGWwA2MOiPnYd72L0/edit#gid=0>:


  *   Mellanox
  *   U. Houston
  *   AMD
  *   ORNL
  *   Oracle
  *   HLRS
  *   HFT Stuttgart
  *   LANL
  *   Sandia
  *   Chelsio
  *   Oscar Vegis
  *   Craig Rasmussen

The deadline is today.

Folks: I don't like this administravia any more than you do.  But I'm 
volunteering to do it, and you're wasting my time by not taking two minutes to 
fill out your part of the spreadsheet.  Please do it ASAP.

Thanks.





On Aug 26, 2015, at 4:12 PM, Jeff Squyres (jsquyres) 
<jsquy...@cisco.com<mailto:jsquy...@cisco.com>> wrote:

It's that time of year again: it's our annual review of those with write access 
to our Git repos.

The purpose is simply to trim those who are no longer active, or otherwise no 
longer need write access to Open MPI repositories.  We don't want people moving 
to new jobs and still having write access to our code bases; this is our annual 
reminder to remove such accounts.

*** I've created a spreadsheet that every organization will need to examine by 
COB Fri, 4 Sep, 2015 ***

What you need to do:

1. Visit this Google spreadsheet

2. Find your organization.

3. Examine each person in your organization:
   - I've marked each Git repo that each person currently has WRITE access to
   *** If that person can be dropped from all Open MPI repos, color that 
person's row ORANGE
   *** If that person still needs WRITE git repo access, place an X in the 
corresponding "Need commit?" column
   *** Once you are done checking each person, color that person's row GREEN so 
that we know this row is done

### Please only mark off members who actually need write access in the 
foreseeable future.

If someone in your org *might* need access at some point in the future, we can 
add them in the future -- it's a quick/easy process to do so.  Meaning: please 
don't mark someone as needing access *now* if they only *might* need access in 
the future.

--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/



--
Jeff Squyres
jsquy...@cisco.com<mailto:jsquy...@cisco.com>
For corporate legal information go to: 
http://www.cisco.com/web/about/doing_business/legal/cri/

Reply via email to