-
Notifications
You must be signed in to change notification settings - Fork 763
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
Make it easier for the community to find packages after the move #3084
Comments
@bradygaster you were going to write up a README change right? |
@anurse - yes the readme you authored in the announcements page was great IMO - anyone have any objection to us linking to that, or do folks think we need to essentially copy that content here? |
Let’s do both. I think a link is easy for people to miss and if it’s copy-pasted it is Ctrl-F friendly. Maybe a copy-paste of the list and a link “for the complete announcement, see aspnet/Announcements#NNNN” |
A few suggestions that came up from the discussion thread on the package move for ensuring people can find which packages live where more quickly. This issue is tracking doing that work. Some of it should be automatic, but we should validate it:
Ensure the Source Repository metadata in the packages is correct so that NuGet.org links will work
Add a list of all
Microsoft.Extensions.*
packages that used to exist in this repo linking to where they now live. This isn't necessarily designed to be a constantly-updated list as new packages are added, but should try to cover the ones that used to be maintained in this repo.The text was updated successfully, but these errors were encountered: