Cardano's Headless Community Events Hub

[GENERAL] Name and surname of main applicant

Peter Wolcott

[GENERAL] Email address of main applicant

peter@tecoreo.com ( Ideascale, Twitter, Discord, Telegram: @sirwolcott )

Additional applicants

Darlington Wleh ( darlington@lidonation.com )

Jonathan Adjei ( Ideascale, Twitter, Discord, Telegram: @jadjei )

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

7

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language.

No

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

No

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.” .

No dependencies.

[GENERAL] Will your project’s output/s be fully open source?

Yes

[GENERAL] If NO, please describe which outputs are not going to be open source. If YES, please write “Project will be fully open source.”

Project will be fully Open Source.

[METADATA] Category of Proposal

Events

[IMPACT] Please describe your proposed solution.

The big idea is to create a distributed repository of Cardano Ecosystem Events. All ecosystem events will be aggregated and stored in git as json files, much like the Cardano Token Registry setup. With all ecosystem events going into a distributed database, groups like Catalyst Swarm, Singularity Swarm Lidonation, Plats Network, Schedulesite, Naptcha (& anywhere else) can use the shared source database to display events their community cares about or can add other features on top of the events data.

We are starting with Git for the V1 to limit centralized single points of failure while we iterate and standardize on an event metadata standard that can potentially move to a decentralized storage solution (eg. Iagon).

To increase accessibility, we will also be developing a simple web interface for non-technical teams to use for uploads.

[IMPACT] How does your proposed solution address the challenge and what benefits will this bring to the Cardano ecosystem?

The OSDE challenge wants to increase the availability of open source projects, open-source frameworks, and accessible knowledge. 

Our proposal will create a data layer with a framework for developers and other companies in the event management space to push new events to the distributed data layer with a standardized schema. 

Some direction suggested by the challenge: Developing common tools, frameworks, core infrastructures, or proof of concepts

This distributed events data layer and tooling around it, perfectly answers the common tools and framework. With adoption of a common way to store Cardano Events, our proposal can become a core infrastructure layer for storing and syndicating Cardano Events. We plan to introduce a CIP draft to further standardize a metadata standard for Cardano Events. 

[IMPACT] How do you intend to measure the success of your project?

This is an open source project. Events is something every team or community have, we will be able to easily track success by looking at;

• How many events are added to the distributed git storage.
• How many community sites are displaying events from the db.
• How many open source contributions (or new drivers) are submitted by the community. 

Collaboration with existing and upcoming Event-related projects and improvements to the Cardano/Catalyst Ecosystem. This solution is intended to begin the ‘headless dApp’ that is the backbone of event distribution across the ecosystem.

This is not intended to compete with any other application or project. 

[IMPACT] Please describe your plans to share the outputs and results of your project?

Our plan is to continue hosting spaces for our intent to collaboratively develop the Cardano Community event webstack. We are NOT targeting users, so our results are directly intended to be built upon in the future. 

Outputs and results will be shared on Swarm and Lidonation announcement channels. 

Progress will be shared through monthly reporting, continued conversations & collaborations.

[CAPABILITY/ FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability?

We are sourcing all of our talent from community members and project contributors building event related tooling in the Cardano Ecosystem. 

One of our co-proposers, Darlington and the @lidonation team have 15+ years of software engineering experience as well as managing dev teams. Lido Nation has a blockchain lab in Kenya with quality devs already contributing to community resources used and loved on a daily basis including by not limited to:

• The Catalyst Explorer
• Lidonation.com
• Roundtable Multisig Wallet

We are currently in search of a CIP Editor & Drafter to spearhead, research and draft a Cardano Improvement Proposal. After consulting fellow community members actively working on CIPs, we estimate:

• 45 days of paid work ( 1.5 months )
• 90-120 days of asynchronous work
• ~2 hour per day 

A metadata standard and instigation of community discourse are vital elements of this project. This work stretches months and takes a significant amount of deliberate focus. It is a conversation, sometimes a negotiation, between stakeholders and builders around the globe.

[CAPABILITY/ FEASIBILITY] What are the main goals for the project and how will you validate if your approach is feasible?

Our objective is to begin aggregating community events in a distributed data layer that future and current projects can access and input event related information. 

We would see this achieved when any project can access the database and use data to display said events in a personal or public portal. This iteration of the project DOES NOT include any UI or user-intended tooling. 

The Cardano Community, being global, will always need a way to coordinate times and share opportunities to meet. Success should be measured by collaborations. We could manually create a large data set of events, but the goal is to invite our Cardano Community Collaborators to build on top of a distributed database we maintain. 

[CAPABILITY/ FEASIBILITY] Please provide a detailed breakdown of your project’s milestones and each of the main tasks or activities to reach the milestone plus the expected timeline for the delivery.

In Progress - Insights & Wisdom Appreciated!

Milestone X: Example Milestone

Outputs/Deliverables 

• 
  

Acceptance Criteria

• 
  

Evidence of Milestone Completion

• 
  

Milestone 1: Foundation (1 month)

• Define Contribution guidelines
• Agree on code stack and initialize project
• Define flat file db structure
• Define Group Model Schema
• Define Event Model Schema

Milestone 2: Receiving the Data (2 months)

• Event uploader headless DApp
• Implement ICS driver
• Implement Event Submission form
• Git integration to create pull requests from submitted events
• Unit/Feature test for enforcing data integrity
• Github action for validating pull requests
• Api to json service
• Openapi spec

Milestone 3: Distribute Data (2 Months)

• Bootstrap application
• Module for fetching and filtering events
• List view of groups with events
• List view of events
• Single group view
• Single view
• UI for visitors to filter and find events

Milestone 4: Drafting CIP + Docs (6 Weeks)

• User Journey Documentation
• Technical documentation for operators and implementers
• Event metadata CIP draft
• Document pull request guidelines

Milestone Final: Education & Marketing

• Education posts
• Twitter campaign
• Youtube campaign

Tickets completion and work being done will be managed via this board:

https://github.com/orgs/swarm-press/projects/4/views/1

[CAPABILITY/ FEASIBILITY] Please describe the deliverables, outputs and intended outcomes of each milestone.

In Progress - Insights & Wisdom Appreciated!

Here are the specific outputs from our work:

• Github repository of events
• CIP draft with event metadata schema 
• Reference implementation on Swarm website displaying events

Additional Outputs

• 2 Articles on lidonation
• 3 After Town Halls
• 3 Twitter Spaces to Educate
• 1 Video Walkthrough Functionality

[RESOURCES & VALUE FOR MONEY] Please provide a detailed budget breakdown of the proposed work and resources.

In Progress - Insights & Wisdom Appreciated!

[RESOURCES & VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

Incalculable <- The Truest Answer

In our experience navigating notification management on all platforms to be informed of Cardano Community Events is an impossible task and this data layer will resolve an aggregation problem that any Cardano Community builder can then sort and display in any desired style or application.

[IMPORTANT NOTE] The Applicant agreed to Fund10 rules and also that data in the Submission Form and other data provided by the project team during the course of the project will be publicly available.

I Accept