README for extensions libraries

[maryamariyan]

Adds README for extensions libraries

[ghost]

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	maryamariyan
Assignees:	maryamariyan
Labels:	area-Meta
Milestone:	-

[ghost]

Tagging subscribers to this area: @dotnet/area-extensions-logging
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	maryamariyan
Assignees:	maryamariyan
Labels:	area-Meta, area-Extensions-Logging
Milestone:	-

[tarekgh]

I added a couple of asks if you can consider it. LGTM otherwise. Thanks for getting this done!

[ericstj]

We might want to mention that these packages are part of the ASP.NET core shared framework in the deployment section.

What's your thinking on readme's in all the related folders for these? Maybe those can link to the main readme for the area and also call out any interesting differences that might exist for those libraries (eg: if they are platform specific like SystemD or WindowsServices, etc)

[tarekgh]

We might want to mention that these packages are part of the ASP.NET core shared framework in the deployment section.

This is a good point and worth mentioning.

What's your thinking on readme's in all the related folders for these? Maybe those can link to the main readme for the area and also call out any interesting differences that might exist for those libraries (eg: if they are platform specific like SystemD or WindowsServices, etc)

We are still adding more readme files to the extension libraries so we should cover all of them. I am hoping the readme be simple enough and not have many links for the user to jump around. kind of simple and inclusive as much as we can.

[MSDN-WhiteKnight]

What are the intended relationships between package readme and library readme discussed there? I'm asking because i were submitting readmes for Nuget packages before this initiative with library readmes (#59630), and they had different format with no "contribution bar" section. As a result, some libraries now have two different readmes, like for System.Text.Json: https://github.com/dotnet/runtime/tree/main/src/libraries/System.Text.Json and https://github.com/dotnet/runtime/tree/main/src/libraries/System.Text.Json/src. Is it planned to consolidate that somehow?

If the library readme is reused for Nuget package, there's one possible issue, relative links to documents within repository will not work when readme is rendered on Nuget gallery. So the link to contribution bar description must be absolute.

[tarekgh]

I prefer consolidating the library and the package readmes if possible.

relative links to documents within repository will not work when readme is rendered on Nuget gallery.

Can we make those absolute links instead?