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_Structure/annotate/7 at Thu, 03 Nov 2022 23:27:22 GMT NomCom - Open Grid Forum

Draft OGF Structure

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

1 1 Redmine Admin
h1. Draft OGF Structure
2 1 Redmine Admin
3 1 Redmine Admin
h2. OGF Structure as defined in "GFD.2":http://www.ogf.org/documents/GFD.2.pdf
4 1 Redmine Admin
5 1 Redmine Admin
* working groups (produce documents)
6 3 Redmine Admin
** chartered w/ milestones, somewhat defined lifetime
7 3 Redmine Admin
** chairs (2/3)
8 4 Redmine Admin
** secretary (opt)
9 4 Redmine Admin
** members (whoever is on mailing list)
10 4 Redmine Admin
11 1 Redmine Admin
* research groups (may produce documents)
12 4 Redmine Admin
** chairs / secretary / members
13 4 Redmine Admin
** vaguagly chartered
14 4 Redmine Admin
** indefinite lifetime
15 4 Redmine Admin
** may spawn WG
16 4 Redmine Admin
17 1 Redmine Admin
* community groups
18 4 Redmine Admin
** chairs / secretary / members
19 4 Redmine Admin
** indefinite lifetime
20 4 Redmine Admin
** represent community input to drive WGs/RGs
21 4 Redmine Admin
22 1 Redmine Admin
* area
23 4 Redmine Admin
** collection of WGs and RGs by topic
24 4 Redmine Admin
** structure of areas are up to GFSG
25 4 Redmine Admin
** area directors are (usually) assigned to areas, overseeing 1 or 2 groups each
26 1 Redmine Admin
27 1 Redmine Admin
28 1 Redmine Admin
h2. Proposed Amendments
29 1 Redmine Admin
30 1 Redmine Admin
* areas are static, not a good match for group topics, very different sizes/activities
31 5 Redmine Admin
** no static areas, but tags to groups
32 5 Redmine Admin
*** DRMAA: API, Compute
33 5 Redmine Admin
*** OCCI:  Cloud, Compute
34 5 Redmine Admin
*** GLUE:  Infrastructure, Compute, Data, Networking
35 5 Redmine Admin
** assign ADs to explicit set of groups, according to their specialization / experience
36 5 Redmine Admin
37 1 Redmine Admin
* feedback between CG and RG/WG not functional, no active CGs left
38 5 Redmine Admin
** focus CGs around short living efforts (plug feasts, workshops, implementations, OGF events, ...)
39 5 Redmine Admin
** very low overhead of forming and disbanding(!) CGs
40 5 Redmine Admin
41 1 Redmine Admin
* RG/WG structure seems to work ok
42 5 Redmine Admin
** weed out dead groups
43 6 Andre Merzky
44 6 Andre Merzky
45 6 Andre Merzky
h2. Proposed Amendments -- Verbose
46 6 Andre Merzky
47 6 Andre Merzky
The OGF structure has shown to be both suitable and appropriate for OGFs functioning, and seems to function reasonably well.  In particular, the hierarchy [members / chairs / AD / GFSG / VP] has shown to be very functional.  Also, the existence of topical areas has given the OGF a useful structure many members identify with.
48 6 Andre Merzky
49 6 Andre Merzky
There is, nevertheless, an observed mismatch on what groups are managed by what ADs: the number of groups managed by any specific ADs varies widely, and load-balancing is formally not trivial, due to the static area structure.  That also makes it difficult to replace ADs, as very specific expertise is needed for the new candidates.  Finally, groups can often not clearly be bucketed into one specific area.  
50 6 Andre Merzky
51 6 Andre Merzky
*We propose to make the AD-to-WG assignments more flexible, and in particular to assign groups on a case-by-case basis, based on the expertise of the ADs in question.  That change would mostly mostly formalize the currently practiced mechanism.  For organizational reasons the notion of topical areas should be preserved though.*
52 6 Andre Merzky
53 6 Andre Merzky
Over the last years, we have observed that community groups and research groups did rarely function as intended.  Research groups were supposed to spawn working groups based on early, exploratory work; community groups were supposed to inform working groups about standardization needs and uptakes, etc.  While there were at least some RGs which functioned as intended, RGs often covered both exploration and standardization.  CG were often very short-lived, as continuous participation of OGF customers in OGF events seems not sustainable for them.  The feedback of standardization needs via CGs has been lacking as well.
54 6 Andre Merzky
55 6 Andre Merzky
*We thus propose a re-interpretation of CGs, as short living, targeted efforts which center around specific activities, such as OGF events, workshops series, plug feasts, standards implementations etc.  It should be trivial to create a CG, and to terminate it once its mission is accomplished -- their main purpose is to provide structural, process and tooling support to these efforts.*
56 6 Andre Merzky
57 7 Andre Merzky
Related, *we propose to rigorously weed out dead groups in a timely manner.*
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_Structure/annotate/7 at Thu, 03 Nov 2022 23:27:22 GMT