Do we want to provide committee member's names in the governance doc ?

[hidyverse]

We are being held up by [items] in the governance doc...one of which is [names] of committee members (for example line 123). Do we want to keep this explicit naming convention or remove for now and move forward?

👍🏻 to remove individual names ❤️ to keep convention and fill out committees with names

[julianpistorius]

My vote: Let's make it explicit.

[julianpistorius]

@val-pf, @alex-r-bigelow, @lossanna ?

[alex-r-bigelow]

(just a reminder that we need to close #13 if we want to enable slightly more formal voting via github)

[val-pf]

I would not put names into the doc, because then we have to actually name/elect the committees. I think it should be a situation where each individual possible committee slowly transitions into a more formal shape.

[hidyverse]

while I agree with @val-pf that actually naming individuals to the committees will be difficult, I would appreciate a direct contact for each committee.

What about creating sub-gmail accounts (e.g. operations.resbazaz@gmail.com) or linking to a slack channel for each committee, in lieu of names?

[val-pf]

That is a good idea, have a transferable email account for Hacky Hour, C&C, etc.

[julianpistorius]

I like it!

[hidyverse]

Updated to reference committee emails in #28. Do we want to go forward with the creation of these transferable emails?

[julianpistorius]

See my comment in #28.

[julianpistorius]

I think we need at least names and GitHub accounts for transparency, accountability, and practical reasons (See below). Emails can be handled through the delegation process described earlier. Can even be something like ResBazAZ+Julian@gmail.com, ResBazAZ+Val@gmail.com, etc.

Can somebody please create an issue or discussion tagging folks from Coffee & Code & conference organizers to nominate & vote on representatives from their groups, and then make PRs to add their names to the governance document?

From the governance document:

ResBaz Leadership

Roles and responsibilities

The following responsibilities and tasks shall be organized by executive committee members (technical governance is expected to be performed by the committee members of the various events and projects):

Social

• Define, evolve, and defend the vision, mission and the values of ResBaz community through clear central governance

• Coordinate the usage of the ResBaz brand

• Act as a central point of contact for ResBaz

• Act as a final escalation point for disputes in any committee, community conflict

Technical

• Control access to ResBaz accounts (e.g. GitHub, email, Meetup, Slack)

• Maintain ownership of ResBaz domain names

• Manage central event data (e.g. festival attendance records, feedback, membership data)

• Oversee ResBaz's financial management (Open Collective)

• Negotiate contracts on behalf of the community

[hidyverse]

OK - we go forward with compromise to include first name and github of at least one representative from each committee.