Remove all the use-write-core configure

[pshao25]

Steps: In all the autorest.md file, remove use-write-core config.

[jsquire]

@pshao25: Please don't file issues like this. This is not actionable and needs more context. Why are we looking to make this change? Who are we asking to take ownership of this? As triage, there is not enough information for me to understand if this is a self/team work item, an ask for something, or a problem.

I'm going to close this out. If this is something we need, please add some detail, labels, and if appropriate to assign directly, do so.

[jsquire]

//cc: @ArthurMa1978

[pshao25]

@pshao25: Please don't file issues like this. This is not actionable and needs more context. Why are we looking to make this change? Who are we asking to take ownership of this? As triage, there is not enough information for me to understand if this is a self/team work item, an ask for something, or a problem.

I'm going to close this out. If this is something we need, please add some detail, labels, and if appropriate to assign directly, do so.

To give you more background, this is exactly what Arthur wants to do. To some reason, there is still some use-write-core config in our repro, which is already deprecated and useless. He asked me to create this issue in our sync meeting with vendors and asked the vendor lead @HarveyLink to assign someone to do this. Seems he haven't got the chance to assign someone, so it is unassigned. In that meeting we were fully discussed of this issue and all the people are on the same page. @HarveyLink Please assign some one.

[jsquire]

@pshao25 : That's fine. Please tag it appropriately rather than leaving it as needs-triage with no context.

[pshao25]

@pshao25 : That's fine. Please tag it appropriately rather than leaving it as needs-triage with no context.

I see. I didn't realize that tag would confuse you. Sorry.

[jsquire]

@pshao25: All issues in the repository require a service area (pink) and category (yellow) label or they get flagged for data quality. Anything tagged needs-triage, needs-team-triage, or needs-team-attention have an impact on our SLA reporting metrics. This has been true of all Azure SDK repositories since the formation of our team.

Can you help me understand why we're struggling to create issues that conform to standards all of a sudden?

[pshao25]

@pshao25: All issues in the repository require a service area (pink) and category (yellow) label or they get flagged for data quality. Anything tagged needs-triage, needs-team-triage, or needs-team-attention have an impact on our SLA reporting metrics. This has been true of all Azure SDK repositories since the formation of our team.

Can you help me understand why we're struggling to create issues that conform to standards all of a sudden?

No special reason. It's just because I don't know any of these things. Sorry for the trouble. I'll follow next time.