Tech specs
The vCA-tool is a SPA (Single Page Application) developed in Vue.js 2 that uses Buefy as a UI components library.
All static data is integrated in the tool, and the work done by vCAs is stored locally in the browser using localStorage.
vCAs are able to use predefined filters in order to focus their attention on specific assessments (e.g. for specific proposals / challenges / assessors, by length, by rating etc.) At the end of the process vCAs are able to export a CSV file fully compatible with the original Google Sheet for vCAs that will be used by IOG to aggregate the reviews and calculate the final classification of each assessment.
In Fund8 (out of the funding scope) we’ll introduce the ability to filter by each in a negative way, excluding a specific criteria instead of including it. All filters, negative or not, can be mixed with each other as before.
For the next funds we plan to update the current version to Vue.js 3, implying the identification of a new UI library (Buefy is not compatible with Vue.js 2) and the integration of it in the tool.
Open source
From the beginning of the creation of the Community Tools we always tried to encourage others to create their own version of the tools, because we believe that diversity in the ecosystem strengthens decentralization and the resilience of the system.
For this reason Community Tools are Open Source from Day 1 and so they will remain so forever.
Please describe how your proposed solution will address the challenge?
This could include info about how the project will align with Challenge KPIs?
How will the outcomes of your project be communicated or marketed once completed?
This proposal will allow us to maintain existing features and digest Fund data to undertake operations for Fund 9 and Fund 10, and eventually adapt it in case of major changes in the Catalyst process.
Continuing to maintain the iterative approach followed since the first introduction of the tool to the community, the proposal will also allow us to add additional features requested by the community and identified by us.
This proposal will add to the Challenge KPI of 'Number of maintenance proposals and groups created' in that it is a maintenance proposal.
Please provide a short summary of the main challenges or risks and your strategy to mitigate them?
Given that the project is already successfully in operation and maintained for several funds, there are always risks about people’s involved in the active development, who could encounter blockers of any type that will prevent them from working and delivery.
For this reason, AIM has already on boarded two additional devs who will be responsible of the maintenance and the development of the tool. We have engaged two quality devs in order to have a backup in case of any problems.