Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add files via upload #34

Merged
merged 1 commit into from
Sep 27, 2022
Merged

Add files via upload #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions documentation/Minutes/MOM_Convergence - 202209160.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Meeting Minutes Convergence Substream - 20220916

Fri, Sep 16, 2022 17:00 PM
<br>
## **Attendees**

* Andrew Wajs(Scenera)
* Deepak Gunjal (Capgemini)
* Kevin Smith (Vodafone – 5GFF)
* Mahesh Chapalamadugu (Verizon - 5GFF)
* Syed Rehman (Verizon - 5GFF)
* Thomas Vits (EdgeXR)
* Lev Shvarts (EdgeXR)
* Alexandre Harmand (TEF)
* Rebecca Odenwaelder (Deutsche Telekom)
* Marc Cornall (GSMA)
* Alexandru Ciinaru (Orange)

## Kickoff disucssion

<span class="colour" style="color:rgb(36, 41, 47)">This call was to initiate the activity of the convergence substream.</span>

| Item | Who | Description |
| ---- | --- | ----------- |
| Substream Objectives and way of working| All | EdgeXR provided a suggestion on the objectives of this substream, below the aligned outcome after discussion <br> 1. Situation: The EdgeCloud Project in CAMARA received already 3 API contributions (from 5GFF, Capgemini, EdgeXR) potentially addressing similar or same functionalities exposing edge cloud services <br> 2. Challenge: (Assumption) The goal in CAMARA is to have single API set for a given developer intent (on a specific abstraction layer). <- This was a point of discussion whether that assumption actually holds true or whether different APIs could be feasible for the same intent. No final conclusion taken at this point. <br> 3. Solution: Original proposal was to work on the assessment of the current/coming contributions but after discussion we concluded that the initial step to enable this would be to create an aligned taxonomy/terminology. This will ensure that we have the right vocabulary to actually do this assesment acknowledging that background of the distributions is diverse with having different taxonomy in mind. </span></li></ol> |
| Logistics | All | 1. In order to be able to continue this substream despite of vacations etc. the group agreed to appoint Kevin (VDF/5GFF) as Co-Lead with Thomas (EdgeXR) for this substream.<br> 2. Group agreed on a bi-weekly meeting cadence; as we have participants from literally all timezones we agreed to shift timeslots every 2 meetings to the next timzone (e.g. by around 8 hours) <br> 3. Agreement that all discussions / documents shall be strictly happen in git|
| Establish aligned Taxonomy| All | As agreed in the initial disucssion the first step is to establish an aligned taxonomy. It was suggested to use the OPG definitions as a basis and then iterate on it in git to come to a consensus. Once good enough (to be agreed by the group when this milestone is hit) the next step (i.e. making an assesment of the scope of the different contributions using that taxonomy) can be initiated. Deepak, Thomas and Mahesh volunteered to get the intitial commit going. |