🗃️
Contributor Access Bundle DBs
/
🏗️
Template for Creating Cross-Stream Pop Up Working Groups [WIP]
🏗️

Template for Creating Cross-Stream Pop Up Working Groups [WIP]

Related to Contributors DB (1) (Working Documents)
Initiative
🤝
CSDO - Strategy & Ops
Contributor(s)
GC Forum Gov. Post.
🗄️ Initiatives DB
link
Related to Action Items DB (Working document)
Due Date
Created date
💡
This is a brain dump on how to create temporary (”popup”) cross stream working groups for Gitcoin.
 
Pre-Group Formation
  1. A Gitcoin DAO contributor identifies an objective that requires significant input from multiple workstreams.
  1. This contributor creates a one-pager that answers the following questions:
    1. What does this working group plan to achieve? (and what Essential Intent(s) the group is aiming to serve)
    2. What workstreams require representation?
    3. Who are the (either) a) a list of agreed-upon participants of the group or b) a list of suggestions of who should be part of the group?
    4. What are the roles & responsibilities in the working group?
    5. What are the roles & responsibilities of CSDO in the working group’s outputs?
    6. Who will drive the working group and what are their high-level responsibilities? (this is important because not all contributors are “full time”—and workstream leads should be notified if contributors on an hourly compensation are being pulled in and potentially requiring budget for their participation more budget needs to be allocated for their participation in this working group)
    7. Where will the group communicate and at what cadence?
    8. Timeline, including at what points CSDO will be invited for input?
    9. Any other relevant details
  1. The contributor shares the one-pager to their workstream lead(s) for feedback, as well as people the contributor would like to invite to be part of the group
  1. (Optional) Short proposal is brought to CSDO to they can discuss the need for and potentially approve this cross-stream pop-up working group
  1. (Optional) CSDO shares feedback with the proposer if they have questions; proposer integrates feedback
  1. (Optional) CSDO approves or denies the request
 
Group Formation
  • The project’s driver…
    • proceeds proposal creation (see example) that outlines roles, responsibilities and intended outcomes of the working group
    • formally invites people to join the working group
    • shares progress with CSDO for input at agreed-upon points in the group’s project timeline/roadmap
    • Integrates CSDO feedback
    • summary of work is shared with the DAO upon completion of phases of work
🗃️
Contributor Access Bundle DBs
/
🏗️
Template for Creating Cross-Stream Pop Up Working Groups [WIP]
🏗️

Template for Creating Cross-Stream Pop Up Working Groups [WIP]

Related to Contributors DB (1) (Working Documents)
Initiative
🤝
CSDO - Strategy & Ops
Contributor(s)
GC Forum Gov. Post.
🗄️ Initiatives DB
link
Related to Action Items DB (Working document)
Due Date
Created date
💡
This is a brain dump on how to create temporary (”popup”) cross stream working groups for Gitcoin.
 
Pre-Group Formation
  1. A Gitcoin DAO contributor identifies an objective that requires significant input from multiple workstreams.
  1. This contributor creates a one-pager that answers the following questions:
    1. What does this working group plan to achieve? (and what Essential Intent(s) the group is aiming to serve)
    2. What workstreams require representation?
    3. Who are the (either) a) a list of agreed-upon participants of the group or b) a list of suggestions of who should be part of the group?
    4. What are the roles & responsibilities in the working group?
    5. What are the roles & responsibilities of CSDO in the working group’s outputs?
    6. Who will drive the working group and what are their high-level responsibilities? (this is important because not all contributors are “full time”—and workstream leads should be notified if contributors on an hourly compensation are being pulled in and potentially requiring budget for their participation more budget needs to be allocated for their participation in this working group)
    7. Where will the group communicate and at what cadence?
    8. Timeline, including at what points CSDO will be invited for input?
    9. Any other relevant details
  1. The contributor shares the one-pager to their workstream lead(s) for feedback, as well as people the contributor would like to invite to be part of the group
  1. (Optional) Short proposal is brought to CSDO to they can discuss the need for and potentially approve this cross-stream pop-up working group
  1. (Optional) CSDO shares feedback with the proposer if they have questions; proposer integrates feedback
  1. (Optional) CSDO approves or denies the request
 
Group Formation
  • The project’s driver…
    • proceeds proposal creation (see example) that outlines roles, responsibilities and intended outcomes of the working group
    • formally invites people to join the working group
    • shares progress with CSDO for input at agreed-upon points in the group’s project timeline/roadmap
    • Integrates CSDO feedback
    • summary of work is shared with the DAO upon completion of phases of work