completed

Open Ideas and Data For Cooperation

$33,470.00 Received
$33,470.00 Requested
Ideascale logo View on ideascale
Community Review Results (1 reviewers)
Addresses Challenge
Feasibility
Auditability
Impact
ソリューション

Build data pipelines off-chain to integrate proposal and community tools in a form suitable for integration by structures of accountability.

Problem:

Catalyst Communityでは、IdeaScale APIはメンバーの個人情報を保持しているため、使用することができません。[1].私たちは、毎回手作業でデータをキュレーションしているため、時間がかかる [2][3]。

Yes Votes:
₳ 162,528,078
No Votes:
₳ 24,361,151
Votes Cast:
709

チーム

This proposal was approved and funded by the Cardano Community via Project F5: Distributed Decision Making Catalyst funding round.

  • Video cover image

This is an Adagov.org Project.

 

 

 

Why is Open Ideas and Data Important?


We build hierarchical, categorical proposal submission systems that are inefficient for messaging and we ask ourselves: "Why don't groups cooperate more on Catalyst?"

The systems we have are perfectly designed to give us the results we're getting.

 

We need more than to generate proposals:

  1. We need a way to assess proposals against a collective direction

  2. We need to ensure projects deliver Return On Intent

  3. We need to ensure project teams are held accountable and rewarded for their contribution. [6]

 

The goal is to create a more holistic, integrated, community friendly system (initially off-chain) that can expose proposal and review data so that we can build systems that can offer curation and accountability. This will improve processes and systems that will help each funding round and build between the gaps.

Currently we manually repeat processes with spreadsheets but as we scale, these will have their limits.

 

 

 

The Truth About Data


Data is the core to data-driven decision making - which provides multiple perspectives on the objective truth. The closer we are to truth, the better chance we have at making successful decisions and funding projects and teams that work.

When we reinforce these systems with peer-review and allow feedback to occur, we get the best results. [6]

Good data hygiene and systems to support this are fundamental to building the technology that drives our community and dealing with issues of scale, fairness, audit-ability and traceability.

Note: Placing this data on-chain is a separate process to experimenting and defining the way these systems will work.

Summary


Data Management is the heart of the Project Catalyst Community and key to a Meritocracy. The success of the community depends on the ideas we pick. Every product or offering evolved out of Catalyst will first begin as a proposal within these tools.

We also want to feed-back these delivery metrics into a believably or merit weighted results to make future rounds easier.

As an extra we would like to gamify the process further so repetitive work, where it cant be automated, is more engaging and that reviewers who contribute and get it right earn recognition.

 

 

 

Who Is This Proposal For?

These tools are for the Project Catalyst community to help:

  1. Voters easily decide who they will vote for in subsequent funds based on performance.
  2. Proposers effectively draft, collaborate and submit their best ideas and find teams as they do so.
  3. Community advisers review, contribute and rate these ideas using supporting tools.
  4. Allow Veteran Community Advisers provide training and feedback ensuring a fair and equitable outcome.

 

 

It will improve the following challenge metrics:


Proof of iteration: Round over round, "pain points" like data curation, processing and reporting would evolve.

Re-election rates: More proposers receive subsequent funding.

Embracing failure: Community would be able to track and see value in & learn from proposals that did and did not work out.

 

 

Auditability


Fund 5 Scope: We will comprehensively examine, select and trial and integrate an alternative idea management platform into data analytics and reporting tools so that reviews can take place faster, more effectively and at scale.

[Completed] Develop a requirements framework for open data sharing between ideation and auditing platform.

[Completed] Develop a comprehensive review of idea management and execution platforms [5]

[Completed] Trail free-to-trail services around idea management. (Trailed Nectir, Monday.com and Ideanote)

[In Progress] Investigate and pursue Data Interoperability - Access to IdeaScale API

[Pending] Investigate alternative integrations / Data and Reports Area

[In Progress] Begin accepting community feedback.

[Vote-Pending] Onboard interested members of community for trail and feedback. (3 month)

[Vote-Pending] Present in swarm which options pose risks and recommendation. (3 month)

[Vote-Pending] Further review of on-chain integration (and suitable rollover pathway). (6 month)

[Vote-Pending] Integrate to existing projects and offer the data back to the community. (6 month)

[Vote-Pending] Develop training materials to allow interested members to connect. (6 month)

[Vote-Pending] Swarm session to review project in context of others. (6 month)

[Vote-Pending] Ensure the interfaces for the framework meets suggestions previously made for IdeaScale (where needed). (12 month)

[Vote-Pending] Provide, open free community curated data with a data model via a common interaction point. (12 month)

[Vote-Pending] Build basic reports so that proposals are fairly evaluated (3 month)

