Skip to content

Conversation

@BillWagner
Copy link
Member

Fixes #32861

The dotnet content team has applied a consistent set of rules regarding recommendations and dependencies in our content. What we haven’t done is state those rules publicly. That resulted in misunderstandings after we removed a previous recommendation. This PR publishes the rules we use.

Fixes dotnet#32861

The dotnet content team has applied a consistent set of rules regarding recommendations and dependencies in our content. What we haven’t done is state those rules publicly. That resulted in misunderstandings after we removed a previous recommendation. We want to resolve that by publishing the rules we use.
Copy link
Contributor

@terrajobst terrajobst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, thanks for putting this together!

Copy link
Member

@IEvangelist IEvangelist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with @gewarren's feedback and suggestions. Let's :shipit:.

Co-authored-by: Genevieve Warren <[email protected]>
@BillWagner BillWagner merged commit 8d9c5d2 into dotnet:main Jan 13, 2023
@BillWagner BillWagner deleted the 3rd-party-dependencies branch January 13, 2023 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Please document a policy for third party libraries in .NET Microsoft Docs

5 participants