-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Quality By Design API proposal #71
Add Quality By Design API proposal #71
Conversation
Hi @benhepworth , thanks for the presentation to the API Backlog call 25th July - as mentioned on the call, there appears to be overlap with Connectivity Insights. From the scope in #70 : report application KPIs to network operator
receive QbD score
receive root cause analysis and recommended corrective actions
request service improvements
@maheshc01 may offer some additional insights (no pun intended) - but overall it would be good to either harmonise or agree how to split the scope. |
…e to be a 3rd party app
Thanks for the feedback @Kevsy . I just joined the ConnectivityInsights mailing list and I see there is a meeting this week. I will email that group to see if I can get on the agenda for this Wed's meeting. There is definitely some overlap and maybe this does indeed belong over there. I'd like to chat further about details with the ConnectivityInsight group and make sure that is the right place for this to land before closing this. ConnectivityInsight has some stuff already that we could re-use (i.e. application-profiles), but there are some things it doesn't have (i.e. a way to send metrics). Will post a more detailed update here after meeting with ConnectivityInsights sub-group. |
Met with the Connectivity Insights group on 8/14. The decision from that meeting is to:
Link to meeting notes here. @camaraproject/api-backlog_maintainers - we are ready for this to go to the TSC for a decision. What are the next steps? |
hey @jgarciahospital - is there anything else for me to do on this in order to get this before the TSC in their next meeting? How will I know when this is on the agenda? |
Pending issue solved, API is now proposed for TSC approval. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per last TSC meeting, group is created and ths pr can be closed
Just that the repository is not yet created (will come soon), and there is the need to collect the code owners and maintainers. Will that happen within the issue? (note: the issue will be closed as well with the PR due to the "fixes:" above) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
PR to be merged as API validated in TSC and group created with participants assigned (thanks @hdamker & @benhepworth). @camaraproject/api-backlog_maintainers can anyone review for merging? |
@caubut-charter @jgarciahospital also here the repository is already created and work has started. Would you mind to merge? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
What type of PR is this?
New API Proposal
What this PR does / why we need it:
API to allow applications to interact with the network.
Which issue(s) this PR fixes:
Fixes #70