🗃️
Contributor Access Bundle DBs
/
Move to the New Open Source Knowledge Base

Move to the New Open Source Knowledge Base

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Jan 4, 2022
Meeting Notes
Type
Tooling
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and we will replace the knowledge base currently at support.gitcoin.co by moving to the new open source knowledge base as our single source of truth.
Proposal
Proposal 1 - Move to the New Open Source Knowledge Base (huxwell)
  • Tension: We need one source of truth for Gitcoin with less barriers to access than HappyFox
    • It is difficult to move forward because there are so many different entities involved
    • updating info in two places as we anticipate moving is becoming tedious
    • using the open source kb would be "walking the walk"
    • Right now no one "owns" the knowledge base
  • Proposal: Move to the new open source knowledge base as our single source of truth and replace the knowledge base currently at support.gitcoin.co
    • Phase One - Discovery
      • Step 1 - Appointments to a DACI model
        • Driver = Huxwell as he has been granted the budget (and blessing) by stewards in this endeavor. He may appoint Riely or other to co-lead with him.
        • Approver = CSDO
        • Consulted = Cross Functional group of "consulted" stakeholders which manage production of content for the knowledge base
          • PG/Grants = Annika, MMM/Product = Sean, FDD = Joe, dGitcoin = Philip, MC = Owocki or emu, Support/Translations = Riely
        • Informed = Everyone else (will make clear list and communicate at the right time)
      • Step 2 - Design PowWow to understand the information flow with consulted group
        • Understand where info & content is generated and at what pace
        • Understand what the incentives are for each stakeholder group to maintain the KB
          • sourcecred + github or did-a-thing discord channel with emojis as weights
        • Align on an info flow model and implementation plan to present to CSDAO gov
          • FAQ: Discord → user asks a question → question is not listed yet → added in KB
          • Support/ticketing system
            • Intercom on the knowledge base and maybe also on other gitcoin websites ?
            • - A dedicated support/ticketing app
            • Discord only with a bot ?
          • FAQ: Brainstorming → what questions or errors users could run into ? → added in KB
          • Handbooks: Workstreams & squad leads generated content & MMM
          • Products: Gitcoin.co & MMM→ tutorials & articles → added in KB
          • Use of templates
      • Step 3 - Get CSDAO Governance approval to move forward with results
    • Phase 2 - Implementation
      • KB squad to ensure up to date info is all ready to go in new kb
      • Engineering to point support.gitcoin.co to new kb
      • Implementation of process
        • Visualization of the process
  • Clarifying Questions:
    • Joe: support.gitcoin.co should be pointing here - should become primary source of truth? when all is clear, then we move?
    • Kris: who approves content? The ones who are involved will approve. Joe: The design will approved here.
    • Kyle: Feels like the customer is the support team + other teams in the dao. Do you continue to see the dao as the customer? DCompass is the dapp, not every will use gitbook.
      • Right now, Happy Fox is our Knowledgebase. And it is without an owner, but with a clear customer of Gitcoin Holdings.
      • The goal would be to move to this knowledgebase, fire Happy Fox and have the DAO use the new knowledgebase with DAO workstream leads able to provide updated content.
    • Kris: What are we approving today? What we already have on the support site we would be moving here. The backbone would be the support part.
    • Annika: Who defines the scope of what’s in the KB? It will be more the workstream who defines this.
    • Kyle: Do we have any analytics with gitbook as we have with happyfox etc? Yes. All the tools work with then.
  • Reactions:
    • Annika: overall, I’m supportive. We need to be superclear on who the customer is, what the specific roles are. Otherwise it becomes difficult to prioritize what goes in there.
    • Joe: Happyfox has advantages, but this OSS version makes it accessible to more people. Supportive.
    • Sean: Supportive of this proposal
    • Kyle: Supportive. Seems like we need to move anyway.
    • Kevin: Agree that it aligns as it is open source. Good to hear that Yuki & Bob are agreeing here
    • Kris: Supportive of open source. Not sure if more than support needs to be integrated, unclear how
  • Amendment notes:
  • Objections?
  • Proposal passed!
🗃️
Contributor Access Bundle DBs
/
Move to the New Open Source Knowledge Base

