FOCUS #404: Service Subcategory

[shawnalpay]

Introduction of column ServiceSubcategory underneath the existing column ServiceCategory to capture finer grouping detail for Services.

Lead Maintainer: Shawn Alpay, @salpaysenturus

Documents:

• Categorization principles
• Slack channel: “# tf-service-categorization”
• Folder: #404-subcategories
• Presentation: Service Subcategories
• Spreadsheet: 24.06.27 Service Subcategories
• PR: #519 Add support for sub categorizations of ServiceCategory #404: Service Subcategory
• Approval deadline: Aug 29, Sep 5,

[jpradocueva]

I am volunteer to convert long markdown tables into HTML.

[jpradocueva]

Action Items, Maintainers meeting, Aug 19:

• [Maintainer-##519] Shawn will assign specific reviewers for the PR and gather feedback through a controlled document.

[udam-f2]

General comments around descriptions for categories is to keep them short, concise and not go into the uses / purpose - which starts to become marketing-ish

[shawnalpay]

General comments around descriptions for categories is to keep them short, concise and not go into the uses / purpose - which starts to become marketing-ish

@udam-f2 Fair enough. Could you possibly make a suggestion on a specific description as an example, and I can extrapolate from there?

[udam-f2]

General comments around descriptions for categories is to keep them short, concise and not go into the uses / purpose - which starts to become marketing-ish

@udam-f2 Fair enough. Could you possibly make a suggestion on a specific description as an example, and I can extrapolate from there?

I thought I provided my opinion on several of these. I think the consistent way might be to check ServiceCategory descriptions and try to keep it at that level. If we don't believe that serves the purpose, we should look to change the way descriptions are written in both.

[jpradocueva]

Action Items from TF-1 call on Sep 10:

• [TF1-#519] Michael: Update the subcategory proposal for serverless compute to include "Managed Compute" as an alternative.
• [TF1-#519] Shawn: Continue exploring best categorization practices for search across cloud providers.
• [TF1-#519] Michael: To update the PR, reflecting the new categories for development, deployment, and QA.
• [TF1-#519] Alex: To review the categorization of multi-cloud vs. hybrid cloud for future discussion.
• [TF1-#519] Shawn: To propose combining directory services with identity management and ensure alignment with security services.
• [TF1-#519] All Members: To review existing service classifications and ensure they align with the new taxonomy in preparation for the next meeting.

[shawnalpay]

Action Items from TF-1 call on Sep 10:

• [TF1-#519] Michael: Update the subcategory proposal for serverless compute to include "Managed Compute" as an alternative.
• [TF1-#519] Shawn: Continue exploring best categorization practices for search across cloud providers.
• [TF1-#519] Michael: To update the PR, reflecting the new categories for development, deployment, and QA.
• [TF1-#519] Alex: To review the categorization of multi-cloud vs. hybrid cloud for future discussion.
• [TF1-#519] Shawn: To propose combining directory services with identity management and ensure alignment with security services.
• [TF1-#519] All Members: To review existing service classifications and ensure they align with the new taxonomy in preparation for the next meeting.

@jpradocueva: I assume you sourced these action items from the recording, but we closed on most of these when we reopened the call after it was accidentally closed. The PR reflects those discussions, and as of the time of this writing, all comments have been resolved. The only applicable action item is the last one: for all members to review and comment/approve ahead of approval at this coming Thursday's Member meeting.

[thecloudman]

I think this has come a long way and is looking good. I'm supportive of the current format and categorization.

[udam-f2]

Needs more work to flush out ambiguities and inconsistencies and drive consensus across a broad group.

[jpradocueva]

Action Items from Task Force 1 call on Sep 17:

• [TF1-#519] Sean, @salpaysenturus : Update PR FOCUS #404: Service Subcategory #519 to reflect the final subcategory names and descriptions, particularly focusing on "development environments."
• [TF1-#519] Michael, @flanakin : Review and confirm is ok with the final changes in the Slack channel before Thursday's meeting.

[jpradocueva]

Action Items from TF-2 call on Sep 18:

• [TF2-#519 ] Sean, @salpaysenturus : Make final changes to the PR descriptions as discussed and prepare for approval in tomorrow’s meeting.
• [TF2-#519 ] All members: Review the finalized sub-categories in preparation for tomorrow's approval.

[jpradocueva]

Approved by the group during the Member' call on Sep 19.