-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add package readmes #91210
Add package readmes #91210
Conversation
Tagging subscribers to this area: @dotnet/area-meta Issue DetailsContributes to #59630 One of the top customer problems that package customers are facing is lack of documentation. As such, we are driving an effort to increase the adoption and quality of NuGet package READMEs. AskTo lead by example and ensure that your packages have the maximum impact, we would greatly appreciate your support in increasing the adoption and quality of NuGet package READMEs. WhyThe README file is an essential part of your package as it provides important information to users and helps them understand what the package is and what it does quickly. Also, README is the first things for users when they view your package on NuGet.org and soon Visual Studio/Visual Studio Code, it is crucial for package authors to write and include high-quality READMEs for their packages. HowThis PR initializes READMEs for all the below listed packages. Please directly push to this branch and also use this PR by your POD area team to review changes. For a great example, please see I will then backport these changes into the release/8.0 branch. The more package READMEs we add, the higher the customer impact. Priority 1 (.NET 8 RC 2)Our goal is to have the below list of .NET 8 packages publish with a README by September 11th in time for the .NET 8 RC2.
Prio 2 (.NET 8 / .NET 9)
cc @lyndaidaii @ericstj @danmoseley @jeffhandley
|
e126656
to
5098dde
Compare
Is markdown going to support adding API xrefs like in dotnet-api-docs? For example, when we write markdown remarks, you can add something like:
Which gets converted to a hyperlink that takes you to the FileStream.Seek method page. |
There is a gap between GitHub flavor markdowns and NuGet.org. Currently we don't support it. We would like to reduce the gap. Happy to create task to take a look at this see if we could support it. Maybe use link label as workaround. |
…time into InSourcePackageReadme
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like some issues with the packages that previously had templates. Probably the best thing to do right now is to revert the sections that aren't filled out - but save that point in a branch so that folks can resume the work after this merges.
Contributes to #59630
One of the top customer problems that package consumers are facing is lack of documentation. As such, we are driving an effort to increase the adoption and quality of NuGet package READMEs.
Ask
To lead by example and ensure that our packages have the maximum impact, we would greatly appreciate your support in increasing the adoption and quality of NuGet package READMEs.
Why
The README file is an essential part of your package as it provides important information to users and helps them understand what the package is and what it does quickly. Also, README is the first things for users when they view your package on NuGet.org and soon other tooling, it is crucial for package authors to write and include high-quality READMEs for their packages.
How
This PR initializes READMEs for all the below listed packages. Please directly push to this branch and also use this PR by your POD area team to review changes. For a great example, please see
System.Text.Json
's package README. Expect to spend ~30min of your time per README. Please try to keep documentation as minimal as possible to avoid duplicating information that is already available on docs.microsoft.com.I will then backport these changes into the release/8.0 branch. The more package READMEs we add, the higher the customer impact.
Priority 1 (.NET 8 RC 2)
Our goal is to have the below list of .NET 8 packages publish with a README by September 18th in time for the .NET 8 RC2.
The below list is sorted by download count.
Priority 2 (.NET 8 / .NET 9)
This list is sorted alphabetically.
✅ (
:white_check_mark:
) -> reviewed & approved🕜 (
:clock130:
) -> under reviewcc @lyndaidaii @ericstj @danmoseley @jeffhandley @MSDN-WhiteKnight