Skip to content
This repository was archived by the owner on Jul 21, 2025. It is now read-only.

jeffmashaw/Fund10-Documentation-Working-Group

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 

Repository files navigation

Proposer, PA, vPA Guidelines Tasks Set-up Doc

Pre Fund 10, started 2022-10-04

Task Guidance

See Sub-Circle Working Group Process Doc: https://quality-assurance-dao.gitbook.io/community-governance-oversight/circle-problem-sensing/circle-problem-sensing/circle-oversight-working-group

Problem Statement Rubric

  1. Identify (What Problem Do We See?)

    One strength of the Project Catalyst Community is there are many passionate and talented individuals with suggestions for improving the four core process documents (Proposer Guide, Challenge Team Guide, Proposal Assessor, and Veteran Proposer Assessor). These suggestions exist across a large collection of documents and conversations from editable Google Docs, to Telegram, to DeWork, and Discord among many other. There are also copies of current and former documents existing across many project catalyst sites such as IdeaScale, ProjectCatalyst.org, CardanoCataly.st. and others. This is decentralization at work!

    However, a problematic side effect of this in our current context is confusion and uncertainty for many who desire to see the process improved. This confusion stems from questions about where and how to contribute ideas and effort. There is right now no single, comprehensive system or method for helping to improve the Project Catalyst Core Documents.

  2. Rank in Catalyst Context (Why is solving this problem important to the mission of Project Catalyst?)

    Solving this problem in a way that remains decentralized and also organized can be challenging. The goal is incorporate as many voices as possible while providing a consensus mechanism for making changes to the documents that have the greatest community support. This will enable the broadest community support and participation without centralizing the process. Developing a collective system that is open and clear for improving the core documents satisfies the Catalyst vision of collective innovation.

  3. Solution Articulation (Describe the gap between the current state and the envisioned state?)

    The goal is to develop a open source system for improving the core documents of the Project Catalyst roles (Proposer, Challenge Team, PA, and vPA). This process currently takes place in the comments and suggestions of a set of Google Documents. This process requires being able to find and edit the Google Documents. Google documents while being easy to use and collaborative are not open source. Nor do they easily have an open versioning system, or are the easy to clone.

    The prosposed solution would involve hackmd.io which pairs with a github repository that would be open source. Hackmd allows for collaborative editing of documents that can be pushed to a github repository. The github repositroy could manage document versioning, and allow for cloning and translating. It would also allow for inidivudals and community organizations to subscribe for change notifcation so that can share the most current version on their own resource websites such as gitbooks.

  4. Define Metrics (How might the value of solving this problem be quantified and/or measured?)

    Measuring success of this project would entail looking at two metrics.

    1. The number of participants in the editing process. If successful, this project would see the number of participants engaging in the document improvement process increase dramatically from fund to fund.

    2. The number of pull requests from the documentation repository. If successful, this would mean that organization and indivudals are linking to the documents

Mission

  • To collate and implement community suggestions for improving Proposer, PA, and vPA Guides
  • To standardize the Project Catalyst Documentation (Proposer Guide, PA Guide, and VPA Guide) for Fund 10 across all info channels
  • To provide consistent objectives for proposals across all three stages (Proposer, PA, and vPA)

Goals

  • Define tasks and deadlines of tasks that need to be done. (1 wk or less)
  • Find tasks from TODO and Community
  • Create them as subtasks in DeWork and in this/or a master Document
    • Assign each task a priority
    • Assign each task an estimated # of hours to completion
    • Assign each task a due date/deadline
  • A documentation portal

Working Group Notes

Relevant Links to Current Task

Current Community Suggestions to Improve Catalyst Documentation

Previous Suggestions to Improve Catalyst:

Fund 9 Source Documents

Proir Source Documentation:

Governance and Other Documentation

About

Just Documentation from hackmd for The Working Group Documentation thingy.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published