[Repository Transition]: Join DedicatedNetworks into Quality On Demand Sub Project

[hdamker]

Request: Join DedicatedNetworks into Quality On Demand Sub Project

We'd like to bring the independent Sandbox API Repository DedicatedNetworks into the existing Quality On Demand Sub Project.

This makes sense as both teams are already working closely together, and the APIs have natural synergies that would benefit from being in the same Sub Project.

Note: We're also planning to rename the Sub Project to something more inclusive like "Connectivity Quality Management" (see issue #498) to better reflect what we're doing and avoid the confusion of having a Sub Project and API Repository with the same name.

Why this makes sense

The APIs naturally fit together

DedicatedNetworks, QoSBooking, and QualityOnDemand APIs all deal with managing network connectivity quality. Having them in one Sub Project will help us:

• Keep the API designs consistent
• Share implementation patterns and avoid duplication
• Make it easier for developers who often need to use these APIs together
• Coordinate our roadmaps and releases better

The teams already work together

We've been discussing this transition in both teams' meetings and everyone supports it:

• The DedicatedNetworks team discussed it on August 25th with no objections
• The Quality On Demand Sub Project discussed it on August 22nd and September 5th with full support
• We're already having joint meetings and some people contribute to both

You can see in addition the discussions in these issues:

• Decision to incorporate DedicatedNetworks into the Sub Project of QualityOnDemand and QoSBooking QualityOnDemand#497
• Scope conflict: qos-booking-and-assignment duplicates functionality of existing dedicated-networks API QoSBooking#37
• Heads-up: New qos-booking-and-assignment API overlaps with dedicated-networks scope DedicatedNetworks#62

Maintainer situation

The combined Sub Project will have a healthy maintainer team:

DedicatedNetworks brings:

• Thorsten Lohmar (Ericsson)
• Peter Kovacs (Nokia)
• Carlos Romero (Telefonica)
• Steve Vickers (Vodafone)

Quality On Demand Sub Project currently has:

• From QualityOnDemand API Repository: 12 maintainers from Deutsche Telekom, Ericsson, Orange, Spry Fox Networks, Telefonica, Vodafone, Verizon/5GFF, KDDI, and CableLabs
• From QoSBooking API Repository: 2 maintainers from KDDI and Telefonica

Together we'll have 18 maintainers from 11 different companies (Deutsche Telekom, Ericsson, Nokia, Orange, Spry Fox Networks, Telefonica, Vodafone, Verizon/5GFF, KDDI, CableLabs), which gives us excellent diversity and far exceeds the requirements for a healthy Sub Project.

What we're asking for

From the API Backlog Working Group

Please review this request and if it looks good, recommend it to the TSC for approval.

From the TSC

Please approve bringing DedicatedNetworks into the Quality On Demand Sub Project.

What happens after approval

Once approved, here's what we'll do:

• DedicatedNetworks stays as a Sandbox API Repository, just now part of the Sub Project
• All the maintainers from the three API repositories become the Sub Project maintainer team
• Move the DedicatedNetworks wiki page under the Quality On Demand section
• Use one mailing list and have regular joint meetings (with breakouts for specific APIs when needed)

The Sub Project will then have:

• 1 Incubating API Repository (QualityOnDemand)
• 2 Sandbox API Repositories (QoSBooking and DedicatedNetworks)

Links and references

Meeting minutes where this was discussed

• DedicatedNetworks meeting:
  • https://lf-camaraproject.atlassian.net/wiki/x/pQDCD
• Quality On Demand meetings:
  • https://lf-camaraproject.atlassian.net/wiki/x/AYDFD
  • https://lf-camaraproject.atlassian.net/wiki/x/JACADQ

Related discussions

• Sub Project renaming: Find a better name for the Sub Project Quality On Demand (not the API) QualityOnDemand#498
• API alignment: Decision to incorporate DedicatedNetworks into the Sub Project of QualityOnDemand and QoSBooking QualityOnDemand#497
• QoSBooking integration: Scope conflict: qos-booking-and-assignment duplicates functionality of existing dedicated-networks API QoSBooking#37
• DedicatedNetworks transition: Heads-up: New qos-booking-and-assignment API overlaps with dedicated-networks scope DedicatedNetworks#62

[albertoramosmonagas]

Hi @hdamker,

Following the TSC approval of this issue, I wanted to check your preference. Should we:

1. Open a dedicated tracker (e.g., “DN → QoD Sub Project – Execution Tracker”) with a full checklist of tasks and owners, or

2. Reuse the existing issue as the tracker, expanding it with a checklist and milestones?

What’s your preferred approach?

[hdamker]

@albertoramosmonagas I guess option 2 is easier. Wiki page is already moved, changes within repository are on the way (camaraproject/DedicatedNetworks#77), only point might be to clarify the mailing lists and meetings.

[albertoramosmonagas]

Hi @hdamker,

One question: considering that #258 has been created, can we close this issue because the rest of the pending tasks are being moved to the other one?

[jgarciahospital]

Closing as repository changes are already ongoing in #258