A spreadsheet outlining items from Roadmap 2020/2021 and potential items for this roadmap is available here.
A Video recording of the meeting to discuss this is available here.
The purpose of this document is to collect various ideas for inclusion in the Fledge roadmap; these ideas can then be presented to the TSC for discussion and prioritization into a roadmap for Fledge for 2022/2023. Community input is requested to extend the set of items for possible inclusion.
Once this document has been reviewed and discussed at the TSC meeting, each potential item will be given an ID, and the voting members of the TSC will be asked to give priority to the item for inclusion. This will determine what items become part of the roadmap for the coming year and which are excluded. It does not guarantee inclusion within Fledge within that year, as this depends on resource availability. It is also recognized that specific user requests may interrupt the roadmap progress and introduce new additions or modifications to Fledge that are not part of the roadmap.
A reminder of the scope of Fledge is included here to help bound and direct the ideas proposed for inclusion in the roadmap.
The roadmap items are broken down into several groups; Core Enhancements, Documentation, the various plugins, Promotion, and LF Edge Project Integrations
We will work to document hard requirements for advanced HA cases.
This year we will concentrate on the low-hanging fruit. Dianomic has working methodologies for achieving limited high availability. These methodologies will be documented and shared.
IBM has lightweight, edge-ready Kuperneties-style models working in the Open Horizon. These efforts will also be shared.
Need detail on this
There are Web API methods that still require documentation
Updated and expanded user guides will be developed to include:
Fledge is a mature product with many users. With the release of version 2.0., it is time to concentrate on getting the word out and sharing experiences.
This integration was started some time ago and needs to be addressed. There is probably some bitrot.
This project is using Fledge in reference implementations
This project has a service which pulls the Docker file from the Fledge repo, building, and running it. They need to show it connecting to the Fledge control plane.
Explore working with them