This is a static archive of the previous Open Grid Forum Redmine content management system saved from host redmine.ogf.org file /projects/nomcom/wiki/Draft_OGF_Management_Structure/annotate/7 at Thu, 03 Nov 2022 23:27:43 GMT NomCom - Open Grid Forum

Draft OGF Management Structure

Version 7 (Andre Merzky, 03/18/2014 12:25 PM)

1 1 Redmine Admin
h1. Draft OGF Management Structure
2 1 Redmine Admin
3 1 Redmine Admin
h2. OGF Structure as defined in "GFD.3":http://www.ogf.org/documents/GFD.3.pdf
4 1 Redmine Admin
5 1 Redmine Admin
* OGF Chair / Vice Chair
6 1 Redmine Admin
** ensure group process, coherence
7 1 Redmine Admin
** organize events
8 1 Redmine Admin
** oversees web presence
9 1 Redmine Admin
** oversees (chairs) GFSG (group management, document process
10 1 Redmine Admin
** is now called 'VP of Standards'
11 1 Redmine Admin
** vice chairs support chairs, selected by chair from GFSG
12 1 Redmine Admin
13 1 Redmine Admin
* GFSG
14 1 Redmine Admin
** area directors + OGF Chair + senior OGF members (AD at large)
15 1 Redmine Admin
** manage document process (with editor)
16 1 Redmine Admin
** manage groups
17 1 Redmine Admin
18 2 Redmine Admin
* Editor
19 2 Redmine Admin
** see "GFD.152":http://www.ogf.org/documents/GFD.152.pdf
20 2 Redmine Admin
** member of GFSG
21 2 Redmine Admin
** manages OGF document pipeline, with support from GFSG
22 1 Redmine Admin
23 2 Redmine Admin
* Advisory Committee
24 2 Redmine Admin
** external strategy advise
25 2 Redmine Admin
** currently non-functional
26 1 Redmine Admin
27 2 Redmine Admin
28 2 Redmine Admin
h2. Previous Amendments
29 2 Redmine Admin
30 2 Redmine Admin
* OGF Chair split into President / VP Standards / VP Community /  VP Liaison
31 2 Redmine Admin
** in practical terms all tasks are again with the VP Standards right now
32 2 Redmine Admin
33 2 Redmine Admin
* OGF Board of Directors
34 2 Redmine Admin
** draws members from paying member organization
35 2 Redmine Admin
** required on legal grounds
36 2 Redmine Admin
** operates currently on bare minimum
37 2 Redmine Admin
38 2 Redmine Admin
h2. Proposed Amendments
39 2 Redmine Admin
40 2 Redmine Admin
* OGF size is small:
41 2 Redmine Admin
** keep board minimal
42 2 Redmine Admin
** define clearly the roles of
43 2 Redmine Admin
*** President
44 2 Redmine Admin
**** external representation
45 2 Redmine Admin
*** VP Standards
46 2 Redmine Admin
**** Chair GFSG, support GFSG tasks
47 2 Redmine Admin
*** VP Events
48 2 Redmine Admin
**** organize OGF meetings
49 2 Redmine Admin
**** could be newly assigned per event, e.g. to local organizer
50 2 Redmine Admin
*** VP Liaison
51 2 Redmine Admin
**** manages interactions with other SDOs
52 1 Redmine Admin
**** could be split among multiple people, but needs clear mandate
53 3 Redmine Admin
*** Area   Director
54 3 Redmine Admin
**** mentors a set of OGF Groups
55 3 Redmine Admin
**** guides the chairs of these groups
56 3 Redmine Admin
**** champions documents from these groups through the document pipeline 
57 4 Redmine Admin
**** ensures inter-group coordination
58 6 Redmine Admin
* flexible AD positions 
59 6 Redmine Admin
** ADs should be allowed to double with any of the VP positions 
60 1 Redmine Admin
*** we have a small pool of people
61 1 Redmine Admin
*** simplifies rotating positions such as VP Events
62 6 Redmine Admin
** match ADs to specific groups, independent of actual area (practiced already)
63 5 Redmine Admin
** note/understand potential conflict of interest if chair comes from a group he shepherds
64 6 Redmine Admin
* involve group chairs in GFSG
65 6 Redmine Admin
** show them the day-to-day activities
66 6 Redmine Admin
** get them involved early (w/o full AD duties)
67 6 Redmine Admin
** auto-add to GFSG list and call invitations
68 6 Redmine Admin
** keep them posted with frequent operations updates
69 6 Redmine Admin
** involve in event planning, etc.
70 5 Redmine Admin
* OGF Board is largely inactive / sparsely populated
71 5 Redmine Admin
** emphasize steering activities (replace advisory board)
72 5 Redmine Admin
*** invite well connected people who 
73 5 Redmine Admin
*** think OGF important but don't have much time (give them a title...)
74 5 Redmine Admin
*** strengthen ties with community (e.g. influx of new groups by suggesting OGF as work venue)
75 7 Andre Merzky
76 7 Andre Merzky
77 7 Andre Merzky
h2. Proposed Amendments -- Verbose
78 7 Andre Merzky
79 7 Andre Merzky
We observe that some of the OGF management roles are not well defined, or that they would benefit from slightly changed definitions.  We propose the following short descriptions (no additions to other roles):
80 7 Andre Merzky
81 7 Andre Merzky
* The OGF president represents OGF to external bodies, and speaks for OGF.
82 7 Andre Merzky
* The Vice President (VP) Standards chairs the GFSG, and supports GFSG operations.
83 7 Andre Merzky
* A VP Events organizes OGF meetings.  That role may be re-assigned to a new candidate per major event.
84 7 Andre Merzky
* A VP Liaison manages OGF interactions with other SDOs.  That role could be split among multiple candidates, but needs a clear mandate.  Ideally, a VP Liaison is member of OGF and the liaising organization.
85 7 Andre Merzky
* An Area Director (AD) 
86 7 Andre Merzky
** mentors a well defined set of OGF groups, 
87 7 Andre Merzky
** guides the chairs of these groups through OGF processes, 
88 7 Andre Merzky
** champions documents from these groups through the OGF document pipeline, 
89 7 Andre Merzky
** ensures inter-group interactions
90 7 Andre Merzky
91 7 Andre Merzky
Below are some recommendations for the roles mentioned above.
92 7 Andre Merzky
93 7 Andre Merzky
*Board Member:* Today's OGF board is largely inactive and reduced to its minimal legal role.  *We propose to refocus it towards a more active OGF advisory role.*  (Note that the actual OGF advisory board is even more inactive than the OGF board.)  For example, it may be worthwhile to ask well connected people to join the OGF board with a well specified small mandate, such as representing OGF in a certain project.  That would allow to involve people which otherwise have no time reserves to actively engage with OGF meaningfully, but are willing to speak up on behalf of OGF.  We also hope that such a board could help to strengthen OGFs ties with the community.
94 7 Andre Merzky
95 7 Andre Merzky
*AD:* To accommodate rotating VP events positions, and to cater for the small pool of candidates, *we propose to allow ADs to double on any VP role.*  As noted in the 'OGF Structure' recommendations, we propose that WGs are more flexibly assigned to ADs than just based on the WGs area.  Further, we noticed that no OGF document mentions any potential conflict of interest for ADs which have been previously active in the groups they are now mentoring.  While we don't see an immediate need of action, this may be worth noting in future revisions of the OGF structure GFD.
96 7 Andre Merzky
97 7 Andre Merzky
*Chairs:* *We recommend to tie group chairs tighter into day-to-day OGF activities.*  While we do not want to increase the work load on chairs, we consider it important to keep them closer to GFSG activities, to event organization, etc.  For example, it might be beneficial for both sides if chairs were invited to every other GFSG call, as observers or reporters.  Along the same lines, chairs should be auto-added to the GFSG mailing list, to keep updated with OGF activities, problems, events etc.  Also, we consider chairs to be essential for organizing OGF events, as the past model (GFSG organizes events) did not scale well.
This is a static archive of the previous Open Grid Forum Redmine content management system saved from host redmine.ogf.org file /projects/nomcom/wiki/Draft_OGF_Management_Structure/annotate/7 at Thu, 03 Nov 2022 23:27:43 GMT