Link to performance requirements

diff --git a/Contribution-guidelines.md b/Contribution-guidelines.md
index 72c103f..e316499 100644 (file)
--- a/Contribution-guidelines.md
+++ b/Contribution-guidelines.md
@@ -8,7 +8,7 @@ Because of this and the available bandwidth of our team we are going to have to
 What this means is that we are putting in place a lightweight process for handling incoming PRs and issues to make sure the right set of people are working on the right set of PRs.
 
 #Bug bar
-In order for a change to be accepted it needs to have a **demonstrably broad impact** of a **mainline scenario** and be **low risk**.
+In order for a change to be accepted it needs to have a **demonstrably broad impact** of a **mainline scenario** and be **low risk**.  The change must also meet these [performance requirements](https://github.com/dotnet/coreclr/wiki/Performance).
 
 While the definitions for mainline scenario and risk can be subjective, the area owner is the right person to ascertain them and provide a recommendation.
 

diff --git a/Performance.md b/Performance.md
index c997f44..bc1e42d 100644 (file)
--- a/Performance.md
+++ b/Performance.md
@@ -1,6 +1,8 @@
 # Introduction #
 The .NET runtime supports a wide variety of high performance applications.  As such, performance is a key design element for every change.  This guidance is designed to share how we collect data and analyze the performance of the runtime.
 
+CoreFX performance guidance is available [here](https://github.com/dotnet/corefx/wiki/Performance).
+
 # Design Phase #
 Make sure to address performance during the design phase of any change.  It is much easier to tweak a design to fit performance goals and requirements before implementation has started.