[MQ] Revisit namespace name AzureAIBestPractices & AzureBestPractices

[xiangyan99]

Describe the bug

These names are too close which may cause confusion for devs and coding agent.

Also AzureAIBestPractices might imply that AzureBestPractices are non-AI.

Expected behavior

N/A

Actual behavior

N/A

Reproduction Steps

N/A

Environment

No response

[fanyang-mono]

@XiaofuHuang mentioned that she will work on moving the tool to AzureBestPractices.

[xiangyan99]

Yes. Just open the issue to track the work.

[XiaofuHuang]

@xiangyan99 Thank you for raising this issue and for the thoughtful feedback regarding the potential confusion between the AzureAIBestPractices and AzureBestPractices namespaces.

We've received several suggestions, including broadening the scope of the current best practices (@fanyang-mono, @JasonYeMSFT ), or alternatively, renaming and clearly distinguishing the two namespaces(@xiangyan99).

We should also consider our future plans (such as evaluation, tracing, etc.) and the overall developer experience. There are several important questions we need to discuss:

• If we use a single namespace:
  • How much flexibility do we have in updating the namespace description as new features are added? Can we fully revise it to accommodate future changes?
  • If both teams contribute new features within the same namespace, what processes should we establish for re-testing to ensure that updates do not unintentionally impact each other's best practices?
• If we use two separate namespaces:
  • How should we define and split the scopes of each namespace?
  • Which name can ensure the namespaces remain inclusive of our future plans?

To ensure we make the best decision for both current and future use cases, I suggest that the PMs and developers from both groups meet to discuss the long-term strategy—whether to maintain a single unified namespace or to separate them more distinctly.

Let’s coordinate a meeting to review the options and align on a path forward after Ignite.