Meeting Notes: ‣

Outcome: Passed ✅

Outcome Summary

This proposal passed, and as CSDO we agreed that as of right now it is the WS Leads discretion on who should get access to emails and that they are accountable for a proper offboarding procedure (which DAO Ops is working to update).

Proposal

Access to Gitcoin email addresses continue to be a blocker at WS level.

• Trusted contributors (TC) have limited cross-DAO notion & google doc access (i.e., they can access and edit Notion at their workstreams but have limited access to editing Notion docs in other areas and Gdocs hosted elsewhere)
• TCs are not immediately aware of contributor events that help with context building, training and deepening engagement with our organization (eg, Gathering Hour, Workstream Updates, etc)
• Multiple WS leads have expressed increased friction for doc sharing and easy scheduling via the shared org calendar.

Moreover, I personally feel that access to a Gitcoin email is not only a functional issue, it is also a signal of trust and value that I feel directly impacts a contributor’s experience of their workplace.

Although these are opinion-based annoyances that can (mostly) be worked around, the issue of email access for non-core contributors continues to emerge as a point of tension that has been inadequately addressed, imo.

Proposal:

Trusted Contributors (in addition to Core/FT contributors) should receive emails if they align with one or more of the following:

1. The contributor is new but has a clearly-written time-staked agreement with their workstream (e.g., someone working in a function who is working on a clearly-outlined, high-context, cross-stream project - example: community engagement strategy). Upon offboarding, that contributor’s email will be sunsetted and no-longer functional

OR

1. The contributor has shown commitment to the DAO, has been an active and integral part of the workstream for at least one season and has clearly-identified roles and responsibilities within the workstream. In a traditional working environment, this person might be considered a “part-time” employee (see MMM’s Understanding Contributor Tiers)

Note that the above makes no mention of weekly hours worked but, rather, follows a set of design principles based on:

https://lh5.googleusercontent.com/KMoxf4Quv67Ujedd4rYh67qLW4TQPl2oZWti48zA8rl7VOD4DyHDroUdHHAGakbExYFtLEJMhJGzTCRaSPfvG6Nw1dMaSSVwrZp89gpggzfxTP2zJ0aoeQA1l_E4vFaz1Lei1C_vz6sX_lusSyA4rM0jUsNzBYYrGZdETppE3dFe56TTX6-mKfQHn8Zk0Q