Proposal Name: Ape Calendar
Proposal Category: ecosystem
Abstract | Two or three sentences that summarize the proposal.
Create a website https://apecalendar.com, and a public iCal url that people can subscribe onto. This will enable the ape community to record events for projects, AIPs, or other related items in order to help spread awareness and knowledge about the ecosystem.
Author Description (mandatory if the AIP is requesting funds) | A brief background of yourself
Dar is a professional software engineer with over 29 years of experience designing, building, and operating web applications with millions of users in domains such as banking, news, entertainment, and others. Been working in web3 for the past six years on various internal corporate Blockchain initiatives using both Ethereum and Hyperledger.
Team Description (mandatory if the AIP is requesting funds) | A brief background of your team involved, if any
The development will be done by Dar, background listed above, and freelance contractors as needed for graphic design, ui/ux design, and software development.
Motivation | A statement on why the APE Community should implement the proposal.
There are many different projects, teams, and AIP authors that do many different discord calls, twitter spaces, video calls and in person meetups that are hard to keep track of when and where they are happening. Additionally, the Ape Calendar can be a place where AIPs can list their progress timeline and milestones as they proceed from idea, to voting, to implementation and ultimately to sunset and archiving.
Rationale | An explanation of how the proposal aligns with the APE Community’s mission and guiding values.
The rationale is to make information available to the community at large to be informed. Also encouraging and facilitating cross pollination among projects by making information freely available.
Key Terms (optional) | Definitions of any terms within the proposal that are unique to the proposal, new to the APE Community, and/or industry-specific.
No key terms are defined at this time.
Specifications | A detailed breakdown of the platforms and technologies that will be used.
A website will be created to host the web calendar and APIs. A breakdown of different types of events will be documented along with authentication and authorization rules established in the first phase of project construction. Once the information providers are identified and personae created, use cases for each persona will be documented along with detailed UI/UX designs to be implemented. To keep things moving forward quickly, a working first prototype will be developed and released showing information which can be gathered from WG0, ApeComms, and other well known twitter spaces or video calls with regular iterations. This will demonstrate the utility quickly while a more dynamic interface is developed. The website will be created with AWS services to start, and a more decentralized architecture can be investigated and developed over time.
A calendar page will look like this, showing the days of the month. On each day, the relevant events will be displayed, such as twitter spaces, or discord stages as an example.
See the screenshot of a week in the calendar:
Edit 5/4/2023 - I no longer think this is an AIP that needs funding and to be voted on at this time.
There are a few different people that have been thinking about this type of solution, and it will be relatively inexpensive to create the web app and subscribe-able calendar without creating mobile applications.
What I think can be done is to prototype this solution with feedback from the community, and later when the time is right for either the DAO secretary or Marketing and Communications groups to decide if they wish to bring the operation and maintenance in house or provide funding from their budgets.
It is difficult at this time to estimate the operating cost of the proposed solution. An estimate is approximately 400 $APE/year (based on $4 USD/APE).
I think it can run to collect events and have people use it for some time and keep track of the cost to better understand for the long term. It can be brought into the DAO operations later under the appropriate office or working group.
Looking forward to hearing your feedback!
Proposals submitted to the AIP Ideas category can be vague, incomplete ideas. Topics submitted here are not required to be submitted as a formal AIP Draft Template, however, you may still use the template if you wish.