Move to the New Open Source Knowledge Base

Proposed By
Essential Intent
Outcome
PASSED
Proposal Date
Jan 4, 2022
Meeting Notes
Type
Tooling
Last edited time
Jul 28, 2022
Meeting Notes:
Outcome: Passed ✅
Outcome Summary
This proposal passed, and we will replace the knowledge base currently at support.gitcoin.co by moving to the new open source knowledge base as our single source of truth.
Proposal
Proposal 1 - Move to the New Open Source Knowledge Base (huxwell)
  • Tension: We need one source of truth for Gitcoin with less barriers to access than HappyFox
    • It is difficult to move forward because there are so many different entities involved
    • updating info in two places as we anticipate moving is becoming tedious
    • using the open source kb would be "walking the walk"
    • Right now no one "owns" the knowledge base
  • Proposal: Move to the new open source knowledge base as our single source of truth and replace the knowledge base currently at support.gitcoin.co
    • Phase One - Discovery
      • Step 1 - Appointments to a DACI model
        • Driver = Huxwell as he has been granted the budget (and blessing) by stewards in this endeavor. He may appoint Riely or other to co-lead with him.
        • Approver = CSDO
        • Consulted = Cross Functional group of "consulted" stakeholders which manage production of content for the knowledge base
          • PG/Grants = Annika, MMM/Product = Sean, FDD = Joe, dGitcoin = Philip, MC = Owocki or emu, Support/Translations = Riely
        • Informed = Everyone else (will make clear list and communicate at the right time)
      • Step 2 - Design PowWow to understand the information flow with consulted group
        • Understand where info & content is generated and at what pace
        • Understand what the incentives are for each stakeholder group to maintain the KB
          • sourcecred + github or did-a-thing discord channel with emojis as weights
        • Align on an info flow model and implementation plan to present to CSDAO gov
          • FAQ: Discord → user asks a question → question is not listed yet → added in KB
          • Support/ticketing system
            • Intercom on the knowledge base and maybe also on other gitcoin websites ?
            • - A dedicated support/ticketing app
            • Discord only with a bot ?
          • FAQ: Brainstorming → what questions or errors users could run into ? → added in KB
          • Handbooks: Workstreams & squad leads generated content & MMM
          • Products: Gitcoin.co & MMM→ tutorials & articles → added in KB
          • Use of templates
      • Step 3 - Get CSDAO Governance approval to move forward with results
    • Phase 2 - Implementation
      • KB squad to ensure up to date info is all ready to go in new kb
      • Engineering to point support.gitcoin.co to new kb
      • Implementation of process
        • Visualization of the process
  • Clarifying Questions:
    • Joe: support.gitcoin.co should be pointing here - should become primary source of truth? when all is clear, then we move?
    • Kris: who approves content? The ones who are involved will approve. Joe: The design will approved here.
    • Kyle: Feels like the customer is the support team + other teams in the dao. Do you continue to see the dao as the customer? DCompass is the dapp, not every will use gitbook.
      • Right now, Happy Fox is our Knowledgebase. And it is without an owner, but with a clear customer of Gitcoin Holdings.
      • The goal would be to move to this knowledgebase, fire Happy Fox and have the DAO use the new knowledgebase with DAO workstream leads able to provide updated content.
    • Kris: What are we approving today? What we already have on the support site we would be moving here. The backbone would be the support part.
    • Annika: Who defines the scope of what’s in the KB? It will be more the workstream who defines this.
    • Kyle: Do we have any analytics with gitbook as we have with happyfox etc? Yes. All the tools work with then.
  • Reactions:
    • Annika: overall, I’m supportive. We need to be superclear on who the customer is, what the specific roles are. Otherwise it becomes difficult to prioritize what goes in there.
    • Joe: Happyfox has advantages, but this OSS version makes it accessible to more people. Supportive.
    • Sean: Supportive of this proposal
    • Kyle: Supportive. Seems like we need to move anyway.
    • Kevin: Agree that it aligns as it is open source. Good to hear that Yuki & Bob are agreeing here
    • Kris: Supportive of open source. Not sure if more than support needs to be integrated, unclear how
  • Amendment notes:
  • Objections?
  • Proposal passed!