There are ~62 .md articles whwere the ms.author metadata value was not set to a doc team member so doc team members will receive notifications. These seem to be related to articles where the original doc team owner wanted to ensure the original author on the development team was still getting notified. Also many of these are missing an original author value in the metadata. It could be when these were scanned before that it was assume an author value existed and so they were accidently overlooked in the last sweep.
There are cases where we want to ensure the ms.author value, which is still recently active and on the development team is moved to ms.reviewer where the intention was to keep an active member on the notificaiton loop. Those will be manually looked for in the resulting issue PR review.
For all .md files in this repo with ms.author NOT set to one of the following values:
wpickett
tdykstra
guardrex
Set the ms.author value to wpickett as a default.
Then during the PR review, tdykstra will review to see what of those articles may be moved to his name per area.
This is the GitHub search Query to find those articles that need an ms.author update:
Search for non-standard ms.author values in dotnet/AspNetCore.Docs
In additon:
The following original ms.author values are for active development team members who were originally listed as ms.author who should be retained on the review loops by moving those values to a new ms.reviewer entry in alpha order in the metadata if an ms.reviewer does not already exist.
wigodbe → 1 file (w3c-logger/index.md)
midenn → 1 file (native-aot-tutorial.md)
dmkorolev → 1 file (asp0028.md)
stevesa → 1 file (angular.md)
brolivei → 1 file (responses.md)
jeliknes → 2 files (apis.md, how-to-choose-identity-solution.md)
chrross → 1 file (http3.md)
tasou → 11 files (all migration/fx-to-core/ articles)
Associated WorkItem - 573786
There are ~62 .md articles whwere the ms.author metadata value was not set to a doc team member so doc team members will receive notifications. These seem to be related to articles where the original doc team owner wanted to ensure the original author on the development team was still getting notified. Also many of these are missing an original
authorvalue in the metadata. It could be when these were scanned before that it was assume anauthorvalue existed and so they were accidently overlooked in the last sweep.There are cases where we want to ensure the ms.author value, which is still recently active and on the development team is moved to ms.reviewer where the intention was to keep an active member on the notificaiton loop. Those will be manually looked for in the resulting issue PR review.
For all .md files in this repo with ms.author NOT set to one of the following values:
wpickett
tdykstra
guardrex
Set the ms.author value to
wpickettas a default.Then during the PR review, tdykstra will review to see what of those articles may be moved to his name per area.
This is the GitHub search Query to find those articles that need an ms.author update:
Search for non-standard ms.author values in dotnet/AspNetCore.Docs
In additon:
The following original ms.author values are for active development team members who were originally listed as ms.author who should be retained on the review loops by moving those values to a new ms.reviewer entry in alpha order in the metadata if an ms.reviewer does not already exist.
wigodbe → 1 file (w3c-logger/index.md)
midenn → 1 file (native-aot-tutorial.md)
dmkorolev → 1 file (asp0028.md)
stevesa → 1 file (angular.md)
brolivei → 1 file (responses.md)
jeliknes → 2 files (apis.md, how-to-choose-identity-solution.md)
chrross → 1 file (http3.md)
tasou → 11 files (all migration/fx-to-core/ articles)
Associated WorkItem - 573786