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.

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

Update text on SDK details screen for Onboarding feature #9172

Closed
4 tasks
Tracked by #8947
ladonnaq opened this issue Oct 15, 2024 · 2 comments
Closed
4 tasks
Tracked by #8947

Update text on SDK details screen for Onboarding feature #9172

ladonnaq opened this issue Oct 15, 2024 · 2 comments
Assignees
Labels
Central-EngSys This issue is owned by the Engineering System team. Engagement Experience

Comments

@ladonnaq
Copy link
Member

Issue: Feedback from service and business partners indicates that the question is confusing. When onboarding a new product, they are usually updating the new API version, and there isn't a new SDK version that enables the product yet. They interpret the statement to mean that there are already published SDKs enabling the product, so they are not selecting it. This misunderstanding is causing Brownfield Scenarios to be incorrectly identified as Greenfield Scenarios. We need to update the statement to clearly ask if there are existing Service SDKs that will include contributions from the product.

Current UI:
Image

Updated UI:
Image

TODOs:

  • Update statements in the UI
  • "Existing public management plane SDKs will incorporate contributions from the product."
  • "Existing public data plane SDKs will incorporate contributions from the product."
  • In the information icon include "Check the Azure SDK release page if you're unsure about existing SDKs for the Service - https://aka.ms/azsdk/releases"
@maririos
Copy link
Member

@ladonnaq

"Existing public management plane SDKs will incorporate contributions from the product."

Could be my English, but this statement still creates confusion. Other alternatives:

  1. "Will this product contribute to an existing public management plane SDKs?"
  2. "Does this product requires updates to existing public management plane SDKs?"

My vote is for 1.

@maririos maririos added the Central-EngSys This issue is owned by the Engineering System team. label Oct 15, 2024
@ladonnaq
Copy link
Member Author

@ladonnaq

"Existing public management plane SDKs will incorporate contributions from the product."

Could be my English, but this statement still creates confusion. Other alternatives:

  1. "Will this product contribute to an existing public management plane SDKs?"
  2. "Does this product requires updates to existing public management plane SDKs?"

My vote is for 1.

I originally wrote a question similar to #1 above but then changed it to a statement so it would work with the current UI. However, I think the question format will be easier for users to understand. I vote for #1.

@ckairen ckairen moved this from 🤔 Triage to 🐝 Dev in Azure SDK EngSys 🚢🎉 Oct 22, 2024
@ckairen ckairen moved this from Backlog to Done in Dev in Engagement Experience Oct 22, 2024
@ckairen ckairen moved this from Done in Dev to Deployed to PPE in Engagement Experience Oct 22, 2024
@ckairen ckairen moved this from 🐝 Dev to 🔬 Dev in PR in Azure SDK EngSys 🚢🎉 Oct 25, 2024
@github-project-automation github-project-automation bot moved this from Deployed to PPE to Done in Engagement Experience Oct 29, 2024
@github-project-automation github-project-automation bot moved this from 🔬 Dev in PR to 🎊 Closed in Azure SDK EngSys 🚢🎉 Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team. Engagement Experience
Projects
Archived in project
Status: Done
Development

No branches or pull requests

3 participants