XSF organizational overview (organigram)

[Echolon]

Dear members,

a little "election promise" from my side was to start over with an overview of the XSF, its organization and resources, as a organizational chart (organigram). Here is my first draft.

• It focuses on the content and structure.
• It does not focus on format and design :smiley:
  • Ideally we can manage it in the future via e.g. json files and render it on the Website
• There are two drafts, where one tries to allocated resources to organs and teams directly.
• I am not sure where to allocate the MediaWiki and Logs.

I am convinced this can be a really helpful tool for overview purposes, especially to newcomers or people who are interested in the XSF and XMPP. Let me know you feedback and if you think something is missing!

Cheers!

[Echolon]

[Echolon]

[dwd]

Some comments:

• I'm not entirely convinced by the name "Organs". I mean, it's technically correct, of course, but it sounds... odd.
• The Board also has a Chair, but the Chair of the Board is an Officer, like the ED, Treasurer, and Secretary. While I think the Board Chair has always been a member of the Board, it's not strictly a requirement.
• All the Officers are technically "Appointed" by the Board; because it's a resolution of the Board, that gets a vote of the Board, but it's not an election in that sense.
• Council, which includes its Chair, are a subsection of Members (whereas the others are not, even if the people therein are usually members). (Council Chairs are usually elected by Council, and are always a member of Council).
• Teams are "Work Teams", and are also made up exclusively of Members. The membership of a Work Team is broadly unspecified, but in most cases they're appointed by Board - in practice, Board just accepts whatever recommendations are given to it by the Team itself, occasionally asking Council.

[Echolon]

@dwd Thank you Dave! That's really helpful.

Would you insist to map the elections connections / hierarchy for such a chart or keep it more in the direction of overview? I updated both charts. Let me know if you also like the idea in general and if you have a preference! (Yes, I read that Council is a subsection of members, will changes this later)

[Echolon]

https://skeptric.com/diagrams-in-hugo/

[cal0pteryx]

There is also: https://mermaid-js.github.io/mermaid-live-editor/

[Echolon]

{{< mermaid >}}
graph TD;
    
    subgraph Organisation
        subgraph Secretary
        A
        end
        subgraph Board
        B
        end
        subgraph Council
        C
        end
        subgraph Members
        D
        A --- D
        B --- D
        C --- D
        end
    end
    
    subgraph Work Teams
        subgraph "Communication Team"
        end
        subgraph "Infrastructure Team"
        end
        subgraph "SCAM Team"
        end
        subgraph "XEP Editors"
        end
    end
    
    subgraph Resources
        E
        F
    end

    
{{< /mermaid >}}

[cal0pteryx]

I think we should stick with an SVG of what you proposed in https://github.com/xsf/xmpp.org/issues/920#issuecomment-844474566 :)

[cal0pteryx]

@Echolon could you post the source file here? Is it made using DrawIO ?

[cal0pteryx]

@Echolon I pushed a first overview diagram in 29fd6d007373c9a2ff562686725deb25204837f8

I went for an html approach, since this is responsive and mobile friendly. It can be viewed here (as soon as it's deployed): https://xmpp.org/about/xmpp-standards-foundation/

Any suggestions? Something missing?