GSoSD Review Discussion Tracking Issue

[emanuelpalm]

As part of #54, we decided on 10 discussion points that need to be resolved before we can proceed to release the GSoSD. Here, the issues related to those discussion points are listed such that we can monitor how those issues are progressing.

Issues whose names are not links have not yet been created, or not yet been added to this list.

1. GSoSD Review Discussion Point 1: Should Arrowhead systems be "lazy" (passive) or "active" (proactive)? #58
   • Lead: Per Olofsson, Sinetiq
2. GSoSD Review Discussion Point 2: What "specification documents" should exist apart from the GSoSD, the Concepts Reference and the Foundational Principles documents? What is the scope of each document?  #66
   • Lead: Pal Varga, BME
   • Related Issues: Arrowhead documentation strategy need to be documented #59, Documentation overview #35.
3. GSoS review discussion Point #3: How do we name clouds, systems, services, operations, devices and other components? Should there be both human-readable names and machine-readable names, or can one type of name be used for both? #69
   • Lead: Cristina Paniagua, LTU
   • Related Issues: Regular Naming Convention for Systems, Services and Service Functions #4, Repository Naming Convention #19.
4. GSoSD review discussion Point 4: How do we name the Orchestration System (Core) and the Choreography System (Support) such that we avoid unnecessary confusion from the Microservices communities? #67
   • Lead: Felix Laringa, University of Mondragon
5. GSoSD Review Discussion Point 5: Should all current kinds of orchestration be supported by the same one orchestration system? #65
   • Lead: Jerker Delsing, LTU
   • Related Issues: The Orchestration process (4.6.0) in details  #55.
6. GSoSD Review Discussion Point 6: The Role of an Authentication System? #64
   • Lead: Per Olofsson, Sinetiq
7. GSoS review discussion point #7: What authorization mechanisms should be supported by the Authorization System? OAuth 2.0? OpenID Connect (together with the "Authentication System")? #70
   • Lead: Olof Schelén, LTU
   • Related Issues: Token access policy standardization #13, User authentication #9.
8. GSosD review discussion Point #8: What terms to use for Services and Systems? Microservices and microsystems? #68
   • Lead: Jerker Delsing, LTU
9. GSoSD Review Discussion Point 9: Should Core systems be useful on their own, or can they depend on each other directly?  #62
   • Lead: Rajmund Bocsi, AITIA
10. GSoSD review question #10: What kinds of backwards compatibility should Arrowhead version 5 offer with regards to version 4? #71
    • Lead: Jan van Deventer, LTU

[emanuelpalm]

My hope is that as we start to close the above 10 issues, we can close some of the related issues as well.

[jerkerdelsing]

Since we agreed on how to handle all of these points I now close this issues.
#1 Per to introduce into GSoSD - issue #58 - DONE but not merged yet
#2 Pal to add to GSoSD- issue # 66 - DONE in GSoSD
#3 communication - not urgent - issues #69 - to v5.1
#4 Felix to introduce into GSoSD - issue #67 - waiting for Felix
#5 Jerker to introduce into GSoSD - issue #65 - DONE in GSoSD
#6 Per to introduce into the GSoSD - issue #64 - DONE but not merged yet
#7 Jerker to introduce into GSoSD- issue #70 - DONE in GSoSD
#8 communication - branding - issues #68 - DONE in GSoSD
#9 Technology - issue #62 - DONE in GSoSD
#10 Technology - issue #71 - DONE in GSoSD