Draft NomCom Process
Version 4 (Redmine Admin, 02/21/2014 03:43 PM)
| 1 | 1 | Redmine Admin | h1. Draft NomCom Process |
|---|---|---|---|
| 2 | 1 | Redmine Admin | |
| 3 | 1 | Redmine Admin | h2. NomCom Process as defined in "GFD.116":http://www.ogf.org/documents/GFD.116.pdf |
| 4 | 1 | Redmine Admin | |
| 5 | 1 | Redmine Admin | * NomCom is elected by community, from active members |
| 6 | 2 | Redmine Admin | * receives list of open positions |
| 7 | 2 | Redmine Admin | * issues call for nominations |
| 8 | 2 | Redmine Admin | ** NomCom members are not eligible for free management positions |
| 9 | 2 | Redmine Admin | ** nominations for President comes from Board |
| 10 | 2 | Redmine Admin | ** nominations for VP and AD come from community |
| 11 | 2 | Redmine Admin | * check availability of nominees |
| 12 | 2 | Redmine Admin | * evaluate nominees |
| 13 | 2 | Redmine Admin | * deliberates over candidate selection |
| 14 | 2 | Redmine Admin | * proposes candidates to board (1 per AD, list per VP/President) |
| 15 | 2 | Redmine Admin | * Board will agree to AD nominations, select/elect VP/President |
| 16 | 1 | Redmine Admin | |
| 17 | 1 | Redmine Admin | |
| 18 | 1 | Redmine Admin | h2. Proposed Amendments |
| 19 | 1 | Redmine Admin | |
| 20 | 1 | Redmine Admin | * OGF Board is largely inactive / sparsely populated |
| 21 | 2 | Redmine Admin | ** allow president nominations from community |
| 22 | 3 | Redmine Admin | ** transfer some decisions on positions to GFSG |
| 23 | 3 | Redmine Admin | |
| 24 | 2 | Redmine Admin | |
| 25 | 1 | Redmine Admin | * size of OGF is small |
| 26 | 2 | Redmine Admin | ** task NomCom with possible extensions of AD terms |
| 27 | 4 | Redmine Admin | |
| 28 | 4 | Redmine Admin | h2. Proposed Amendments -- Verbose |
| 29 | 4 | Redmine Admin | |
| 30 | 4 | Redmine Admin | Over the last The OGF Board has shrunk in its visibility and activity, and at this point represents the bare legal minimum, operating on the minimal set of required activities. |
| 31 | 4 | Redmine Admin | |
| 32 | 4 | Redmine Admin | In the 'OGF Management Amendments' section will also propose several measures to address the board functionality, but specifically in the context if the NomCom process, we propose: |
| 33 | 4 | Redmine Admin | We thus propose to adjust the NomCom process to this situation -- but |
| 34 | 4 | Redmine Admin | |
| 35 | 4 | Redmine Admin | * allow nominations for OGF Presidents from the wider OGF community (at the moment, only the board can nominate presidential candidates). |
| 36 | 4 | Redmine Admin | * transfer the following decisions to GFSG: |
| 37 | 4 | Redmine Admin | ** agree to AD (re)election |
| 38 | 4 | Redmine Admin | ** agree to VP (re)election |
| 39 | 4 | Redmine Admin | ** agree to President (re)election |
| 40 | 4 | Redmine Admin | |
| 41 | 4 | Redmine Admin | |
| 42 | 4 | Redmine Admin | As the size of OGF (in numbers of active members) has been shrinking over time, we consider it a viable strategy to allow ADs, VPs and Presidents to serve longer than their originally allotted term (see 'OGF Management Amendments' section). In fact, that change would only reconfirm and formalize what is current practice. NomComs duties should be extended to cover the candidate re-confirmation process for such term extensions. |
| 43 | 4 | Redmine Admin | |
| 44 | 4 | Redmine Admin |