Notes on 3rd party dependencies #1272
Conversation
ghost
assigned 
|
@anhowe @seanknox @jchauncey FYI, a 1st draft on the language that describes how we intend to express a structured dependency management strategy |
|
This is great. Worth mentioning that all dependencies need to be registered with Microsoft OSS to be cleared for use? |
| @@ -54,6 +54,14 @@ workflow for doing this is as follows: | |||
| 5. When you are ready for us to review, push your branch to GitHub, and | |||
| then open a new pull request with us. | |||
|
|
|||
| ### Third Party Dependencies | |||
There was a problem hiding this comment.
Ive added an issue about updating labels (#1277) so when people submit prs/issues that need dependency updates/additions we can track them.
|
My only comment to this is I wonder if this should be some where more visible? |
|
@seanknox I'm inclined to defer on how much info we publish about that. Who would be the best resource to determine how we want to say that? |
Fair enough. As long as there's a process we (ACS) follow to ensure dependencies are registered, that's what matters. |
What this PR does / why we need it: add docs on how we manage 3rd party dependencies in the project
Release note:
This change is