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.
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.
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.
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.