From 2a2c2f3f83615ce4c01ed76d90118c18a222c155 Mon Sep 17 00:00:00 2001 From: Lee Dohm Date: Sun, 26 Feb 2017 20:37:54 -0800 Subject: [PATCH] Fix broken links --- _articles/legal.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_articles/legal.md b/_articles/legal.md index c0c761b6149..e9969bd55ce 100644 --- a/_articles/legal.md +++ b/_articles/legal.md @@ -137,13 +137,13 @@ If you're releasing your company's first open source project, the above is more Longer term, your legal team can do more to help the company get more from its involvement in open source, and stay safe: -* **Employee contribution policies:** Consider developing a corporate policy that specifies how your employees contribute to open source projects. A clear policy will reduce confusion among your employees and help them contribute to open source projects in the company's best interest, whether as part of their jobs or in their free time. A good example is Rackspace's [Model IP and Open Source Contribution Policy](https://processmechanics.com/2015/07/23/a-model-ip-and-open-source-contribution-policy/). +* **Employee contribution policies:** Consider developing a corporate policy that specifies how your employees contribute to open source projects. A clear policy will reduce confusion among your employees and help them contribute to open source projects in the company's best interest, whether as part of their jobs or in their free time. A good example is Rackspace's [Model IP and Open Source Contribution Policy](https://processmechanics.com/a-model-ip-and-open-source-contribution-policy/).