[Vote-Pending] Build review and cross review tools and systems that can help anomalies be identified. (3 month)

[Vote-Pending] Idea Atomisation - Break proposals down into smaller components for continuous review and reuse in later Funds. We will connect with other groups in F5 that are working on this concept.

[Proof Of Concept] Proposal Wizard - Guided proposal wizard to educate and direct novice Catalyst users to submit proposals: http://submit-proposal.adagov.org.

[Vote-Pending] UX / UI Design consultation sessions toward a Social UX/UI system.

[Vote-Pending] Onboarding and Training of Administrators and Devs.

 

 

 

Fund 4 Scope: Vote for us in F4! Setup Adagov and Design Consultation Sessions for Social UX: Swarm Sessions.

[Self-Funded] [80% Complete] [Proposal: http://fund4.adagov.org] [Complete] Create channels of communication in line with that of Project Catalyst. [Complete] Test the appetite for a Working Group / Community of Interest [Complete] Begin onboarding projects that genuinely share the same principles and values: Voltaire Assistant, Swarm Sessions [Complete] 4 Workshops: Swarm Sessions 01-08 [Complete] Establish understanding of high level group constraints, wants and needs. [Self-Funded] Take advantage of corporate/ team discounts to provide groups with tooling: Miro, Airtable [Complete] Subdomain [email protected] and limited hosting to project / proposal teams. [Vote-Pending] Establish a members agreement that would state basic rules of engagement with adagov.org [Complete] Update our communications for visual engagement: https://adagov.org [Complete] We may provide endorsements / guides for interoperable or cooperating projects in F5.

 

 

 

Budget


  1. Tools and Licences (Community Data Portal, Tools Hosting Swarm Sessions)

$8400 USD for Stacker, 15 Administrators Community Size 2000, 2 Years - API w/ 5 Tp/s

$8640 USD for Airtable, 15 Administrators, Community Size 2000, 2 Years

$7860 USD for Miro, 20 Administrators, 2 Years, Day Passes for Occasional Administrators, Community Access

  1. Review and Identification Tasks $1000

  2. API Endpoint PII Deidentification, Processing and Integration Work $5000

  3. Swarm Sessions and Training $2500

  4. Training Creation, Hosting and Explainers $250

Total = $33470 USD

 

 

 

Feasibility

How can we build production grade software this quickly and cheaply?

  1. We'll investigate existing solutions in the field
  2. We'll pick the solution that covers the most features with the best UX for a reasonable price
  3. We'll negotiate a better enterprise licence model for our community
  4. We'll negotiate to have developers enhance the tools further as a part of licencing
  5. We'll configure the tech to match the requirements.
  6. Where gaps exist we'll create integrations to connect to other tools.
  7. We'll overcome risk of delivery by leveraging a class of applications known as middleware
  8. We'll ensure integrations can deliver data reliably and securely to publically accessible sources
  9. We'll audit our work to ensure PII is not being leaked
  10. We'll review and present progress regularly to the community.

 

 

 

Impact

Our objective is to have a smoothly working alternative dataflow and data reporting setup as soon as possible. We estimate if our Fund 4 vote is successful, we can have such a system by Fund 7. We will continue to work with the community and IOHK in training and handover. The key goals of this project are high impact items for the community:

  1. Automate much of the repetitive work done between funding rounds by community advisors so they can focus on community and proposer issues, growing proposals, maintaining community documentation and standards and providing feedback.
  2. Provide the community with standardised open access to data so they can grow and build out the tooling ecosystem.
  3. Support off-chain decision making with data while on-chain systems are established.

 

 

 

References


[1] Catalyst Problem Sensing has 74 out of 223 entries related to incomplete UI / UX or have needed alternate solutions

[2] Project Catalyst Discord [31/03/2021@2:14 PM] #reviewing-the-reviewers. See: https://discordapp.com/channels/756943420660121600/810761956210376735/826701078590390322

[3]

[4] http://fund4.adagov.org

[5] http://ideamanagement.adagov.org

[6]

 

 

Launch Date


Project is in Alpha at http://apps.adagov.org.

Release in Sep 2021.

Definition of Success

Received emails from [email protected], How my proposal impacts the challenge metrics, Broken down my budget requirements, Defined expected public launch date., How I address the challenge question, Submitted this proposal to only one challenge, Definition of success after 3, 6 and 12 months, Included identifying information about all proposers

コミュニティ・アドバイザー・レビュー (1)

Comments

Monthly Reports

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3分 24秒
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4分 3秒
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3分 48秒
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2分 16秒
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3分 14秒
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3分 19秒
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4分 59秒
    Darlington Kofa
0:00
/
~0:00