💬

Vishnu <> Kyle re: Notion Access, System Update

Date
🔗 Initiative
🔗 Working Documents
Agenda
Attendees
Agenda
Attendees
 
Action Items DB

Table

🗄️
Action Items DB
Action Item
Funder(s)
Done
Last Touched
🔗 Initiatives
Round
Due Date
Priority
Grantees
Status
Do Date
🔗 Owner
Created
Workstream
Column
🔗 Related Meetings
 
Meeting Minutes
  1. Updates
      • Notion system is pretty much good to go —> planning to merge into GitcoinDAO account tn
        • Set up as a big "build in public" system for the DAO
      • Only thing left for DAO Notion will be to redirect/archive current DAO pages + create documentation
      • Next big challenge will be figuring out how to build habit/ritual of using + updating the Notion
       
      • Re: climate round + grantees —> if they are an org will need an offramp to fiat
        • Setting up business relationship with Kraken, Coinbase
        • For web2 grantees —> maybe just get them a rainbow or metamask
          • Need to get them access to L2 funds —> metamask might be the best
            • Rainbow will connect to both
        • Ideally if they are web3 —> can get a gnosis safe going
          • Just adds more legitimacy to their grant —> best for long term success
 
  1. Notion access
      • What levels of contributors are there and what level of access should they get?
        • Would rather create and apply these roles with LOTS of access first —> then ratcheting back if needed
          • Better than vice versa (creating perms after the fact)
           
          1. Notion coordinators (Admins who manage, maintain, organize the Notion)
              • Access level: Full access (for DAO)
               
          1. WS leads (lead and guide a workstream, admin of that workstream)
              • Access level: WS level
               
          1. Squad leads (sub-workstream, and access to that level)
              • Access level: Give access at initiative level + WS level
               
          1. DAO contributors
              • Access level: Individual pages
                • Would they be able to get access to universal DBs through their individual dashboards?
              • Edit workstream too (at squad lead's discretion)
              • initiative level
               
          1. DAO applicants
              • Public facing landing page for applications + below
              • Worried about exposing PII and doxxing people
               
          1. General community/public
              • Public facing landing page for applications + below
               
  1. Driving Adoption of Notion system
      • Payment details —> make payment run thru Notion
      • Influencers within Gitcoin
      • Creating lots of video documentation
      • Community calls
      • Squad for Notion operators from each workstream
 
  1. Combining Holdings + DAO Notions
      • VGK + KBW to sync later
 
💬

Vishnu <> Kyle re: Notion Access, System Update

Date
🔗 Initiative
🔗 Working Documents
Agenda
Attendees
Agenda
Attendees
 
Action Items DB

Table

🗄️
Action Items DB
Action Item
Funder(s)
Done
Last Touched
🔗 Initiatives
Round
Due Date
Priority
Grantees
Status
Do Date
🔗 Owner
Created
Workstream
Column
🔗 Related Meetings
 
Meeting Minutes
  1. Updates
      • Notion system is pretty much good to go —> planning to merge into GitcoinDAO account tn
        • Set up as a big "build in public" system for the DAO
      • Only thing left for DAO Notion will be to redirect/archive current DAO pages + create documentation
      • Next big challenge will be figuring out how to build habit/ritual of using + updating the Notion
       
      • Re: climate round + grantees —> if they are an org will need an offramp to fiat
        • Setting up business relationship with Kraken, Coinbase
        • For web2 grantees —> maybe just get them a rainbow or metamask
          • Need to get them access to L2 funds —> metamask might be the best
            • Rainbow will connect to both
        • Ideally if they are web3 —> can get a gnosis safe going
          • Just adds more legitimacy to their grant —> best for long term success
 
  1. Notion access
      • What levels of contributors are there and what level of access should they get?
        • Would rather create and apply these roles with LOTS of access first —> then ratcheting back if needed
          • Better than vice versa (creating perms after the fact)
           
          1. Notion coordinators (Admins who manage, maintain, organize the Notion)
              • Access level: Full access (for DAO)
               
          1. WS leads (lead and guide a workstream, admin of that workstream)
              • Access level: WS level
               
          1. Squad leads (sub-workstream, and access to that level)
              • Access level: Give access at initiative level + WS level
               
          1. DAO contributors
              • Access level: Individual pages
                • Would they be able to get access to universal DBs through their individual dashboards?
              • Edit workstream too (at squad lead's discretion)
              • initiative level
               
          1. DAO applicants
              • Public facing landing page for applications + below
              • Worried about exposing PII and doxxing people
               
          1. General community/public
              • Public facing landing page for applications + below
               
  1. Driving Adoption of Notion system
      • Payment details —> make payment run thru Notion
      • Influencers within Gitcoin
      • Creating lots of video documentation
      • Community calls
      • Squad for Notion operators from each workstream
 
  1. Combining Holdings + DAO Notions
      • VGK + KBW to sync later
Â