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?version=5 at Thu, 03 Nov 2022 23:27:46 GMT Draft OGF Management Structure - NomCom - Open Grid Forum

« Previous - Version 5/7 (diff) - Next » - Current version
Redmine Admin, 02/14/2014 02:01 PM


Draft OGF Management Structure

OGF Structure as defined in GFD.3

  • OGF Chair / Vice Chair
    • ensure group process, coherence
    • organize events
    • oversees web presence
    • oversees (chairs) GFSG (group management, document process
    • is now called 'VP of Standards'
    • vice chairs support chairs, selected by chair from GFSG
  • GFSG
    • area directors + OGF Chair + senior OGF members (AD at large)
    • manage document process (with editor)
    • manage groups
  • Editor
    • see GFD.152
    • member of GFSG
    • manages OGF document pipeline, with support from GFSG
  • Advisory Committee
    • external strategy advise
    • currently non-functional

Previous Amendments

  • OGF Chair split into President / VP Standards / VP Community / VP Liaison
    • in practical terms all tasks are again with the VP Standards right now
  • OGF Board of Directors
    • draws members from paying member organization
    • required on legal grounds
    • operates currently on bare minimum

Proposed Amendments

  • OGF size is small:
    • keep board minimal
    • define clearly the roles of
      • President
        • external representation
      • VP Standards
        • Chair GFSG, support GFSG tasks
      • VP Events
        • organize OGF meetings
        • could be newly assigned per event, e.g. to local organizer
      • VP Liaison
        • manages interactions with other SDOs
        • could be split among multiple people, but needs clear mandate
      • Area Director
        • mentors a set of OGF Groups
        • guides the chairs of these groups
        • champions documents from these groups through the document pipeline
        • ensures inter-group coordination
    • AD positions should be allowed to double with any of the VP positions
      • we have a small pool of people
      • simplifies rotating positions such as VP Events
    • match ADs to specific groups, independent of actual area
    • note/understand potential conflict of interest if chair comes from a group he shepherds
    • involve group chairs in GFSG
      • show them the day-to-day activities
      • get them involved early (w/o full AD duties)
      • auto-add to GFSG list and call invitations
      • keep them posted with frequent operations updates
      • involve in event planning, etc.
  • OGF Board is largely inactive / sparsely populated
    • emphasize steering activities (replace advisory board)
      • invite well connected people who
      • think OGF important but don't have much time (give them a title...)
      • strengthen ties with community (e.g. influx of new groups by suggesting OGF as work venue)
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?version=5 at Thu, 03 Nov 2022 23:27:46 GMT