Detailed Plan

About the project

The Community Landing Page (AKA Community Site) is set up to be a community operated, edited and developed site for the Cardano Project Catalyst Community. It's been in operation since Fund 3 and with successful funding in Fund 4 has started experimenting with voting on the community voted and submitted Github issues.

The Community Landing Page is designed to offer a launching platform of resources and tools for various stakeholders in the process: Voters, Proposers and Community Advisors. As well as offer information to the casual participant and interested person.

The site links to resources such as community guidelines, communications channels and provides access to data and information such as community statistics, fund timelines and official and unofficial community generated project resources.

The site hosts the popular Community Tools https://cardanocataly.st/en/tools/
that includes CA, vCA and voter tools. We are also partnering with Victor Corcino with generating and displaying community statistics. The related proposal can be found here: <https://cardano.ideascale.com/a/dtd/Catalyst-Exploratory-Data-Analysis/368899-48088>

Key Metrics:

Users since we started recording

• May: 592
• June: 2711
• July: 2843
• August: 4705

Bounties:

• Completed: 3
• Active: 7
• Current Bounty Hunters: 3

Github Metrics:

• Issues: 33 closed, 65 open
• Pull Requests: 89 closed
• Commits : 222
• Contributors: 10

Past successfully funded proposal in Fund 4:

<https://cardano.ideascale.com/a/dtd/Project-Catalyst-Landing-Page/341718-48088>

Relevance to Project Catalyst:
We are in top search results for cardano catalyst related queries on Google and DuckDuckGo

Github & the bounty system:

The project repository can be found here:
<https://github.com/Project-Catalyst/project-catalyst.github.io>

We are in the process of building the bounty system, first conceptually, then by building a dedicated software solution. Currently community members can request features using issue reporting in github: <https://github.com/Project-Catalyst/project-catalyst.github.io/issues/new>

Voting can be done by reactions, as explained in this blog entry: <https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/>

Here is a list, we rank them by effective score, "thumb up" +1, "thumb down" -1, "heart" +2, "rocket" +3, the higher the score the more focus it gets, it might result in higher bounty, or changing the category of the bounty. Here is the list of bounties, if you have a github account, come and vote, help us!:

<https://github.com/Project-Catalyst/project-catalyst.github.io/labels/bounty-hunter-needed>

As the bounty system is implemented you'll be able to submit 'issues' requesting updates, content and fixes to the site through a dedicated interface. These will then be able to be community voted upon. Bounties will then be assigned to most relevant issues and offered to the community to resolve and be rewarded.

Set bounties can increase if not picked up by a bounty hunter. Ideally a cadence is set at the time the bounty is created, depending on it's urgency. In this way a kind of market force is offered.

The amount paid in bounties will depend on complexity and volume of work needed to complete. This is an experiential process and is under continual development and community discussion.

Auditability

Auditability and tracking of the process is done and will continue to be done in a transparent way, although some of our goals are unspecific, because what the bounty budget will be spent on depends on the community.

<u>Tracking</u>

The tracking of bounties from previous funds can be found in this document: https://docs.google.com/spreadsheets/d/11vywFU4wEh_7aHnBwIL4NHKgXLYKu9MWurICNyloToM/edit#gid=0

<u>We want to make bounty record publicly available on the website, we are also considering submitting the data to the blockchain.</u>

<u>Visitors</u>

Site usage is another live statistic that we would like to include on the site. A KPI to watch would be month on month growth of users of the site. It's difficult to put a hard number, it depends on the growth of the catalyst community as a whole.

<u>Relevance</u>

Search engine results - We want to maintain our high results in search engines for relevant topics. We are currently on the first page of results, usually in top 5. <u>We want to maintain our relevance</u>

<u>Efficiency</u>

We would be looking at ensuring that a bulk of the funds got to community members from outside the steering team. However, internal bounties will be created when necessary and long term open bounties can also be claimed but the steering team to ensure development is continued at pace. <u>At least 80% of bounties done by way of external bounties</u>

<u>Transparency</u>

The setting of bounties is currently done by the steering team but will be explored how to adjust this over time. A bounty can be set in consultation with the implementer and room is viable for them to be adjusted should the estimated bounty be set too low.

We aim to improve the transparency by <u>providing reasoning for each bounty.</u>

<u>Engagement</u>

We are activating community members and engaging developers, serving as a gateway into the ecosystem. If someone wants to contribute and earn some ADA, they need to learn about Cardano and go through the process of creating a wallet.

We want to engage <u>at least 1 new developer per week</u>. (4 per month)

<u>Bounty Interface & Process</u>

Deliverable: We want to have a well defined and documented bounty system with a MVP implementation so implementation of bounties is streamlined and automated as much as possible. This includes a way for the community to influence the bounty level (ADA).

<u>User Satisfaction</u>

We want to add a simple way for readers of the website to grade their experience with the website/ article and submit improvement suggestions.

<u>80% user satisfactions score (4/5) is our goal.</u>

We want to meet all our goals within th 3-6 months horizon.

Public availability

The site is already public, updates from bounties are applied as soon as they are done by the bounty hunter.
Bounty system is currently publicly available through github.

Budget Breakdown

Internal maintenance/development payments up to (we will aim to make this as low as possible): $3000

These include things like administration, bounty setting, tracking, management of bounty hunters, general management of the site.

Publicly available bounties: $7000

These are the bounties that will be decided by the community, and solved by the community. A mechanism might exist where long term open bounties will be picked up by an internal dev team to ensure that the site development continues.