Note: Only the desktop version of the software is considered within scope for the v1 release. Follow up releases will be applied to all other platforms in order to catch up. The desktop version was selected as it supports the integration of all features.
The following outlines the necessary features required in order to meet the objective for a verion 1 release of Verto. All facets are to be considered complete before a final version 1 release.
In short, this version will focus on the following:
- Maximization of Security
- Data Sovereignty
- Third Party Plugin Mechanics
- Build Integrity
In order to accomplish our goal, we will break down this roadmap into the following features.
The goal of this feature is to create a build pipeline that will, upon all pull requests, build and test the software for all platforms.
For this phase of development, we are looking at an MVP with the following tasks:
- Linter
- Automated Security Audit
- Test Suite
- Build Artifacts
Out of scope for the first version:
- Release Management
- E2E
- Platform specific testing
The goal of this phase is:
- Research
- Impact assessment
- Estimation of effort
- Go / No Go decision on the migration efforts for migrating to webview
- Updated roadmap to reflect the decision made
The goal of this phase is to create the MVP for the management of identity within Verto. This MVP includes:
- Local storage
- Third party API
- Documentation on usage by plugin developers
Out of scope:
- Multi-tenancy
- Multi-identity management services
- Limited to local storage
- Data storage solution using w3c standard
- Data retrieval and store solution
The goal of this phase is to create the MVP for the management of third party app extension within Verto. This MVP includes:
- Loading and validating of the plugins
- Isolation of plugin (no visibilty into the parent view object) functionality
- Integration mechanics for the SI feature to 3rd party developers
- Plugin + Verto availablity mechanics. The process of having an app approved.
Note that the following is out of scope for this version of the feature.
- Decentralized distribution of plugins
- Update notification services
- Visual dashboard management of plugins
- Decentralized marketplace mechanics
- Automation on 3rd party functionality integration
- A single plugin will be shipped with Verto. This plugin will adhere to all the mechanics and integrity checking that future plugins will be subject to, however, this plugin will not be distributed, discoverable, etc.
- App runs in a sandbox and shares data with the SI API.
- Review process defined and documented for inclusion into the Verto ecosystem
This feature will manage the installer and updater process. Note that it has a dependancy on the migration to Webview. Regardless, this feature needs to be optimized for better user experience and security.
The outcome is based on the go / nogo for the migration of electron to webview. Once this decision has been made, this section, as well as any estimates, will need to be updated.
Regardless of the decision, the installer will need to:
- Download and start the latest stable release for your platform
- Enable the integration of plugins
This feature intends to do the research and gather the requirements for more advanced usecases for authentication management. For example, integration with 2FA.
The team will provide:
- Documented strategy and implementation specs with research outcomes
- Estimation of effort
- Updates, if any, to this version of the roadmap
The workload above will be broken down into the following phases.
120 - 160 hrs
In this phase:
- Research will be conducted
- Documentation repo set up
- System level documentation
- Work unit decomposition
- System Architect
- System architecture documented and available for public review.
- Developer bounty strategy defined
- Defined backlog of work units
24 - 40 hrs
Goal This phase is about setting up the system for developers to begin developing the features in a clear, productive, and intuitive way. This, in general, consists of the following facets:
- Build infrastructure: This is the local build as well as CI build environments.
- Developer experience: Tools that facilite the developer experience and maximize their contribution.
- Documentation: The strategy, location, and management of documentation as the system begins to take form.
Additional goals, outside of engineering, is to publish broadly in order to receive community feedback on the direction of the architecture.
- System Architect
- Security Analyst
- Senior Developer
- Build integrity complete with local and CI build functions.
- Developer experience maximized for broader community contributions.
- Community feedback channels created and monitored
N/A
No end date. As it is envisioned that the development team be decentralized and capable of working on individual work unit. Work units are tasks that is part of a feature.
This is the phase of developing a feature and preparing it for release. The phase follows the guidelines for Volentix such as:
- Code Lifecycle Management
- Documentation
- Security
For a full description of the documenation process please see our documentation.
- System Architect
- Security Analyst
- Community Developer
- Community Contributor
- Features meetings the standards of Volenix and is ready for release.
In some cases, dependencies between other systems and other teams exist in order to facilitate a feature's completion. For example, VDex may be required to publish an API in order for Verto to consume it.
There are no known dependencies at this time.