Project Technical Lead:
Project Committers detail:
Initial Committers for a project will be specified at project creation. Committers have the right to commit code to the source code management system for that project.
A Contributor may be promoted to a Committer by the project’s Committers after demonstrating a history of contributions to that project.
Candidates for the project’s Project Technical Leader will be derived from the Committers of the Project. Candidates must self nominate by marking "Y" in the Self Nominate column below by Jan. 16th. Voting will take place January 17th.
Only Committers for a project are eligible to vote for a project’s Project Technical Lead.
Please see Akraino Technical Community Document section 3.1.3 for more detailed information.
|Committer Bio||Committer Picture|
Self Nominate for PTL (Y/N)
|Gerry Winsor||Nokiafirstname.lastname@example.org||Gerry is a Senior Consultant with Nokia NSW, who has worked on Hybrid Cloud designs & deployments since 2012. Gerald has been responsible for design & productization of Hybrid Cloud Management and API Management solutions, and has delivered Developer Ecosystem management solutions for numerous MSPs.|
Use Case Details:
Companies Participating / Committers
Requested Release / Timeline
Akraino Portal (Dashboard & GUI)
Akraino Portal provides user interface to deploy edge sites, install additional software, initiate add-on services, enable testing services, etc.
a. e2e testing for Tempest to verify open stack installation & readiness
Impacted Blueprint Family - Network Cloud
See attachment for additional details
The following document lists detailed reasons for having a Portal, how it improves the overall functionality of Akraino and very detailed mockup's of suggested portal screens which represent movement to a new and more modern design paradigm with better human factors. These materials were presented at the first weekly Portal Feature Project Team meeting.